VST Live: Issue - All status of all layers of VST project overwritten to "Solo" (bug)

[SKO]

Dear VST-Live-Team,

I did a cleanup in my VST live project and tried to reduce old / redundant songs (173, 174, 175, 177, 178, 180).

That means I renamed the song into “placeholder” and deleted the included layers and created only a new layer which is empty.

Afterwards I recornized that all layers in the whole project were set to “solo” which is an unexpected system behaviour of VST live.

I did a test and the system behavious is reproducable. I can provide my VST project file in a private chat to the Steinberg Team for analysis.

@musicullum : Please could you help me to analize this issue.

Kind regards

Sam

[SKO]

Original-VST-Project-File provided to Spork + Musicullum on 15.5.2026, 1.39 CET

[ArthurNeeman]

Would be nice to see step by step list of actions you did. Otherwise it’s not clear where you did what. I tried on a simple project with 100 songs and some layers, but cannot get them soloed.

[SKO]

Thank you Arthur for your fast response :-).
I will prepare some detailed screenshots for you.

Kind regards

Sam

[SKO]

Description

1. Open VST-Project File (provided to Musicullum + Spork)
2. Filter for redundant songs “dance-Mix”

Song No. 58 is the current version of song and should not be deleted.
The other songs (173 + 174 + 175 + 177 + 178) are not needed anymore.

3. Go to song 173
4. Delete all layers (cut)

5. Rename song 173 to “placeholder”: Final result:

6. Do the same step for song 174 with final result:

7\. Do the same step for song 175 with final result :

8. Do the same step for song 177 with final resul t:

9. Do the same step for song 178 with final result:

Save VST Project als new project file

After the project is saved with a new filename (“VST library-afte r damage”)

Nearly Songs with its layers in the project have the status “Solo”. Before Save Project this was not the case. Only few exceptions.

Example with a song were all layers are set to SOLO:

Before this steps were proces sed it l ooked like:

I provided to Musicullum and Spork a link an online foldere the the VST project file is stored in 2 versions (before damage / after damage). With the description of the singe steps I hope that this issue is reproducable. I tested it 3 times and it was everytime reproducable by following the steps wh ich are mentioned above.

I hope that this information and example files are helpful.

Many thanks for your offer to analyze from your side Arthur!!!

Kind regards

Sam

[ArthurNeeman]

Thanks.
My analysis shows that this cannot be replicated in a new project. (w/o access to your project). Maybe after frequent updates VL operates with stored structure a bit differently, therefore this bug is reproducible only on project created with older version. I had similar situation last year and VL team did their best to fix it.

BTW you also can tray all those steps on new project to be sure - create 5 songs, 3 layers in each, then do all the steps you wrote and see if it behaves the same. I’m almost sure that this bug won’t occur.

[musicullum]

Did all as you said but no such problems.

• renamed Songs 173…(all those you mentioned) to “Platzhalter 31, 32” etc
• removed all Layers of those Songs and added new (my default Layer…maybe check that new Layer does not have Solo set? Or try to set Layer/Save Default Layer" again before anything else?
• saved as “test”, exit, load, select Song 5 and no solo anywhere (as far as I can tell).
• make sure “Master Solo” is off before saving.

[ArthurNeeman]

Does it mean that Solo states in whole project should not be saved at all?

Doublechecked: everything is saved, but only all tracks have Solo On even if saved with Mute On. But all Layers in all songs have all states saved and restored correctly on project load.