Octatrack OS 1.40A: bug reports

Could be OSX.

I use this app called NTFS by Tuxera
Let’s me use none Mac formatted HDs
It’s cheap and has no update fees.

Maybe try that?

2 Likes

yeah… I guess it is an OSX issue, based on the series of events. I’ll check out the NTFS app if I can’t solve it in other ways. Thanks!

Don’t know if it will work but something to try is having the OT connected by usb and powered on before turning on the computer.

Yeah, thanks. I’ve done all the normal stuff like that.
Switch cable, cable first then power… different USB port.
Then I went OSX diving. Reset SMC, Reset NVRAM. Nada.
So…
I bought a new CF card (SanDisk 64gb Extreme). Bingo!
I’m back in the game!
Guess the OG Card from Elektron (32gb, new graphics)… which is pretty much new is wonky.
So - sorry everyone, this wasn’t a bug report.

4 Likes

Recently discovered this bug.

Summary: Live recording with MIDI sync receive enabled doesn’t wait for input when rec+play is pressed

Expected: According to the manual when clock receive and transport receive are selected the Octatrack should wait until a MIDI message is sent to begin recording.

Observed: When both clock receive and transport receive are selected in the MIDI settings the sequencer still starts immediately when a user hits rec+play to enter live recording mode.

Bug or a silly user
Since the update, I have a problem with sound disappearing on a Through track that takes sound from modular. Recording controls are properly indicating that the input is hot but the headphones/master output of that one particular track disappears for lets say a 16steps and then comes back again after the same time and again and again. I tried starting new project but after some time of playing (mostly with modular so the chance that I pressed something is super limited). Any advice? I don’t think I had that problem before an update…

I experienced an interesting bug today.

First pattern, tracks 1 and 5 set to THRU machines from inputs A B and C D respectively. Works fine!

Change to a new pattern, then to new part. Set tracks 1 and 5 to THRU machines again, set trigs… nothing. No audio from those tracks, even after a double press of stop. Have to change to another pattern/part (or maybe just part) and back again for it to work.

Maybe I’m missing something since I’ve had a break from the OT for a long time, but this seems like a bug that wasn’t there before? Can anyone replicate? It’s from a project that was from last year (and thus before 1.40), so maybe that’s the issue…?

Did you try re-saving the project then reloading? Maybe also try re-saving the parts.

I’ll give those a try tomorrow, thanks for the suggestion :slight_smile:

And deactivate scenes just in case :wink:

Hadn’t touched scenes yet on those patterns! As mentioned it works after switching away from the pattern and back, and even keeps working after a double press of stop once it starts working.

I’m finding the Plate reverb doesn’t work on Track 2.

Turn mix to max and hear nothing.

Copy that track to any other track and it works.

Anyone happy to try/confirm?

works fine here.
Sure you don’t have a scene engaged that is holding the MIX at another level?
(like I actually did myself just yesterday, ha)

Or is the gate parameter al the way down (closed) with setup page GVOL up ?
Are plate filters all the way open (HP full left, LP full right) ?

There are a few places in the plate reverb parameters where you can make it sound ineffective.

1 Like

Confirm plate reverb working fine on track 2 here as well, new project.

1 Like

Hi there, I am currently experiencing a weird issue where note-offs of one midi track seem to be cutting off notes of a different midi track.
I use the octatrack as master for an eurorack case and an akai mpc one.
The Octatrack sequences midi of the eurorack with the help of a vermona qm2 “midi to cv” interface.
In my specific case I use the octatracks
midi track 2 to control midi channel 12 of the qm2 and
midi track 3 to control midi channel 13 of the qm2.

On trig 1 of midi track 3 I set a c2 that is slightly longer than a “whole note”.
As a result I hear an endless c2 note which is exactly as I would expect.
I can record that into the mpc and see that the mpc recorded c2 notes, starting and ending at the beginning on each beat.

The confusing part starts, when I play c2’s on midi track 2 as well.
When I set a c2 trig on step 1 with a quarter note length it seems that the note-offs from midi-track 2 also shut off the notes on midi-track 3.
The following is what the mpc records on midi-channel 13 which is assigned to midi-track 3. I started the recording with midi-track 2 muted and unmuted it at beat 5.
When the notes on track 2 are not c2 then the pattern would not change.
OctabugMpc

It is slightly more confusing on the eurorack side.
Here it seems that the notes are not set to off after a not-off from track 2 but it still changes behaviour when unmuting track 2.
Also, the change in behaviour happens even if the notes on both tracks are different.

The following images are photos from the Mordax data where the lowest red line represents the gate that is comming out of the qm2.
The blue line is the generated envelope and the green line is an envelope, triggered when the adsr has recognized a new attack.
The gate comming back to 0 is not visible in the images due to the coarse time resolution of 500ms.
It is, in this resolution, sometimes visible when track 2 is unmuted but not when track 2 is muted.
The peak back to 0 becomes visible for both variants when the resolution is set to 20ms however.

midi-track 2 muted:
rack_t2_muted

midi-track 2 unmuted:
OctabugDataUnmuted

Did anyone else experience this issue as well or is this even a setup thing that I am missing?

Not sure what is your issue, but with OT, some synths, midi to cv common Notes Off issues can be related to this :

OT sends Notes On with velocity value 0. It doesn’t send Notes Off.
It’s a midi standard. All midi stuff should be able to receive both, but sometimes its only Notes Off.

(If it’s your case, a midi processor can change Notes On Vel 0 to Notes Off).

@sezare56 thanks for the reply.
When searching the forum if my issue popped up before I saw that other people had issues with that behaviour of the octatrack.
It may be related to my issue, but in my case the Problem is that muting and unmuting midi-track 2 has an effect on midi-track 3 even so they have different midi channels assigned.
midi track 2 -> midi channel 12
midi track 3 -> midi channel 13

1 Like

If you check what is really sent by OT with a software monitor like Midiox, it would help to deceipher this…
I didn’t use any midi to cv gear, except Analog Four.

I tried to check the midi signals from the “mpc midi monitor” but unfortunately it is not really usable and I do not have a midi interface to my computer yet - I guess I should by one now :wink:

1 Like

A lot of gear doesn’t, new and old. It was originally a hack to save some bandwidth (Noteon with a velocity of zero is slightly smaller than a real noteoff) and became widely used because it usually worked with most MIDI gear but it can definitely cause problems sometimes. I don’t know if it was ever actually officially adopted into the MIDI spec (it was definitely out of spec for 1.0 and I can’t find anything about it in 1.1), but I’ve used synths developed in the last couple years that won’t work with the OT (and some other sequencers and controllers) because of that. Usually it’s not an issue, though. When it is it’s mostly either old stuff that actually strictly adheres to the MIDI spec because it was the standard at the time, or recent stuff by small developers who strictly adhere to the MIDI spec because they don’t know that can be an issue in practice.

MIDI 1.0 spec pA-4:

Blockquote
If an instrument receives two or more Note On messages with the same key number and MIDI channel, it must make a determination of how to handle the additional Note Ons. It is up to the receiver as to whether the same voice or another voice will be sounded, or if the messages will be ignored. The transmitter, however, must send a corresponding Note Off message for every Note On sent. If the transmitter were to send only one Note Off message, and if the receiver in fact assigned the two Note On messages to different voices, then one note would linger. Since there is no harm or negative side effect in sending redundant Note Off messages this is the recommended practice.