Hello,
Just installed VS10+ and wanted to create a DVD from video files I used for VS7. Using the same project properties, it will no longer fit on a DVD with VS10+. Is there something I need set for it to be the same? Thanks
The video is 2 hr 30 min. With the VS7 properties it's 4.3g and with the VS10+ properties it's 4.69g.
VS7 properties
MPEG files
24 Bits, 720 x 480, 29.97 fps
Field Order B
(DVD-NTSC), 4:3
Video data rate: Variable (Max. 4000 kbps)
Audio data rate: 384 kbps
MPEG audio layer 2, 48 KHz, Stereo
VS10+ properties
MPEG files
24 bits, 720 x 480, 29.97 fps
Lower Field First
(DVD-NTSC), 4:3
Video data rate: Variable (Max. 4000 kbps)
Audio data rate: 384 kbps
MPEG audio layer 2, 48 KHz, Stereo
DVD Size different from VS7 to VS10+
Moderator: Ken Berry
There's a couple of possibilities that might be causing the size difference:
1) did BOTH projects have Motion Menus? Is it possible that the VS10+ Project has Motion menus and button transitions?
2) the VS7 project might have used a lower AVERAGE bitrate. You could try lowering your bitrate in VS10+ to VBR 3800 (I would also recommend Dolby Digital audio at 224 instead of mpeg audio)
Regards,
George
1) did BOTH projects have Motion Menus? Is it possible that the VS10+ Project has Motion menus and button transitions?
2) the VS7 project might have used a lower AVERAGE bitrate. You could try lowering your bitrate in VS10+ to VBR 3800 (I would also recommend Dolby Digital audio at 224 instead of mpeg audio)
Regards,
George
Yeah... It could be the audio. MPEG audio isn't standard for NTSC, and Video Studio may be converting it to LPCM behind your back. (LPCM has a bitrate of 1536kbps.) But if that's the case, it's converting the video too.... LPCM alone would make the file bigger 4.69GB. 
The file size is only determined by the playing time and combined audio & video bitrate. Bitrate is kilobits per second, and that can simply be scaled-up to megabytes per hour.
Here's a Bitrate Calculator.
(The calculator says 3770kbs with Dolby @ 192kbps or 2430kbps with LPCM audio.)
The file size is only determined by the playing time and combined audio & video bitrate. Bitrate is kilobits per second, and that can simply be scaled-up to megabytes per hour.
Here's a Bitrate Calculator.
(The calculator says 3770kbs with Dolby @ 192kbps or 2430kbps with LPCM audio.)
[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]
-
bm
No Motion Menus or button transitions.GeorgeW wrote:There's a couple of possibilities that might be causing the size difference:
1) did BOTH projects have Motion Menus? Is it possible that the VS10+ Project has Motion menus and button transitions?
2) the VS7 project might have used a lower AVERAGE bitrate. You could try lowering your bitrate in VS10+ to VBR 3800 (I would also recommend Dolby Digital audio at 224 instead of mpeg audio)
Regards,
George
The VS7 project wouldn't conver to VS10+ so I did it manually by entering the project settings. The settings used are what the video file is.
Trimming the master file comes out to the same size in both VS7 & VS10+. It's just when you go to create a disk and add the file or files, they come out larger than the original as well as larger than VS7 creates.
Thanks
-
NoM.O
I don't know if it has any bearing on your problem or not, but one thing I noticed is that you have your VS7 properties set to Field Order B, and your VS10+ properties set to Lower Field First. VS10+ should be set to Upper Field First.
As a test, I just opened a DVD compliant mpeg in VS6 which listed it's properties as Field Order B. I then opened the same file in VS10+ which listed it's properties as Upper Field First. So even if this doesn't explain the difference in file size, you probably want to change that anyway.
peace.
As a test, I just opened a DVD compliant mpeg in VS6 which listed it's properties as Field Order B. I then opened the same file in VS10+ which listed it's properties as Upper Field First. So even if this doesn't explain the difference in file size, you probably want to change that anyway.
peace.
Nice catch on the Field OrderNoM.O wrote:I don't know if it has any bearing on your problem or not, but one thing I noticed is that you have your VS7 properties set to Field Order B, and your VS10+ properties set to Lower Field First. VS10+ should be set to Upper Field First.
As a test, I just opened a DVD compliant mpeg in VS6 which listed it's properties as Field Order B. I then opened the same file in VS10+ which listed it's properties as Upper Field First. So even if this doesn't explain the difference in file size, you probably want to change that anyway.
peace.
The older Ulead software used Field-A/B (vs. current Lower/Upper respectively).
Might not explain the "size" differences (although if the originals were dvd-complaint, then VS10+ might want to re-render due to the change in field order), but at least, as mentioned by NoM.o, it will help maintain the original Field Order...
Out of curiosity, what are the properties of the original files
Regards,
George
-
Trevor Andrew
Hi
Can you tell us a little more about the working procedure you are using.
Are you simply trying to open a ¡¥project¡¦ made in VS 7 using VS 10
All VS 7 projects should open using VS 10.
Or
Are you importing a video file (mpeg2) to VS 10
If the later, then you should have no size problems, provided the video files is not rendered again.
Trevor
The VS7 project wouldn't conver to VS10+ so I did it manually by entering the project settings. The settings used are what the video file is.
Can you tell us a little more about the working procedure you are using.
Are you simply trying to open a ¡¥project¡¦ made in VS 7 using VS 10
All VS 7 projects should open using VS 10.
Or
Are you importing a video file (mpeg2) to VS 10
If the later, then you should have no size problems, provided the video files is not rendered again.
Trevor