Launchpad has imported 10 comments from the remote bug at http://bugzilla.audacityteam.org/show_bug.cgi?id=176.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2010-07-02T05:01:04+00:00 Gale wrote: FFmpeg libraries or packages built in 2010 will not be recognised by Audacity (Help > Show Log will show "undefined symbol: match_ext"). FFmpeg libraries built after June 1st 2010 will prevent Audacity compiling. See Release Notes for details. Simply fixing for 2010 builds of FFmpeg will break 2009 builds, yet we want some backwards compatibility. Can the code support 2009 and 2010 with some kind of runtime detection of the FFmpeg version in use? Reply at: https://bugs.launchpad.net/audacity/+bug/602934/comments/0 ------------------------------------------------------------------------ On 2010-10-28T04:01:07+00:00 Gale wrote: Created an attachment (id=54) Patch by Tim Harder to detect FFmpeg versions from 2010 Reply at: https://bugs.launchpad.net/audacity/+bug/602934/comments/13 ------------------------------------------------------------------------ On 2010-10-28T04:26:03+00:00 Gale wrote: Tested attached patch from Tim Harder. Success on Windows 7. Audacity recognises FFmpeg 20 July 2009 from the FFmpeg-for-Audacity installer. On Ubuntu 10.10, Audacity cannot find the installed ffmpeg 4:0.6-2ubuntu6 library containing libavformat.so.52.64.2 (Unicode release, standard configure FFMPEG: using LOCAL libraries). Help > Show Log shows "undefined symbol:match_ext", so Audacity seems not to have picked up the FFmpeg version correctly. However hardcoding for "av_match_ext" as per Release Notes does allow Audacity to find FFmpeg. Reply at: https://bugs.launchpad.net/audacity/+bug/602934/comments/14 ------------------------------------------------------------------------ On 2010-12-28T23:07:03+00:00 Gale wrote: The current situation seems thus for most people. If you self-compile FFmpeg greater than 0.5 and point 1.3.13 to it, Audacity either: * does not recognise FFmpeg * recognises FFmpeg with errors which may lead to repeatable segfaults * appears to recognise FFmpeg but can't recognise valid files on import On Ubuntu 10.10 if I point 1.3.13 (compiled with default ./configure that produces "use ffmpeg=local") to the Synaptic-installed Ubuntu FFmpeg package, 1.3.13 seems to fully recognise FFmpeg and works properly without crashes. (Steve does get intermittent crashes in that scenario importing WMA or AC3 files which had been exported by 1.3.12). I just confirmed my results by reinstalling Ubuntu 10.10, and rebuilding Audacity with default ./configure against Nikola's av-match-ext patch (http://forum.audacityteam.org/download/file.php?id=2253). If I then recompile Audacity with default ./configure against the attached bug 176 patch, I'm back to Audacity not recognising FFmpeg with the "undefined symbol:match_ext" error. Discussion at http://forum.audacityteam.org/viewtopic.php?f=18&t=39251 Reply at: https://bugs.launchpad.net/audacity/+bug/602934/comments/15 ------------------------------------------------------------------------ On 2011-01-28T15:49:53+00:00 Benjamin Drung wrote: The patch attached to bug #233 is a superset of (= contains) the patch from comment 1. Reply at: https://bugs.launchpad.net/audacity/+bug/602934/comments/16 ------------------------------------------------------------------------ On 2011-02-07T13:59:02+00:00 Gale wrote: Benjamin, So where are we now? We have your patch attached to bug 233 which appears to work on Ubuntu using the Ubuntu-distributed FFmpeg (leaving aside the WMA crashes in Bug 274 and possible licensing issues from build-time linkage). I and a couple of other people could never make the patch attached to this bug work on Ubuntu when self-compiling FFmpeg and building Audacity with default ./configure. There was always "undefined symbol:match_ext" error when loading FFmpeg from Preferences. The patch did not cause a problem on Windows - Audacity still recognised the libs from the FFmpeg installer we supply. However we still have the previous reports (http://forum.audacityteam.org/viewtopic.php?f=18&t=39251) where people loading latest FFmpeg from Audacity Preferences found Audacity does not recognise legitimate FFmpeg-supported files on import, showing "av_open_input_file() failed" in Help > Show Log. I assume your patch attached to bug 233 will not address that if you do not set USE_SYSTEM_FFMPEG. What happens in your bug 233 patch if user uninstalls Ubuntu's FFmpeg or otherwise sets SVN FFmpeg as the system FFmpeg, then sets USE_SYSTEM_FFMPEG? Is there some way you can test such a scenario? If FFmpeg files are not recognised in that case then it seems we need a new bug for that. Fixing bug 176 but not bug 233 seems less controversial to me. If we are going to address 233 at all it would "seem" more convenient to address 176 by applying the bug 233 patch, but might it be safer to separate them anyway? I have more comments in bug233#c11 . Reply at: https://bugs.launchpad.net/audacity/+bug/602934/comments/17 ------------------------------------------------------------------------ On 2011-02-07T16:26:36+00:00 Benjamin Drung wrote: > I assume your patch attached to bug 233 will not > address that if you do not set USE_SYSTEM_FFMPEG. The patch should work with newer FFmpeg version regardless if USE_SYSTEM_FFMPEG is set or not. > What happens in your bug 233 patch if user uninstalls Ubuntu's FFmpeg Nothing if Audacity was compiled without setting USE_SYSTEM_FFMPEG. Audacity would crash on startup if the is no other FFmpeg version installed which is binary compatible if Audacity was compiled with USE_SYSTEM_FFMPEG. When the audacity Ubuntu package is compiled with USE_SYSTEM_FFMPEG, it will depend on the FFmpeg packages. If you uninstalls Ubuntu's FFmpeg, it will uninstall audacity too. > or otherwise sets SVN FFmpeg as the system FFmpeg, How do I do that? Compile with ./configure --prefix=/usr? > then sets USE_SYSTEM_FFMPEG? Is there some way you can test such > a scenario? If FFmpeg files are not recognised in that case then it seems we > need a new bug for that. Do you want me to install SVN FFmpeg and then compile Audacity with USE_SYSTEM_FFMPEG against it? Reply at: https://bugs.launchpad.net/audacity/+bug/602934/comments/18 ------------------------------------------------------------------------ On 2011-02-07T22:42:44+00:00 Gale wrote: (In reply to comment #6) > Do you want me to install SVN FFmpeg and then compile Audacity with > USE_SYSTEM_FFMPEG against it? Benjamin, I'm really just trying to find out if we need to start a new bug for a problem with Audacity apparently recognising SVN FFmpeg but then giving an error dialogue in the GUI when importing FFmpeg files. That is, is the problem specific to latest FFmpeg builds, but doesn't occur with a build from a bit earlier like the current Ubuntu FFmpeg? Or is it to do with how Audaoity has been configured? Three people on the Forum including me, and a couple of others I know of get "av_open_input_file()failed" in the log when the import failure happens with SVN FFmpeg. Steve gets "Failed to retrieve file times for '/nyquist worker/' (error 2: No such file or directory), Error: can't open file '/nyquist worker/'" when using SVN FFmpeg. Steve's issue could possibly be some conflict with Nyquist Workbench. Steve's and my problems go away when using the Ubuntu FFmpeg (except for the WMA and AAC export problem). So it would be great if you (who knows more what you are doing :=) could install SVN FFmpeg and compile Audacity with USE_SYSTEM_FFMPEG. Steve and I were compiling with default ./configure and the configure output was showing "using SYSTEM libraries" for FFmpeg. I can't find out what the other four people were doing exactly. If local libraries are used instead of system, is that for the case where you link to a library version you have not installed? If so, how do you configure Audacity to the correct path for the local library? Reply at: https://bugs.launchpad.net/audacity/+bug/602934/comments/19 ------------------------------------------------------------------------ On 2011-02-08T18:13:22+00:00 Benjamin Drung wrote: I have installed SVN FFmpeg and compiled Audacity with USE_SYSTEM_FFMPEG. It compiled (which means that all required functions are available) and Audacity gave me the options to use FFmpeg for exporting audio, but here's the sad part: Importing and exporting through FFmpeg failed. In the log I found this: Export ac3 file: Error: can't open file '/' (error 21: is a directory) Error: FFmpeg: ERROR - Can't open output file "/home/foo/bar/baz.ac3" to write. Error code is -2. Import mp4 file: Opening with libav Error: can't read from file descriptor 20 (error 21: is a directory) Error: av_open_input_file() failed for file /home/foo/bar/baz.mp4 Error: Importer::Import: Opening failed. I will give a full explanation how I compiled everything in the forum: http://forum.audacityteam.org/viewtopic.php?f=18&t=53227 Reply at: https://bugs.launchpad.net/audacity/+bug/602934/comments/20 ------------------------------------------------------------------------ On 2011-02-09T11:43:49+00:00 Gale wrote: Moved "importance" to "repeatable". Reply at: https://bugs.launchpad.net/audacity/+bug/602934/comments/21 ** Changed in: audacity Status: Unknown => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/602934 Title: ffmpeg import/export not working with ffmpeg version in maverick -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
