Hello,
When i mute part, i can do it by bottom row (normal known behavior), but also the top row.
So it’s confusing.
Being able to mute only on bottom row will make the workflow more consistant.
Or it could also being interesting to be able to mute differently between upper and bottom row.
Like top row track 1-16 mute.
Bottom row group 1-4 mute.
Thanks in advance,
Have a good day,
Rgds,
I think that the current implementation is more consistent - confusion is something which can vanish over time once you get used to it 
The rationals behind the current implementation:
If the lower GP button row would have a different function in the (Parameter) Mute page, it would change its behavior in other pages - e.g. instead of muting groups, you would now mute tracks — this would be very confusing as well
Best Regards, Thorsten.
What’s the point for 1 and 2 to be able to mute by bottom and upper row.
As i understand only the upper row is affected by the page + mute so:
press Mute button: parameter layers can be muted/unmuted with bottom rows because you are in the corresponding Parameter Mute page
depress Mute button: tracks can be muted/unmuted with botton rows, because you are in the corresponding Mute page
change to different page (e.g. Edit page) while Mute function still active for lower GP row: lower GP row is used for Mute, the upper GP row for the selected page
Sound well less confusing don’t you think?
It could be set via an option menu, if you really prefer the confusing i think point of view.
It’s the problem with this device, one did the workflow and that’s it stoned for years, it really miss in the option menu some flexible behavior configuration but it’s already another one of my post!
However the most annoying is that it also select track, but that’s also another one of my post!
I just tested and discovered also the third behavior.
What your saying is even wrong it’s the bottom row which act when you select page + mute and the top row which is muting!
Seriously what the point selecting step while muting or track with the third behavior?
I can’t even go back to standard step edit whitout powering it off, it’s stuck in a weird mode where it show a detailed each step information!
This machine is a total mess, it’s a shame it could have been excellent, but there is so much work to make it just less buggy and more usable to actual standard workflow!
Like the song , to set a 128 step song, you need to set the measure per step + the pattern synchro which is in fact disabled, to work, as only the step by measure should be set, and pattern synchro an eventual override, also pattern sync and enabling should be in the same option page!
And f course no info in the quick manual about this!
I’m sorry if i sometimes rude, but please understand:
My back is hurting like the hell!
I did this device four years ago, and has been in storage till i decided to give a second try!
I’m sorry but the multiple actual buggy/inconsistent workflow is just even with the second try the hell.
I did a review to warn people 4 years ago, and most of them have confirmed.
This device is incredibly capable, but i prefer to use an mpc one, or an arturia beat step pro, or even cubase if i could, it so much more efficient, however i don’t do it because, i need 128-256 step/pattern chaining with mutiple memory slot (here 16, vs 8 for the qy700, but only one patten) select able (jam) which this device is the only one having all in one, and the mpc, is just cubase like, so not a step sequencer!
I still think that if we can manage that people can use it mostly without getting the manual, it would outperform the circklon , which had much more user , so much more feedback, and much more consistent workflow!
In summary, it don’t miss a lot to make it the best of these type!
The best HW sequencer isn’t the most powerful one, but the one you can use straight out of the box, and make patterns as fast as music flow, arturia, akai know it so much!
Of course there is the blm, but cirklon didn’t and is better workflow, and frankly on the bed having already this one and a controller for the synth is well enough space!
Follow up here:
< base_url >/topic/35114-around-dial-function-button/?do=embed&comment=204677&embedComment=204677&embedDo=findComment#comment-204677
Wrong post reply!