DISCLOSURE: Movie Studio Zen is supported by its audience. When you purchase through links on this site, we may earn an affiliate commission.
Question DVDA rendering Video
Replied by DoctorZen on topic DVDA rendering Video
Posted 21 Apr 2023 16:18 I haven't used DVDA for a long time now, so my knowledge is not as sharp as it used to be.
You can't rely on the File Size of your videos to be what guides whether your project will fit on a 50GB blu-ray and not require re-rendering.
It's all about Total Length in Time.
You have 3 hour and 35 minutes (215 minutes) in total, which is quite long, even for a 50GB Blu-ray disc.
What all this means, is that BOTH of your videos must use a Bit Rate, that does create a total file size that exceeds 50GBs (it's actually less than 50GBs in reality.
When I was making Blu-ray discs, I always used this online Bit Rate calculator, which will tell you what settings to use in VEGAS Pro.
dvd-hq.info/bitrate_calculator.php
I have taken a screen shot of the settings that match the info you have provided.
Please note that this is using the exact total time you gave me.
In reality, it is safer to use a Safety Margin as well, to make sure you stay in the Bit Rate budget.
In a 215 minute total time project, it would probably be best to use at least an extra 3% to 5% to allow for variables.
Example: 215 x 1.03% = 222 minutes
215 x 1.05% = 226 minutes
*Please note, if you enter 222 or 226 as the time, you will have to generate new bit rates!
Inside of VEGAS Pro, the Bit Rate calculator is expecting you will be rendering with MainConcept MPEG-2 for Blu-ray.
**Remember, VEGAS Pro uses an extra 000 for bit rates. 37300 becomes 37,300,000 etc...
I didn't muck around with I-frames and left at Vegas defaults.
Render both videos first and then check total file size.
Also, remember to render separate Audio Streams - that file size also goes into the total pot!
You can't rely on the File Size of your videos to be what guides whether your project will fit on a 50GB blu-ray and not require re-rendering.
It's all about Total Length in Time.
You have 3 hour and 35 minutes (215 minutes) in total, which is quite long, even for a 50GB Blu-ray disc.
What all this means, is that BOTH of your videos must use a Bit Rate, that does create a total file size that exceeds 50GBs (it's actually less than 50GBs in reality.
When I was making Blu-ray discs, I always used this online Bit Rate calculator, which will tell you what settings to use in VEGAS Pro.
dvd-hq.info/bitrate_calculator.php
I have taken a screen shot of the settings that match the info you have provided.
Please note that this is using the exact total time you gave me.
In reality, it is safer to use a Safety Margin as well, to make sure you stay in the Bit Rate budget.
In a 215 minute total time project, it would probably be best to use at least an extra 3% to 5% to allow for variables.
Example: 215 x 1.03% = 222 minutes
215 x 1.05% = 226 minutes
*Please note, if you enter 222 or 226 as the time, you will have to generate new bit rates!
Inside of VEGAS Pro, the Bit Rate calculator is expecting you will be rendering with MainConcept MPEG-2 for Blu-ray.
**Remember, VEGAS Pro uses an extra 000 for bit rates. 37300 becomes 37,300,000 etc...
I didn't muck around with I-frames and left at Vegas defaults.
Render both videos first and then check total file size.
Also, remember to render separate Audio Streams - that file size also goes into the total pot!
ℹ️ Remember to turn everything off at least once a week, including your brain, then sit somewhere quiet and just chill out.
Unplugging is the best way to find solutions to your problems. If you would like to share some love, post a customer testimonial or make a donation.
Unplugging is the best way to find solutions to your problems. If you would like to share some love, post a customer testimonial or make a donation.
Please Log in or Create an account to join the conversation.
Forum Access
- Not Allowed: to create new topic.
- Not Allowed: to reply.
- Not Allowed: to edit your message.
Moderators: DoctorZen
Time to create page: 1.132 seconds
