Comment 1 for bug 1058380

Hi,

Thanks for taking the time to report this issue. As I now find out, the way I handled the migration from ffmpeg to libav in Ubuntu was incomplete.

Winff depends on libav-tools or ffmpeg. Apparently, as can be expected in Ubuntu 12.10, you have libav-tools installed. The problem is the detection of avconv/ffmpeg executable. I could fix that easily for new installs (I was even convinced that I had done that), but it is a lot more difficult to fix it correctly for people already having run Winff before, as the path to "ffmpeg" is stored in user settings.

As Ubuntu 12.10 is following the libav instead of the ffmpeg version of the library and tools, he proper way to fix this for people running into this bug is NOT by installing the ffmpeg package but by changing the path in the Edit -> Preferences -> Linux -> "Path to FFmpeg Executable" to /usr/bin/avconv

I now notice that the warning that you get when the wrong path is configured is wrong: "Could not find FFPlay" instead of "Could not find FFMpeg."

I now notice that I forgot to update the description of the winff package as it should mention libav too.

So summarizing:
- description of the package should change (either not mention ffmpeg or ALSO mention avconv
- detection upon first run of winff should find avconv if installed
- error message upon conversion when converter can not be found is mentioning the player instead of the converter
- error messages should be updated to not only mention ffmpeg
- preferences window should not mention only ffmpeg
* I don't consider really depending on ffmpeg the solution for this bug

Paul