That patch should essentially be the patch from bug 176 (which "theoretically" works with SVN FFmpeg) with the addition of allowing automatic linking against system FFmpeg without using Preferences (if USE_SYSTEM_FFMPEG is set).īut it's untested what happens with that patch if user self-compiles SVN FFmpeg then sets USE_SYSTEM_FFMPEG to try and use that SVN FFmpeg (or doesn't, trying to load it through Preferences). Gale Andrews wrote:So next up, we have the patch which Benjamin did for Bug 233 which runtime-detects the version of FFmpeg, and (if USE_SYSTEM_FFMPEG is set) allows automatic linking against system FFmpeg then greys out the "Locate" and "Download" buttons in the FFmpeg section of the "Libraries" Preferences.Īnd that patch supersedes the other patches and code changes? That is, it should be applies to a "clean" svn source? There were also problems with AAC export (which files then crash on import) but I understand these issues only occur with the native FFmpeg AAC encoder. We both got the Bug 274 WMA export crashes. which picks up the Ubuntu-distributed FFmpeg. That Bug 233 patch was tested by you (Steve) and me with default Audacity. So next up, we have the patch which Benjamin did for Bug 233 which runtime-detects the version of FFmpeg, and (if USE_SYSTEM_FFMPEG is set) allows automatic linking against system FFmpeg then greys out the "Locate" and "Download" buttons in the FFmpeg section of the "Libraries" Preferences. You get the "undefined symbol:match_ext" error when loading FFmpeg from Preferences, the fix for which is actually included in that patch. configure against the "runtime detect" patch from bug 176, Audacity does not recognise FFmpeg. 18&t=39251.įor (a few) others, the files *are* recognised but Audacity usually segfaults on just about any FFmpeg task.įor others including myself who tried self-compiling latest FFmpeg, then compiling Audacity with default. Code: Select all static int ufile_write(URLContext *h, const unsigned char *buf, int size)īut then latest FFmpeg as used in Audacity does not (for some people ) recognise legitimate FFmpeg-supported files on import, showing "av_open_input_file() failed" in Help > Show Log.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |