Markers vs parts

VST Live
1

Hello

I’m experiencing a consistent visual freeze/hitch in VST Live when switching Parts in a song.

**Project setup:**

- 14 audio tracks (backing tracks/stems, all routed to Main Out)

- 3 shared layers accross the whole song

- Lyrics track

- Notes track (used for beat references)

- 1 MIDI channel for DMX control (via Freestyler)

- 1 Video Track

Everything plays back smoothly during continuous playback in a single Part.

However, every time the project switches to a new Part (manually or via timeline), the playhead (cursor) freezes for 1–3 seconds. During this freeze:

- The playhead stops moving

- Video playback stutters/freezes

- Lyrics and Notes tracks stop updating/scrolling

- Audio continues perfectly (no crackles, dropouts, or timing issues)

The issue gets worse/more noticeable as I add more Parts to the song.

What I’ve already tried (no improvement):

- Increasing ASIO buffer size (up to high values)

- Toggling video multithreading on/off (Preferences > Video)

- Running File > Preload (or Preload Parts)

- Lowering video resolution/quality (smaller file size, lower FPS re-encode)

- Testing in both VST Live 3.0 (latest patch as of today) and VST Live 2.0 (latest patch)

- Simplified tests with fewer elements

Practical work around: Avoiding Parts altogether works fine (everything smooth), but I’d really like a way to visually mark song sections in the track view without creating actual Parts—for quick reference during editing/rehearsal (similar to Cubase Markers or Cycle Markers).

Is this a known issue with larger part counts or complex projects? Any other suggestions for preloading/optimizing, or a feature request for non-Part markers/locators?

Thanks for any insights or dev attention!

Valentin

2

I’m currently using VST Live 2 (latest version). I work with long setlists, several audio tracks routed to a single output. Each song usually has more than 10 parts, and each part contains two audio stacks: one for bass amp simulation and one for guitar amp simulation (ToneX), plus two global stacks for vocals.

In addition, I’m using six independent audio outputs (click, bass, guitar, vocal 1, vocal 2, stems), with several VSTs inserted, I don’t have any issues as long as I first preload the parts and then manually step through each part using the navigation arrow keys.

I’m not using layers or VST instruments.

I’m using a Mac m1 Max

1 Like
3

So there is not a workaround for identifying all sections of a song other than PARTS?

4

Parts are reflected in Song track too. Did u try SongTrack already for visual Guide?

1 Like
5

Yes I did. Parts are what Im trying to avoid, because transitions between parts, stops for a couple of seconds the the play head (stutter). The more parts, the worst it gets.

Sorry, I know its a long read, but the original post have all the details.

Let me know if you have any advise.

Thanks!!

6

Can you please point to the thread where you detail that problem.

Also try:
If you dont use parts functionality here is what I would suggest indeed:

  1. Update VL to most recent
    2 try PARTS wo loading Song LAYERS/STACKS
    3 songtrack is there
    4 Now try adding just Global Stack / Layer (if needed), but still dont use SongLayer/SongStack

Better?

1 Like
7

@vsosa1314 For our information - what spec is your PC, which OS and what is your audio device?

1 Like
8

Hello,

Here are the specs. (Running VSTL 3.018)

DELL

WINDOWS 11 Home vs 26200.7623

Ryzen 9 (6900HX series

16 Gb RAM

1 TERA ssd

FOCUSRITE 4i4

9

Hello, this is the first post on the thread..

Thanks for any advise.

10

Oh,ok!

Could you try my steps Markers vs parts - #6 by fkalmus

1 Like
11

I’d have a look at task manager when the problem occurs. Also maybe change the app cpu priority.

1 Like
12

Yes it works with Global Layers.

I´ll try doing it on the real project to see if there is an improvement.

BRB

1 Like
13

Hello, Got the culprit of the problem

1- Started a fresh project

2- Imported all the Audio. (14 tracks)

3- Imported MIDI Tracks.

4- Imported Video (1 Track)

5- Loaded the “Song” Layers (3 layers)

At this point, I saved and tested the project with no PARTS created, and it Worked Flawlessly

6- Created 14 PARTS

Tested again and Worked Flawlessly (Layers only on One Part)

7- Shared the Layers in all the other PARTS

Tested again and Worked Flawlessly (Layers on ALL Parts)

8- Copy the TEMPO track (created with CUBASE since the song was not recorded to a click)

Tested again and BOOM, the problem started immediately

Thing is, the TEMPO TRACK is indispensable for the project.

I don´t think there is a workaround this one guys.

Let me know your thoughts

Valentin

2 Likes
14

wow @vsosa1314 ! you’re awesome finding the culprit for your previous problem (I was very interested because happened me once but couldn’t narrow it)

With your receipe more probably @musicullum and @Spork will be able to inspect this !

1 Like
15

… is it possible to get access to this full project to analyse it?

Thank you for all your help!
Michael.

2 Likes
17

Just sended a direct message.

Thanks

18

Hello @Spork Let me know if the files are correct, or if you need any other info.

Best regards

Val