Ever since I started using Audacity 2.1.1 i’ve run into a pretty strange error, when importing any audio into audio that is 2 streams or more, when given the option to choose what stream I want to import, in place of where Audacity would show what codec the stream is using is foreign symbols, on top of this it takes Audacity 2.1.1 a significant amount of time more when compared to how long it takes to import on 2.0.6.
Is there any way i can fix this as i’d rather not have to go through the trouble of reinstalling 2.0.6 every time i need to import an audio file.
Is the file you are importing into 2.1.1 also an AAC file?
Did you change the version of FFmpeg you are using?
If possible please post an example file on Dropbox or similar and give us the address to download the file.
If not, please obtain “MediaInfo” from http://mediainfo.sourceforge.net/en/Download/Windows. Get the version without installer, because the installer may harm your computer. The version without installer is safe. Post what MediaInfo says about the file (View > Text).
Thanks for the attachment. Even if it’s an Audacity rather than an FFmpeg problem, it will probably be hard to do anything about this without an example file. Is there a site that serves these files, or a specific software that creates the files with two audio streams, or can you post an example file that isn’t private?
Or you can click the “PM” button under my user name on the right and attach a file to a Private Message just for me. You can attach an MP4 file up to 2 MB, so the file you already have is small enough.
Anyway, running Windows and Audacity in English language, I can confirm that Audacity 2.1.0 and 2.1.1 have the corrupted text in the codec name, but 2.0.6 does not. Fortunately our latest development code does not show this issue, so perhaps our move to wxWidgets 3 has fixed it.
I can’t test speed of import because I don’t have long MP4 files with multiple audio streams.
2.1.2 should be released at the end of September or early October. If you want to test the “Nightly Builds” of our development code, grab the latest build from the top of gaclrecords.org.uk. Note that these development builds may have bugs due to the work being done to transition to wxWidgets 3.