VP23 cannot use Flicker Control

anthony-chiappette wrote on 9/10/2025, 8:30 PM

I bought the standard upgrade to VP23 and installed it today. I opened a project that I had started in VP22. The project has 5 video tracks, 3 audio tracks and about 13 text / animated text tracks. I have applied flicker control to 3 of the video tracks. I can open the project in VP23, but once it reaches the point in the timeline where the Flicker Control is applied. The video freezes, but the audio plays. From that point the program is unresponsive. I figured I'd just finish the project up in VP22, but no can do. Since I saved the project in VP23, it will no longer open in VP22. I finished doing what I needed to do without running preview and completed the project. So I figured I see if I could render it. That wasn't possible either. The rendering starts and just locks up when it gets to the point where the Flicker Control is applied. It locks down tight. NOTHING can be done. No crash notification, it's just locked frozen. So I had to kill it in task manager, several times before it finally closed.

I tried several times to preview the video in 23, but it always does the same thing. The program locks up and I have to kill it. I reopened the project in 23 and went and removed all of the Flicker Control effects, and the project runs fine in preview mode and I am currently halfway through rendering and it's running smoothly.

Why can't I apply flicker control in VP23? I used it all the time in VP22. While it does cause the preview to lag and stutter, it's still useable. It also added a huge amount of time to rendering, but at least it worked and VP22 never froze up.

Comments

anthony-chiappette wrote on 9/10/2025, 9:53 PM

UPDATE: I spoke too soon! The rendering froze solid at 70%. After I killed VP23, I reopened the project and rendered it again. This time it froze at 63%. I knew I should have waited to install this until the initial bugs were worked out. Now I have to do the project over from scratch in VP22.

Dexcon wrote on 9/10/2025, 10:50 PM

Since I saved the project in VP23, it will no longer open in VP22

Though too late now, it has been recommended many times on the forum over the years to rename a project when moving the project onto a later Vegas Pro version so that the 'old' .veg project file can still be used in the older VP version if need be. And regular renaming of the project (e.g. name-v1, name-v2, name-v3) as the edit progresses is also a good idea just in case the latest .veg file corrupts for some reason - it's then just a matter of going back to the previous .veg file. Though some editing will need to be redone, at least the project doesn't have start all over. Keeping a copy of project .veg files elsewhere (e.g. the cloud such as OneDrive, an external HDD, memory card/stick) is also a good idea just in case of a C drive failure/problem on the computer - and I've had that happen.

In Vegas Pro 22, do you have Advanced Save activated under the Tools menu? If yes, you may still find a recent project save in the folder which has been chosen for advanced saving.

Otherwise, to get your current VP23 project back to VP22 without having to start the project again from scratch, there are 2 processes that may work:

1. Copy (Ctrl-A / Ctrl-C) the project's timeline in VP23 and paste (Ctrl-V) onto a fresh VP22 timeline. FX unique to VP23 won't paste and nor will project or track level FX, but common FX should paste; or

2. Using File/Export in VP23, export an EDL Text File and then use File/Import in VP22 to import the project into VP22. This method will only export/import the project's edited media timeline - but no FX at all.

bitman wrote on 9/11/2025, 4:05 AM

@anthony-chiappette One thing to try on VP23 is to disable the hardware decoder to use: go to preferences, tab File/IO then set hardware decoder to use to "off".

See if that helps, please report back if it helps or not.

anthony-chiappette wrote on 9/11/2025, 7:25 PM

Hi. That doesn't work. I get the same results - audio plays, video frozen, program is locked up.

Eric-Weichhart wrote on 9/11/2025, 7:51 PM

You may have a backup copy from VEGAS 22 you can recover. If you're using Windows, you can type this on Explorer:

%localAppData%\VEGAS Pro\22.0

I would recommend to sort by date modified, but you will find the .veg files Vegas use to recover during a crash

anthony-chiappette wrote on 9/12/2025, 11:59 AM

Hi, Thanks. VP22 didn't crash so much, so there's very few .veg files there. The last is from August 25th for VP22, before I started this project. I'm already about 70% done redoing the project in question in VP22. Thank you. I'm sticking with VP22 for the foreseeable future.

paul-marshall wrote on 9/13/2025, 8:48 AM

I can confirm Flicker Control crashes VP23 here. Working well in VP22.

bitman wrote on 9/13/2025, 12:30 PM

I can confirm it too, Flicker control cashes VP23 (hang)

bitman wrote on 9/13/2025, 1:22 PM

@anthony-chiappette I think I may have a temporary solution for you: I can simulate the VP23 crash with flicker control, but it does not seem to crash if I set my Vegas preferences, tab editing, dynamic RAM preview max to 0.

anthony-chiappette wrote on 9/13/2025, 3:45 PM

I will try that. Thanks. I'm also going to enable DX11, which is off in prefernces.

anthony-chiappette wrote on 9/13/2025, 4:15 PM

THANK YOU! That works like a charm, but what will that do to overall performance?

RogerS wrote on 9/13/2025, 9:02 PM

Dynamic ram preview is a preview buffer so I'd expect somewhat worse playback and much longer render times.

RogerS wrote on 9/13/2025, 9:03 PM

I wouldn't check DX11- elsewhere a developer wrote those checkboxes are for incomplete features.

anthony-chiappette wrote on 9/14/2025, 12:33 AM

I wouldn't check DX11- elsewhere a developer wrote those checkboxes are for incomplete features.

I checked it to test, but then I unchecked it.

anthony-chiappette wrote on 9/14/2025, 12:34 AM

Dynamic ram preview is a preview buffer so I'd expect somewhat worse playback and much longer render times.

So far, with the project I'm working on, I see no difference in the preview. I haven't rendered yet, so i will look out for the render time to see if there's a big difference.

bitman wrote on 9/14/2025, 1:56 AM

@anthony-chiappette Do not enable DX11 yet, it is for future improvements, not yet to be used. It should have been in the internal preferences, but things are what they are sometimes!

bitman wrote on 9/14/2025, 2:02 AM

@anthony-chiappette Glad to help.

The fix to set the Dynamic ram preview to zero is just a workaround until the Vegas team fix the issue
(I have informed them). I have seen rendering time affected by being up to 3x slower, but how much slower all depends on the source, FX and output format.

anthony-chiappette wrote on 9/15/2025, 8:23 PM

Hi. Yes, render was too slow, it was estimating almost 4 hours to render. I cancelled it. I copied all the assets to VP22, and made the necessary adjustments to the animated text events. It rendered in about 1 hour 20 minutes, for a 35 minute video in VP22. Without flicker control, a 35 minute video with many tracks will render in about 22 minutes.I'm not using 23 when I need to have flicker control activated.

craftyMan wrote on 9/29/2025, 7:41 AM

@anthony-chiappette I think I may have a temporary solution for you: I can simulate the VP23 crash with flicker control, but it does not seem to crash if I set my Vegas preferences, tab editing, dynamic RAM preview max to 0.

Thank you very much for sharing this temporary solution. It worked here as well. We hope it can be fixed in a future update.

craftyMan wrote on 9/29/2025, 7:42 AM

@anthony-chiappette Glad to help.

The fix to set the Dynamic ram preview to zero is just a workaround until the Vegas team fix the issue
(I have informed them). I have seen rendering time affected by being up to 3x slower, but how much slower all depends on the source, FX and output format.

I exported a project of about 5 minutes and didn’t notice much difference in render time.