Octatrack MKII (MK2/2nd Gen) specific bugs thread

[darenager]

Noticed something odd today - not sure if it affects mk1 too as I no longer have my mk1:

Sending CC48 to control xfader only works when not in midi sequencer, at first I just though maybe I have midi direct cc turned on, but it does not make a difference if it is on or off, I think it is a bug as other cc’s for other parameters seem to work fine.

@sezare56 @tnussb @palm @jb @thetechnobear @Lieder @avantronica @AdamJay did any of you notice this?

[AdamJay]

I’ll investigate @darenager

[AdamJay]

Can confirm @darenager
External MIDI CC control of Crossfader CC#48 only works when the OT MK1 is in sampler/audio mode.
As soon as I hit the MIDI button, the crossfader stops responding to CC#48.

[tnussb]

I haven’t noticed it until you mentioned it (tested and can confirm / mk2).

Yeah, looks like a bug. I can’t think of a reason why it should stop working when in midi mode.

[darenager]

Bug report submitted

Edit: Perhaps not a bug but a bit daft that some (most) CCs are allowed and some not, appendix C3 gives the list thanks @roadmoviemusic for the link to the previous discussion.

[roadmoviemusic]

@AdamJay

External MIDI CC control of Crossfader CC#48 only works when the OT MK1 is in sampler/audio mode.
As soon as I hit the MIDI button, the crossfader stops responding to CC#48.

I don’t think it’s a bug, it’s actually (quite hidden) in the manual:

Incoming MIDI message automatically routed to same MIDI output

Yes, indeed that’s helpful. I think I’ll bookmark this thread… and MidiOx is (still) my faithful friend for decades now. This feature looks weird but it’s actually quite useful! There is however a question on the direct connect feature I don’t understand yet. I want to control the crossfader with a midi footpedal. The midi implementation chart says: crossfader = CC #48. It doesn’t state a channel. So I programmed my pedal to send this CC on the autochannel. I was in midi mode and had a midi …

[darenager]

I should clarify that I am using the auto channel (in this case 11) and CC direct control off, so it should logically work, I can understand the desire for it not to work when CC direct is on as CC48 might be needed for something else, so in that case it would make sense to disable it, can’t see any point of it not working when CC direct is off though.

So midi loopback control of Xfader not possible if in midi sequencer.

[AdamJay]

@darenager

I should clarify that I am using the auto channel (in this case 11) and CC direct control off, so it should logically work, I can understand the desire for it not to work when CC direct is on as CC48 might be needed for something else, so in that case it would make sense to disable it, can’t see any point of it not working when CC direct is off though.

Same here. Auto channel, and CC direct off.

Meanwhile external control of the other CC#s do work fine (levels, Fx parameters) when in MIDI mode.
Of course, those aren’t auto channel, though.

[oktatracker]

So, any bugs left that didnt get addressed in 1.40?

[tnussb]

At least one got left in (found during beta testing), because they ran out of time due to the anniversary.

Bug Details:

Randomization bug (ALL EFECTS):

If an effect is loaded into FX1/2 on any audio track of an unsaved PART and the user randomizes (FX1/2+YES) the effect page, then undoes it (FX1/2+NO), the parameters will not be initialized.

[oktatracker]

Easily fixed in firmware 1.50 in 10 years