Octatrack OS 1.40A: bug reports

Can confirm. :wink:

1 Like

Another weird one, on a new project, track 1 would not show running lights when playing pattern 1, switching to pattern 2 it worked as expected. So I cleared pattern 1, and that fixed it.

I believe that when I started the project pattern 1 was set at 16/16, then I changed it to 64/64, I think this may have caused the bug.

Trying to change arrangement when sequencer is running results in “STOP FIRST!” message, but even after pressing stop the message persists, making it impossible to change arrangement, exiting arranger then going back and trying does not clear the erroneous behaviour, only a power cycle does.

I am on MK2 can anyone test, also MK1 users too?

Hi!
Does anybody met with this behaviour? When in midi chromatic mode triggering button1 and last one (page / scale setup) one of both will stuck playing. On any controlled external midi device. Can anybody reproduce this?

1 Like

Another one MIDI bug i found:
When i send CCs into Kyma from MIDI control pages it not only sends corresponding CCs but also random CCs on same chanel. Like i use only cc01 and cc02, whatever and it sends also cc81, cc34, and sometimes even something serial like cc121, cc123, cc124… cc127 in a row. Because of this Kyma’s controlled params behave abnormal, like stuck in the same places periodically and so on.


there should not be сс10, сс08, сс00 with repeating value on this pic since i use only cc01 and cc02

If i do same things from Renoise everything is perfect.

Also if i don’t use any CCs from Control pages everything is ok, it shows only clock stream

Not very clear. Would you post pictures of OT settings ?

Do you mean CTRL1 and CTRL2 pages ?

Are these also activated or do you have only CC1 and CC2 activated ? (Function + Knob press)

Yes i mean CTRL1 and CTRL2 pages
Only CC01 (CC2) and СС02 (CC3) are in use


Actually this is a new blank project to test it out, i had same behaviour before on CTRL2 page with CC71, CC72 for example

@data-purge did you check to make sure audio tracks are not sending CC’s?

i.e is AUDIO CC out set to INT?

Though if i use Renoise’s MIDI monitoring tool everything is OK, also controlling Micromodular’s parameters from OT is OK too

So it is just Kyma-specific problem i guess

Yes

? Why would OT send midi data to Kyma and not to others ?

I’ve had a failing optocoupler in a piece of gear make it recieve different (but still valid) MIDI data from different pieces of gear even though they were all sending the same data. Had to do with the interaction between the output level slew rate of the different devices MIDI output circuit interacting with the defective optocoupler differently. The shape and amplitude of the leading edges of the individual bits would directly affect whether the data got corrupted and if it did, in what way. Took about a week to figure out with help from the Mutable Instruments community. Swapping in a new optocoupler fixed everything and I haven’t had an issue since. The damage was almost certainly from static discharge from the pick-and-pull foam in a new hard case discharging into one of the pins on the MIDI input jack the first time I put the synth in. It worked perfectly, I put it in the case to test the fit, and when I took it out less than a minute later the optocoupler was corrupting data.

Point being, there are all sorts of counterintutive things that can happen with digital data that have nothing to do with software and fall outside of what we usually think is possible in the digital domain.

The newer Kyma systems are USB, right? I wonder how the ground isolation is, interference getting into the ground in audio gear from computers, power supplies and occasionally ground loops (but usually computers) through USB has given me all kinds of weird problems over the years.

Is the Octatrack USB port connected to anything when you use it?

EDIT: do you have anything connected to the Octatrack’s MIDI input?

1 Like

Maybe Kyma interpret it so i don’t know. Actually it behaves ok with Renoise and general MIDI controllers a’la akai mpd8 or novation zero sl via midi din or usb midi. But with OT it behaves strange

Yes they can use USB soundcards now while communicating via ethernet with editing software on computer. In my case all midi communications are thru firewire soundcard and its midi port. Gonna test it with usb midi interface and usb soundcard now.

EDIT: SKIP TO THE EDIT AT THE END OF THE POST FIRST

I haven’t had ground noise/interference issues with Firewire but I’ve also used a lot fewer firewire devices so that could jsut be luck. I was always under the impression that the spec for Firewire actually included some ground isolation (USB doesn’t) but I could be wrong.

The chances of it being a data corruption issue happening in the analog domain are a lot lower than it being something happening in software, but it’s something to keep in mind if you can’t find anything simpler.

You could dry passing the Octatrack MIDI through another piece of gear that you know works fine with both the Kyma and the Octatrack, using a soft thru (so MIDI out from the Kyma to the other piece of gear, passed directly to the MIDI out on that gear rather than the MIDI through and then into the Kyma). That would help rule out hardware problems. If passing the MIDIthrough another piece of gear so the Octatrack and Kyma were never directly passing data between each other makes the problem go away then it’s probably a hardware issue with the Kyma and Octatrack not working together electronically for some reason; if the problem stays then it’s probably not hardware.

A MidiPAL or clone is great for this because it puts out a nice, clean, strong MIDI signal. When I ahd that optocoupler falure the clue that finally helped us figure it out was that the problem synth would always work perfectly with any MIDI source if it was routed through the MidiPAL (just a straight soft thru with no processing) - even sources that the synth wouldn’t respond to at all if they were directly connected. It’s a really useful tool for all sorts of things - one of the best purchases I’ve ever made - but one I never hear much about is cleaning a MIDI signal (any quality MIDI router or other gear with a soft thru and quality MIDI i/o circuitry is good for this, but the MidiPAL is really convenient and has a hole bunch of useful diagnostic tools). You could also pass it through a DAW if you have a separate MIDI interface in addition to the Kyma.

However you accomplsh it, if you don’t find a software cause for the problem, the next step I would take is to see what happens when the MIDI out on the Octatrack and the MIDI in on the Kyma have some kind of clean, known-good buffer between them.

EDIT: you could probably easily make a simple MIDI buffer patch in the Micromodular, now that I think of it. Just something that passes all of the data from the input straight to the output. Patch the OT MIDI out to the in of the Micromodular and the out of the micromodular to the in of the Kyma and see if the problem still happens.

1 Like

I tested OT midi output with esi midimate II to kyma via usb and everything works fine. Sorry for false alarm!
It is focusrite saffire’s midi seems to pass corrupt data.

3 Likes

Yep

2 Likes

Weird, but probably the best case scenario once you ruled out some kind of patching or configuration error.

Edit: Not a bug, see a few posts down.

Found another strange one, on a mono sample getting slight difference in level between L+R when using compressor, R channel is slightly louder according to my VU meter. When comp mix is zero both channels are same, when mix is above about 18 difference happens, it is also non linear, so some mix values it does not happen, especially over about 80.

Easiest to check with a kick, make sure sample is mono, RMS settings don’t affect the outcome of the level difference.

These are the settings I used

[quote=“darenager, post:245, topic:144192, full:true”]
Found another strange one, on a mono sample getting slight difference in level between L+R when using compressor, R channel is slightly louder according to my VU meter. When comp mix is zero both channels are same, when mix is above about 18 difference happens, it is also non linear, so some mix values it does not happen, especially over about 80.

Easiest to check with a kick, make sure sample is mono, RMS settings don’t affect the outcome of the level difference.

These are the settings I used


[/quote]

It’s normal, Anniversary Edition works properly once per year. :pl:

Only noticeable with VU meter on analog mixer, or also by ear ? I’d check with other metering…

2 Likes