MP3 Export in 10.2 Incredibly slow

Hey guys,

Every other export works fine, but when I try to export using the Podcast MP3 Compressor setting @160kbps or regular Master File Audio Only export (MP3 Setting) it is incredibly slow and hangs. It used to take roughly 30 seconds to export an hour, now I've left my computer overnight and it still wasn't done in the morning. I've uninstalled/reinstalled both Compressor and FCPX 10.2 and trashed my preferences and had no luck.

I've had to resort to exporting an AAC which takes a few seconds and then opening that up inside of Compressor and using Compressor to re-encode it to MP3. This re-encode only takes a few seconds with the same exact 160kpbs Compressor setting that I'd like to do the first time. I've also tried sending the project to Compressor and it still hangs.

Any ideas?? This used to be a part of my weekly project workflow, and now I have to use this weird workaround. Not a big deal, but still very weird.

Did you notice if the render wheel in the timecode bar reaches a certain number ( from 0 to 100 ) where it stops and hangs? Or, does it never get off of 0? If either is the case, you might try deleting the render files for that event or library and try your export again.

Have you found any solutions? I spend time on with Apple tech and they finished my hour session with them by just having me revert back to 10.1.4 for audio exports. That's a pain using two FCP systems. Was wondering if you had found any luck?

Same experience, takes no time at all on 10.1.4 for an audio only export either as .mp3 or .wav, but in 10.2 takes forever or hangs.

I tried a 5 minute export of just audio in 10.2.
Export as mp3 took about 50 seconds. Export as WAV was pretty much instantaneous.

Sorry for the delayed response. It's still not working properly for me (even after the 10.2.1 update). It just takes forever or hangs. I've deleted render files and everything and still hangs. The only workaround is to export it as an AAC audio file instead and then bring it into Compressor (not sending it to Compressor from FCPX because that takes forever too) and exporting it from Compressor using the MP3 settings. That will at least allow you to use the newest version.

It's weird because EVERYTHING else performs great, but NOT THIS. Any other ideas guys?

Hi Jordan,

What is the original format of the audio on your timeline? Is it MP3 or m4a?

- Ronny

The process is that I have it in a compound clip. I sync up new audio to the old audio and pull down the old audio. The new audio is an .aif file. What's weird is that it exports fine as an AAC file. Not sure what's up as this process worked just fine before 10.2.

I've got the same issue here. Original audio is multi channel AIFF embedded in a mov file with ProRes - captured via a AJA Kona 3.

No solution here, but I would suggest a better workflow would be to export AIFF rather than compress to AAC and then compress again. Export and compression in Compressor seem to be as fast as they ever have.

I'll be reporting this to Apple also.

same problem here

I always choose to export the entire project (when it's done) as MOV, and they use some small&free software to extract the audio. MP3 outputting is quite quick (about 20 mins for a 1:30 long footage) if you use handbrake. I'd prefer not to do this with FCP.

I've always used Audacity to create MP3 files. But I have rare need of that now, such an outdated codec. Like .m4a way better.

Export audio only as AIFF, let Audacity make life easy.

Found a quick work around Not using 3rd party software.

In FCPX 10.2
1. Share (Write) file as .wav or .aiff
2. Create new project.
3. Import wav file just created
4. Share (Write) file as .mp3

This procedure was performed for a one hour show. The write time for the .wav file took about 15-20 sec. The mp3 file took about a min. All in all the whole procedure takes about an extra min or so. Not a fix but a good work around when a client requires an mp3.

Note 2: For some reason, FCPX 10.2 does not like a video layer when writing mp3's (which took over an hour to write). Hope this helps.

I am pleased to report that not only did the Apple Feedback guys get back to me on this issue originally, but they followed up by asking me to check if the 10.2.2 update fixed it - WHICH IT HAS!

Awesome!

And really quite remarkable that Apple is still giving support on a product I purchased on first release in January of 2012 - especially on what is probably a fairly obscure issue that doesn't effect a lot of users...

Thanks Pro Apps guys!