certain features might benefit from finer controls i think. might be the easiest way to make this thing ten, one hundred, or one thousand times more powerful.
Maybe I’m mistaking but I remember having seen usb gain in the settings menu. Page 6/7 or 7/7 maybe ?
I recorded on mac without problem using model:cycles as input/output, I got problems when using different drivers as input/output ( ie: distortion and sample rate problems). Same on PC with using standard asio. Recorded in bitwig in both case.
I just sold the unit so I can’t conduct further testings at this point.
1 Like
i know what you’re talking about but unfortunately the USB gain is not the answer. i’m not entirely clear on what that function does but in any case it doesn’t offer attenuation, only gain.
Pretty sure you can preview a lock while sequence is running if you don’t click the data button to enact the lock, but just press the associated track (1-6) button (while still holding the trig down for the lock). It’s a bit tricky because you then have to turn the data button to move on to the next sound and then push the track button again, but it saves waiting for the sequence to hit the trig again (and keeps the number of saved locks down).
what about “double-click” on the FUNC button to hold, like a caps lock sort of thing?
1 Like
How about an option to have menus automatically close after a settable amount of time without use (5-60 seconds).
1 Like
Full parameter revert when using Control-All like the Digitone.
Presently If you turn more than one parameter with Control All it will not revert those parameters - only the most recently changed parameter. Then you have to do the reload pattern which is like double the work just to revert.
And please… Remove the timeout of the Control All function.
Option for global tempo. It would be great to be able to gradually change tempo and play multiple patterns in a live set
1 Like
Could it be possible that Model:Cycles (and Samples), when configured in Midi Sync to accept midi clock, and to send midi clock, DO NOT send its clock when it is receinving an external clock.
Actually I have chained the Model:Samples to the Cycles and I am sending from a midi controller, from time to time, an external clock and start/stop commands to sync several equipments.
When I do this, it seems that Model:Cycles still sends it clock on the midi out which is connected to the model:Sample and this last one receives 2 clock signals ?
Not to speak of my midi bus highly sollicitated.
Why I keep the Send midi clock feature on ?
Because on special occasions I want to stop thegeneral clock send for every equipment and start playing the Model:Cycles from its keyboard and have its tempo sent to its model:Samples slave.
We see in the Tempo menu that model:Cycles (and Samples) is able to detect the external midi clock (could it display the corresponding BPM would be another nice feature), so it should be possible that it stops sending its own clock ?
I would like the ability to scroll through the presets via knob, while the sequencer is in real time record mode and record my knob movements into the sequencer, very similar and akin to the capability of sample slot switching on the Digitakt via the source knob while the sequencer is Live recording!!!
hopefully not repeating someone else (there’s a lot to go through and i did go through the thread but just not today) but a “lock mode” for the 16 bottom buttons would be an amazing feature: where you could store various programs per button and perform them live/into the sequencer even maybe. this would allow for all sorts of pseudo-features including scales, jumps in parameter shifts not possible instantaneously with knobs, etc. but… yeah… hopefully i’m describing it well-- each button would store a preset or set of parameter changes and you could play it on the lower keyboard like how a sampler keyboard plays sounds on each key basically.
Rytm does this with “scenes”, so perhaps that’s the more appropriate terminology to communicate
Hi,
There should be a way to change a track parameter on all tracks by sending one CC on a dedicated midi channel , the same value on all the tracks, especially for pan and volume.
Actually if I want to changfe the volume using a midi expression pedal, I need to send 6 times the same CC value, one for each of the track.
Its is very not easy to manage, especially when you have Model:Cycles and Model:Samples in the same midi network…
Would be cool if func+lfo-speed knob could adjust the lfo depth
3 Likes
Just hold the LFO button and turn the encoder for the parameter it’s controlling to change the depth.
8 Likes
Merge tracks: I would love a command which “merges” two tracks into one, while preserving the patches/machines that are dialed in for each track separately. In cases with a “clash” - where the merged track would ideally have two different machines playing at the same time - the original track’s patch/machine could take precedence.
LFO to multiple parameters: it would be great if an LFO could be used to blend between entire patches. For example, one could press two p-locked trigs while on the LFO dest option to assign the LFO to all parameters that differ between two machines.
Really though it’s obvious you guys (Elektron) know exactly what you are doing, and I think the device is basically a work of art already. Bravo.
2 Likes
How would it work? There’s only one LFO knob
I guess my idea was that you’d still have only a single LFO but it would modulate two (or more parameters at once. No need for multiple knobs, just multiple destinations.
4 Likes
I really just want the official battery 
3 Likes