The song at the first position in the song list has a Tempo Track with a tempo map and a Signature Track with a signature map.
Following 3 songs do not have a Tempo Track or a Signature Track.
After loading a new song which has a Tempo Track with tempo map datas to position 4, the new loaded song’s tempo map contains now the tempo map data from the former song now at position 1. The original tempo map of the loaded song is now overwritten.
Which is defenitly fatal!
Fatally the moved song at position 1 has lost its original Signature datas. It contains now Signature data values which defenitly do not belong the the song. And I don’t know from where they come.
I remember that the song at position 1 has been before at position 4.
It was moved from position 4 to position 1
I edit the overwritten tempo map in song 4 manually back to the correct values.
Now the tempo map in song at position 1 is overwritten and contains now the data which edited manually in song at position 4.
This is really crazy.
It seems there will be a data confusion when moving a song to an other position and setting or loading a new song to the old position. The data of the old song at this position are not replaced by the data of the new loaded song.
This is probably a major bug in initialisation of the song position!
I tried to replicate this, but no success. Maybe I didn’t understood something right. In my test every track is playing at its own tempo, according to tempo and signature changes. Added fourth song from media bay to the project didn’t make any changes to existing three songs, first of which have complex tempo changes and many signatures. Everything is in place and works as expected.
Used 3.0.44. Update you too! vstlive.net
When reporting a bug on pre-release version, always use latest build. Because many of us are using latest pre-release and if someone is trying to help or check the issue and versions differ, all tryings may be of little value.
I also tried to reproduce your problem, but without any success. As @ArthurNeeman already suggested, please make sure you’re using the latest version of VST Live. If the problem persists, could you make your project available for us to check?
I have gained two insights according to Tempo and Signature Tracks in VSTLive.
1st:
With every change in the Tempo Track imediately in folder “tempo” a new file of type “.mprjtempo” will be created. That means that the number of <.mprjtempo> files increase with every editing any item in the Tempo Track without removing old files.
Old files are removed while save a song “Song → Save Song…”
2nd:
But, when you save a “Song → Save Song…” the folder of the saved song does not contain the latest <.mprjtempo> file with the actual modifications, it seems it contains the very first <.mprjtempo> file of the saved song containing old or even wrong Tempo Track datas! Which is definately wrong, it must have the latest <.mprjtempo> of the song! Otherwise the saved song has unvalid Tempo Track datas!
This causes definitely problems when you import this song to a new project.
And it seems, that the same problem happens with the Signatue Track.
I’ve got many problems with this circumstances.
This needs to be checked from the VSTLive developer team very urgently.
If you Save Song from Song menu and confirm that it saves also assets and choose the folder, then it will create tempo folder under specified folder and will put there signle file that contains all tempochanges. When you import that song in your project, it will copy its .mprjtempo file into current project’s tempo folder.
While you edit tempo track, it creates new .mprjtempo on every change. It’s unusual, but acceptable as long as it doesn’t consume the last 25 GB of your HDD.
You can always make an Archive of whole project, backup old folder (always do backups!), remove all files and move your created clean archive to the old place. It’s healthy to do that from time to time. Also Lyrics track (its files) will be concatenated into one file.
Yes, that needs to be done for undo, save etc. Should be no big deal unless you have very many tempo changes.
2nd: see Arthurs comments. Save Archive is your friend. And for Save Song, you need to tick the option to include assets. That is true for all event type media (midi, tempo, time signature, dmx, lyrics, chords…hope I forgot none) and media type media as well (audio and video).
The data problem I discribed is obviously solved.
Setting the “Locked” status at Tempo Track and/or Signature Track to ON causing the data problems I discribed.
Leaving it OFF (default) all workes fine without any data problems.
My general idea about the Locked Status was, of course, to protect the datas. Therefore I set it always to ON.
Thank you for your replay. I don’t know. I only can say that it definitiv happend, more than once. I have projects for 2 separately bands. And on both projects the data confusion happened.
Probably I send the project without the wav tracks to you and you try it out by yourself.
And I have another suggestion:
If VSTLive saves the Tempo- and Signature-Map data in an readable ASCII format, for example .XML, with a recognizable relation to the song name instead of a binary file with cryptic name, it would be much easier to create and edit those data.
I‘m afraid, this would mean opening hell‘s gates wide open. To allow mission critical data to be edited outside the app - whoa, chances are huge for things to go terribly wrong - midshow.
Hallo Kai,
I agree to you for system relevant datas.
But a Tempo-Map or a Signature-Map just belongs to a user created song and has nothing to do with the system.
Inside VL there is a piece of program code (e.g. C++ objects) which reads the external file, decides weather the data format is valid or not and then sets the data to the corresponding song. And an importer class can be programmed to read and handele binary datas or an .xml file with ASCII datas. The result is the same.
If it is properly programmed it never harms the system.
I heartily disagree. What you suggest implies the impossible: You create a tempo map outside VST Live. You, then, expect the app to import that map, automatically correcting all those things that can already go wrong by simply saving a „simple“ (haha) ASCII file?
And musically speaking: How shoud VST Live relate that tempo map to your song if it has changed? Always load your tempo map? Delete it automatically (burn after use .. )?
meanwhile I - personally - would welcome improovement on TPO track.
Telling example: if making a TPO ramp in cubase, the tiny increment info gets lots after importing into VL. Also the select all and drag up/down left/right is impossible however very usefull in different scenarios… (usually still more easy to export a dummy MIDI track from C15 and re-import the tempo into VL with that dummy MIDI file)
To allow mission critical data to be edited outside the app - whoa, chances are huge for things to go terribly wrong - midshow. 
What you suggest implies the impossible: You create a tempo map outside VST Live. You, then, expect the app to import that map, automatically correcting all those things that can already go wrong by simply saving a „simple“ (haha) ASCII file?