Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums VEGAS Pro Preview Window Freeze

  • George Dean

    April 24, 2019 at 9:05 pm

    Renato,

    I would make some small changes in your Preferences, which you probably have tried, but perhaps humor me….

    Preferences > Preview device tab > (Display adapter) uncheck ‘Wait for vertical sync’

    Preferences > Video tab > Dynamic RAM preview max, change it from ‘0’ to ‘200’

    Preferences > Video tab > Maximum number of rendering threads from ‘2’ to ’12’

    Then restart Vegas Pro and start a fresh project. Add some media to start a fresh project, a little bit at a time. Play the preview as you go along, if things work fine at first, keep adding and checking the play back until you either have a good size project compared to the problem project, or you run against problems, then report back here how that test proceeded.

    As for the proxy. Vegas Pro can build a 720p proxy of your 1080, or 2K, or UHD, or 4K media. As a default, Vegas pro will build proxies when you add 4K/UHD media to the Project Media bin. Your media is 1080p, so you need to manually build proxies. Right click on a source media video in the Project Media bin, and from the menu select ‘Create video proxy”. Depending on how large the video will depend on how long Vegas takes to build the proxy. There is a progress bar displayed at the bottom left of the timeline. The proxy is written to the same folder as your source media, but you will not see it in the Project Media bin.

    Add the source media from your Project Media bin to the timeline. Vegas Pro will automatically use the smaller resolution 720p proxy for viewing if your Preview Quality is set for ‘Draft’ or ‘Preview’. If you set the Preview Quality to ‘Good’ or ‘Best’, Vegas will automatically run the preview from your original 1080p source. When you render your project, Vegas Pro will automatically use the 1080p HD source media.

    So using Vegas Pro Proxy feature, once you have selected to build the proxies (either one at a time or select them all and proxies will be built for all the video you selected) is automatic after that and you do not have to switch anything out before rendering.

    About Snapshots: If you feel the amount of snapshots you use is causing the problem, then the test project (above) I suggested should reflex that, once you get to a certain point if you see the same issues you are having with your current project. I would not think a bunch of snapshots (providing they are about the sme resolution as your project, would be the cause.

    Another thing you can try, is copy everything in your project along with the .veg file to a different folder on your hard drive. Rename the original folder, as an example the folder name is ‘Snapshot Project’ to ‘X-Snapshot project’. Then load the veg fie form the new folder and if Vegas Pro prompts for the project source files, point it to the new folder. Sometimes garbage gets somehow associated with a project causing strange actions and simply changing the location will help. It is a long shot, but others have reported success doing this.

    Best Regards……George

  • Renato Gyuris

    April 26, 2019 at 2:30 pm

    I did these steps
    Preferences > Preview device tab > (Display adapter) uncheck ‘Wait for vertical sync’

    Preferences > Video tab > Dynamic RAM preview max, change it from ‘0’ to ‘200’

    Preferences > Video tab > Maximum number of rendering threads from ‘2’ to ’12’

    Vegas crashes too and now crashes during rendering.

    I drag 6 1080p videos to Vegas. The preview is smooth. With 7 1080p video, it’s a little bit laggy.

  • George Dean

    April 26, 2019 at 2:36 pm

    Renato @ “I drag 6 1080p videos to Vegas. The preview is smooth. With 7 1080p video, it’s a little bit laggy.

    Did you create proxies for all these videos, and are you preview with quality set at ‘Preview’ or ‘Draft’? If, so they should preview smoother. Of course how smooth depends on any FX’s or filters you may be applying.

    Best Regards……George

  • Renato Gyuris

    April 30, 2019 at 6:29 am

    I dragged it simply to timeline underneath each other and played all at the same time. I didn’t create proxies. I set all videos transparency to 50% so I see all videos. The preview quality was Good (Half)
    I thought it’s a crash test.

  • Renato Gyuris

    April 30, 2019 at 6:32 am

    I try video editing with proxies maybe Vegas will be stable.

  • Renato Gyuris

    May 2, 2019 at 11:13 am

    I recognized thumbnails on timeline reload every time when I take a snapshot. Not just timeline thumbnails but project media thumbnails reload too. I don’t understand why reload these thumbnails every time I take a snapshot.
    I decided to turn off thumbnails on the timeline. For two day Vegas does not crash.

    When it was turned on (Head, Center, Tail) it feels like after many snapshots vegas memory will be full and vegas can’t work properly.
    I feel after restarting PC, vegas starts with empty memory and works well. After many snapshots, the memory is full again and Vegas has problems again and only restarting PC helps for a short time.

  • George Dean

    May 2, 2019 at 1:51 pm

    Hi Renato,

    This is strange indeed. I cannot duplicate this in Vegas Pro 16. Do the thumbnails reload in a fresh new project from the once time, or does it take many snapshots before the thumbnails start to reload/repaint? I only made about 25 snapshots, if it takes more than that before you see this behavior than I will test with more, otherwise my systems is not behaving the same as yours. Also, I just updated Vegas Pro 16 to the latest build 424. Is this behavior in VP15 and/or VP16?

    This behavior sounds like perhaps the cached application data is causing a problem, did you do a full reset as I asked in a previous reply?
    – – – – – – – – – – –
    I would start with the simplest fix first with a full program reset, hold down ‘Ctrl+Shift’ keys, while you double left click on the Vegas Pro desktop shortcut. A small window will appear. Check the box ‘Delete all cached application data’, then left click on ‘Yes’. This will reset Vegas Pro to it’s original installation settings and delete the pesky cached application data that will sometimes make Vegas do strange things.
    – – – – – – – – – – –
    You can load the Windows Task Manager and monitor the CPU and RAM usage. It may be helpful for you to monitor this as you proceed with another test.

    Best Regards……George

  • Renato Gyuris

    May 3, 2019 at 6:45 am

    Thumbnails reload only when I take snapshots with Vegasaur. I report the problem to Vegasaur.
    I didn’t reset de cache. The reason why I didn’t reset because on my home pc the problem is the same. I don’t think both computers have the same cash problem.
    Since I’ve turned off thumbnails on timeline vegas does not crash.

  • Renato Gyuris

    May 7, 2019 at 7:28 am

    My colleague has exactly the same problem. He doesn’t use Vegasaur.
    I think thumbnails on the timeline and in the project media window have something to do with the crash.
    When the thumbnails on video events is “Head, center, Tail” and I cut the clip Vegas generate new tail and center thumbnails.
    Maybe Vegas doesn’t like when I working while Vegas generate the thumbnails.

  • George Dean

    May 7, 2019 at 2:10 pm

    Renato, perhaps you can provide a step-by-step of what you do and when you get the freeze.

    Regardless of VP16, VP15, or VP13, when I do a snapshot it is pretty much instant that it writes and saves the file and the thumbnail appears in the Project Media bin. That’s the same whether I have no timeline thumbnails, head only, head, center, tail, or All showing.

    However, years a ago when I was on a duo-quad processors, I would get a few seconds delay in the time it took to write and save a snapshot and during that time Vegas would be waiting for that process to complete before it would go on. That was a delay not a freeze. Once the thumbnail for the snapshot appear Vegas would continue. That might also be the same on a large or complex project on some systems.

    Best Regards……George

Page 2 of 3

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