More noobing: Track starts sampling without recorder trigs

[Open_Mike]

I’m in a sleep deficit lately so I don’t have the strength to do my usual forum search reference posting, I just feel there’s more strangeness reports than before. I keep reading people power cycle and then things work which wouldn’t have anything to do with settings but possibly part weirdness, if the part wasn’t fully kicked in (having to do with how track settings are still active until a trig on that track is reached) and power cycling loaded it fully.

Edit: I would have tried a part reload on the quirk I mentions happened to me today a few posts back, but I had tweaked a part that I liked the saved version and didn’t want to loose the tweaks right then. Actually had the idea to switch to another pattern/part and then back and it worked…

[sezare56]

So beside the known bugs (pre-sliced buffers, quirks with parts and the one found lately by @sezare56 about CCs getting recorded when they shouldn’t), everything is fine.

I can’t say everything is fine.
Pre-sliced samples seems to work but some bugs on Rec Setup settings when you change parts for example…

[Open_Mike]

Those have been there… Especially if your switching from a part with a pickup…

OT Known Bugs & Workarounds Document

Brief description of issues: Older: -Switching from a pattern/part with a pickup to a pattern/part with a flex on the same track # as the pickup will trigger the pickup loop instead of flex sample if the pickup was not playing before switching, Confirmed… scene locks from pickup track also may remain on new flex track… Workaround: make sure pickup loop is running before switching, muted if necessary. -Switching from a pattern/part to another pattern/part that has recorder trigs, sometimes t…

[tnussb]

when you change parts for example…

That is one of the “quirks with parts” I mentioned.

And with “everything’s fine” I meant that the standard features work as they should. No troubles with rec and play trigs. Also no troubles when switching rec sources and basic stuff like that.

[Open_Mike]

There’s bugs with the conditionals and tempo multiplier which gives me hope for new firmware, the thing they introduced is broken…

Octatrack: The Arranger and One-Shot Trigs

Okay I had a look at this where I stripped out everything to narrow it down (no neighbours, no tracks apart from the two to trigger backing samples, no arranger even) Edit: oh and short samples, so this isn’t even about the logistics of long backing tracks This is what I found: Conditional “1st” trigs do NOT trig as expected IF the scale mode is ‘per track’ and the master multiplier is 1/2 or less The trig on the first pattern you play works okay, but not any pattern switched to after that L…

TRCs and One Shots not triggering in Arranger with 1/2 Master scale

This is just on the OT. The A4 is only to reference why I’m using 1/2 scale. I can replicate by having two rows on arranger, both 1/2 master scale. the first pass on the second row will not play one shots, “1st” or a “1 of #” like “1 of 2” but it will play “2 of 2.” It’s like the first time through already happened though of course it hasn’t.

I think @clancy might have more bugs for us…
I design my project and workflow specifically to not encounter them, besides today, trying new stuff…

[sezare56]

What about this one?

Midi loopback bug id'd - might help your headscratcher moment

Hey all. Just found a bug in the OT to watch out for if you ever use midi loopback. I thought some of you might be interested in this one because it answers some of those WTF? moments. I was using loopback, and could not figure out why changing LFO depth in the LFO setup page of one of my midi tracks was making an audio track cut out. If IRC, @defenestration was trying to identify some of these types of things. Simple to reproduce. Try it out: Connect midi in to midi out. Make sure that Trac…

That means if you control a synth with a midi track and change its lfo settings you can also change audio tracks settings. Unacceptable.

Ok that’s midi loopback, but it prooves OT is not finished. And even without midi loopback, I suppose OT sends the corresponding 28-33 CC messages on the channel corresponding to the corresponding audio channel.
I go back to the PO33!

[Open_Mike]

Traitor!
The flex overlords will not be pleased.
More Octahuasca for you to restore your blind faith!

[Open_Mike]

When record and play trigs are on the same step you need to shift the play trig with microtiming to the right otherwise you may not hear the live audio. This behaviour looks like it is not recording while indeed it is.

Only for recording OT tracks using the Scr3 setting. For recording inputs you can have the record trig in the exact same spot as the play trig and you hear the recording being made as its happening…

I do keep asking if those with the issue are using Src3?

[sezare56]

I record the PO33 with OT.
Can’t bring OT in my pocket…
Just saying some new bugs corrections would be welcomed.

[Open_Mike]

I know… Let’s get some Octatrack Love please Elektron!

[sabana]

Surely these are all simple fixes.

[Open_Mike]

Some have been there all 4 1/2 years I’ve had my OT and I don’t know how long they were there before that, possibly since birth…

[clearside]

Just curious what OS I should be on? My first OTmKII (the bunk one from my other post) had D on it shipped to me. I have C. They don’t have anything other than C on the elektron website so this has me wondering what OS should I be on. Have they really not updated since 2017?

[Open_Mike]

You can’t get D, C is the one for you. Total speculation but D might just be for slight hardware component changes or factory testing routines. I’m almost positive there’s nothing new as far as bug fixes. And yeah, last update Nov 2017, it was major adding trig conditions and no one saw it coming, MK2 runs same OS as MK1, the OS also added support for the new MK2 buttons…

[tnussb]

You can’t get D

You can get 1.30D by directly requesting it via email from Elektron support.

[Open_Mike]

I stand corrected, for C users as well or just for units shipped with D? Any declared differences?

[Marklaar]

I had some time at the weekend. Started a new project and live sampling just works as intended. Now if I go back to that problematic project it also works. I don’t even know how to reproduce that “bug”. I did not do any special or different than last time. WTF?

[Open_Mike]

You say you haven’t used parts yet, but possibly did you switch patterns in different banks? A different bank means a different part is used, so possible it had something to do with the recorder setup part switch weirdness that we mentioned sometimes can happen under certain circumstances… If you switched banks that is…

[Marklaar]

If I switched banks or parts then it was an accident as I’m really focusing on one thing at a time to understand the OT.

[tnussb]

I stand corrected, for C users as well or just for units shipped with D? Any declared differences?

Good question, but why should the D version only work or be accessible exclusively for units shipped with it? I don’t see any real reason why they should change their practise. And “no”, never seen any release notes.