Will try to reproduce when I have a little more time! First time ever playing live with the OT tonight!
3 Likes
Made a video to show how it works on my OT. OS is 1.30B.
Sorry that it took so long, made the video already back in august, but I didnĀ“t have a YT account and then kinda forgot about it.
3 Likes
Donāt be, thank you, especially because you used a different manner to clear recording slot : it works with CLEAR SLOT in FILE menu! 
But not with FN + CLEAR in REC SETUP menus, nor slot list. Wtf? 
Could you try other ways?
3 Likes
Iāve tested with Func + Clear in the slot list highlighting recorder buffer 1 and also with Func + Clear with recording setup open.
Works 
2 Likes
Running 1.31 and am not having any issues with sampling and playback at the same time.
Iām not sure if those above are slaving the OT to another Midi Clock but doing so causes problems when sampling and playback at the same time.
Anyway - I came here to find out where / when the screensaver is. Is there a setting or does it just kick in after X number of mins?
1 Like
Yes, but do not expect any heavy dimming. It is barely visible. Just wait 5 min.
2 Likes
Thanks.
Interestingly, my new OT MKII froze 3 times yesterdayā¦ it was plugged into my computer via USB. After reading reports about this I disconnected the USB cable. It hasnāt frozen so far since. Running latest OS.
1 Like
āCurrently running OS 1.31 - Apr. 24, 2019ā
Hello, having an issue on my Octatrack. While in the playback menu the RTRG goes to the greatest value, without touching the knob. Iām not getting this glitch in any of the other menus. Please watch the short video I made showing this issue.
upon further inspection, some of the tracks while in the amp menu are increasing to the max value on the BAL the same way as in the Playback menu 
https://youtu.be/hid1N1F1-p8
Do you receive Midi Control Changes ? (RETRIG = CC20, BAL=CC26)
Try without Midi In.
1 Like
Unplugged midi keyboard. Seems to have solved the issue. Is the issue the midi keyboard?
Highly probable if itās the only gear connected.
Iād check its manual if you donāt know why.
1 Like
Could be a faulty knob or fader sending out cc values.
Sometimes happens, theyāll always send out the same value even though no one touched it (i.e. CC 20, value 120) or might even start to repeatingly send a bunch of values.
If the keyboard is the only thing connected to your OT, can you check which knob or fader sends those cc messages?
Is there anything connected to the midi in of the keyboard (midi thru active?)?
2 Likes
Iām going to go through the keyboard and hopefully find the issue, itās a pretty old keyboard TBH. I only use the midi out on the keyboard, no other inputs.
Which one ? Curious about it.
Maybe possible to disable CC send.
Axiom 49 like first gen.
Not that old! If you canāt disable CCs of faulty knobs /faders, you can assign them to CCs unused by OT.
1 Like
Always best to just use a midi monitor when in doubt if a device (and which one) sends any (unwanted) midi messages.
IIRC, there is freeware midi monitor software for all OS available.
If you can verify you got a faulty knob/fader/button that sends cc messages on its own without touching, try turning/pushing/pulling it for a while. Iāve had stuff like that happening on my older controllers, could always be solved with a bit of wiggling.
1 Like
Octatrack mk2 - OS 1.31ā¦
ok, dont know this is a bug , perhaps user error ā¦ given by newbie statusā¦ but here goes
so I was playing yesterday for a while, for a pretty long period of time, and was having no issues at all.
then I realised on audio T2 (Neighbour) the trigs were not firing - none of the automation was working. 
(it was unclear then this might have started happening unfortunately)
it was not muted, nor cued and every other track was absolute fine , and i could see that no trigs were firing (no play icon against the track)
so i tried (all to no avail)
- disconnecting midi cables, to ensure no quirky midi coming in.
- arming track trigs (they appear armed anyway)
- replacing trigs, and automation
- checked āsettingsā , pattern/global - but could not find anything that explained it, or would be relevant.
- changed T2 to a static, loaded a sample - still not triggering (so this is what I used from here for test)
- copy a āworking trackā over to T2
- tried T2 on a different bank/pattern/part
- tried T2 on a different existing set/project
- created a brand new project
all the time just T2, all other tracks were working fineā¦
I was stumped, but wanted to get to the bottom of the issue, to make myself familiar with how to get into the situation.
but after a new project still had the issues. I started to think it might be just a bug/quirkā¦ as my understand was a new project, would only inherit global propertiesā¦ none of which explain the behaviour.
so I finally switched off/on - and it immediately started working fine!
(on every project that id been messing about with testing, were all not working correctly)
so is this just a bug? have others encountered it?
OR
is it possible that i sent it some midi, that some how disarms all trigs on a particular track, and persists even when you switch projects?
Possibly, if it didnāt work with a new project.
I donāt remember that kind of issue.
No FILL conditions, Plays Free, Arranger Mutesā¦?
Can you reproduce the issue?
I want to understand everything too, but if you are new to OT, sometimes itās better to forget strange issues, and strangely you have less and less issues while progressing. 
2 Likes
nope canāt reproduce ā¦ unfortunately it was a bit unclear when it started.
fill conditions would be cleared with a new trig,
play feelā¦ nope checked pattern settings.
arranger mute - not intentionally, so would have had to have come via midi but are these active whilst not in arranger mode?
ā¦ and all the above, Id assume would be cleared by creating a fresh project.
my only thought so far, is that some odd midi event caused itā¦
interestingly earlier in the āsessionā , I had some hassle with āturbo midiā, between my pyramid and the octatrack - it seems to fail the negociationā¦ so no midi was getting thru, so I turned on/off turbo midi on both pyramid and octatrack a few times - and it āsorted itself outā.
(I then decided to just turn it off to avoid future issues )
perhaps during that āexchangeā some how the octatrack got itself into an odd state with track 2, possibly via corrupt midi messages - ā¦ itās really the only odd thing that happen whilst i was playing with it during that session - everything else worked as expected.
anyway, yeah, Iām not stressing about itā¦
i only mentioned it, in case someone else ever spots it too,
or in case there was some odd setting that carries over between projects i was unaware of.
i doubt iāll see it againā¦ and if i do, hopefully iāll spot it quicker and so have more ideas on what happened leading up to it.
1 Like