If the box to close media files when Vegas is not the active application is unchecked, then you won't be able to open audio or video clips for edit in another application, like an audio editor or another Vegas instance, unless you shut down the locking Vegas instance 1st. I do quite a bit of audio tweaking in secondary Vegas instances, often with a different Vegas version, so I would never uncheck that option myself. When it works correctly, the 1st Vegas instance automatically reloads the audio clip re-rendered by the secondary instance the moment it regains focus and automatically rebuilds its audio peaks.

If you cannot do that smoothly with the box checked, I would suspect an inconsiderate app that locks all the files it touches and leaves them that way... some browsers and audio editors are known to do that. For instance, older versions of Sound Forge don't have a checkbox option like that and cause trouble if I forget to close them before returning to an open Vegas session. Many browsers stay resident even after I've told them to shut down and might need to be killed off by Task Manager... I avoid playing renders locally with a browser for that reason. Fwiw, I use MPC-BE & MPC-HC to preview video renders and find them both very well behaved.

Hi Howard,

First time I hear of the box to close media files...don't know where it is? But I'm not using media in Vegas to be used in another application, just in Vegas.

Thanks

Michel.

Hi Howard,

First time I hear of the box to close media files...don't know where it is?

 

@michel-plante 

I found that if you have these two boxes checked and leave the screen (minimise to desktop/go to browser), on going back Vegas takes time to rebuild the timeline if Vegas takes too long you may get windows giving a not responding message. In any case I find this slows down Vegas to an extent that I never have these options checked. However you may have a different experience.

I am in agreement with @andyrpsmith. Regardless of whether or not you are using media in another program, flipping out of Vegas Pro (e.g. to another window of any sort) and then back to Vegas Pro can create a long delay in the timeline before becoming useable again - the longer the project on the timeline, the longer the delay in recovery (in my case the timeline can be many hours in length). To get around this, I've long unchecked 'Close media files ..." (highlighted by @Gid) and if I want to use another program (e.g. Sound Forge, RX or SpectraLayers) from an audio event on the timeline, I open a 2nd Vegas Pro instance (doesn't matter if it's the same VP version or an earlier version), copy the audio events to that new timeline and link to the wanted audio editor from that other VP (short) timeline which has 'Close media files ...' checked so that VP can link to the audio editor. The flipping delay is negligible because the timeline is audio only and the timeline short in length.

Hi Howard,

First time I hear of the box to close media files...don't know where it is?

 

@michel-plante 

Hi,

It was checked by default in preferences.

Thank you

Michel

I am in agreement with @andyrpsmith. Regardless of whether or not you are using media in another program, flipping out of Vegas Pro (e.g. to another window of any sort) and then back to Vegas Pro can create a long delay in the timeline before becoming useable again - the longer the project on the timeline, the longer the delay in recovery (in my case the timeline can be many hours in length). To get around this, I've long unchecked 'Close media files ..." (highlighted by @Gid) and if I want to use another program (e.g. Sound Forge, RX or SpectraLayers) from an audio event on the timeline, I open a 2nd Vegas Pro instance (doesn't matter if it's the same VP version or an earlier version), copy the audio events to that new timeline and link to the wanted audio editor from that other VP (short) timeline which has 'Close media files ...' checked so that VP can link to the audio editor. The flipping delay is negligible because the timeline is audio only and the timeline short in length.

Hi Dexcon,

I'm open to every suggestions, will try that and see what happens.

Thanks

Michel

@michel-plante Hi, I too have it unchecked, I don't work in other apps, not very often anyway but I do edit for hrs at a time so I take breaks, clicking away from VP & then when coming back to VP the timeline is still up n running, no delay waiting for it to reload... 👍

I think there was a time a version or two back where VP was crashing, it might have something to do with nesting & this feature, I think after they fixed that it was checked On by default, either way I have it unchecked.

I found that if you have these two boxes checked and leave the screen (minimise to desktop/go to browser), on going back Vegas takes time to rebuild the timeline if Vegas takes too long you may get windows giving a not responding message. In any case I find this slows down Vegas to an extent that I never have these options checked. However you may have a different experience.

Rebuilding the timeline? That might have to do with thumbnail generation. I've don't experience that because I turn them off in Video Preferences. They were a big problem for me when I first opened multicam projects with hundreds of splits from one camera to another... when a 2-hour timeline is 1st displayed in it's entirety by Vegas, the thumbs are too small to see anyway. But the timeline keeps twinkling for minutes while they get recreated. If they do that to you every time you minimize, that's new.

I've also experienced issues with excessive rebuilding of audio waveform-peaks. Only seems to happen to video clips if I leave one version of Vegas to look at the project in an earlier version in the earlier version's project format. Peak files rebuild coming and going by both versions. Even if I deleted the audio tracks in each project in favor of an audio mixdown track. I avoid that issue by enabling an internal setting: Build peaks for visible events only.

Howard, thanks for the info about internal Build Peaks for visible events only, didn't know about it. Is there any downside to enabling it?