-
DVDA 3’s Optomized DVD size totally wrong?
Posted by Paul Gregory on December 28, 2006 at 3:22 amI have a DVD in Architect 3 which has 2 MPEG2 files in it. Explorer in DVDA says the file size of each is 1.34GB for each as does Windows Explorer itself. I can see that the audio needs to be converted to AC3 for both files. When I check the Optomize DVD in DVDA it says that the 2 files are 2.76GB each & need to be re rendered to fit onto a single layer disk. Surely re rendering the MPEG2 so that the audio for DVD is in AC3 can’t account for anything like this increase of size. Does anyone know whats happening?
Thanks in advance
George Wing replied 19 years, 4 months ago 3 Members · 4 Replies -
4 Replies
-
George Wing
December 28, 2006 at 4:03 pmI guess it wants to re-compress your video files using a higher bitrate than the originals.
Are the original videos (1.34gb) already dvd-compliant? What are their properties, and what type of DVD are you creating (PAL or NTSC)? How long are the videos, and what video bitrate is your project using?
Did you turn on “Reduce Interlace flicker” for your videos — that could cause a re-compress of compliant mpegs.
Regards,
George -
Paul Gregory
December 29, 2006 at 5:41 amBoth files were just standard MPEG2 files created in Vegas & therefore should be compliant.
The anti flicker filter wasn’t turned on. Just to see if I could see where the problem was I opened a second instance of DVDA 3 & only dragged the 2 questionable files onto the workplace, then looked at the optimize DVD function & the correct size was displayed. I then turned on the anti flicker filter but this didn’t change the estimated output size. I’m not going to waste any more time on this just move on.
I must confess that I was surprised that you said that turning on the anti flicked filer would result in the re rendering of any MPEG2 files. I have seen several questions posted in these forums that always went unanswered about deinterlace filters. Like for instance Vegas allows you to render a MPEG2 file using progressive scan & DVDA apparently doesn’t so what does DVDA do when its asked to make a DVD that contains progressive scan input? Does it just accept it as is or does it re render to interlaced?
Thanks in advance
-
Allen Zagel
December 29, 2006 at 10:47 amEver Since DVDA-2, and I don’t remember DVDA1 did that also, I’ve noticed that it inflates the video size, sometimes horribly. Over the years on this forum I’ve gotten some possible answers but nothing definitive.
Pretty muych if I have a somewhat large video, I render it to AVI and bring it into DVDA, then after I’m finished authoring, I click the “fit-to-disc” option in the optimize dialog box and wind up fine.
Even is DVDAx says it’s too large, I bring it into DVD Lab Pro and get a more accurate file size, then do my authoring in there.
Happy New Year
AllenASX Media Productions
https://www.asxvideo.com -
George Wing
December 29, 2006 at 1:57 pm[The Old Fart] “The anti flicker filter wasn’t turned on. Just to see if I could see where the problem was I opened a second instance of DVDA 3 & only dragged the 2 questionable files onto the workplace, then looked at the optimize DVD function & the correct size was displayed. I then turned on the anti flicker filter but this didn’t change the estimated output size.”
Did you turn on “Reduce interlace flicker” for the VIDEO TITLE, or just for the MENU? When I turn it on for the VIDEO TITLE (not the menu), DVDA indicates the video will need to be re-compressed.
In general, if you start with compliant mpeg files, then their size should not change unless you tell DVDA to re-compress, or you do something in DVDA that will cause DVDA to need to re-compress (like turning on Reduce Interlace Flicker on the Video Title, or creating a PAL dvd when your source mpeg is NTSC, or adding multiple video angles, or in DVDA4 adding a button-over-video that is more than just a mask BOV…).
Regards,
George
Reply to this Discussion! Login or Sign Up