That would surprise me. Afaik recorders recording level is always the same and doesn’t depend on track machines. SRC3 T1-T8 recordings don’t depend on target track Level, but Thru SRC VOL and AMP VOL matters.
There is CC59, its values correspond to notes. But IIRC it doesn’t work if standard mode is disabled.
It does seem to be the case for me, at least with T5 which is what I’m using as a thru track, might try some others later. Might be different if I record from A/B C/D instead of MAIN, will have to test that too.
Aye I played around with that earlier but like you said it doesn’t work outside of standard mode so it’s a bit useless. Seems like there’s some CCs not being used that could be used for REC1/2/3 which would be useful.
Imho it is a rec source unity settings problem, not the machine selected with the same track recorder. Don’t hesitate to ping me if you can reproduce/proove it.
Not sure it if suits you, but with CCs you can use CC 53, Recorder Arm.
CC53 Recrdr Arm [0]=Rec disarm, [1-127]=Arm
Unable to manually trigger a midi track to start playing when in “plays free” and “direct” mode.
Still trying to figure this out. I made a new project and set it up pretty much the same way, and there’s no difference in level between MAIN recording on a flex track and a recording made on a thru track’s recorder played on another track. So basically I can’t reproduce this yet.
On the problem project I’ve gone through everything I can think of, LFOs, scenes, AMP, trigs, MIX leves, etc. I can’t find any reason for the difference in playback level, and right now it honestly just feels like something is bugged specifically in this project. I don’t mind remaking it from scratch, wouldn’t take long, but it’s annoying.
I did try saving a copy of the buffers, one file from the thru track and one from a flex. Putting them in a DAW there’s no appreciable difference in level, so it seems to be recording correctly but not getting played back at full volume?
I am totally baffled by it.
EDIT: Wait I think I’ve found the culprit, seems the gain setting the attributes in the AED is +12 on the flex track recorder and 0 on the Thru track recorder, not sure why that’s happened or why it doesn’t happen on a fresh project but I’ll do some more testing and tweaking and see if I can just fix it with that.
I hope so ! 
Recording buffers are set to +12db by default. Once I was surprised to have one set to 0db, but it was because I previously loaded a sample without in the buffer. (Samples without Sample Setting .ot files are loaded with 0db Attributes Gain.)
Yeah that’s probably what happened. I’ve never needed to touch that setting before so it was very confusing to me 
stumbled upon this mindbending issue yesterday:
trigless trigs act as normal ones if:
let’s say B2 has trigless. i put this pattern in Arranger, activate ARR and play. so far so good. but if i assign scenes for that row in the arranger, trigs would actually trigger the sample.
probably long-discovered issue anyway
I couldn’t reproduce it.
yeah, i just rechecked on a new project, my description wasn’t complete.
the given pattern should contain only triggless trigs. so the case is:
@sezare56 i’m still not sure what’s the exact behavior when this happens in the project it reproduced initially (slide trigs might contribute), but in a blank state project it seems that trigless just doesn’t work at all
@sezare56 thank you for checking
So I can confirm trigless plocked parameters have no effect with a neutral scene assigned in Arranger. 
Trigless work if you use a regular trig at the beginning of the pattern though.
Recording a 7 bar sample sets the tempo incorrectly.
Eg. set tempo to 96.0
Record a loop for exactly 7 bars (quantized to pattern length of 112).
The recorded sample’s tempo is now changed as it assumes it’s 8 bars not 7 bars.
This is exceptionally bad if you’re using pickup machines since the tempo will be changed on you.
It should uses the current tempo for the recorded sample, or at least a way to tell it to use the current tempo instead of guessing incorrectly.
I would definitely like to see an option to have it not automatically calculate a tempo for every recording so that I could use the timestretching via playrate more predictably, and without needing to go into the AED menu to match the sample tempo to the current tempo.
If the cable is plugged into the back of the OT but not connected to the computer on the other end, that needn’t be unplugged, right? I’ve had around 3 occasions in the last couple days where I had to reboot the OT to make things work and I’m desperately looking for reasons.
While learning new stuff and I’m like “… OK that should work” but it doesn’t work so I reboot hoping that it DOES NOT fix it, I’m hoping it’s user error that I can learn from… but the reboot does fix it and I’m left hopeless! Examples were sample locks on static tracks not playing at all until a reboot, another was MIDI CC p-locks being ignored/not sent until a reboot.
(I’m on 1.40B)
known bug, at least to me, even reported. Anytime i eject the mounted volume in the file system (mac) or disable USB mode (octatrack) i also have to take out the cable on the octatrack otherwise the machine will freeze. And if i take the cable out i get informed that i took the cable out. Funny - otherwise would have forgotten. 
Guessing there is a hidden feature and it doesnt work “yet”. You can guess what feature that would likely be that needs to know if it is still connected. And we don’t have that feature because it simply does not work properly ^^. But i am still on 1.40A
To clarify, I’m talking about having the USB plugged in to the OT but not connected to the computer, I didn’t think this would cause problems but I’ve removed it now. Maybe my chain of cheap power adaptors is causing some irregularities? I don’t know.
I get that message when I disconnect the OT from the computer, but not when just removing the physical cable without it connected to the computer first. This led me to believe that I didn’t have to remove the physical cable as well but we’ll see.
when you hit any pattern related button (bank/pattern and so on) after you Exited the USB disk mode on the octatrack you are very prone to freeze when at that moment the cable is still connected. That is the message on screen that the cable is disconnected on the OT side was a new feature that was not available in the earlier firmware. And the freezes only appear since the new firmware has this feature. So when the OT can figure out the usb cable is disconnected means there is still some reader hosting up but the firmware seems not to take its own assumptions correctly and therefore does something that must be completed before it goes on. It can not complete, it freezes. I mean a freeze is a pretty heavy symptom. And there are not much scenarios in which a machine can freeze… It should rather carry on when the USB connected even gets accidentally disconnected. Even automatically reconnect when the cable is plugged again. So the question is why after unmounting does the new firmware tell me that the cable was disconnected? It can only be that after unmounting the usb disk mode is still doing stuff or never left - now we have an unknown state and can also not figure out the state but still try to figure out the state rather than assume the state is changed (disk mode off or disconnected therefore ‘likely’ off as well)… can you follow this idea, whats going on?
short: why do i need to get informed “USB CABLE REMOVED” after i dismounted already and the entire project is already reloaded. Why does the USB connection still do stuff after disk mode was exited? questions over questions… Elektron?
@Tapepusher you have an MK1?
the series of events is this…
now do same same but at 7) when you hit the bank button here the OT freezes
to me thats clearly a sign the sorting of events is messed up.
Can you not hit the bank button at that time? did I miss something or is there a reason why you must press bank immediately after the project loads and before unplugging the USB cable?
I think this is a bug(or very old known issue) with such an easy workaround they havent bothered to do anything at all about it and thats why we still see the dialogue. Ok with me, I’d rather them spend their time on fixing bugs that do cause major issues/limit intended functionality.
Sorry will not go into that direction… because you actually say, i should remember not to use the octatrack after i connected with USB to avoid a freeze. I mean thats what you ask me to do…
pressing bank is just an example, it can freeze at any other button as well, just with bank btn i tested the last time in the write up of the post. And thats a major bug that is happening on MK1 and MK2. I also know that a similar bug was fixed somewhere OS 1.11 to 1.2 and again OS 1.2B to 1.2C. You can certainly count on that i would spare my time in another way if that bug would not be so dangerous for all my projects. Cause a freezing machine is the worst thing that can happen to files and i can not backup everyday so others can go on and think, “cool, i don’t have that bug”.
I don’t get the OT (mk2) freezing when hitting Bank and removing the USB cable.
Would you mind giving additional details?
@Watto this is a bug reports thread, and the cause of the bug related to a usb cable left plugged has never been identified, which is why it has not been addressed.
I can’t see why you would try to shut someone down, especially when they are giving details on the procedure.