Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide direct link to FFmpeg download for Windows #1459

Open
myfirstnameispaul opened this issue Sep 16, 2021 · 0 comments
Open

Provide direct link to FFmpeg download for Windows #1459

myfirstnameispaul opened this issue Sep 16, 2021 · 0 comments

Comments

@myfirstnameispaul
Copy link

myfirstnameispaul commented Sep 16, 2021

Issue Summary

For most users who don't know what FFmpeg is or what it does or why they are being told to download it, the page currently linked does little to clear things up for them, because the page directly linked is a page loaded with links, assuming the user understands to click the Windows icon and not download the source code, there are two links that display in a box. It isn't clear which link to click. Clicking either takes the user to a page that is likely confusing and difficult to discover what they are supposed to download.

Steps to Reproduce

  1. Visit What are the recommended video settings for publishing? page and click download the executables link in the Install and configure section.
  2. Visit both links in the Windows EXE Files section on the FFmpeg website download page.
  3. Note that neither of these links provides a clear path of instruction for what needs to be downloaded to get the necessary FFmpeg files.

Since I use Linux and just install from repos, I don't have a way to figure out a solution to this problem, but this problem really should be resolved so that average users can at least figure out how to use the site. A user with a 30 minute 25mbps video can't upload through Odysee; users with 40 minute 10mbps videos get complaints about videos constantly pausing and being unwatchable, and they are all likely very frustrated, and assuming they can even discover the lbry.com page, will have to be very dedicated to figure out how to implement the recommended solution, which means very few less experienced users ever reach this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant