Bugzilla – Bug 48
FFmpeg: Poor reporting of 'Library not found'.
Last modified: 2019-05-13 07:00:52 UTC
* Importing FFmpeg formats when FFmpeg library missing should raise the "FFmpeg not found" error, not the generic "not supported" error. Provisional fix in place, but throws multiple FFmpeg errors per file, then the relevant error for the particular format * In non-FFmpeg builds, attempting to import FFmpeg-supported formats should give an error that suggests downloading FFmpeg. Impossible to fix completely without breaking Importer abstraction: in non-FFmpeg builds ImportFFmpeg plugin does not exists and cannot suggest anything to user, while Importer should not know which formats are supported by ImportFFmpeg, thus being unable to suggest anything either.
It would apper to me that P1 Bug #1693 is a modern incarnation of this long-standing unfixed P4 bug
(In reply to Peter Sampson from comment #1) OOPS sorry that should be Bug #1692
No longer a summary bug.
Testing on W10 with 2.3.2 RC001 The message in Libraries prefs is now (and has been for a long time) >FFmpeg library not found with an invitation to search for it or download it That to me (and my "mystery shopper") perfectly clear. The Steps to reproduce quote >Observe: >A: The error reported is 'not supported' rather than 'FFmpeg missing'. Also if you already had FFmpeg installed and then the library of folder containing it gets moved or renamed when you next launch Audacity you get a fulsome warning message telling you what's up. And I can recall no users complaining about this being unclear Accordingly I shall close this long-standing bug
