Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums VEGAS Pro Vegas 9c still with rendering issues

  • Vegas 9c still with rendering issues

    Posted by Scott Francis on November 7, 2009 at 4:59 am

    Hello,

    I am still getting “not enough memory” errors when rendering MPEG files. Settings are for M2T 1440×1080 60i which is my native resolution. Cannot render to the same file type without often having the memory error. I have seen that numerous other have the same issue. I can render to 720p with no problem, as well as mpeg2 no issues. I have been using the same protocol for years with Vegas 7, 8 and 9 and have only recently had these issues with memory errors. Does the same thing on another one of my computers as well. Both are dual and quad core machines with 4gig of ram, XP Pro machines and have been using them for projects for years. The only change is Vegas….any thought? And thanks!!

    Marc Pletix replied 15 years, 7 months ago 9 Members · 12 Replies
  • 12 Replies
  • Or Tal

    November 7, 2009 at 9:05 am

    I’ll tell you what I do, and It’s working for me

    1. before you render, clean the project media (remove unused files) this is the lightning icon on the project media tab/

    2.after that save the project to a new file. it removes all unused media from your ram.

    2. restart your computer

    3. Ctrl+Alt+Del, processes, disable anti virus, and unnecessary proccesses by hitting the Delete Key

    4. open VEGAS, and RENDER. don’t use the computer while rendering.

    does it work ? 🙂

    Or Tal

  • Scott Francis

    November 7, 2009 at 2:57 pm

    Thanks for your input…I have tried all this before and to no avail. I have 3 computers in my video suite and only one is on the internet and even has antivirus, the other two are strictly for video and optimized for video production. I have “saved as” to a new file with it re-writing all my used files to another folder after removing unused files and it still locks up. What’s really interesting is that I can render a 12 camera angle project with mercalli, neat video, color correction, pan crops and other f/x’s fine. When I then time-line all the videos (this is from a concert so I have 12 songs) and add titling it gives me the errors. I have kept all my renders in the native format (1440x1080i) and am trying to render to that format…absolutely weird! If I render to 720p or mpeg2 out of that timeline…no problem…I am at a loss!

  • Or Tal

    November 7, 2009 at 3:23 pm

    HEY Dude. I understand your frustration. lots of work

    2 more things to try:

    1. when you render try check the “use network rendering”, even though you don’t have any, just try click next and next and see if something good happens….

    2. check if it freezes on a certain point on your video. may’be some event on the TL makes VEGAS crazy. try to play with it, change things or just render this event to a new track. do you get any red screens on your TL ?

    don’t lose hope…(:

    Or Tal

  • Rob Xpyakyalo

    November 8, 2009 at 7:22 am

    OMG has Sony gotten in over their heads on this? So many people having problems… To tell you the truth, it’s obviously not so many people having problems at all, it’s VEGAS having problems. I have had problems when my video clips reach 1 hour 15 minutes. About there the whole computer gets real unstable, until just zooming in on the timeline can bring it all down. In fact I’m starting to wonder who these Sony programmers are and have they thoroughly tested this stuff yet? This is ridiculas! Now there have been solutions like “buy a 64 bit version of Windows”. Don’t be flippin ridiculas! You pay $400 bucks for Vegas it better well have some solutions forthcomming. Save the headaches for the video engineers. This forum gets what? 20 posts a day? Some are easy solutions for amateurs and newbs but these rendering and memory problems should NOT be a headache for ANYONE. The program seems to have MAJOR issues. I think a version 7.5 REDUX is in order, and start over again from about there. Things worked then. I loved Vegas back then. It was the underdog of video software but then Sonic Foundry had it working well. Then Sony poked away at it. And presets? Why would they remove the old rendering presets and options? Stupid. Corporate stupidity. Sorry guys, girls for ranting here, but I am SO disappointed in this latest Vegas product. This forum is filled with people having problems, and not getting solutions because the problems are always slightly different and are unrepeatable on different computers. It’s comming apart at the seams…
    Ayla Xpyakyalo The Xntryk 1

  • Jake Sanders

    November 9, 2009 at 11:34 am

    Aww man, the more forums I read the more I’m starting to think I made a bad decision switching to vegas.

    OK WEll, I’m having the same problem as Scott but a little worse. I cant even selectively render a small part of my timeline now. I am on a mac and using boot camp but I am now thinking that is not the problem. I partitions 40 gigs for the windows side, have 4 gigs of ram and dual processor but I’m getting this “low on memory” crap too! I turned my paging file all the way up (virtual memory) and have restarted, save to new file, etc… still hatin life. anybody find any good ideas yet???? I’m on a deadline and dont think I can even render my project… very nice. Going back to premiere after this one..

    J

  • Paul Goelz

    November 10, 2009 at 7:33 pm

    FWIW, I came to Vegas from Premiere Elements for the very reason you want to go back. On my XP Pro 32 bit 4GB RAM system, Premiere had serious resource issues when editing clips or projects longer than about 20 minutes. I found Vegas quite a bit better but I could still crash it with large projects. When I switched to Vista 64 bit, things got quite a bit better still.

    The issue I think is that although you have 4GB of RAM, a 32 bit OS can only deal with 3.2GB, and splits that 50/50 between the application and the system. It is the same with virtual memory….. I think the most it can hand out to an application is 2GB.

    This gets a little better with a 64 bit OS, since it can deal with more than 4GB RAM, but unless your application is 64 bit, it still is limited to 4GB max.

    At least that is how I understand it.

    Paul

  • Scott Francis

    November 10, 2009 at 7:51 pm

    I don’t buy it, I have had this exact same system for over a year, using Vegas since version 7, then 8 now 9….it has only been since 9 that I have had this issue. I have always used XP pro and 4 gig of ram. This has to be a Vegas issue……unless I am missing something! Thanks for the input though!

  • Paul Goelz

    November 10, 2009 at 8:00 pm

    My experience is limited to Vegas 9 and Premiere Elements 4 and 7. However, I re-read your original post and you say you have issues renedering to MPEG. From what original format? The resource issues I have had were editing 1080i h.264. That seems to stress either system, but Vegas less than Premiere. All of my original footage is 1080i h.264, so I can’t comment on something less stressful like MPEG.

    Paul

  • Dale Spetz

    November 11, 2009 at 1:16 pm

    I cannot speak to 32-bit Vegas9c, but I have had increased render success with Veg9c-64(on very complex projects) by setting the threads to the max (16) and running 4 seperate drives (OS + scratch + source + destination). Might be worth a try for you, too.

  • Bob Peterson

    November 15, 2009 at 10:02 pm

    Why not just revert back to Pro 8? That seems a lot simpler than starting anew with Premiere. I always keep at least one older release available in case time is needed for the vendor to work bugs out of the new version.

Page 1 of 2

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