Yeah sure.
Running everything from an SSD scratch drive, internal M.2.
First gen threadripper, 128gb ram, 1080ti. Nothing crazy, but plenty fast for this kind of work

Hi @Timcarrdp, are the <.sfk> waveform files being saved (or lost? If they are missing, Vegas has to rebuild the audio waveforms each time the project is reopened, which can take a lot of time if the audio events are numerous and/or long.

Hi @rraud! The .sfk waveform files are intact and there. Also, from my experience any rebuilding is done once the project is open, and in the background. This litrally hangs, windows complains vegas has crashed, but if you leave it long enough it sometimes comes back. I say sometimes, because as I try to open this save (Been trying all night) it keeps crashing on me.

One thing you could try just to see if it speeds it up is do a SAVE WITH MEDIA to a unique file. That may take a while, but then load and see if it is any faster. Do you only have one drive? I find multiple drives (one for OS and programs and at least one other for files) speeds things up but I am primarily talking spinning drives. I don't know how much difference that makes with SSD. And the other thing, if your SSD is reaching capacity, from what I read online that slows them down tremendously.

Ive got 12 drives and ive currently got one just dedicated to this project (thats one of the SSDs), so no its not the same as the windows install or the vegas install or anything. But also, they are all SSDs.

Ill give the save with media ago and report back.

Its all interesting to me, I've been cutting projects this way for years - ive never had this issue before.

EDIT: Save with media does not work, same issue still stands.

Does anyone know where any other log files are stored other than the ones in the appdata folder? Is there a way of turning on a log (maybe in the internal settings?) to log the progress of a project loading so I can see whats going on and make some guesses?
I mean for all I know, it could be a rouge plugin or some other random thing that is causing the hiccup

@Timcarrdp 

Perhaps, if you display the Task Manager and Resource Monitor you can get a hint about what the system is doing and where it's doing it in the 17 minutes it takes to handle the file.

Then look at the Windows Reliability History to see if the system is leaving any tracks.

Thanks for the suggestion, but nothing out of the ordinary in resource monitor or process monitor, that was one of the first things I tried.

Never thought to look at the reliability history. But I just did, nothing there either. Just the events when I had to force close it through taskman.
 

@Timcarrdp The location of the Vegas temp folder may be the source of trouble. If you have Vegas projects on their own media, you could try moving the temp folder to faster media too. It's location is controlled in General Preferences at the bottom of the menu. It's normally in C:\Users\<LOGIN NAME>\AppData\Local\VEGAS Pro\21.0\ which is on C:.

Another thing to check out are your major settings. If you do a settings export, it's a text file that you can examine with Notepad... there may be some funky paths stored there from other Vegas installs if you ever saved and imported them. I would suggest rather than editing/importing the exported file, try doing a Vegas reset and recreate all the settings changes manually. Reset Vegas manually by holding down ctrl-shift keys before and during Vegas startup. After it does the reset, also attend to any Vegas windows layouts you had and recreate them manually too. Pay particular attention to the location of Vegas window layouts... they are not supposed to be shared by different Vegas versions.

If your troubles didn't begin till build 208, it might have to do with some changes to Vegas decoding. Try checking the box for legacy-avc in I/O Preferences and see if that helps.

We are aware of long load times for projects with some specific types of media. We are working on a solution.

@Timcarrdp The location of the Vegas temp folder may be the source of trouble. If you have Vegas projects on their own media, you could try moving the temp folder to faster media too. It's location is controlled in General Preferences at the bottom of the menu. It's normally in C:\Users\<LOGIN NAME>\AppData\Local\VEGAS Pro\21.0\ which is on C:.

Another thing to check out are your major settings. If you do a settings export, it's a text file that you can examine with Notepad... there may be some funky paths stored there from other Vegas installs if you ever saved and imported them. I would suggest rather than editing/importing the exported file, try doing a Vegas reset and recreate all the settings changes manually. Reset Vegas manually by holding down ctrl-shift keys before and during Vegas startup. After it does the reset, also attend to any Vegas windows layouts you had and recreate them manually too. Pay particular attention to the location of Vegas window layouts... they are not supposed to be shared by different Vegas versions.

If your troubles didn't begin till build 208, it might have to do with some changes to Vegas decoding. Try checking the box for legacy-avc in I/O Preferences and see if that helps.

Thanks for this suggestion. I had already gone down that road before posting. I didnt check the avc codec, but doing so now doesnt make any difference unfortunately. I cant say if it was 208 that it appeared with, as ive never had this issue. But recreating the issue in VP20 doesnt seem to be hard, so id assume its been there for a while.
 

We are aware of long load times for projects with some specific types of media. We are working on a solution.

Thanks for this, hopefully that can be a hot fix soon? In the mean time, is there any work around I can do? I remember a few years ago having this issue with MOV files, any large project (feature films etc) had issues. But, that was worked out to be the 32bit Quicktime codec, and once that was swapped it was fixed. But the workaround for that was to change the container for MP4 or something else.
Hopefully theres a workaround for this here?

Ill post a video of the issue in a few minutes

Reencode all the media to say ProRes and swap video files in VEGAS?

Reencode all the media to say ProRes and swap video files in VEGAS?

Ive offlined all my clips so its just audio. Same issue.

Ok so interestingly, if I cut the project in half, it seems to resume full speed. Thats a massive pain to do however, and I really want them to all be in the same timeline without nesting etc etc. Im sitting through a playthrough with the director next week, and want to be able to tweak whatever without going into multiple projects.

I should note, it doesnt matter what half is removed. So that rules out a singular/group of rouge clip or codecs causing issues.

 

Here's a clip of the issue(s).
I recorded the opening of the project 3 times and the first 2 came out to 14 minutes, 17 minutes and the last one I included in the clip at close to 7 minutes.

Once the project is open, the other issue I have (apart from it immediately doing an autosave and taking ages) is where some of the audio tracks have really long times to do anything to the event. But then, throw that same event on a new track and it goes back to full speed. Put it on the old track, and back to slow. it may not look to slow here, but when your talking 4 or 5 operations, that really adds up to minutes when something that usually takes seconds.

So for possible causes of this issue, if it's not media is it audio Fx applied to certain tracks or events?

Just removed FX and cleared project history, same issue. Unless it somehow persists in the project once removed from an event.

@Timcarrdp said: "Audio files are all broadcast waves that ive had no issue using in the past."

SWAG

As a diagnostic test, would you consider converting the Broadcast Wave Format files to 16 bit or 24 bit PCM and replacing them in your Vegas project.

/SWAG

Saw your post last night and tried that today. Seems to be the same issue unfortunatly. Although, I did this by relinking the media in the project. So I dont know if the project has some old evidence left in it that causes this bug, but I did the usual steps of cleaning the media bin etc etc.

If audio is causing the trouble, it might be your audio hardware and/or drivers at fault. I use usb audio interfaces myself and audio rendering is lightning fast. I stay away from the built-in Realtek stuff. Only thing that ever slows it down is when audio waveform graphics need to be regenerated. Can you tell if rebuilding those peaks is what's happening during the load delay? If it's not that, I be looking at the audio hardware and drivers.

Hi,

@Timcarrdp 

Did you manage to resolve this issue? or some alternative way? In my case, I have recently consulted this forum to become aware of the problems faced by users in this current version. I was a user until version 17 of VMS which was discontinued! So I waited a while and then in 2 years I ended up migrating to Magix MS 2023 to avoid any incompatibility of new ventures with Windows 10/11 hardware and also not needing so many resources from Vegas Pro etc... But my needs are changing w/ regarding the necessary resources and I am evaluating VPX (since in this time I have adapted to the functionalities of these Magix concepts) or returning to Vegas pro (basic). But this question of yours has a lot to do with my current project. (In 2023, when I downloaded the test version of Vegas Pro 21, unfortunately, I did not evaluate these issues that you are facing).

(Have you considered how the current Windows pagination is configured? Maybe this version 21 may have or tried to follow a new path different from the previous ones? Many developers started to change considerably as the libraries involved also changed, such as QT, etc...)

Thanks!

If audio is causing the trouble, it might be your audio hardware and/or drivers at fault. I use usb audio interfaces myself and audio rendering is lightning fast. I stay away from the built-in Realtek stuff. Only thing that ever slows it down is when audio waveform graphics need to be regenerated. Can you tell if rebuilding those peaks is what's happening during the load delay? If it's not that, I be looking at the audio hardware and drivers.

Audio drivers and hardware is tested fine. Tested 3 different audio interfaces, and even the built in ASIO driver, but thanks for the suggestion. As stated before, the waveforms are also not the issue.

Hi,

@Timcarrdp 

Did you manage to resolve this issue? or some alternative way? In my case, I have recently consulted this forum to become aware of the problems faced by users in this current version. I was a user until version 17 of VMS which was discontinued! So I waited a while and then in 2 years I ended up migrating to Magix MS 2023 to avoid any incompatibility of new ventures with Windows 10/11 hardware and also not needing so many resources from Vegas Pro etc... But my needs are changing w/ regarding the necessary resources and I am evaluating VPX (since in this time I have adapted to the functionalities of these Magix concepts) or returning to Vegas pro (basic). But this question of yours has a lot to do with my current project. (In 2023, when I downloaded the test version of Vegas Pro 21, unfortunately, I did not evaluate these issues that you are facing).

(Have you considered how the current Windows pagination is configured? Maybe this version 21 may have or tried to follow a new path different from the previous ones? Many developers started to change considerably as the libraries involved also changed, such as QT, etc...)

Thanks!

No nothing yet. Unfortunately the only post from the team themselves seems to just suggest they already know its an issue, but no work arounds or any further help. Nothing in relation to the slowdown in the software. As much as I love and defend Vegas to everyone I work with (I usually have to defend it to everyone, especially since the removed AAF export and the XML export is so so broken and needs an overhaul... I can't professionally share with others. Timecode is still an issue, theres nothing to do with timecode sync.

But now this issue popped up, I'm kinda over defending it. The actual support team don't seem to be helping either.

Unfortunately the only thing this thread has taught me, is that I will have to move to new software since Vegas is clearly not up to the task of a professional workflow.

I have a client coming in tomorrow to sit through this edit and work out some kinks in the soundtrack. Im not sure I can edit, watch it crash, and then ask them to wait 15 minutes while it loads up again, only to be dog slow while trying to work.

Ive been using Resolve for coloring since version 9. It's edit features seem to have come a long way. Media Composer (and the free version First) seems to have also come a long way, and modernized itself a lot since I last used it (I bought version 5-6 or something in 2011 after I was outgrowing Movie Studio Platinum. I hated the PC version so much, that I gave Vegas Pro a go and stuck with it ever since).
I would give these ago before learning Vegas @Betovalle, since the support seems to be lacking and Vegas looks to have now focused on the "prosumer" market with no real evidence of the professional market, since its missing essential professional features as I described above.
In Vegas' defense, I do think its one of the fastest cutters Ive ever used. I do like the way the timeline and cutting works. Its a real shame its kind of lost its professional market, but I understand the money is in the prosumer market and people gotta eat.

Sorry about that rant but hope that answers your question.