[Matthew Rozzi]

I have no idea what I did, but as I continued to tamper and test it started working appropriately. I even tried a preset that I had tried before (which had failed) and it exported super quick (~2 min). It wasn’t a computer restart either; I tried that early on and it did nothing. Right now, my settings are:

H.264
Frame Rate: 29.97
Field Order: Progressive
Profile: High
Level 4.2
VBR 2 Pass
Target bitrate: 2
Max bitrate: 3
Maximum depth and render quality are both checked

So I don’t know what I did to fix this, it’s a mystery. However, I’m still struggling trying to get the video under 25 mb while preserving a decent image. If anyone could help with that, that’d be great. Thanks for the help so far.

[Matthew Rozzi]

I just tried exporting with the video tracks turned off. It started exporting super fast. So it’s the video, not audio.

Actually, specifically it’s one image in particular. I’m using the same image twice: it’s in the background with the opacity decreased and with a gaussian blur. Then on top of that are the text, and the same square image but smaller and with no effects. By elimination I realized that the only thing that made any difference was the image I enlarged. I tried just turning off the blur but it still was slow, so it’s the image itself. But still, when I lower the target bitrate as low as it can go for troubleshooting purposes, with that image turned on, exporting takes an incredible amount of time. There must be a better way to export this, this doesn’t seem normal.

[Matthew Rozzi]

We’re using Pro Tools. And I’m using Premiere Pro CC.

It’s not the fact that it’s mp3. To troubleshoot, I tried exporting another file that I had already exported months ago, and it exported super fast. That project was also just an mp3 over image. The mp3 was also done with Pro Tools. So there’s something wrong with this particular project. The photo I’m using is less than 1 mb. The song is 9 mb. Not really that huge of files.

[Matthew Rozzi]

I’m having the same problem. This is weird. Maybe some faulty update that we installed without knowing?