Mute, mute but also select

[anonyme-x22]

Hello,

 

i've seen that if you mute and unmute, at unmute part it also select the track.

Is it possible to remove his behavior because it's confusing as for example i edit track 1, if i play with mute and unmute of other track, most chance are that the edit step part will be set to other than Track, and if i do not look carefully, thinking i m on track 1, i will erase/modify the wrong track.

Things that happen to me frequently.

 

Thanks in advance,

Have a good day rgds,

[srmaietta]

This was added in v4.094 I believe, in 2017.  Don’t think removing this would be a simple change. It’s something I’ve gotten used to. 

perhaps could be added as an option?  

[TK.]

Yes, this could be added as an option of it disturbs

Actually I don't remember why it has been changed this way in v4.094 (missing traceability... ;-)

Best Regards, Thorsten.

[anonyme-x22]

Well it actually don't work logically, you have to select one, and the other after are selected, it's more a bug!

The consistent behavior would have been mute+select all the time!

Frankly what's the point, you should select track by track button

Yes at least an option please!

I know we can adapte to many bug or inconsistent workflow, but do you think it's the right way!

It remember my work, how that do not work as expected, open a bug, but for the moment use the weird path!

[TK.]

I noticed that there was already an option to disable "Auto-Select unmuted Track" (10/34), but it was only considered for the 1st GP row in mute page, and not for the 2nd GP row

This is now fixed: http://www.ucapps.de/mios32/midibox_seq_v4_098_pre9.zip

Best Regards, Thorsten.

[anonyme-x22]

Hello,

Many Thanks.

Will try it.

However i think the mute+select behavior is buggy, you should consider mute+select as soon as you mute and no the weird way it does it actually!

Rgds,

 

Edited April 5 by anonyme-x22

[anonyme-x22]

Hello,

Yes it works consistently now with option disabled and my preferred choice.

Many thanks.

 

However as i said and it is mentioned in the option auto select unmuted track.

Why only at unmute time?

Does it is not more consistent when enabled that it select muted/unmuted track?

So the option name would be  auto select track in track mute page?

Moreover if you select mute button then track now it lite the track and the mute button much better behavior by the way, where you can mute top row and select track by bottom row.

So does this option auto select unmuted track in mute page is still relevant for the enabled one?

Whatever you live the option i think it's important in that case for other user to have auto select track in track mute page instead 

Rgds,

 

Ps: Users if you read this please tell us:

Does the

- if you select mute button then track it lite the track and the mute button, where you can mute top row and select track by bottom row.

is sufficient for you?

Does the ability to select and mute track in the mute page (button) make any sense to you?

If yes:

Would it be more consistent to select at mute or unmute time, than just at unmute time?

Thanks for you greatly requested thought.

 

Edited April 5 by anonyme-x22

[TK.]

When I recall it correctly, the user who requested this special handling wanted a quick selection of the EDIT track after unmuting it, that's all.

If such a track selection also makes sense for mute - I don't know and would like to know the exact scenario before adding another option.

Best Regards, Thorsten.

[anonyme-x22]

Hello, 

I understand that's was a need!

Question don't you think that this need is covered with:

Mute+Track button where you exactly have a quick selection of mute/track select!

Furthermore i could have requested wanted a quick selection of the EDIT track after unmuting/muting it?

However yes what's % of people using this use case?

For me the use case requested is making all nonsense!

So consistency to keep everything good would be:

option auto select unmuted track

option auto select muted track

option auto select un/muted track

Again the question is does all those behavior are not covered with mute+track select button!

The goal is to ensure not too much redundancy in a behavior and if really needed that all user could set according their need!

So again i you want to keep this you need:

option auto select unmuted track

option auto select muted track

option auto select un/muted track

to accommodate everyone needs!

Again the % of people using this instead of using mute+track button should be so low that it's better the remove the case!

But i asked people it's time for them to raise their uses case, if not the easiest is always took as default meaning here not auto select at all on this page!

Rgds,

 

 

 

[TK.]

Please take care for your wording - it sounds like you are blaming me!

Some years ago I quickly added a requested feature for a particular user, and now I'm blamed by you that I didn't spend more time to introduce higher flexibility (without knowing exactly for what additional options would be useful to judge if the implementation goes really into right direction).

Your recommendation to use mute+track button: you can do this already by disabling auto-select unmuted track, so you personally should be fine with that, right?

Majority of other MBSEQ users don't have a second GP button row, please consider this when doing proposals.

I would like to close this topic - if somebody can describe a scenario where auto-select track on mute would be useful, I could add this option, but I'm not doing this because somebody thinks that I did a bad job and should do everything totally different just to get it right in his own universe.

Best Regards, Thorsten.

[anonyme-x22]

Hello,

Hold down, If you think i blame you you're totally wrong!

I just want to involve you in the full thinking i got for improving the ui/making actually a consistent, most user happy, behavior to value workflow!

I'm sorry you see it like this, but you know it's like this when you arguing about thing, as i've manufactured a lot of business ui, i was arguing which a lot of different people, most over the developers where always thinking they were blamed because they took a way alone, and this way is arguable as soon as other notified it, and as no use case prior the dev, it ended like this!

This project involved only yourself at the beginning, but now we are about 100 user, so you're no more alone.

You're always been the most one to respect, but i think it's time to open more widely your development to user point of view without thinking, that every request is in order to blame you, and that the criticism which insn't blame is the key point in order to advance in ui improvement or any domain.

If everything is good, you never improve like one of my managers was saying, so he did never put over 95% of goal achievement, even if everything was perfect and you did not get any criticism on them! 

Frankly, i would love that someone just blame me for the two album i put on share, even get a ton of criticism, you should be honored, that people look at your work, instead of having the felling of being blamed!

Ignorance of someone work by people is perhaps the worst thing you can get!

The way i work is easy, i take a picture, see what is wrong, write idea in how to remove/improve the issue.

Now as i said whatever it is for after muting or unmuting, or both, this isn't a worth to value behavior against the track+mute option, however it can't stay like this because it doesn't accommodate all user!

As i said the most easier, flexible with 100% of user accommodation is to add the three option:

option auto select unmuted track

option auto select muted track

option auto select un/muted track

 

Also, take into account that a professional UI designer, when he do something, he want it the best for all, not only for himself.

Frankly i don't use track+mute page as well as i already set the option to disable auto select.

However and again I want it to benefit for most user.

Rgds,

Ps: if you asked me about a use case it's simple:

The tx81z use one channel for voice edit.

The pattern use ch1-8.

So the first thing i need is to mute then select the channel i want to edit

Set the channel of the track to the corresponding voice channel of the tx81z.

Edit the voice on the tx81z.

Unmute the channel on the seq4v+ in order to get the sound.

Another use case:

Let's say i want to edit the channel but before i want to mute all others,

The last muted channel should be selected prior to voice edit.

Another use case:

I want to edit something muted before unmut it.

It valid the option of un/mute with selection.

Another one, i want to mute track 2-8 and select the last track.

Of course i want to mute unmute channel 2 and 8 and select the last muted for edit!

Use case i can find you so much...

Edited April 6 by anonyme-x22