Perform Mode (or whatever to call it) in which adjustments are not automatically saved. You can play and modify your pattern but next time you load it it’s intact. This would also protect your patterns from unwanted unintentional changes from touching accidentally to encoders or CCs coming from MIDI setup.
So just adding “save state” to already existing Perform mode?
Doesn’t saving a kit do just this? An honest question.
Well, clearly people have different ways of handling this problem… Saving it, saving that…
Simply put my idea is just NOT automatically saving anything. I think you know when you wanna save your pattern. At the moment t it’s in a state you wanna keep it like that. Then you save IT (not the whole project). Other times you don’t need to worry if it’s somehow modified (touching accidentally, MIDI from other gear or from DAW) and then automatically saved. Simply like it is in all (?) the other synths on the market.
EDIT: I can see my own thinking is qoing a bit off from original idea. More and more I think about that from my own perspective and my own setup I would prefer the idea of having this “normal mode” where you save individual patterns by hand. Rest of the project is intact. At home you normally work with one or perhaps few patterns carefully and know when those are finished and when it’s time to save them. You may take some other patterns as starting points and experiment with them and then go back and forth between patterns etc. You may use MIDI gear or DAW (sending CCs) all this can cause hidden problems to your project. So saving pattern X would be a clear decision that X is finished and this you wanna keep like that. Other patterns are similarly earlier saved in the project and then safe from unvoluntary hidden modifications.
I’m sure someone has said this already, but it would be great if there were an option to have korg-style sequencing, where trigs remember their p-locks when you unselect them instead of losing all that data.
Firstly because it’s a useful performance tool for making melodic variations.
But also because of all the times I’ve accidently hit a trig (for instance when trying to mute or select a track) and then lost all the data on it.
2 Likes
In the meantime, my workaround is to randomise a page and lock all the parameters to a trig. Laborious but also fun.
1 Like
Randomization of a specific parameter across all trigs in the current track’s sequence, ideally with an adjustable amount.
1 Like
I’d love to have more options to work with velocity on all Elektrons. Tonverk would benefit the most from this with its velocity layers, but other machines as well.
Some things I’d love to see:
- Disable velocity recording when using the onboard keys to live record. Or at least give us the option. The onboard buttons don’t register velocity, so they shouldn’t fix a value to steps recorded live with these buttons. If it’s not possible to deactivate this for some reason, give us the option to make the default velocity value set in the trig ogs the value that’s recorded live. It already does this when entering steps by using grid mode, so why doesn’t it do the same when usi mg the onboard keys?
-
- Allow us to use velocity as a modulation parameter for LFOs.
2 Likes
Just submitted this bad boy to elektron:
-
Syntakt specifically: Please give us the NOT versions of the N:X trigger conditions (!(3:4), !(6:8), etc). I’d love to be able to set a trigger to not fire on the 7th out of 8 loops, for instance, and it’s not always feasible to just make the pattern longer. Also, perform kits.
-
Tonverk: page looping. Also, individual control of MIDI channel per track and ability to turn their MIDI channels off. Tonverk can’t be used on the same MIDI node as other gear downstream from a different sequencer right now because of this and it’s really annoying. Also, pattern mutes in song mode as the digis and syntakt have and euclidean sequencing.
-
For all Syntakt/Digitone2/Digitakt2: An “internal MIDI machine” machine type that allows for using one sequencer track to trigger or LFO or envelope modulate things like global FX parameters and the macro mod sources. Preferably this would not have a dedicated MIDI channel but be able to specify in the LFO’s or triggers a target that was either global or machine specific (like a trigger or LFO that modulates aftertouch or pitch bend on every track at once or just on one track). This would allow people to do much more elaborate sound design sequencing on their machines without needing either a separate MIDI control surface or MIDI loopback.
-
For all Syntakt/Digitone2/Digitakt2/Tonverk: Page looping settings incorporated as a possible setting within song mode like pattern mutes are. This would allow for something like a scenes approach.
-
Increment option on triggers for any machine that can support it (needs to have conditions and probability also available for these IMO). Default is always ADV:1. JUMP:N to go directly to N step, ADV:N to advance by N steps, BACK:N to step backwards N steps, RAND for a jump to a random trigger. I’d say JUMP/ADV/BACK/RAND in one encoder selection, N in another. Parameter locking specific triggers with conditions like this would be really sick and updating the full sequencer to BACK:1 instead of ADV:1 allows for easy implementation of pattern reverse.
(3) and (5) are the ones that I think would have the most impact on people being able to make really interesting music. (5) is obviously influenced a lot by OP-XY/Drambo step components but I tried to make it “elektron-y” in suggested implementation rather than just say “do step components” because I think step increment type/amount has a better chance of showing up one day than something like accumulators and a lot of the other step components on OP-XY are things that would be addressed by (2) anyway.
2 Likes
QoL request for Transfer app: a big button to perform a single-click backup of your entire device (projects, sounds, samples…)
5 Likes
yeah agreed on this one, it’s not intuitive.
3 Likes
I’d love to see microtiming as a modulation destination.
4 Likes
Implementing a dual sample player machine on some other Elektron samplers would be fun and useful.
1 Like
would love to be able to hold a trig down and randomize the current page as p locks per trig by hitting page + yes
4 Likes
Parameter slides should be a must… all the new elektrons feel hindered without it
9 Likes
Feature Request
I am not sure whether this has been requested before cough, cough:
Delay parameter on the AMP page that would delay the AMP envelope’s attack phase: for funky, LFO-able swings, grooves and for sound stacking via track layering 
3 Likes
While I endorse the request, you can achieve something like this now in reverse by randomising the page and saving the locks on affected encoders to a trig, a tip I saw on here a few years ago.
2 Likes
This is a brilliant idea - I’d like it as a performance control as well outside song mode. I like the idea of adding performance depth to the page setup / page button. Also, it would help break tracks away from each other even further, making each pattern more fluid… exciting thought
Yeah it jus frustrates me that if I want to introduce one bar, then double it into a two bar pattern after a couple of bars, then do that again, that’s either a manual task or individual patterns and it would be cooler to program that behavior into the sequencer so I can be actively performing with a different track
1 Like