The main problem of mute state not saved is now fixed in version 1.1.43 but the problem of solo state is still present and impact also the mute state by a side effect I think :
Open a project
Go to the mixer
Set solo for one or more tracks
Save the project
Close VST Live
-Reopen VST Live and the project
=> the solo state is not set and the mute state triggered by the solo state is not set (if we set manually the mute state to a track, it works)
but in stating that the problem of not saving the mute state of the mixer channels has been solved with version 1.1.43 of the software, were you also referring to the mute state of the output channel?
I say this, because I keep noticing that the mute state of the output channel is not saved at all even with version 1.1.43.
Out channel mute not saved is a different issue. This is deliberately taken out of all saved mute/solo handling, and removing that restriction is not as easy as one might think. So it will take until at least the next version after the one to be released today (if all goes well).
thank you for the clarification, not knowing the internal architecture nor the technology used to implement the software, intuitively it would not seem like something so different from the mute of other channels… but intuition is often wrong!
This issue is supposed to be fixed in version 1.1.50/1.1.51 ? I see in changelog that there is a fix in v1.1.50 who can correspond to this topic but in v1.1.51, the issue is still present.
we have fixed in the “Solo/Mute Engine” in last version. That’s right. VST Live had some issue with it. Save/Restore “Solo/Mute” state for every channel is coming next. It’s not that easy …