Workflow consistency error between controller and GUI

New project in GUI (we aren't using the controller here)
Go to Mix View.
Click down and AUX in mix view.
Go to AUX 1 bus.
Observe you cannot change the order (pre/post) until you select a value in the AUX destination such as Ext.1.

Now check Maschine Studio controller, if you set the value in the AUX destination to None you can still change the order to Pre/Post.

So.. either the GUI needs to display "Order" at all times or the Maschine Controller should not display the knob as available until an output value is selected. One or the other...

(Edited for clarity)

 

Oh my word. I'm not sure I can use Maschine any more until this "workflow consistency error" is fixed.

If this is the case, though, it does seem inconsistent and should be reported and ideally fixed, but do we really always need the bombast and the hyperbole when discussing these (relatively minor) issues? Just a thought...
However, I have no problem setting the "order" parameter at any time, even when the destination is set to "none"... Tried it on Sound and Group level.

 

I'm going through everything I see, I try not to judge what is major or minor, or whether somebody classes fixing it as irrelevant to them.. I tend to run away from that, just is it a bug or not.

 

Maybe not judging, but certainly making EVERY LITTLE THING INTO A MASSIVE DEAL , intentionally or not.

As for this, I can't reproduce. The GUI works as expected here.

 

I'm just point blank reporting it with no comment, you would know if I find it a massive deal or not, I would start throwing my toys out of the pram. Yes I can repro or no I can't is quite sufficient most of the time.

> As for this, I can't reproduce. The GUI works as expected here.

Just to be clear what controller and OS?

I'm using Maschine Studio controller and windows.

Thanks.

 

Windows 8.1 and Mk2 controller, though have not checked this with a controller yet, just the GUI part ("Observe you cannot change the order (pre/post) until you select a value in the AUX desination such as Ext.1."), which works as expected .

 

The issue is with the inconsistency between the GUI and the controller. What behaviour is right or wrong I make no judgement on. Either way could make sense to me although I have my own preference... Cheers...

 

But you stated that you "cannot change the order (pre/post) until you select a value in the AUX desination such as Ext.1.", which is not the case here and so there is no inconsistency between controller and GUI.
(Just quickly tried with a Mk1 and it works the same, as far as I can see. The order (pre/post) can be changed regardless of whether the destination is set.)

 

I think I royaly screwed up, I shall change #1. In the GUI you need to go to mix view then click on AUX.

 

Ah, I see what you mean now. I never use mix view and wasn't doing for these tests. The way it looks to me is that it's not a bug, as the mix view chooser for order only appears when the destination is set. So it's one of those preference/improvement things, I think really.

 

Well if you are going to have consistency as king in my view you can't pick and choose.

For instance b-righteous had a good point here, check link and my response below it:
We have to guess loop brace start/end points - please fix!

With the loopbrace issue it should show in the Windows GUI and the Maschine Controller in the pattern areas. Neither do so that, so this makes it a clear enhancement request, even though it basically makes pattern view for me unusable in the controller in a lot of scenarios.

What we are talking about here is almost the exact opposite scenario...

There is a clear inconsistency between one part of the GUI and another, and the controller. So I view this as a clear but trivial bug. Trivial bug <> Enhancement request.

 

Can you edit the aux routing from the mix view (and not just from the Sound/Group channel properties tab) on the Studio then? As I said before, I hardly ever use the mix view and can't remember even on the other controllers.

 

Nope. and that's the not the point here, it's the behaviour of the GUI control/knob itself which is inconsistent across various views, the display logic is wrong (visible/invisible) in one instance. The issue itself is not about it being present, or not being present across various views.

If the order button wasn't being displayed in the mix view in the GUI or controller it would still take an enhancement request to fix it (if indeed it was an apt thing to do or not). I originally created my loop brace issue in the feature request forums before the consistency debate was brought up. It's still a feature request regardless of the debated scenario.

 

I just see the mix view as separate and the channel property tabs as what are directly mirrored between GUI and controller, which are consistent. Probably because I never use the mix view, I just don't care about it being a bit different.

 

Yup but caring about whether or not it should be fixed is entirely down to priority. I think we both agree trivial and anyway NI will decide .
What the issue is, and how it is categorised is an entirely different matter.

Cheers...

 

Still an issue in 2.3.1 (trivial).

 

Still a trivial issue in 2.4.7