View Full Version : Procoder 3 Oversized output
six13
6th December 2010, 01:15
I have been using Procoder 3 to convert files to mpg 2 DVD VOB files. I use mastering quality, 2 pass VBR and ac3 audio. When I look at the output size and it is larger than 4.7 GB I decrease the bitrate till the output size falls to 4.7 GB typically around 5200 kbs for a 2 hr movie. I then change min bitrate to 1000 kbs and maximum bitrate to about 7500 kbs so I get a good variable rate. After all these changes the output size still shows 4.7 GB so I believe that my output will fit on a DVD 5 but I end up with a folder that is too large for a DVD 5
Is there a Procoder .ini file or somthing that I can set maximum sectors so I don't get oversized output? I am left to use a fast transcoder to compress the output about 3% so it will fit a DVD 5.
Groucho2004
6th December 2010, 01:42
I am left to use a fast transcoder to compress the output about 3% so it will fit a DVD 5.
Did it ever cross your mind to apply this 3 % reduction to the predicted output size in Procoder?
Edit:
I don't know how accurate Procoder's calculations are but I prefer to calculate the bitrate including multiplexing overhead myself. If you are interested I can dig up the formulas and post them here.
six13
6th December 2010, 01:56
well procoder 3 shows me the output size as the avg bitrate changes based on what I enter for the avg bitrate and it also factors in the audio track size. Last time I processed a file I used 4.6 GB rather than 4.7 GB so I had a cushion. I don't see where I can enter a output size in MB's so that the program will shrink to fit. The only thing I think I can do is perposly undersize the output as shown by the Procoder 3 GUI. Last time I used 4.6 GB and it was still to large for a DVD 5. My point is that the program isn't very accurate at determining the output size, is there a setting I can alter?
I am not using Procoder 3 with DVD-Rebuilder. I am using Procoder 3 to do all the authoring, encoding.
six13
6th December 2010, 01:59
please post the formula. Pretty strange that Procoder 3 doesn't do this properly on its owm. i may reinstall
Groucho2004
6th December 2010, 02:06
Last time I processed a file I used 4.6 GB rather than 4.7 GB so I had a cushion.
How does Procoder define 1 GB? 1,000,000,000 bytes or 1,073,741,824 bytes? If it's the latter (1024^3), then 4.6 still way to much. Based on "1024^3 bytes = 1 GiB" the maximum that will fit on a DVD5 is 4.36 GiB.
I'll post the formula tomorrow.
six13
6th December 2010, 02:41
How does Procoder define 1 GB? 1,000,000,000 bytes or 1,073,741,824 bytes? If it's the latter (1024^3), then 4.6 still way to much. Based on "1024^3 bytes = 1 GiB" the maximum that will fit on a DVD5 is 4.36 GiB.
I'll post the formula tomorrow.
thanks, this problem just crept up. My output previously would be 4.32 or 4.33 GB 's when the Procoder 3 GUI would display 4.7 GB's so I think it factors in the 1024 figure. I previously could burn to DVD with no problem.
Groucho2004
6th December 2010, 13:21
Here are the formulas for DVD bitrate calculation:
navpacks = NumberOfFrames / GopSize
assetpacks = (VideoSize + AudioSize + SubtitleSize) / 2025
padding = navpacks * 1012
TotalSizeDVD = ((navpacks + assetpacks) * 2048) + padding
To calculate the bitrate:
VideoSize = ((((TotalSizeDVD - padding) / 2048) - navpacks) * 2025) - AudioSize - SubtitleSize
Bitrate = VideoSize * 8 / MovieLength
six13
6th December 2010, 23:44
thank you
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.