Parts 2 and Part 3 will consistently show up in practically the same state as Part 1.
At this point, however, returning to Part 1, click again on the Solo button of the TRK 1 channel to disable the solo status of the channel and then move to the other parts; you will notice that the channels in Part 2 and Part 3 will appear in the unexpected state:
unfortunately, simply using the small example project that I have already shared within this topic and the new version 1.4.51 of VL, I find that, for a Group channel, just a couple of repeated on/off steps of the Solo button are enough having the mute/solo states of the channels involuntarily changed again in the other parts.
I hope it is possible to fix this bug soon as it is quite annoying during band rehearsals.
For channels such as Song, Song Group and Global Stack, a single on/off switch of the Solo is enough to encounter the bug.
… thank you very much for your patience and your continuous feedback, @Giuseppe_Loffredo. I see the problem now. The last bug-fix will be removed, it’s simply wrong.
But I found the original problem. It’s a combination of the “Global Shared Audio Control” Preference and the Mute/Solo controls of the shared Layers in different parts.
It’s fixed now and will be added to the next Pre-Release.
Please re-try again with the next Pre-Release and let us know if it’s working,
Michael.
I understand that the problem has its complexity, especially in being tested, but unfortunately it seems that the fix does not completely resolve the issue.
Apparently, there is still an anomalous behavior affecting the Mixer channels relating to the Stacks of a Part.
At this point let’s enable the Solo state of a Mixer channel, for example the Song 1 channel in the Part 1, and notice that all the channels of all the parts correctly appear as:
Returning to Part 1 and deactivating the Solo state button, we obtain for Part 2-3-4-5 that the Mixer channel relating to the Stack in the part, i.e. the P-Stack channel, remains erroneously in the Mute state:
I would add that, in testing the fix released for version 1.4.52, I think I discovered another bug linked this time to the use of the Mute button, a bug for which I created the topic:
unfortunately, after some tests I verified that the original problem of this topic does not seem to be solved at all.
After using the Solo button on TRK 1 channel a few times and returning to the unsolo state, I once again, apparently randomly, found the P-Stack 1 channel of Part 4 in the Mute state without any direct action on my part.
Unfortunately this problem is not a small one, since in saving the project I risk finding channels in the Mute state against my will.
. Open project and select MIXER
. “Part 1” is selected
. Select SOLO of the TRK1 channel
. Select “Part 2”, “Part 3”, “Part 4” and “Part 5”
. Select “Part 1” again
. Click SOLO of TRK1 Channel again
. Select “Part 4”
The “P-Stack 1” channel it not muted.
Any tips what I can do to run into problem?
Michael.
The bad news (and believe me, I know something about it) is that the behavior I point out to you is not deterministic at all, but random, even if frequent.
First of all, it is not necessarily P-Stack 1 on Part 4 that goes muted, but this channel (I think because it is linked to the parts)in any of the parts except the one where you used the Solo button on the Group channel (Track 1 in my test description).
However, if you insist on alternating the state of the Solo button on a Group channel (even without moving from the current part) sooner or later you will find the P-Stack 1 channel randomly muted on another part.
I would also like to point out that I observe this behavior both on my two final projects and on the project, obviously, that I passed to you which was created new.
Unfortunately, as I told you before, I know well that these are the worst bugs.
Did you have the opportunity to insist again on trying to reproduce the issue or did you decide to abandon me to my sad fate?
Jokes aside, I hope you can soon reproduce the issue and fix it because, as I wrote to you, I’m always afraid of saving the project with which Part channel involuntarily in the Mute state.
Ah, I just tried the little project I gave you again with version 1.4.56 of VL and I can confirm that the issue is still present.
As always, thank you for the support and all the work you are doing!
… I’ve tried it so often, but I cannot get it reproduced. Do you think it is possible, @Giuseppe_Loffredo , that you create a screen recording about it? Maybe I see a point which helps me to get it reproduced?
below is the video of one of the possible cases that can occur randomly:
In this specific case, at the first use of the Solo button first ON then OFF, the P-Stack 1 channel correctly returned to the Unmute state in all parts.
Trying a second time, however, Part 5 presents the P-Stack 1 channel inexplicably in the Mute state.
… finally, @Giuseppe_Loffredo. We’ve found the cause of the problem. It’s fixed now and added to the next update. Could you please give it another try?
