tnussb
42
OT MK2 machines get delivered with 1.30D pre-installed for quite some time now (first reports are from Dec/'17).
I wonder why 1.30D got never officially released via the support page for more than a year now (so there are also no release notes available).
Do you have D? Does it behave this way?
Still I canāt imagine all C users have this happening, Iām quite sure people have been sampling with play trigs involved. Makes me think thereās other settings/order of operations involvedā¦
Still some bugs on 1.25H. Today I switched from a bank/part with a pickup on T2 to a bank/part with a thru on T2 and a one-shot recorder setup, I could not get it to sample. Would arm the one shot, press play, and nothing. Switching to another pattern/part on that bank and there T2ās one shot recorder would sample, then back to the pattern/part that wouldnāt sample and it worked finally.
Iāve reported a similar part switch recorder setting bug to electron and they confirmedā¦
1 Like
tnussb
44
1.30D is absolutely fine. It works as it should especially the bread-and-butter features like recording. Play trigs stopping recording trigs? Nope. Start of sampling without recording trigs? Nope (or better: only when sending special midi notes as listed in the manual). It operates as it should.
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.
So I wouldnāt read too much into these reports until they are reproducible on other machines with fresh projects, too.
2 Likes
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ā¦
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ā¦
Those have been there⦠Especially if your switching from a part with a pickupā¦
1 Like
tnussb
48
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.
2 Likes
Thereās bugs with the conditionals and tempo multiplier which gives me hope for new firmware, the thing they introduced is brokenā¦
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ā¦
3 Likes
What about this one?
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! 
1 Like
Traitor! 
The flex overlords will not be pleased.
More Octahuasca for you to restore your blind faith!
1 Like
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?
1 Like
I record the PO33 with OT. 
Canāt bring OT in my pocketā¦
Just saying some new bugs corrections would be welcomed.
3 Likes
I knowā¦
Letās get some Octatrack Love please Elektron! 
1 Like
sabana
55
Surely these are all simple fixes.
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ā¦
1 Like
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?
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ā¦
1 Like
tnussb
59
You can get 1.30D by directly requesting it via email from Elektron support.
1 Like
I stand corrected, for C users as well or just for units shipped with D? Any declared differences?
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?
1 Like