Im still quite new to Electron Machines and im wondering, how this reload pattern funktion is supposed to work.
In the Manual it states: “This is a special feature avail-
able in addition to the general, automatic, saving of patterns which occurs when patterns are
changed”
and : “The RELOAD PATTERN command is great when improvising live. Any changes made to the active
pattern, like adding bass line notes or similar, can immediately be undone.”
This workes fine, but only as long as i stay in the pattern. When im modifying a saved pattern (as in a live situation), then changing to another one,
when im going back to my first pattern it has the changed state. With no chance getting it back like it was. the reload button doesnt work anymore.
So how is the workflow here? im constantly afraid of accidentily changing my carefully thought out patterns! Wouldnt it be cooler if it would save the manually saved state in addition to the autosave? so you could always go back as long you dont oversave manually?
I agree entirely. Auto-saving patterns impedes my workflow (for the same reasons you mention) rather than benefits it. And it’s easy enough to manually save a pattern should I want to keep any changes.
I’d like to see this auto-save feature removed. It just seems counter-intuitive.
I tried it again, doesnt work.
It works with kits, though.
So if i do Parameter changes it gets autosaved, after goint to another pattern linked to another kit, and then going back, it still has my changes but im able to get back to the saved state of the kit (with a reload).
But with Patterns it doesnt work for me. Somehow incoherent.
Yes, I’d like to see that change too. Pattern editing and saving should work just like kits do.
For now there are completely different storage workflows for all parts of the A4’s structure. Patterns, Kits, Sounds, Projects, Globals all behave differently in terms of saving, editing and recalling states.
Just a way to put the Aut-Save on/off would be great.
But I need the auto-save because it’s the only possible way to record over existing patterns in chain-mode.
The solution would be a memory-bufferfor eatch pattern. So maybe that’s not as simple as changing the software.
I doubt it will be simple or even if it will be feasible at all. Patterns take up a lot of memory, that’s probably the reason why we don’t have that feature for now.
Anyway, what would be missing or what I currently miss is an indicator to see if a Kit has been changed from its last saved state. Then also a compare function would be nice, but then we’d be in conventional workflows anyway and one could just implement some manual save mode like on all other machines. I wouldn’t mind if there would be some kind of cross-pattern edit buffer.
The thing is, I’m not a big fan of auto-save. UI designers tend to think an analog metaphor of manipulating data destructively is more “natural” and easier to handle for people. Yet it means giving up all the benefits of non-destructive editing that made computers great for the last 30 years…
Absolutely not, it is just the ‘stupid’ way an Elektron works! Every gear saves in a normal way and you can recall the save after turning all the knobs, it will still load your save, but Elektron made it more complex, even stupid to jam sometimes. It’s all because of that +drive in combo with non volatile memory and autosave! Autosave off has been requested many times for a lot of machines! They learned a bit and now make other macines without the stupid kit system. That’s a bit better but the autosave is still there! With MD I named all my kits the same slot where I used them (f.e. kit H12 is actually pattern H12 and so on…) Same with A4, but here you can save even way more! Nobody is going to reload a project or pattern when transitioning to another pattern in a jam and that’s the biggest problem!
yeah depends, I prefer to just copy my patterns I like and make variations and rename instead of working with the hassle of kits and fucking it all up on the other patterns!
