You have some output Fx applied that Vegas is not able to process for real time preview. One example is Sharpen with an AI model applied, but there are others. Forum help with troubleshooting generally starts here, paying particular attention to providing all of the essential information in Section C, plus thorough details about your timeline effects and filters.

https://www.vegascreativesoftware.info/us/forum/important-information-required-to-help-you--110457/

Also, certain Fx can only be a applied at the Media Level, or Event Level, pre-Pan/Crop. Your best bet here is the Help Menu, as some newer effects require entirely different treatment in the project hierarchy than most legacy effects. These differences are not apparent when applying the effects normally, and can easily trip you up.

@Marty74 when you get to that point, press CTRL-S and the project WILL save. Then you need to kill and restart VEGAS. If you notice this happening CTRL-S does still save the project so you can keep from losing anything. As soon as you stop playback and click anywhere on the screen, the whole screen will turn "grey" and you'll have no option but to kill VEGAS. I saw this quite a bit in version 19. Much less in 20 and only once in 21 so far so they are working on resolving these issues.

@Marty74 when you get to that point, press CTRL-S and the project WILL save. Then you need to kill and restart VEGAS. If you notice this happening CTRL-S does still save the project so you can keep from losing anything. As soon as you stop playback and click anywhere on the screen, the whole screen will turn "grey" and you'll have no option but to kill VEGAS. I saw this quite a bit in version 19. Much less in 20 and only once in 21 so far so they are working on resolving these issues.

yes, that's what i do, it was doing this since beginning i used vegas pro, 13 14 15 16 17 18 19 21.. lol, but didn't know why. thanks to everybody.

You have some output Fx applied that Vegas is not able to process for real time preview. One example is Sharpen with an AI model applied, but there are others. Forum help with troubleshooting generally starts here, paying particular attention to providing all of the essential information in Section C, plus thorough details about your timeline effects and filters.

https://www.vegascreativesoftware.info/us/forum/important-information-required-to-help-you--110457/

Also, certain Fx can only be a applied at the Media Level, or Event Level, pre-Pan/Crop. Your best bet here is the Help Menu, as some newer effects require entirely different treatment in the project hierarchy than most legacy effects. These differences are not apparent when applying the effects normally, and can easily trip you up.

thanks for the link, i use chromakey (vegas), smooth contrast, maybe luminosity / contrast, so it's pretty old stuff, nothing new. and color correspondance plugin. i had this issue a lot in the past. but my computer is not that great. i7700 + 1050ti.

thanks for the link

You are welcome. For further troubleshooting support, provide the complete details asked for.

@Marty74, it seems strange that you'd have seen this in so many versions. I really didn't see this until, I think, version 18 and, since then, each subsequent version has gotten better and better at this not happening.

thanks for the link

You are welcome. For further troubleshooting support, provide the complete details asked for.

I will , just that i have internet issue since 5 months and can't stay online , so must prepare all stuff etc ... i thought the link was a "solution" lol, i read it and "ok .. "

i had another crash (the crash above happen when not using the color pick), and support finally replied to me, about this.. interesting ! ...

"Our developers have debugged the error report you provided.  This appears to be an issue using the eyedropper tool. This is a known issue which will be resolved in a future application update.  In the meantime the workaround is to not use this tool until an update resolves the issue.  "

anyway,

find screen catpure and details below.

- not a "big project". not a lot of Fx at all. only plugin "new" i used on this project is BBC Primate studio, the masking one. other plugins used are color correction, luminosity and contrast, simple crop and masking and track movement (it doesnt move)

