Reply to thread

Message

<blockquote data-quote="Jay Ashworth" data-source="post: 131413" data-attributes="member: 8260">Re: Behringer X32 Firmware v3.0 Feature RequestsHaving now gotten my fingers on faders of a 2.04 unit, I have a couple of other observations to make.Number one: tied faders behave very poorly if you grab both faders at the same time. They fight with each other. It seems to me it ought to be possible to special case that so that if tied faders notice that&#039;s happening they can just release the tie on the fader temporarily.&nbsp; On a related note, it is impossible to tell from the control surface that two channels are tied, so you are guaranteed to do this if you don&#039;t already know.&nbsp; I can think of a couple of ways to indicate that graphically on the Scribble screen that would not take up a lot of space.Secondly: it seems to me, and that this could be just me--so many things are just me-- that it is difficult to stand on a given point in a signal flow and see where it&#039;s coming from. I had a cable plugged in to XLR Out 14, for example, and I didn&#039;t know what was feeding it (it turned out to be fed from matrix 1). Since the way you do that routing is to go to the source (a bus or matrix) and select XLR out 14 as its destination, it&#039;s difficult to work the other direction. Unless there is a place to find that that I haven&#039;t found yet.Finally: the encoders below the screen go the wrong way. Or at least they go the opposite of the direction I would expect to have to turn them in order to move the cursor is up and down things the way that I would expect to move the cursors up and down things.I believe I understand why the the direction that was chosen was chosen...&nbsp; But this is what computer hackers call a miswart. You have to do it the opposite of the intuitive way for it to actually be intuitive for users. Again, maybe this is just me, but it&#039;s irritating. I I suspect it&#039;s a left-hand versus right hand operator thing. Perhaps the designer&#039;s a lefty?</blockquote>

[QUOTE="Jay Ashworth, post: 131413, member: 8260"] Re: Behringer X32 Firmware v3.0 Feature Requests Having now gotten my fingers on faders of a 2.04 unit, I have a couple of other observations to make. Number one: tied faders behave very poorly if you grab both faders at the same time. They fight with each other. It seems to me it ought to be possible to special case that so that if tied faders notice that's happening they can just release the tie on the fader temporarily. On a related note, it is impossible to tell from the control surface that two channels are tied, so you are guaranteed to do this if you don't already know. I can think of a couple of ways to indicate that graphically on the Scribble screen that would not take up a lot of space. Secondly: it seems to me, and that this could be just me--so many things are just me-- that it is difficult to stand on a given point in a signal flow and see where it's coming from. I had a cable plugged in to XLR Out 14, for example, and I didn't know what was feeding it (it turned out to be fed from matrix 1). Since the way you do that routing is to go to the source (a bus or matrix) and select XLR out 14 as its destination, it's difficult to work the other direction. Unless there is a place to find that that I haven't found yet. Finally: the encoders below the screen go the wrong way. Or at least they go the opposite of the direction I would expect to have to turn them in order to move the cursor is up and down things the way that I would expect to move the cursors up and down things. I believe I understand why the the direction that was chosen was chosen... But this is what computer hackers call a miswart. You have to do it the opposite of the intuitive way for it to actually be intuitive for users. Again, maybe this is just me, but it's irritating. I I suspect it's a left-hand versus right hand operator thing. Perhaps the designer's a lefty? [/QUOTE]

Verification