Hi everyone, hope you can help me
When I try to mute/unmute multiple tracks pressing the relative buttons simultaneously, both via quick mute mode or via T1…T8 tracks, some of the buttons go unrecognized.
For example:
I want to unmute T1, T2 and T3 simultaneously, so i press 1, 2 and 3 trigs at the same time in quick mute mode (or FUNC + T1, T2 and T3 little buttons around the display), but not all these 3 tracks get unmuted, only T1 and T2 get unmuted (or T1 and T3, or T2 and T3).
Is a normal behaviour for this device?
I know is possible to press FUNC + [MULTIPLE TRACKS] in quick mode, but in some cases it is less immediate.
It’s happened to me before but not consistently. Hard to tell if its the OT or you just missed the right pressure with all your fingers at the exact same moment. Does it happen consistently or does it sometimes work?
Unfortunately, this happens a lot, so much so that it cannot be relied upon in a live context.
I can assure that I press the buttons with the right pressure, because I also thought this was the problem.
I’ve certainly had it not work at the best times during a set, but also it work fine. So, hard to say, but I wouldn’t say it’s typical behavior from my understanding. You should technically be able to mute all 8 tracks at once in either method.
technical answer here.
The mutes are stored in bitfields of one single number and read out as such… There is no queue of events to work thru, in other words there is no keyboard buffer. Anything is analog analysed…
And also knobs reset the internal “longpress-timer”. Which is round about 0.3s… long (can’t remember the exact time maybe it was 0.4, 0.5 or 0.6s), anything pressed longer than this timespan is recognised as new bit-pattern of pressed buttons, which ultimately leads to the button pressed before that last bitfield to be ignored.
So this behaviour is not a bug, it is result of the OT’s nature to allow long and short press or even double (click) pressing of buttons.
Which sadly also means in the rare case of hands with very varying finger lengths this happens more often… Knowing this i’d recommend in performance to lay the fingers on the knobs first without pushing, then hit FUNC and push all down at once, release and voilá it should do what you expect.
another tip for performance, with mute/unmute via midi (which is a serial signal) this behaviour never comes in your way. Hit a midi button, its send over, it mutes/unmutes, done.
Yeah, that shouldn’t happen. Just to clarify, you get the same behaviour when you use the track buttons (function + track 1, track 2 etc…) like when you use the trig buttons (open mixer mode or quick mute mode and mute/unmute with trig buttons)?
That would point to a problem on the software side. If one works, but not the other maybe you have a bad switch.
(please correct me if I’m explaining this incorrectly)
You can also go into quick mute mode, hold down FUNC and then select the tracks you want to mute and then release FUNC to have them all be muted/unmuted at the same time. I find that to be the most reliable practice, but you do have to be fast in a live situation.
You’re absolutely correct, but has I’ve said in the topic (perhaps by explaining myself unclearly), I find it a little less immediate as an approach in case I need to make a quick decision.
So, using an external midi controller the “problem” could be bypassed? I would like to pair it with something that has also faders, in order to decrease volume without loosing fx tails (reverb, delay).
As for the talk about the timing of key presses, maybe I didn’t get it right, but to me it seems to press the keys at the same time, without letting too much time pass between them.
Not yet, I opened it solely to clean traces of dust from the display, there didn’t seem to be much on the board.
In any case, I had a level of anxiety equal to someone who has to deactivate a bomb
Before reopening it, I’d rather see if other reasons were the cause.
the bypass issue will persist. Mute is mute, not step sequencer mute but audio mute. The arranger lets you circumvent that but has no midi API. Yet turning the volume via midi is indeed not hard cut, unless you do so.
The non-responsive mute buttons unexpected on the machine itself are bypassed when you do midi, because midi signals are filled onto a row of “empty” bytes which means they arrive one after each other and as such are interpreted one ofter each other. Which means they basically mute/unmute immediately right after each other. Like taking a stack of cards and handing them out one by one.
Manually pressing mute/unmute is applied on push-down, not on button-release. And any new push-down also assigns a new bitpattern and intersects it with the mute-bitpattern before.
[.•••|....] … 0.25s pass, mutes/unmutes are applied on push down, you still hold those. [•...|..•.] … additional bitpattern of later pressed keys. Another round of tracks to flip mute as long you still hold FUNC down.
Dont get confused by the indicator LED of the selected track (mk1: orange[muted] or red[unmuted]).
I try to recreate the issue, maybe i can learn something… on MK1 i am unable to reproduce it… is it maybe MK2 (rectangular buttons) related?
All buttons on my OT are 100% reliable. Switches don’t last forever and can be replaced, but it’s weird that you have that problem both with track buttons and trig buttons.
When you open the mixer, you can hold function and then cue mutes, meaning they will mute/unmute when you release the function button. You said you also have a problem when you do that, right?
Check this out: open track in live edit mode to place trigs.
• hit one empty trig, turns red.
• hit it again and keep your finger longer than 0.5s on it, trig stays as is, does not remove
• hit it again, just tip it, trig gets removed.
the feature allows you to see assigned parameters of a trig or simply remove it or place it.
proof of concept, that basic UI feature is implemented for all trig buttons and track buttons (will not select track if pressed long, with FUNC it will still mute/unmute) and likely more buttons.
