It was more user error simply due to plugging in a midi controller. Users were accidently sending cc93 from an external controller unknowingly and with no marker in the digitakt ui to signifying things were muted this caused major problems. The only way to unmute tracks when solo was activated was to unsolo and with no indicator what track was soloed even experienced elektron users had issues.
I do wish they had found a different implementation rather than removing it though.
I think the CC was the issue. If you were mucking about setting CCs while the box was running, if you passed over 90 [I think it was] and solo got set without you knowing it, people didnāt know where to look to fix it. Suddenly nothing werked. And folks got all antsy.
I like having a CC for solo. But I get why itās gone.
Much easier to solo one track than mute 5 with the possibility of not triggering properly. It seemed like when you tried to press more than three at once, would get some that wouldnāt mute.
It looks like itās gone [still]. Even if you go up a few posts, I had noted this. Solo used to be there, but it seems like a bunch of people would unknowing/accidentally soloed a track and could figure out why all tracks went silent but one.
Me, I would make the stupid move of selecting a CC value for a knob whole recording, effectively setting p-locks on all the values as I scrolled thru the list. A lot of times passing solo, in turn, muting all the other tracks
Sorry, seems like solo is still gone. You COULD set up a master control somewhere that mutes at tracks with a button. But youād have to make a button for each track you wanted to solo. Enterā¦MAX/MSP
Old thread but I wanted to give this a boost in case anyone from Electron is listening- I really miss solo, it is such a pain with the new Digitakt update to have mute everything to listen to the new sliced tracks etc.
I am sure there must be a way for them to implement this!