Hi, i have the problem with the trigger parts deleting.
I open my project, select song.
Thanks in advance.
I had the same problem. I solved it by deleting the user data.
Hi @Cucuso, that sounds cool I’ll give that a try. Thanks 
Hi,
Is it possible to get access to the *.vlprj file? Then we can analyse it. Drop the file here or send me a PM.
Thank you,
Michael.
Hi @Spork, thank you for your response, here is my project file.
Fugitives Set AI.vlprj (1.5 MB)
Thanks in advance .
@Cucuso , That seems to have worked for a temporary fix.
Thanks for the tip.
I noticed the same issue well before version 2.2.16. I wanted to report it, but hadn’t found the time yet. Glad you did!
Okay, so at last nights rehearsals it happened again. All trigger parts for a song were gone only this time when i went back to 2.1.36 which is a stable version for us, the parts were still missing 
so i had to set them all again. Very frustrating as we have 2 big gigs coming up. Will try with 2.2.18 and see if its cured, hopefully 
. Will keep you posted.
Hi guys, so tried 2.2.18 and still its deleting trigger parts on random songs. Also when when setting the song action to start next song at the start marker, there seems to be a second or so of no audio output, and so misses the start of the next song.
Hi, so here is the project file with the deleted trigger parts and the missing start of song audio.
Fugitives Set AI.vlprj (1.6 MB)
Hi, @Spork, @musicullum . Thank you for the latest release.
Unfortunately my isues of the trigger parts getting randomly deleted and the audio dropout at the start of a song are still present, hopefully they might be fixed in the next release. Thank you for your continued hard work and support in making Vst Live, as Tina Turner sang “Simply the best” 
That is to be expected if there is heavy load on the Song. There are no seamless transitions from Song to Song in VST Live yet. A Song is like an entire DAW Project (like a Cubase project), and it takes minutes there for a loaded project.
“Preload” will help to “prime” Songs, also after the first time the Song has been startet it might be much better.
What can we do to reproduce?
There is also dmx and video, and a start offset. This means it needs to locate multiple times, and locating is particularly heavy with certain videos. If the video content starts later (after Song Start Offset), you may consider to start the video (and whatever else content) later, if possible, after song start offset, so to give it some air to breathe. MIDI and audio should be close to immediate, depending on the number of tracks.
Finally, for the next version, we improved to omit locate to zero, which is now mandatory when a Song is beeing loaded, but not necessary if there is a Song start offset. Give it a try.
Hi, @musicullum, thanks for the quick response and advice you have given, however we have had and do not have any issues with version 2.1.36 using the same project file. The song starts exactly where we place the start marker with no delay or audio dropout. I always pre load on opening the project. The trigger parts being deleted is a tricky one as its random, but when it happens if i do not save the project at that point, then go back to v 2.1.36, then the triggers appear back in my project. If i save the project when the parts get deleted then go back to 2.1.36 the triggers stay deleted. I dont know if that helps in any way.
Thanks, Johnny
absolutely, will check.
Reg. Song change slow, we found another issue with your project. There are multiple Songs which are not in the setlist, but those are somewhat active when they should not. That also helps, check out the next version.
Ok, did not realise that. 
will check with next version, fingers crossed 
thanks for all your help with this it is much appreciated as always. 
Please tell me what do do to see the problem.
There are a lot of Songs in setlists that are not active. your picture shows a Song selected (7 min…) with just one Part.
Which of the Parts in the active setlist are supposed to have trigger times?
