This was very odd.
I had track 1 running a 16th rolling bass, with no P-locks.
A4 was clock slaved to Octatrack, via a Kenton 1-in, 5-out thru box.
3 times that track dropped Osc1 a full octave in that the tuning went from -12 to -24 all on its own.
I was playing with another slave at the time (Rytm).
Can’t easily reproduce, so will keep an eye out to see if I can spot a potential pattern.
Is it possible that OT sends some messages on the same midi channel which is assigned for A4 track’s channel while you turning knobs on the OT or etc.?
That’s the obvious thought, but if there was an event on the OT doing that, you’d expect it to happen on every loop.
There were no events on the OT, at that point I was only using it as master clock source.
one octave , thats nothing compared to a drop of one meter on the wrong corner :-9…
well i think you might overseen some settings , a glitch ? but if its a bug you should be able to reproduce it somehow.
hey Purusha, do you have the OT sending PRG CHANGE?
If this is the case, make sure you assign a specific channel for this duty…do not use the default channel that should be the AUTO…
I wasn’t sending program change at the time, but I’m wondering if OT might have randomly sent one anyhow…?
I didn’t get much chance to play last night, but I think it may be related to the beat itself since when I turned the unit on, I had to reload the kit since it had dropped an octave again.
When I next get chance, I’ll try sending program change to change to A2, then back to A1. I suspect it’s as simple as that.
It was just a surprise that it dropped down an octave whilst I was tweaking a slave device.
the actual bug actually drops the OSC1 to -64 …
I think you may be correct on this one - thanks! Although, I’m fairly sure the drop I saw was -12 to -32.
Still strange that OT might be randomly sending program change though.
I had some odd behavior once where I couldn’t adjust a specifi parameter, or I’d adjust it then it would revert seemingly on it’s own. I don’t have an A4 any more but if I recall correctly I had something setup in performance mode that was causing the problem.