Parameter lock not working in performances

I have 3 performances, 1 has 3 locks, 1 has 26 locks, 1 has 19 locks. Parameter lock is no longer working. Have I run out of disk space for locks? If so I thought I would get a message. Or could there be something wrong with my Rytm Mk2?

Handbook p. 28-30: 48 parameters in total lockable per kit across the 12 performance macros.

Edit: same for scenes.

3 Likes

Thanks a lot, at least I know there’s nothing wrong with my Rytm. Can’t believe it’s so low though, I’m putting a live set together and I’m out of space before I can even finish 3 performances. Am I doing something wrong or do others find this very low?

Yes, I also find the number low. A workaround can be to use several kits (with same sounds but different scenes/performance macros).

1 Like

Ah, nice workaround hadn’t thought of that. Do you know if it is possible to remove specific locks from a performance…for example if I want to keep a performance but get rid of some unnecessary locks so that I’ll have more for another one?

Yes, you can delete single parameter locks within a performance macro in performance edit mode. When you select a track with TRK+PAD and then press the performance macro, parameter lock values appear with inverted characters. You can delete a parameter lock by pressing the corresponding data entry knob.

Sorry - it is a bit difficult to explain in writing. In short, deleting single parameter locks is done by pressing the corresponding encoders (i.e. in the same way it is done for parameter locks on sequencer steps).

Another important point of performance macros as compared to scenes is that you can combine them by pushing (or assigning to the qperf knob) several performance macros at the same time. This way you can creatively combine several performances that each impact a small number of parameters.

Got it, you’ve explained it very well, thanks!

Another great tip I hadn’t thought about。 Hope the limit on a kit will be removed in an update, don’t see the point of it, but at least we have all of these workarounds. Thanks! :grinning:

I guess it’s due to hardware limitation. This stuff has to be adressed from the OS by the hardware, so it’s not like there’s no end and you probaply wouldn’t want your Rytm to glitch out due to cpu usage^^
Parameter locks also have a limit (then you get a message on the screen), although I’ve never reached the limit on any machine.

2 Likes

This. Each parameter modified by a performance needs some time. 48 is already quite a long list to work through to still get the impression that it happens immediately.

2 Likes

Ah, ok, makes sense Schnork and tnussb, thanks for explaining that. It’s still the best drum machine ever, I just need more time getting to know its intricacies and preparing for these issues in advance. :sunny: