Solo behaviour

When I solo a group or pad and unsolo it again, all muted groups/pads also become unmuted? Is it supposed to be like this? It's a little unintuitive I felt.

I'm using the 1st generation controller with software version 2.0.6

Your thoughts?

 

Hello,

if i solo a bassdrum in group 1 and have a bass in group 2 the bass is not muted and if i then solo the bass and unsolo it again only bassdrum is playing in group 1 (solo it before) thats the normal behavior!?

Uwe

but i´ll try it if i am on my music pc

 

sorry, I'm not sure I understand what you said
anyway imagine you have two groups (A and B).
steps:
1. mute A
2. solo B
3. unsolo B
why does A become unmuted too by action 3.?

 

Hello

i think it´s ok unsolo means unsolo (i know in some daw´s group a would stay muted) matter of taste
so muting by solo an other group goes over muted by muting an group?

Uwe

 

I don't get what you meant.. mind explaining?

I'm asking if it's a bug or just the way it's supposed to be I haven't seen any DAWs or mixers which mimic this, which is why I feel it is not intuitive, and hence my question.

 

This is expected behavior. The solo is absolute and affects all sounds regardless if they where muted or not. This is not taken into consideration. When you engage solo it mutes all but what is soloed. Solo off simply unmutes everything.

 

On no planet does causing all muted tracks to suddenly turn on, by soloing and un-soloing a track describe "expected behavior". Yes, soloing will solo a track regardless of mute (often), but un-soloing never un-mutes tracks anywhere else that i have ever seen. One fix would be to allow this to be defeated by a preference. Another would be adding some sort of "unmute-safe" to various tracks, although just saying it describes how abnormal this is. Another fix would be to have a separate solo and mute button like every other program.
On every update i install i check this, expecting to be changed, just because i can't imagine how native instruments would not fix this. Nobody's perfect, so no hard feelings intended, but this should really be fixed. It is basically a workaround for people with only a mouse to achieve "DJ" style drops, but this is not a toy. Honestly, writing this, i have to feel like i missed this being fixed already and simply am complaining about something i must have missed somehow, because it is so incredibly unintuitive for anyone who uses a lot of software or equipment. Please NI fix as soon as possible. Thank you.

 

Unfortunately, it does in Maschine i.e., it's expected behaviour and not a bug. HOWEVER, I hate the way it works too and wish there was at least an option for the previously muted Sounds/Groups to remain muted when unsoloing. And for solo to "respect" any routings e.g., soloing a Group whose main output goes to another Group actually creates silence. To me, this is ridiculous.

 

yeah, sorry to add confusion if anybody thought i meant this was a bug. I just meant that this behavior, although programmed specifically to act that way, is totally unexpected by common practice. So yes, i guess someone could say that this totally unexpected behavior is expected, if the person is talking about behavior not caused by a bug, as opposed to saying it would be behavior expected by people that use lots of software while trying to maintain their sanity. haha I guess soling works a few different ways, for example in pro tools you can solo a muted track (quick way to turn everything off and listen to something that is locked to PT), and also solo a track that goes to a muted bus, cubase is really weird with solos, and traktor seems to be fader and volume dependent as opposed to having solos, i can't remember off-hand, but nobody has this thing where you un-mute a track by soloing and un-soloing another track.

 

bad design imho. it wouldnt take much for NI to "fix" this but i doubt it will happen