Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums VEGAS Pro Can’t render to RAM

  • Can’t render to RAM

    Posted by Nick White on April 14, 2012 at 10:48 am

    Studio 11. Toshiba Satellite, w2GB RAM, 400g HDD.

    I have successfully done this many times recently, but not now :(. At the project settings I have, I was able to do up to a minute, if I closed a lot of stuff that was not needed.

    For a nice smooth playback (laptop) I want to render a segment of the video in RAM. I select / loop a portion, then ask to render to RAM. Different things happen: nothing, the selected/looped a section takes up the whole video, the selected/looped section shrinks to 0. In no case to I get any time passing, and there is obviously no rendering being done.

    I do use a “game accelerator” (Game Booster 3) and that has helped in other areas, but it makes no difference on or off.

    I have made some option changes in Vegas recently, but none seem connected.I will return to default, and see if that helps, but it would be handy to know which, if any, could cause this to happen, or if it’s something external I need to be looking for.

    I have tried restarting Vegas, rebooting.

    Incidentally I have just noticed that the loop point markers (little yellow tringles)O appear to have disappeared altogether.That has not happened before.

    Any help appreciated.

    EDIT:. I defaulted all settings in General Preferences. That made no difference. I am using Panasonic AVCHD 1080p footage, but that is what I have been using all along. I also tried a new project, with no addede tracks etc, just one track of Video with its audio. Still no go.

    Nick

    Nick White replied 14 years, 1 month ago 3 Members · 10 Replies
  • 10 Replies
  • Joseph Tessier

    April 14, 2012 at 1:46 pm

    Nick, I’m assuming your Dynamic RAM max preview is set high enough. Also, have you added more events to your timeline or media to your project that may be using most of your RAM? Since you’re running w/2 GB of RAM your project may not have much to spare.

    J. Paul

    System Specs: I7 3.4 Ghz Quad Core 16GB Ram Win 7 Home Prem x64 VegasPro 11 NVIDIA GeForce GTX 550

  • Steve Rhoden

    April 14, 2012 at 4:21 pm

    Firstly, As Joseph pointed out also, make sure the Dynamic Ram
    Preview in Vegas Preferences is at Max Available.

    Steve Rhoden
    (Cow Leader)
    Film Editor & Compositor.
    Filmex Creative Media.
    1-876-832-4956

  • Nick White

    April 15, 2012 at 3:02 am

    HI. Thanks for the replies.

    I did edit to say that I had a new project with only one stream. However I ran out of time to edit …again…and say that I realised that system RAM was not what made rendering to RAM possible and that I had 450M set aside for that. I did not use max available, as the Help warned that this could cause trouble if it used up TAM for other things. 450M was plenty with my project settings to make a RAM version of a minute or more, until it stopped working.

    In addition to other symptoms, I now see that if I select some time, the loop points sit at each end, but when I try to render to RAM, the _selection_ disappears, but the loop points remain. So results are inconsistent.

    I have between 800-100 MB of RAM available, and sometimes I little more. However this was what I had last time it worked.

    Is there an enable switch for the facility, apart from setting the RAm amount to 0/positive amount?

    Nick

  • Nick White

    April 15, 2012 at 3:03 am

    Sorry. I meant to say I had between 1000 and 1200 MB available.

    Nick

  • Nick White

    April 15, 2012 at 3:20 am

    OK. I know this is bad from a diagnostic POV, but I was getting a bit desperate about a couple of things.

    I uninstalled and reinstalled Vegas Studio and now I have my Help back _and_ I can do RAM renders again.

    Nick

  • Nick White

    April 15, 2012 at 3:28 am

    To add info. After reinstalling, I reloaded the project that I was running when the trouble started: it had a few extra tracks and added audio etc.

    It renders to RAM fine.

    So again, unless there is a switch, other than setting the available RAM to zero, to turn off RAM rendering, then I can only shrug and wait to see if it happens again.

    Nick

  • Nick White

    April 15, 2012 at 11:10 am

    More info. This is weird. IT… happened again. I started a new project to test something entirely unrelated. I used my standard 320*200 25i UFF Project Properties (small footprint when I want to create a RAM render). I dropped in a 1080p AVCHD file to edit. I t4ried to create a RAM render. Nothing.

    SO. With no logic in mind I reset the Project Properties to match the source. 1920 1080p 50fps. I did a RAM render. It worked. But of course it gave me about 3 secinds’ worth with HD p etc.

    I reset the PPs to 320/200 25i UFF…and the RAM render worked fine, giving me a minute of really smooth preview.

    Trouble was I then repeated the process. New project, still at 320/200 25i, with a 50fps 1080p source…. and the render went fine.

    SO ATM I have a workaround, AFAICS, but not a reason.

    Nick

  • Steve Rhoden

    April 15, 2012 at 5:02 pm

    At times in this field Nick, a work around is all you’ve got….lol

    Steve Rhoden
    (Cow Leader)
    Film Editor & Compositor.
    Filmex Creative Media.
    1-876-832-4956

  • Nick White

    April 16, 2012 at 1:45 am

    HAH! Thanks for the encouragement. 🙂

    Bleeding edge stuff all over again, for me. I have been doing midi/ digital audio for years…..since Cakewalk came on a…yes…_a_….floppy disc! I have seen it push that bleeding edge as it progressed in Audio as well as MIDI, but these days Audio romps home on the modern PC. Video still seems to be pushing things and the software is not up with audio for stability IMO.

    Anyway, I posted in case anyone else struck it and maybe someone will remember.

    Nick

  • Nick White

    April 16, 2012 at 9:54 am

    OK. This is now a proper problem for me. It keeps happening, and now I cannot fix it by resetting the project properties.

    I assume that nobody else has eve had this. Does anyone regularly do the RAM thing?

    Nick

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