** Changed in: audacity
Status: Unknown => Fix Released
--
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
--
ubunt
(In reply to comment #102)
> This might be something that the devel subscribers would like to discuss.
> Personally, I say go for it...
It's expected FFmpeg 0.6.2 will be released for Win/Mac users when 1.3.13 is
released. A cursory test of 0.6.2 on Win XP suggests 0.6.2 is OK.
This is RESOLV
** Changed in: audacity
Status: Confirmed => Unknown
** Bug watch added: Audacity Bugzilla #134
http://bugzilla.audacityteam.org/show_bug.cgi?id=134
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
(From update of attachment 147)
this version was committed.
--
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-b
Are we providing FFmpeg 0.6 binaries for Win/Mac for 1.3.13 Beta?
--
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
--
ub
(In reply to comment #101)
> Are we providing FFmpeg 0.6 binaries for Win/Mac for 1.3.13 Beta?
This might be something that the devel subscribers would like to discuss.
Personally, I say go for it...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
Leland committed as r11055 so Status changed to DEVEL - FIX MADE, though I have
tested as much as I can. Would Bill like to test this on Mac?
--
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
(In reply to comment #97)
> I'm going to go ahead and commit the version 11
Agreed. M4A quality slider issue is now at bug 344.
--
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 imp
(In reply to comment #92)
from Gale Andrews 2011-04-01 14:17:13 BST ---
> The only point about backwards-compatibility as I see it is to save people
> coming from 1.3.6 and 1.3.7 (which had our earliest version of FFmpeg) having
> to get the latest FFmpeg when they upgrade Audacity. Even without
Okay. So I'm going to go ahead and commit the version 11. Gale and I will
work out what the M4A options should be as a separate patch since that will
take some discussion and testing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
The only point about backwards-compatibility as I see it is to save people
coming from 1.3.6 and 1.3.7 (which had our earliest version of FFmpeg) having
to get the latest FFmpeg when they upgrade Audacity. Even without this patch
those 1.3.6/1.3.7 users would have to upgrade to the current FFmpeg a
(In reply to comment #93)
> I totally agree that the Quality method should be used. But, I think LRN had
> it right when he used a slider. We wouldn't be able to provide an accurate
> value if we tried to assign a bitrate to a specific quality value.
Of the three apps I know about, SUPER (using F
(In reply to comment #92)
> Leland, do you think the reason LRN went for quality was because FFmpeg has a
> problem if you simplistically specify the bit rate? Although users don't
> like/understand those quality settings, they seem to be functional - higher
> quality = higher bit rate. Can you se
(In reply to comment #91)
from Leland Lucius 2011-04-01 00:48:46 EDT ---
>>
>> Why change several wxLogDebug() calls to wxLogMessage()? I would think that
>> type of info would only be clutter to most users, and relevant only to those
>> of
>> us building Debug versions.
>>
> Did that because i
(In reply to comment #88)
> Tried v12 on win 7 x64 so far. Main finding so far is that exported bit rates
> are not correct. Exporting a stereo music track, both with FFmpeg 0.5 and 0.6
> and according to Medianfo and iTunes,
>
> 24 kbps exports as 60 kbps
>
> 96 and 256 kbps both export as 150
(In reply to comment #89)
> Scanned the patch. Nice work with the function declaration macros, made it a
> lot more readable. And your changes are well documented.
>
> Why change several wxLogDebug() calls to wxLogMessage()? I would think that
> type of info would only be clutter to most users, a
Scanned the patch. Nice work with the function declaration macros, made it a
lot more readable. And your changes are well documented.
Why change several wxLogDebug() calls to wxLogMessage()? I would think that
type of info would only be clutter to most users, and relevant only to those of
us buil
Tried v12 on win 7 x64 so far. Main finding so far is that exported bit rates
are not correct. Exporting a stereo music track, both with FFmpeg 0.5 and 0.6
and according to Medianfo and iTunes,
24 kbps exports as 60 kbps
96 and 256 kbps both export as 150 kbps (the exported files are the same
si
Created an attachment (id=153)
Change m4a export options to bitrate
This changes the m4a export options to a more common bitrate instead of
quality.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/60293
(In reply to comment #84)
> Is this supposed to wait until after 1.3.13 is released? Or should it get
> committed now?
I would agree to committing it because I think it would reduce the number of
Linux complaints about FFmpeg, and it's been pretty well tested on my systems.
But you need someone el
I don't know if my vote counts, but I would like to see this patch committed.
If the patch is not included in the upcoming release, I will apply the patch in
the Debian/Ubuntu package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
(In reply to comment #81)
>
> Does this cover everything?
>
I believe so. Let's get the v11 patch committed to get it into the hands of
more users and more environments to see if there's more issues.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
(In reply to comment #83)
> So whoever commits the bug can resolve it fixed because it has had its QA
> testing already. Thanks, Leland.
Is this supposed to wait until after 1.3.13 is released? Or should it get
committed now?
--
You received this bug notification because you are a member of Ubu
(In reply to comment #80)
>> AAC export on Ubuntu (native encoder using "M4A files") is still wrong -
>> seems to be a silent file - "playable" but very small file size.
> I'm pretty sure the small file size is expected, but the silent file is not.
> Can you send me one of those via email?
I hav
> What I want to do now to complete testing is to generate AMR/AC3/M4A/WMA files
> outside Audacity and try those on Audacity on Win and Ubuntu.
This did not provide any problems in terms of correct audio being imported.
All the residual issues from this AFAICT are now at bug 317, bug 338, bug 339
Leland
Applied v11 on Windows and Ubuntu (uninstalled FFmoeg HEAD so back to Ubuntu
FFmpeg).
Only minor WMA problem left is visibility of exported metadata to other apps -
see http://bugzilla.audacityteam.org/show_bug.cgi?id=134#c5 .
32-bit WAV files come in OK via FFmpeg as 32-bit on Win and
(In reply to comment #79)
> AAC export on Ubuntu (native encoder using "M4A files") is still wrong - seems
> to be a silent file - "playable" but very small file size. Are we still
> expecting that?
I'm pretty sure the small file size is expected, but the silent file is not.
Can you send me one o
(In reply to comment #77)
> Is the new FFmpeg support in these patches backwards-compatible beyond 0.5? So
> if someone on Win went from 1.3.6 Beta to 1.3.13 Beta, they would not need to
> update their FFmpeg? I don't think it matters if not, just asking.
Probably not. I only tested as far back a
Is the new FFmpeg support in these patches backwards-compatible beyond 0.5? So
if someone on Win went from 1.3.6 Beta to 1.3.13 Beta, they would not need to
update their FFmpeg? I don't think it matters if not, just asking.
--
You received this bug notification because you are a member of Ubuntu
Created an attachment (id=147)
Don't just bypass the metadata dialog, bypass writing the tags too!!!
This skips writing the tags if they aren't supported by the format. It was
only a one line change, so "major" testing shouldn't be required.
--
You received this bug notification because you are
(In reply to comment #74)
> My only issue was with the stereo m4a I exported using Ubuntu's FFmpeg so
> using
> the native aac encoder. This is the log when importing it into Audacity with
> either version of Audacity:
> Error: Stream 0 start_time = 0, that would be 0.00 milliseconds.
>
I
Thanks for the tips, Benjamin.
Leland, I applied v10 and I exported all four FFmpeg formats using FFmpeg HEAD
and all three available formats (amr is not available) uing the Ubuntu FFmpeg.
I imported the seven files using both versions of FFmpeg.
My only issue was with the stereo m4a I exported
(In reply to comment #70)
> (In reply to comment #69)
> Thanks Leland. Will try v10. For those who try the patches one after the
> other,
> is there an easier way to apply the patch than manually deleting then
> restoring
> the affected files before patch? E.g. could I actually apply your v10 pat
There are two ways:
1. Use -R to revert the previous patch (patch -R < previous.patch).
2. Use svn revert to revert the changes.
--
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
(In reply to comment #72)
> 2. Use svn revert to revert the changes.
Oooo, I like that one. Didn't know about it. I'll have to give that a try
next time.
Thanks,
Leland
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
(In reply to comment #69)
Thanks Leland. Will try v10. For those who try the patches one after the other,
is there an easier way to apply the patch than manually deleting then restoring
the affected files before patch? E.g. could I actually apply your v10 patch
over an earlier patch version?
--
Y
Created an attachment (id=142)
Reuploading v10 patch...
--
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
(In reply to comment #64)
> AC3 import OK. AC3 export gives a zero byte file but the same happens with
> standalone ffmpeg at the command line "LIBAVUTIL_50 not defined in file
> libavutil.so.50 with link time reference". I gather I may have to find
> libavcore, from Googling the error?
>
Not sure
Created an attachment (id=140)
Forces usage of ac3-fixed encoder
I took the easy way out and forced usage of the "ac3-fixed" encoder.
--
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:
ffm
(In reply to comment #61)
> I won't be trying v7 for a while so if you are around please let me know what
> you think about the above error.
It's because your building with system libraries. I have not tried that since
I added HEAD support. I will see what I can do to get it to build using syst
Created an attachment (id=141)
AC3 encoder should be detected for all versions now
Okay, this one should detect the proper AC3 codec for FFmpeg HEAD and older
versions.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
(In reply to comment #66)
> Created an attachment (id=140) [details]
> Forces usage of ac3-fixed encoder
>
> I took the easy way out and forced usage of the "ac3-fixed" encoder.
And the easy way was (at least the way I did it) was stupid. I'll work on this
again when I get home tonight.
--
You
Thanks Leland, I built Audacity against your v8 patch and am using
FFmpeg HEAD.
WMA and AMR NB export and import OK (at least Audacity's own files).
AC3 import OK. AC3 export gives a zero byte file but the same happens with
standalone ffmpeg at the command line "LIBAVUTIL_50 not defined in file
l
I don't know what FFmpeg version Steve has but I'm trying now with git ffmpeg.
I couldn't find out how to configure FFmpeg for a native AMR*b encoder/decoder
or even if there is one, so I got opencore with the dev package and I
configured FFmpeg thus
./configure --enable-shared --enable-libgsm --e
Created an attachment (id=139)
Yet another patch...
Okay, this one should allow building again the FFmpeg HEAD headers. The last
couple of patches allowed Audacity to use FFmpeg HEAD libraries, but not build
against the headers. I'd left out a bit of Benjamin's original patch...
This also preve
Created an attachment (id=138)
Add WMA metadata support for later FFmpeg versions
--
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
Created an attachment (id=137)
Add WMA metata support for later FFmpeg versions
This patch includes a fix for bug #134 where WMA tag support was missing. It
was fixed on 2010-02-15, so if a libavformat with a version greater than
52.52.0 is used with Audacity, then WMA tags can be specified.
Lel
(In reply to comment #53)
> Actually, there isn't a native AMR encoder, just a native decoder. And that
> decoder returns to Audacity as floats. I "think" AMR files are always 8-bit
> 8000Hz, but I could be entirely wrong about that.
Sorry but I got confused by discussion of two decoders. So the
(In reply to comment #55)
> I ran into
>
> ImportFFmpeg.cpp
> ..\..\..\src\import\ImportFFmpeg.cpp(874) : error C3861: 'lrintf': identifier
> not found
> ..\..\..\src\import\ImportFFmpeg.cpp(878) : error C3861: 'lrint': identifier
> not found
>
> on Windows Unicode Release.
Sorry about that Gal
(In reply to comment #57)
Looks good here (Ubuntu 10.10)
--
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
Created an attachment (id=135)
Provides support for later versions of FFmpeg
This provides all of the previous changes, plus:
1) On import, if the sample format from FFmpeg is 8-bit or 16-bit, then it
will be imported into Audacity as 16-bit. Anything else gets imported as
float.
2) Export opt
I ran into
ImportFFmpeg.cpp
..\..\..\src\import\ImportFFmpeg.cpp(874) : error C3861: 'lrintf': identifier
not found
..\..\..\src\import\ImportFFmpeg.cpp(878) : error C3861: 'lrint': identifier
not found
on Windows Unicode Release.
--
You received this bug notification because you are a member o
(In reply to comment #52)
> (In reply to comment #48)
> > newer FFmpegs include a native amr decoder and the default sample format
> > for
> > them is float whereas the default for the opencore amr decoder it 16-bit.
> Thanks for the new patch. Yes I recall now about FFmpeg only supporting 16-bi
Created an attachment (id=134)
Now includes support for non 16-bit input samples
I would like to have tested this a tad more, but I have to get to work and I
wanted to get it out before I left.
This adds support for input sample formats other than 16-bit and should correct
that amrnb problem.
Le
So the issue is that Audacity doesn't support any sample formats from FFmpeg
other than 16-bit. So audio from decoders that do not output 16-bit samples
will not import properly into Audacity.
You may prove it by creating a WAV file in 32-bit float format. Then try
importing it. Make sure you h
(In reply to comment #48)
> newer FFmpegs include a native amr decoder and the default sample format for
> them is float whereas the default for the opencore amr decoder it 16-bit.
Thanks for the new patch. Yes I recall now about FFmpeg only supporting 16-bit
input. But you mean the native "encod
Forgot to mention that this problem existed in at least 1.3.12, so it's not a
new issue...
--
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 ve
(In reply to comment #46)
Thanks for confirming the import crashing has gone, Steve.
> AMR narrowband appear to be exported correctly, but when imported the file is
> double the original length and at half the original frequency.
I was wondering, how do you get AMR NB support with Ubuntu's FFmpeg?
(In reply to comment #46)
> AMR narrowband appear to be exported correctly, but when imported the file is
> double the original length and at half the original frequency.
This is because the newer FFmpegs include a native amr decoder and the default
sample format for them is float whereas the defa
(In reply to comment #45)
Results so far with patch v3-ffmpeg-0.6.1.diff
Ubuntu 10.10
System FFmpeg F(52.64.2),C(52.72.2),U(50.15.1)
Export and Import successful for short mono and stereo files as WMA, M4A and
AC3.
AMR narrowband appear to be exported correctly, but when imported the file is
doub
(In reply to comment #42)
Thanks for your further patch. Likely to take a little while before I get round
to it.
> How important is HEAD support?
I would say most who are interested in compiling and not just using the distro
package of Audacity will "head straight for HEAD". They see no need fo
Created an attachment (id=132)
Provides support for later versions of FFmpeg and HEAD
An update to the patch that should work for our existing 0.5x up through
HEAD...though HEAD should be tested a bit more.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
(In reply to comment #41)
> (In reply to comment #39)
> > use libfaac for encoding (Windows and OSX) and use the native FFmpeg aac
> > decoder instead of libfaad
> OK, I think we could get away with that on Windows and OS X without a release
> note if there are no technical issues with it. I assum
(In reply to comment #41)
> Added note to "current issues" about SVN FFmpeg.
How important is HEAD support? The reason I ask is that they have changed
things around a bit in the library (on 2010-06-22, my 25th wedding anniversary
;-)) and have "broken" a kludge we had in place to support Unicode
(In reply to comment #37)
> (In reply to comment #36)
> > if everyone is also satisfied, I'd like to go ahead and commit it and move
> > on to the detection simplification.
> If you're OK I'd still like to try with SVN FFmpeg, since that gave endless
> trouble before. I assume you have done this, b
(In reply to comment #38)
> Yet another (and I'm trying it now), would be to have both the native and
> libfaac/libfaad enabled (Windows and OSX). It may be possible to present both
> options to the user. It's certainly possible via the ffmpeg command, but via
> the custom ffmpeg options dialog,
(In reply to comment #33)
> 1) No extreme time differences between m4a and other ffmpeg formats.
> 2) The native exporter is faster than faac
> 3) Faac exported files sound better
> 4) Any file imported with faad gets imported as stereo
> This was all done on the Mac...
Thanks for your tests,
(In reply to comment #39)
> use libfaac for encoding (Windows and OSX) and use the native FFmpeg aac
> decoder instead of libfaad
OK, I think we could get away with that on Windows and OS X without a release
note if there are no technical issues with it. I assume you have
libfaac-encoded a native-
(In reply to comment #32)
> (In reply to comment #31)
> >> I think you will be able to repro it on Windows (and I assume on FFmpeg
> >> 0.6.1
> >> too, but I have not tried with 0.6.1 yet). What happens on Mac?
> >
> > Same sort of thing. If I create a mono M4A file using 0.6.1 and then try to
(In reply to comment #37)
> I don't see we can do a "Stereo Tracks to Mono" on an M4A imported via libfaad
> as it would take too long. But could or should you do some hackage in our
> FFmpeg code so that it imports "first time" as mono? I think the answer to
> that
> is "is this a libfaad bug"? I
(In reply to comment #31)
>> I think you will be able to repro it on Windows (and I assume on FFmpeg 0.6.1
>> too, but I have not tried with 0.6.1 yet). What happens on Mac?
>
> Same sort of thing. If I create a mono M4A file using 0.6.1 and then try to
> import it using a v0.5 library, it will
(In reply to comment #36)
> if everyone is also satisfied, I'd like to go ahead and commit it and move
> on to the detection simplification.
If you're OK I'd still like to try with SVN FFmpeg, since that gave endless
trouble before. I assume you have done this, but since I'm inexperienced there
is
I have FINALLY figured out, at least for me, why the m4a files would import as
mono when the above patch was NOT applied. It basically boils to me being an
idiot.
When I was originally testing the patch, I'd realized that the QuickTime
importer was doing the import, so I reversed the order of the
(In reply to comment #34)
> (In reply to comment #33)
> > 1) No extreme time differences between m4a and other ffmpeg formats.
> > 2) The native exporter is faster than faac
> > 3) Faac exported files sound better
> > 4) Any file imported with faad gets imported as stereo
> > This was all done
(In reply to comment #27)
> I think you will be able to repro it on Windows (and I assume on FFmpeg 0.6.1
> too, but I have not tried with 0.6.1 yet). What happens on Mac?
>
Same sort of thing. If I create a mono M4A file using 0.6.1 and then try to
import it using a v0.5 library, it will alway
Created an attachment (id=126)
Just a combination of 0.6.1 support and the import crash fix - try 2 :-)
Re-recreated the patch. :-)
--
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:
ffmp
(In reply to comment #23)
> That OGG slowness thing is separate (bug 311) but I have never seen it so
> far.
>
> Why would the copy-in Pref affect OGG > OGG? Audacity should copy the OGG in
> irrespective of that setting.
I'll respond in bug #311.
Leland
--
You received this bug notification
(In reply to comment #26)
> Created an attachment (id=125) [details]
> Just a combination of 0.6.1 support and the import crash fix
Actually this patch lacks the three new files in lib-src\ffmpeg\libavutil
attributes.h
avconfig.h
error.h
which you will need to grab from the original patch:
htt
(In reply to comment #26)
> I have been unable to pin down why M4A imports are silenced. Actually, I no
> longer see this, so if y'all can attach a file to this bug that consistently
> imports as silence that'd be great.
For me, the same file will sometimes import as silence and sometimes not. The
(In reply to comment #28)
> (In reply to comment #26)
> > Created an attachment (id=125) [details] [details]
> > Just a combination of 0.6.1 support and the import crash fix
> Actually this patch lacks the three new files in lib-src\ffmpeg\libavutil
>
Oops, sorry about that. Will create it again
OK on fresh checkout and make dep before and after applying attached patch then
make dep before and after bug 317 patch, on Ubuntu 10.10 with the Ubuntu
FFmpeg...
* I seem to get consistently safe exports of AC3, WMA and AAC. However AAC
export is far too slow.
* I seem to get consistently safe
Created an attachment (id=125)
Just a combination of 0.6.1 support and the import crash fix
This is a combined patch that include the 0.6.1 support and the fix for the
import crash from bug #317.
I have been unable to pin down why M4A imports are silenced. Actually, I no
longer see this, so if y
For those experiencing slow exports after importing an OGG file, can you try
changing "Edit->Preferences->Import/Export->Read uncompressed..." to "Make a
copy..." and then exit Audacity, get back in, and try to reproduce the
slowness.
For me, it no longer occurs. And since the slowness happens wi
(In reply to comment #14)
Confirm that it builds ok with system FFMpeg on Ubuntu 10.10
An import WAV, MP3 and FLAC with FFmpeg, but importing WMA segfaults.
Can export WMA successfully (Bug 274)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Leland wrote:
> Should I regenerate the above patch with the fix from bug #317?
Yes, I think that would make it easier for others to test.
> What are the outstanding issues?
All FFmpeg bugs "should" have the "FFmpeg" keyword:
http://bugzilla.audacityteam.org/buglist.cgi?keywords=FFmpeg&resolutio
Okay, I'm getting kind of confused. Is this working for anyone at all? Should
I regenerate the above patch with the fix from bug #317? What are the
outstanding issues?
Leland
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
(In reply to comment #19)
> builds ok with system FFMpeg on Ubuntu 10.10
> (c)an import WAV, MP3 and FLAC with FFmpeg, but importing WMA segfaults.
Have you tried the patch in bug 317 for FFmpeg import crashes? That needs to be
applied on top of the patch attached here.
--
You received this bug n
Gale, are you still having issues with the patch? It really should affect
anything other than FFmpeg files. Could you try it against a fresh checkout?
Also, did you happen to a "make dep" in the "src" directory before/after
applying? (would be a good idea to do it.)
Leland
--
You received th
(In reply to comment #17)
> did you happen to a "make dep" in the "src" directory before/after applying?
>(would be a good idea to do it.)
As per comment 15 I applied the patch then did make clean, then ./configure;
make dep; make. Did not do "make dep" before the patch (except that I did it
befo
> Is this the Ubuntu FFmpeg or SVN FFmpeg?
It's the Ubuntu FFmpeg package.
--
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 maveri
(In reply to comment #14)
> I tested the patch from comment 10 with the system FFmpeg and it works on my
> system.
> Exporting and importing ac3, flac, ogg, wav, wma worked.
> System: Ubuntu 11.04 (natty) development version
> Audacity: trunk configured to use all system libraries
Hmm. Is this the
I tested the patch from comment 10 with the system FFmpeg and it works on my
system.
Exporting and importing ac3, flac, ogg, wav, wma worked.
ogg imports and exports are very slow (bug #311).
The m4a export produces a file containing only silence. Should I open a new bug
report for it?
System:
Also see bug 313 comment 1. Import of any formats (even non-FFmpeg) is
generally flaky after applying the patch in comment 10 here. WMA imports will
always
segfault, but so will WAV, MP3 and FLAC imports (most, but not all of the
time). I have to suspect this patch in comment 10, because:
* If I u
See bug 141 comment 3 - undefined symbol match_ext in HEAD after running 1.3.12
Ubuntu package.
--
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 ffmp
Only tested so far on Ubuntu 10.10. Ubuntu-distributed FFmpeg is listed on
opening Prefs on initialised or non-existent .cfg.
Should be tested with self-compiled FFmpeg.
Side issue for discussion: although FFmpeg version number is listed in Prefs,
when you click "Locate...", then "Yes" in "Succe
Created an attachment (id=113)
Provides support for later versions of FFmpeg
This patch provides support for the more recent versions of FFmpeg. It still
supports for the existing pre-built Windows and Mac FFmpeg binaries. It also
incorporates the fix for bug #274 and provides compile-time verif
tion 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 201
** Changed in: audacity (Mandriva)
Importance: Unknown => Medium
--
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
--
** Changed in: audacity (Debian)
Status: Unknown => Fix Released
--
ffmpeg import/export not working with ffmpeg version in maverick
https://bugs.launchpad.net/bugs/602934
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu
** Branch linked: lp:debian/sid/audacity
--
ffmpeg import/export not working with ffmpeg version in maverick
https://bugs.launchpad.net/bugs/602934
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@
1 - 100 of 119 matches
Mail list logo
