Hello,
I have imported (5) different mpg's into DVDMF5. It shows the 5 different thumbs, and I would like to combine clip 4 and clip 5 so in the menu screen, it just shows 4 choices. So when I combine (join video) 4 and 5, it shows the size of the project to be 4.5 gigs, where before I combined, it showed 3.7 gig. When I sepearte the two, it goes back to 3.7 gig.
I thought that was strange, and I decided to burn anyway. Bufore burning, a screen came up that it may not fit, but went on anyway. It burned fine, and the dvd is showing a size of 3.7 gigs. What would cause this?
Join Video - adds to filesize problem
I doubt anyone here knows why it's mis-calculating, but it's all determined by the bitrate... the bitrate on the final DVD, not the bitrate of the source files. You can mathmatically convert bits-per-second into GB per hour. Here's a handy Bitrate Calculator.
[size=92][i]Head over heels,
No time to think.
It's like the whole world's
Out of... sync.[/i]
- Head Over Heels, The Go-Gos.[/size]
No time to think.
It's like the whole world's
Out of... sync.[/i]
- Head Over Heels, The Go-Gos.[/size]
-
maddrummer3301
- Posts: 2507
- Joined: Fri Dec 10, 2004 10:24 pm
- Location: US
Hi,
The reason is the mpeg files were not created by the ulead encoder and the program itself doesn't know the "True_Average_Bit_Rate".
To perform this properly would be very time-consuming and the files would need to be analyzed prior to joining them.
Because you are JOINING them then the new mpeg file that's created is based on it's length of TIME and the encoding settings you have setup as your "Project Settings" (under the GEAR icon etc).
When you JOIN any files in MF "AND IF" they are dvd compliant then the program joins them using "Smart-Render". That is why they come out properly building an .iso file etc.
But, IF the files are NOT dvd compliant then the calculation meter is "Correct" and they are rendered to the encoder settings your project is set for.
Dvd Recorders use a different encoding method. If you set a dvd recorder up to record at SD (Standard Play 2 hours) then:
Maximum_Bit_Rate = 9000kbs+ (Panasonic is usually 9558kbs / Sony is usually 9800kbs)
Average_Bit_Rate = @4200kbs +/- 20%
Minimum_Bit_Rate = @1000kbs
But, as an example one could have 2 or more dvd compliant files that are encoded at different bit rates. Now when you join them the resulting file must have only one set of properties. You can't have one mpeg file that has an average bit rate of 4200 and simply join it to another with an average bit rate of 7000. That can't work by the mpeg2 spec's. The file will not play correctly and be out of audio sync on the final dvd after multiplexed into a VOB container file. Why? Because Mpeg2 files are extremely complex and when they are encoded they are using video_buffer settings within the mpeg2 file not to mention many other complex settings.
Just a quick example: If you fast joined 2 dvd compliant files into one file if the first file was running at 4000kbs at frame 3000 and the joined file where joined was running at 7000kbs then at frames after 3000 (the joining point) the video buffer size encoded in the mpeg2 file would be depleted to fast when the 7000kbs information is processed. You dvd player will say "Cannot Play this File". Also, the joined mpeg2 file will play alright in a computer just playing the mpeg2 file but will most likely be out of audio sync on the dvd when multiplexed to a VOB container.
I think that ulead should try to add a small interface on how to re-calculate the disc.
Something such as "Use calculation based on compliant settings" etc.
There isn't a problem with ulead and it's calculations. The confusion is ulead products offer "Advanced" encoding methods and one can take advantage of directly controlling the encoder settings. Usually these features are only available on more expensive video software.
Ulead offers these features with low cost programs such as MF and VS along with the fact that one must be very knowledgable and how to apply and use the DVD spec's along with specific mpg2 spec's.
To understand the ulead products one needs to have a fair amount of knowledge with video spec's. It's not something you just jump into and learn in a few days. It takes years.
And it's not that someone on this board can't answer the posters original question. It's the fact that the answer is a long winded boring repetitive answer like this one.
MD
The reason is the mpeg files were not created by the ulead encoder and the program itself doesn't know the "True_Average_Bit_Rate".
To perform this properly would be very time-consuming and the files would need to be analyzed prior to joining them.
Because you are JOINING them then the new mpeg file that's created is based on it's length of TIME and the encoding settings you have setup as your "Project Settings" (under the GEAR icon etc).
When you JOIN any files in MF "AND IF" they are dvd compliant then the program joins them using "Smart-Render". That is why they come out properly building an .iso file etc.
But, IF the files are NOT dvd compliant then the calculation meter is "Correct" and they are rendered to the encoder settings your project is set for.
Dvd Recorders use a different encoding method. If you set a dvd recorder up to record at SD (Standard Play 2 hours) then:
Maximum_Bit_Rate = 9000kbs+ (Panasonic is usually 9558kbs / Sony is usually 9800kbs)
Average_Bit_Rate = @4200kbs +/- 20%
Minimum_Bit_Rate = @1000kbs
But, as an example one could have 2 or more dvd compliant files that are encoded at different bit rates. Now when you join them the resulting file must have only one set of properties. You can't have one mpeg file that has an average bit rate of 4200 and simply join it to another with an average bit rate of 7000. That can't work by the mpeg2 spec's. The file will not play correctly and be out of audio sync on the final dvd after multiplexed into a VOB container file. Why? Because Mpeg2 files are extremely complex and when they are encoded they are using video_buffer settings within the mpeg2 file not to mention many other complex settings.
Just a quick example: If you fast joined 2 dvd compliant files into one file if the first file was running at 4000kbs at frame 3000 and the joined file where joined was running at 7000kbs then at frames after 3000 (the joining point) the video buffer size encoded in the mpeg2 file would be depleted to fast when the 7000kbs information is processed. You dvd player will say "Cannot Play this File". Also, the joined mpeg2 file will play alright in a computer just playing the mpeg2 file but will most likely be out of audio sync on the dvd when multiplexed to a VOB container.
I think that ulead should try to add a small interface on how to re-calculate the disc.
Something such as "Use calculation based on compliant settings" etc.
There isn't a problem with ulead and it's calculations. The confusion is ulead products offer "Advanced" encoding methods and one can take advantage of directly controlling the encoder settings. Usually these features are only available on more expensive video software.
Ulead offers these features with low cost programs such as MF and VS along with the fact that one must be very knowledgable and how to apply and use the DVD spec's along with specific mpg2 spec's.
To understand the ulead products one needs to have a fair amount of knowledge with video spec's. It's not something you just jump into and learn in a few days. It takes years.
And it's not that someone on this board can't answer the posters original question. It's the fact that the answer is a long winded boring repetitive answer like this one.
MD