Quote:
I'd probably submit it to support and see what they say. I'd like to read the response. I still believe they must be using some form bitrate control based on complexity of audio. That thought may also fit the wondering experience documented by BillyR for his clips.
I created various audio forms of increasing complexity. My time line was nothing more than 30second black color board and then my imported WAV audio in track 1. For the last documented case, the white noise stereo was added to track 2 while keeping the simplistic mono sound in track 1.
I created 3 custom MPEG-4 profiles based on the default 1920x1080 13Mbps profile with audio bitrates of 96, 192, and 256.
The results are in the attached table. One can easily see the final result from PD encoding is a very strong function of audio complexity which really hints towards some form of bitrate control.
Jeff
If that's the case it's a good argument for using H.264 for HD video. I don't know about others, but the bitrate I specify is the bitrate I want. However, as I mentioned, I got that result for 14 of the 16 files I recently rendered at 720p 25 fps and 3000 Kbps. One rendered at 177 Kbps, which was acceptable, but the other at 106 Kbps was not, so I rendered it as an H.264 AC-3 and got 192 Kbps.
The puzzling thing about all this is that the two files that didn't render properly came from the same master file from which I rendered 3 clips. The first one rendered at 106 Kbps, the second at 192 and the third at 177. Subsequently I rendered 3 more clips from another master file from the same source, which I examined in Mediainfo and all the specs were the same as the first one, and all 3 of those clips rendered at 192.
This was a special case and doubt if I'll be working on those types of files again, so for me this issue is over.
Dell Precision 7510 Laptop
Windows 7 Pro 64-bit | Intel(R) XEON(R) CPU E3-1505M v5 @2.80 GHz
RAM: 32 GB
Windows Experience Index 7.5