Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums VEGAS Pro My rendered file is too big?

  • My rendered file is too big?

    Posted by Dave Bauer on May 7, 2011 at 6:30 pm

    I am rendering an AVI file to MPEG2. The length of the file is 01:44:43. I am using VBR 2 Pass DVD Architect NTSC video stream template. I am using John Cline’s calculator to arrive at the average bit rate. I have changed the defaults in the calculator from 1% safety margin to 5% and 1 kilobit to 1000. My audio is at 192 kbps. The calculator gave me readings of 3232 – 5392 – 9440, I than rounded down to 3200 – 5300 – 8000. I feel the calculator is set correctly as I used one of Mike Kujbida’s earlier posts of a year ago to be sure it was correct. I have also run this thru two different calculators and the AVBR numbers came out a little higher, safety margin I feel was the reason for that. I feel something in the properties has changed???? I do no remember changing anything but then again I have been wrong. If you need more info I will post it.
    Thanks in advance for your help,

    Dave

    Mike Kujbida replied 15 years, 1 month ago 2 Members · 9 Replies
  • 9 Replies
  • Mike Kujbida

    May 7, 2011 at 6:56 pm

    Dave, if DVDA is telling you it’s too big, just ignore it as it has a long history of incorrectly reporting file sizes.
    I just finished doing a series of DVDs that around 2 hr. each and every single time DVDA told me it was too large.
    I ignored the warnings as I always do and it proceeded as expected with no problems.

  • Dave Bauer

    May 7, 2011 at 7:05 pm

    Mile,

    My renders are comming out at 4+GB, should give me a file in the 4000MB range. I have run this old home movie 4 times and it is always the same.

    Dave

  • Mike Kujbida

    May 7, 2011 at 7:22 pm

    Dave, that’s still under the 4.3 GB limit so go ahead and burn it.

  • Dave Bauer

    May 7, 2011 at 7:56 pm

    Mike,

    I should given the exact file size, the mpg file alone was 4.63GB. I have never had this problem as I always render the AC3 file first, the calculator gives me a video size file and I allow 117MB for authoring overhead, just my way of doing so I know how close I am to 4480MB for the DVD. This is the first time I have had this problem, something or someone, “ME” changed something to get the big mpg files. I just have not been able to figure out what “ME” did.

    thanks,

    Dave

  • Mike Kujbida

    May 7, 2011 at 8:24 pm

    Dave, WE didn’t do anything wrong, apparently Sony did 🙁
    A search on a few other Vegas forums turned up a few users who are complaining that something has changed with rendering in Pro 10.
    To quote one user:
    I’ve found that its (Pro 10) MPEG2 rendering sizes are random and unpredictable. They can vary by nearly 15%.
    Needless to say, this should not be happening.
    All I can suggest is use Pro 9 or 8 to render, render again with Pro 10 or lower your Avg. value.
    Not much help, I know, but it’s all I can think of.

  • Dave Bauer

    May 7, 2011 at 8:38 pm

    Thanks Mike, I have been pulling out what little hair I have left trying to figure this out. I do not have v9, I just bought v10 back in Feb. on the upgrade deal. I will adjust down and see what happens. Thanks again, all of you guys are top notch for devoting all the time you do.

    Dave

  • Mike Kujbida

    May 7, 2011 at 9:08 pm

    Dave, I sure hope it works for you as I know only too well how frustrating it can be to get the last step in the process finished.
    Good luck with it.

  • Dave Bauer

    May 8, 2011 at 12:48 am

    Mike,

    I took another route. I opened Vegas Pro x86 and used Debugmode Frameserver and used CCE to encode the file. Worked like a charm and I am in DVD A ready to burn.

    Thanks again,

    Dave

  • Mike Kujbida

    May 8, 2011 at 1:17 am

    Dave, congratulations for coming up with an alternative method that works.
    I’ve read on other Vegas forums that CCE is a better encoder so you might want to keep on doing it that way.

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy