MPEG2 file on DVD

[DVDDoug]

The weird thing is... If neither VS11 or VS12 are re-rendering, why is there a difference????

Is it possible that VS11 was re-rendering? ...Maybe VS11 recognized something "wrong" with the files and treated them as non-compliant???

MPEG-2, VBR 9100, Dolby Digital 5.1 (bitrate 448).

There could be an issue with the high bitrate. (VBR means Variable Bit Rate and I don't know if 9100 is the average or maximum.) The DVD spec allows a maximum video bitrate of 9800kbps with a combined video, audio, and subtitle maximum of 10,200kbps.

You can estimate average bitrate with the following formula:
Bitrate = (140 x File Size in MB) / Playing time in minutes

If that formula shows you have a combined average audio/video bitrate of around 9500, it's a good bet that your peak bitrate is out-of-spec. If your average is less than 9000, then 9100 is the peak bitrate and you're not out-of-spec.

But, some DVD players apparently have difficulty with high-bitrate "burned" DVDS. The usual recommendation is to keep the bitrate below about 7000kbps.

You might try shooting some experimental footage with your camera at a lower bitrate to see if that will solve the problem on future projects.

There is a chart here that shows no quality improvement when you go over 8000kbps (with standard definition MPEG-2).

[Heesenproductions]

The weird thing is... If neither VS11 or VS12 are re-rendering, why is there a difference????

Is it possible that VS11 was re-rendering? ...Maybe VS11 recognized something "wrong" with the files and treated them as non-compliant???

MPEG-2, VBR 9100, Dolby Digital 5.1 (bitrate 448).

There could be an issue with the high bitrate. (VBR means Variable Bit Rate and I don't know if 9100 is the average or maximum.) The DVD spec allows a maximum video bitrate of 9800kbps with a combined video, audio, and subtitle maximum of 10,200kbps.

You can estimate average bitrate with the following formula:
Bitrate = (140 x File Size in MB) / Playing time in minutes

If that formula shows you have a combined average audio/video bitrate of around 9500, it's a good bet that your peak bitrate is out-of-spec. If your average is less than 9000, then 9100 is the peak bitrate and you're not out-of-spec.

But, some DVD players apparently have difficulty with high-bitrate "burned" DVDS. The usual recommendation is to keep the bitrate below about 7000kbps.

I took 2 clips with total size 1436mb (containing video, audio, transitions, titles and scroll, plus photoslideshow included). Playing time: 20min. Video action: dancing. Original source: multiple camerashooting. I have calculated it using your formule with the result: 10 052. Using a vbr of 9100, would this be a problem?
I once experimented with 8000vbr (original shooting 9100vbr). I got the same problem: intermittent broken video- some players can't even play beyond this point. Interesting fact: I don't get this problem with single camcorder shooting, only with multiple camcorder shootings. I don't know if the camcorder can be set to record at 8000vbr, but I'll have a look into the manual.

[Trevor Andrew]

Hi

Ok I get the idea,
I didn¡¦t realise you were forcing VS to render.

Thanks Jeff--sorry for the HD confusion, the OP did use AVCHD?

The problem seems to be frame related, at least the quality results would indicate this.

Your original video files are Upper Field. The standard VS templates use Lower Field,
When you do Share Create Disc and render the video the properties under the Options Cogwheel will be used, they will probably use Lower Field, unless you change them, which you say you have.
If you were to edit the project settings to match the video then do share Create Disc-Add Media , you should not have to change the settings in the burner module.

You have four versions of your movie, one from the original unedited files, a second from the finished project, a third on DVD that¡¦s been rendered, and a fourth on DVD not rendered.

Can you compare the video properties of each of these videos.?
Just to make sure they are all the same.

[Banji Abereoje]

Hi all. In my own case I experimented wt a 10mins video captured in avi format frm a cam.

Firstly, Share>Create video file>NTSC dvd (as in its default)....this rendered for 65mins. I saved it as .VSP

Secondly, Share>Create Disc. In d module, I imported the .vsp file wt Add VideoStudio project; made about 4 window-menu chapter; ticked Do not convert compliant MPEG files; proceeded to final burn module. Since it's experiment, I selected the max recording speed.

To my surprise, this still took about 37mins before the final output: altho' the final playback is sweet on DVD player.

The messages were 'converting videos' 'video/audio multiplexing' .... Is it supposed to go thru this long re-rendering? Or is it that my settings were not right somewhere?

I'm doing this in readiness for a 100mins video to be burn to DVD. Won't this take a whole day? I'm scared. Pls bail us out.

My spec is P4 2.8ghz XP with VS8.

Thx good fellas.

[Banji Abereoje]

... So if you create an MPEG2 DVD compatible file in VS (it renders a first time), how do you then burn it to DVD?

If you then open a new project in VS, 'import' the newly created MPEG2 file and then go to 'Share' to create a DVD it renders a second time....

. In a follow up to my last question, could I have captured to Mpeg2 first from cam to save rendering & re-rendering time?

Thx in adv.

[Black Lab]

Is it supposed to go thru this long re-rendering?

Depends what you are starting with. You say avi, but avi is a container format that can include dv-avi, divx, etc.

If you are starting with dv-avi then no, it shouldn't take that long. If you are starting with another of the more compressed formats then maybe it would.

Or is it that my settings were not right somewhere?

What are they? We are not mind readers.

[sgraham]

If you see your project being re-rendered it may be because you selected Upper Field first and then went to Compression tab to finish (which is logical as that is tab on farthest right). If you have not changed your Project Setting to read Upper Field First VS will always revert back to Lower field, even if you set Upper Field (unless you change it to Upper Fiield as the last thing you do before clicking OK). Also, you may want to test on output as Frame Based. I find those look good both on TV as intended and also on computers. - Steve

[Ken Berry]

Firstly, Share>Create video file>NTSC dvd (as in its default)....this rendered for 65mins. I saved it as .VSP

Secondly, Share>Create Disc. In d module, I imported the .vsp file wt Add VideoStudio project; made about 4 window-menu chapter; ticked Do not convert compliant MPEG files; proceeded to final burn module. Since it's experiment, I selected the max recording speed.

To my surprise, this still took about 37mins before the final output: altho' the final playback is sweet on DVD player.

The obvious answer is that you don't seem to understand the workflow. If you initially selected Share > Create Video File > DVD, this would have created a DVD-compatible mpeg-2. You didn't save "it" (i.e. the mpeg-2) as a .vsp file -- you saved the project as a .vsp file. But a vsp file is NOT a video file. It is a small text file telling the program what video files are included in the project, where they are on your computer and what editing has been done to them.

When you opened the burning module (Share > Create Disc > DVD) you added the .vsp file. You should instead have added the mpeg-2 file you created. Then, making sure the 'do not convert compliant mpeg files' box is ticked in the middle of the three icons in the bottom left of screen, you would not have the whole thing re-rendered. It should have just converted any menu to video, then multiplexed the audio and video, then burned the disc.

[sgraham]

Ken - right right I assumed the guy was outputting an MPG and then create new project to make a DVD and drop that MPG in. but you STILL have to watch that you do not pick the Compression tab last. If you have set Upper Field and then go to Compression and hit OK VS will revert back to Lower field if that is what your Project Properties say (and they do by default). - Steve