It's saying an extimated file size of 12mb which is roughly what I need for the web application. I'm getting 219mb (tried twice). I can trial and error to reduce the export size but the webm export takes about an hour to spit out my machine. It'll take a few tries to export and it's so timeconsuming considering the overall output size.
Is it possible to make the estimated and actual export size more in line?
PC - Intel(R) Core(TM) i7-6900K CPU @ 3.20GHz 3.20 GHz 64.0 GB RAM
My sample was UHD 56 seconds, exported as VP9 1600 Mbps constant bitrate. Prediction was 11MB; export file was 11.6MB. I have no explanation for the difference you are seeing.
I am using PR 22.3 (the latest update with the new Export workflow). To get familiar settings, I sent the file to AME. But I went back now and looked at the new workflow, and I get the same estimate (as expected).
Oh, I see you said 58 seconds above. Well, at 1,600 kbps that should yield a file of 11.6 MB for the video, plus a little extra for the audio. So the estimation is right, but I guess the encoder isn't making the size you're asking for.
Probably something I'm doing wrong in the plug-in. Will look into it. In the meantime, drop that encoder bitrate.
I did a second test, with the output set to 25fps. As expected, the exported file was slightly larger (11,889KB vs 11,604KB). FYI, I'm Win10.
I'm just not seeing the difference.
Alan, I'd take a look at the too-large-export file with Mediainfo. Post a screenshot in tree view.
Also, I looked at the settings again. The default appears to be Constant Quality at 50. 23.976fps predicats 188MB. At 25fps, it predicts 196MB. I wonder if you didn't get the Constant Bitrate at 1600 to stick?
My export of the 25fps contant quality 50 produced an actual file that is 178,322KB.
12
Replies
AdChoices