- gear is i7-7700 + 1050ti Palit KalmX (can't upgrade :( for different reasons ) 32 Gb DDR4.

- Vegas Pro 2021. this issue was there in previous Vegas Pro, but since i upgraded to 21, i have much more issues than before. 19 was pretty stable.. and crash less. today, the project crashed with the same dot point issue 10 times. (thanks for the automatic backup).

- on track effect, it's color correction, and color correspondance (for the piano)
- on event effect, it's on 2 tracks (my french horn / trumpet friend), BBC primate studio.
- and on some other event it's luminosity and contrast.

it's simple musical video, mainly done split screen with black generated media and cropped or with mask to generate split screen corner / line. nothing else. I'm trying to use Nvidia card for vegas, and intel for output. before on 19, i was doing intel on everything, but they told "21 is less buggy and work better" so let's try.. ;).

- source : all of them are in 1920x1080. H264.

- Movie : 23.976 Bluray source.converted to H264/mp4. audio track 48khz (not used or deleted)
- Horn / trumpet : 25 fps (unfortunatly) H264x32 , audio track 48khz (not used)
- my own tracks : 29.97 (piano and synth). 1920x1080 10mb/s. 44.1 khz (muted, not used)
- audio track used : 2 tracks, master out from Cubase in 24 bits 44.1 khz, in Flac. Masterized in Soundforge 17 Pro. result track : Flac 24 bits 44.1

Ouput final video : Magix H264 1920x1080. 10 mb/s, 320kbs AAC. 44.1 Khz.

would prefer to convert 25 and 29.97 to 23.976 (i have TopazLabs VideoAi) but my graphic card is too slow for that.

Output is always ont he frame rate of the movie.

screen capture below :
1/ overall project (17mn long)

2/ general setting

3/ video setting

4/ I / O Setting

5/ visual output screen setting

6/ closer looks to tracks and which one use plugins

7/ capture of plugins used

Driver used : last one from nvidia posted yesterday. intel one updated with windows 11 Pro (insider preview beta). mostly up to date in general

hello, a video is more easier to undertand than explaining it. sometimes, the dots next to the frame number under the preview blink without stopping and nothing is updated anymore. after that, no other solution to close Vegas Pro, which then crash.

 

That looks like encoding bug where part way through a render Vegas stops encoding, but it's not smart enough to know anything is wrong and will stay like that forever. The encode can't be recovered from, but Vegas is still semi alive. You seem to be seeing the timeline version of that. I'd be interested to see the solution

I have this regularly when taking a snapshot, (using the snapshot button on the preview window). So, it is a different (but similar) issue. It has always confused me why this is happening.

Example (V20 latest version):

• Short 4K video (I don't think the file type is relevant)
• Video can be played until it is smoothly running
• Pause
• Take a snapshot
• Try to use frame fwd and rev
• There is a long delay (usually about 10 seconds and the dots mentioned in this thread happen) before the preview window shows the actual video again

I have pretty powerful machine (see sig), all fully up to date latest drivers etc.

It has always confused me, why simply taking a snapshot seems to force this recalculating (or whatever it is doing) ...

In case more info is helpful; This is my method for preparing YouTube thumbnails. I will take video of myself with various emotions/gestures. then use the snapshot to capture the ones I like. Then pull the snapshot into an editor to prepare for thumbnail.

If you guys feel this is not relevant, please mods feel free to move to another thread. :-)

@Phil_P  ... I think that this is a different issue to that raised by the OP. In my experience over the years, there is a delay after clicking on the snapshot icon because Vegas Pro populates the Project Media window with the snapshot image - and that's not an instant process. Once the snapshot appears in the Project Media window, the timeline is freed up and useable again.

If you guys feel this is not relevant, please mods feel free to move to another thread. :-)

@Phil_P Unfortunately mods don't have the ability to do this. We can only move threads, not individual posts. Suggest you start a new thread if you wish to pursue this.

That looks like encoding bug where part way through a render Vegas stops encoding, but it's not smart enough to know anything is wrong and will stay like that forever. The encode can't be recovered from, but Vegas is still semi alive. You seem to be seeing the timeline version of that. I'd be interested to see the solution

yeah me too lol. at least knowing where the issue come from, so it could be fixed... or at least, avoided.

sometimes, session of vegas pro work ok during many Hour, and some times, and it's the same projet, this kind of issue happen, and the weird part.. i close it (ending task), relaunch, and the same issue happens maybe 1 to 2 mn after that etc .. yesterday it did it 10 times, so i gave up, closed vegas and did something else lol... :(

@Marty74 said: "sometimes, session of vegas pro work ok during many Hour, and some times, and it's the same projet, this kind of issue happen, and the weird part.. i close it (ending task), relaunch, and the same issue happens maybe 1 to 2 mn after that etc .. yesterday it did it 10 times, so i gave up, closed vegas and did something else lol... :("

If you want to learn whether all the issues you experience are from the same source, follow look at Windows Reliability History.

View Reliability History