Selection slow in Vegas 19 (double click event)

nonam3 wrote on 6/1/2022, 1:03 PM

Hello,

I have big project (around 6 tracks with over 3000 events in them, 1h30m length but video is of 30m rest is audio in first track) and in Vegas 19 when I move to some point in time line and double click on event selection appears after 800ms - 1.5s, there is definitely visible lag (it doesn't matter if video is playing or not, same situation). Same lag when playing video and then jumping to other place in timeline.

Same project in Vegas 16 works fine.

Any advice more then welcome.

Spec: Threadripper 3960X, 96GB RAM (3600 MHz, CL14), RTX 3090.

Comments

Alex-Pitel wrote on 6/1/2022, 4:18 PM

Try to update Vegas 19 to latest build. They fixed in latest three builds as I remember.

My portfolio:

My PC:

Windows 10

CPU AMD 3900x

RAM 64gb

GPU1 RTX 3900 (24gb)

GPU2 Intel ARC 380

MB: Gigabyte x570 Aourus pro

Processor: AMD 3900x, RAM 64GB (2x 16gb+ 32gb)

BIOS: reBAR, Above 4G disabled! ((.

Camera Canon r6, R10, Sony A7iii, A77ii, A99, A6300

Preferred footage: h265 (hevc) 422 10 bit, c-Log3

 

jetdv wrote on 6/2/2022, 9:52 AM

@nonam3, I took a project, expanded it to 1.5 hours, and then did a ton of splits in it and got it up to about 1500 events. I did not see any issues using VEGAS Pro 19 build 646.

nonam3 wrote on 6/2/2022, 10:27 AM

I'm on VEGAS Pro 19 build 550 - so maybe it was fixed in latest update. Not urgent for me just wanted to notify / report about this issue.

nonam3 wrote on 6/8/2022, 2:44 PM

Tested on build 636 and issue is still persistent.

I think it is related to the audio track. My setup is audio track (multiple actually, only one un-muted) + video tracks (in current time only one video and one un-muted audio track and multiple muted ones above, video tracks also have sound but are muted).

Testing by opening project and waiting for it to settle (load thumbnails, wave forms etc.) then playing project (have loop playback enabled) and double clicking on tracks once on far left side then on right and so on.

When doing selection without audio tracks (deleted them, but video still have audio track and is muted) it appears to be selecting faster then when audio track is present but it can also be related to project event count as those audio track are cut to BPM (music video).

There is also another issue with audio delay and audio event deletion. When playing project and deleting audio event ahead of current play position audio drops for a second (better then in VP16 as this causes crash there).

Just writing this for posterity. The project that I tested with have 19 files (6 audio m4a and mp3 length varies some have 1h+, 13 video mp4 H264 constant FPS, 854x480 every one, length varies some have 5m - 30m).

Side note here: seams like My posts are mostly complaints, but there is a reason for this ... Vegas is awesome and I like it very much and want for it to be stable as much as possible :D.

NOTE: using Studio NVidia drivers: 512.96

nonam3 wrote on 6/19/2022, 2:02 PM

Hello,

Got some time and prepared comparison video showing Ui responsiveness in Vegas Pro 16 vs 19.

The project contains: 74 tracks, 35704 events, only 1 video and audio track active, 29 audio track grouped and muted.

At the end of the video there is comparison of selection. Vegas 16 is around 5.5 times faster then 19.

Also there is another issue. When rendering project with audio (doesn't happens when there is no audio in the project) Vegas (16 and 19) access microphone.

Is there reason why Vegas accesses microphone during project rendering ?

Update:

Vegas 16 361
Vegas 19 636
Windows 10 Pro. TR3960X, 96GB RAM, source material on SSD.

NOTE: I know this is huge project and "solution" is to just divide it but that's not the problem. This post highlights that there is some performance regression on Ui level that happens between 16 and 19 and that's the main point of this post. This happens also on smaller projects, but it's less noticeable.

nonam3 wrote on 10/26/2023, 10:18 AM

Tested with Vegas 20 and 21 and issue is still there.

I did noticed that performance degradation happens over time and it is like there is single list of all track events that is getting bigger and iteration over that list slow down and the more powerful ST CPU you have the more events You will need to add for this issue to surface.