Interesting. I twiddle knobs in one pattern+kit. Go to another pattern+kit. Come back to the first and the kit isn’t reset to saved state, as it used to be in prior OS’s.
I power cycled it and the issue remained. (Though after reboot kits are reset, but that’s a different, expected thing.)
Checked it again to be sure. It really doesn t work here
Well lucky me… it appears to be one track in one kit that doesn t reset correctly. It does update the GUI but not the actual sound parameters.
Track 3 with RS hard engine.
Whatever is happening here is nasty because it’s tricky to pin down
I tried just what you described from a new project and the first pass of the modded kit played back edited, the second kit change on that occasion played through as stored
i.e. the reload feature didn’t operate at the first chance, but did at the second opportunity
This is not right
So I added another reference track (because only T3 !) well I got the issue more problematically with T9 - the GUI parameters were updated but the kit sounds were most certainly not (a maxed out decay on a CH is easy to spot)
I wondered if it related to the Lesser track of a shared voice, but same issue with T10
so despite going through a Chain cycle with kit changes the sound was not being updated but the graphics were - to get the sound right the Reload Kit key combo worked (but the graphics stayed put as they were already right but different to the sound)
So the guys at Elektron need to look into this
Please advise @dtr if you send a Ticket or I will
I can assure you in my testing earlier where I used very obvious parameter changes the Kits were updating properly - but in this new project (perhaps a clue) or simplified/directed test the issue is certainly there
good catch, quite a nasty one if you rely on that feature
Elektronauts hive-mind at work! Good investigative work there.
So it’s some tracks and/or engines not reloading properly, not all.
My project was created pre-OS 1.50.
I had already sent in a ticket with the claim that kit reload isn’t working at all. That needs to be amended with your findings. It looks like I can only add to the ticket once it’s been read and opened by Elektron, which is not the case yet so have to wait for that. If you want to send in your own ticket in the mean time that’s all good with me. Let me know.
Analog rytm MKII and Cubase pro, the AR sends note on every midi track/instrument on cubase pro v 10.0.50 (overbridge disabled - connection MIDI over USB)
WHAT:
I want to send the note/data recorded on trak 1 and 2 on my AR mkII to my Virtual synths on Cubase…it seems that the midi events on track 1 & 2 of my AR are sent in all the channel of cubase, I mean like merged (like the OMNI ON) in one track and send to the daw. Seems is impossible to work in multi …is a omni off/on problem???
SOLVED : USE INPUT TRANSFORMER ON EACH TRACK
SETUP used on AR mkII
SEQUENCER MENU:
quantize live rec OFF
kit reload on chg OFF
auto tra switch OFF
MIDI CONFIG:
turbo speed OFF
out port func MIDI
thru port func MIDI
input from MIDI+USB
output to MIDI+USB
output ch TRK CH tested also with AUTO CH (same issue)
param output CC
encoder dest INT+EXT
pressure dest INT+EXT
mute dest INT+EXT
receive notes ON
receive cc/nrpn ON
QUANTIZE MENU
Track 1 and 2 send midi ON
MENU CHANNELLS
track 1 to 12 -> channel 1 to 12
track fx channel 13
per channel 14
auto channel 15
prog ch in ch 16
prog ch out ch AUTO
Seems like a Cubase problem? In Ableton, I have MIDI Tracks listening on a single channel, and it’s only receiving the MIDI Notes of that respective Track Channel (using Output CH: TRK CH)
I just tried now with Renoise 3.2 and I had a successful setup…strange that I cannot with Cubase 10 pro…
SOLVED, on Cubase the routing is hidden with a button called INPUT TRANSFORMER that allow to split the data by midi channel.
I’m having this problem on my MK I. Though it’s only happened so far in the project for the sound pack Future House with stock kits 1, 2, 5, 6, 8, 9, 10. Totally unable to edit the scenes to those specific kits. Likewise when holding down / having selected a scene to edit, no pads flash red, only kit 6 does of those listed (but params still can’t be changed). The only parameters that can be edited in said kits are ones that are already edited by the scene
AMP Page, HOLD Parameter : is it a normal behaviour? You have to turn the encoder to the right first. By doing that, the HOLD Parameter goes from 127 to 1 instantly. Then, you can increase the value by turning the encoder to the right. It’s not working like that on other devices who already have graphics like Digitakt and Digitone. Anyone?
The AUTO-setting is at 0 on Rytm but 127 on Digitakt.
Isn’t weird that you have to turn the encoder to the right, then it jumps to 1? Bug or by choice?
The HOLD Parameter defaults to 0 (AUTO)…I am able to turn it to the right immediately with no jumps.
It doesn’t go from 127, it goes from auto (marked with semiquaver type symbol). Auto varies whereas 127 is a fixed length
Not a bug, plus it goes to 1 from auto, not 0
But graphically, I was expecting the same behaviour as the Digitakt or Digitone.
??? The DN doesn’t even have a Hold parameter, and all of their Attack / Decay / Sustain / Release go from 0 - 127
So… the program change bug where connected Elektrons that have master length set to INF change patterns a bar late - that’s still not fixed? That’s insane, how many years has it been?
Found this on mk1:
can anyone confirm? thank you
