-
-
Notifications
You must be signed in to change notification settings - Fork 265
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
Disabled check for ffmpeg. #122
Conversation
Should we check either |
It is definitely an option, however I went for the easiest fix for a blocker. Besides, youtube-dl is not bundled or vendor-locked. Their requirements may change in a future version (for instance, they may decide to drop support for avconv or they may introduce another option). There is no simple and reliable way for podsync to determine whether the environment is sane unless you do version checking... I just don't think it's worth the effort tbh. |
youtube-dl can work independently from ffprobe/avprobe, however podsync can't. So if there is no ffprobe or avprobe, it'll fail. And it'll be frustrating if your feed does checks once a week and it turns out it doesn't work a week later, so it's important to check that the env is sufficient and fail early. |
It may fail to work for many other reasons (like the 429 error I mentioned). You should always check the logs and if it's really important set up some kind of alerting mechanism. But that's another story. podsync never uses ffmpeg directly, so making some checks on behalf of youtube-dl just doesn't feel right to me. Especially considering possible introduction of new Downloaders in the future which may not require youtube-dl at alll. |
Can you please check 4afc477 |
It will fix the blocker for now, yes. |
Thanks. I'm going to close this one then |
Some Linux distributions (e.g. Debian) have
avconv
instead of ffmpeg.youtube-dl
can work with either, but podsync insists on havingffmpeg
in the $PATH. This PR removes the check which allows it to work in Debian. Also, after applying #121 the lack of ffmpeg becomes immediately obvious in the logs: