Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums VEGAS Pro Size limit by project???

  • John Rofrano

    January 31, 2013 at 6:58 pm

    [Edmundo Ferreira] “Got no lucky with stereoscopic projects…”

    Oh, sorry I wouldn’t know. I’ve never edited 3D. I guess there is no way to do this then.

    ~jr

    http://www.johnrofrano.com
    http://www.vasst.com

  • John Rofrano

    January 31, 2013 at 6:59 pm

    [Mike Kujbida] “I always give DVDA rendered MPEG-2 and AC-3 files and never have any problems other than it telling me that the file is too big.”

    Yea, this is what I use as well and have never had any problems because DVD Architect doesn’t have to re-render the file and it just takes the file size at face value.

    ~jr

    http://www.johnrofrano.com
    http://www.vasst.com

  • Stephen Mann

    February 1, 2013 at 2:56 am

    It sounds like you are letting DVDA re-encode the file to fit the disc. If so, big mistake. I very frequently have 1.5 to 2-hours on a DVD, sacrificing a bit of quality to make it fit on the disc. Encoded filesize is entirely dependent on the bitrate. The default bitrate in the MPEG encoder in Vegas is good for about 70-minutes of video.

    Google “Mark’s DVD Bitrate Calculator”. This one has never let me down. Just plug in the variables, select VBR and transfer the results to the Customize Preset in the Render As menu.

    Steve Mann
    MannMade Digital Video
    http://www.mmdv.com

  • William Mims

    February 1, 2013 at 3:00 am

    Stephen: Thanks, good to know. How do I keep it from re-encoding it?

    Mims

  • Stephen Mann

    February 1, 2013 at 3:24 am

    You give DVDA a DVDA compliant MPEG2 file (using the DVDA template in Vegas) less than 4.37Gb and DVDA won’t try to recompress it.

    Steve Mann
    MannMade Digital Video
    http://www.mmdv.com

  • Larry Brewer

    February 18, 2013 at 10:33 pm

    Maybe this is my chance to re-invigorate a thread I started Dec 13. My issue then was failure to open a .veg file. The .bak file would not open either. This was, for me at least, a very large Vegas 12 project. as much as 50+ hrs of HDV footage.(maybe more) As the editing progressed, my veg file got slower and slower to open, and then finally failed to open. the veg file was 3,846kbs when it refused to open. A restore file from a few days earlier did open, but it’s size was only 3,478kbs. I reverted to that file, lost 2 days work, began editing and again made it to 3,800 kbs when the new file failed to open on the next session.

    Looks like I hit a brick wall. can you say “size limit”?

    so I doubled my RAM to 24GB and the performance did not change.

    The vegas120.exe in task manger process window showed approx 1,200,000k when they reached the point where they would no longer open.

    The fileIOsurrogate.exe32 showed showed over 700,000K at the point where the project would not open.

    I got no where in my last thread about this issue. Just a “ask Sony”. They recommended I install build 486 to solve the problem. LMFAO..

    After that install nothing would open, not even the old restore file. The issue there turned out to be thumbnail creation. long story.

    So…. I’m not asking anyone reading this for a solution to my little problem here. Just reaffirm that either “YES” we have built Vegas 12 projects that exceed 3,846kbs, or “NO” that is the largest .veg file we have ever heard of.

    i7 quad core, intel mobo, 24 GB ram, windows 7 Ultimate 64 bit, 120GB SSD system drive. 4TB raid0 media drive

  • Larry Brewer

    February 22, 2013 at 7:32 pm

    I guess that’s one way to shut a thread down.

    Is maximum .veg file size a sacred cow (pun intended) not to be discussed? I sure can’t get an answer.

  • Jorma Nippala

    February 22, 2013 at 8:13 pm

    No drives formatted in FAT32?

  • Larry Brewer

    February 22, 2013 at 8:24 pm

    no

  • Larry Brewer

    February 23, 2013 at 1:51 am

    The drives are all formatted NTFS, and the .veg file size I’m talking about is just under 4 meg, so not really a fat 32 issue.

Page 2 of 3

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