It’s not uncommon for the program to freeze and disappear from the screen along with the results of the last hour’s work. Of course, it’s important to save regularly, but when I’m engrossed in my work, I often forget to do so. Most serious software programs have an auto-save feature. As far as I understand, VL has this feature (backup files) , but it’s not very user-friendly. Today, my program crashed five times , almost every hour. I spent two hours out of five repeating what I had done before.
It would be great if the program could save to a separate temporary project frequently, at least once per some minutes (as the user specifies), and when loading, it could compare the time of the project’s save with the time of the temporary version and offer a choice of which to use. This is how it’s done in Cubase.
I’ve read in other forum threads that the auto-save feature can significantly reduce performance. But this is easily solved. There should be a “Performance mode” button that not only disables unnecessary features, but it also blocks controls that constantly change their settings on their own, or check box “auto-save” in settings . If users can understand the program, they will know when to press a button like this.
We do not accept crashes at all, please send crash dumps, thanks!
Stability is prio No. 1 for us, and that is why VST Live has no autosave feature. As mentioned elesewhere, we will even reject saving while transport is started. Even though we try our very best to ensure that it can do that, it creates a very complex situation where active multiple engine processes may interfere.
We suggest to use Automatic Version on Save, usually, VST Live project files aren’t large files and you can delete some later.
faster to have occasional crackles, then need to suspend rehearsal /soundcheck for 20secs… But that is controlled by my needs. So I use SAVE during PLAY in time critical moments.
But in the Automatic Version, I still have to save manually, it doesn’t really change anything. I tried this mode the day before yesterday and refused it. I’m constantly changing the version number without it, but I know exactly where and what is saved. This mode allows you to go back to the old versions if you mess up something, but save it. And it does not protect against the option when the program crashes in any way.
The most important thing a person has is time, and so does the user. It turns out that for many reasons, not just because of auto-savе, the preparation time for a project in Cubase and VL with the same functionality is not just different, but many times different.
I’m sure that auto-save is a very simple thing. It’s the same as manual saving, but it’s done at specific intervals, so it’s unclear why you don’t want to make it available to the user and allow them to choose whether to enable it or not.
And it seems to me that it is necessary to separate the mode of performance and editing. A casual movement of the hand of any of the participants in the process can lead to unpleasant consequences. For example, yesterday at rehearsal I accidentally turned on the metronome, it’s good that it was not a live concert. Of course, we can’t foresee all the situations in life, but there are things that definitely do not need to be changed during the performance or it can be solved by settings.
I need to be able to lock the program from accidental changes after setting it up, so that I can be sure that nothing will change before the performance. This is because there are always surprises, even during playback, and with a project that has 15 songs and many layers, I can’t be sure if it’s my own actions or if something has happened in the program.
Maybe you’re right, but I decided to play it safe and made duplicates of projects in Cubase in parallel. I spent a week and a half on the song, which I made in Cubase in 2 hours and which works without surprises, in VL, and not at all because the process itself is so different, but because there are always some events that cannot be tracked and controlled. I’m pretty sure that everything will work at the concert exactly the way I did. Two things that completely prevent me from going there are the delays when starting songs and some hope that something will improve here, because I want to continue working on the light and synchronizing the entire group. But in this situation, it turns out to be easier and faster to do all this with different reliable means than in a single program (great program), but which constantly throws surprises at the most inappropriate moment of time. I think I’m not the only one with such thoughts.
Yes yes yes!!! The people of the country of VL will pray for you for this option. Of course, there is no need for auto-saving during playback, and there is nothing to save at that moment. In fact, it would be better to add a checkbox so that it can be turned on and off (to lock this option), so that you don’t accidentally start playback.
In Cubase, I think the auto-save feature works well with temporary files, and it tells you if there’s a newer version than the one you previously saved when you restart the system.
It’s not about crackles, it is about crashes which are more likely to happen in such complex situations - engine tasks busy while higher level tasks try to access for project information, file access while audio load or even save (record) etc. Repeated, we do everything to prevent such problems, but the likeliness of failure is higher.
But as said we can add auto save (postponed until transport is stopped) and will leave the option to save during playback/record/whatnot as you so wished…
, almost every hour. I spent two hours out of five repeating what I had done before.
