Would everyone be happy for parameter override, parameter write modes to be gotten rid of in favour of just plain automation?
I.e fader/knob movements are just recorded into the pattern rather than per step as they are now?
I’m guessing yes, but I could be wrong.
Sounds like a poll would be in order here 
It’s wishful thinking to have all the above I suppose, but I do like the parameter override system. However it would be awesome to have automation, not gonna lie. Especially for the filters.
Personally, I use the parameter override quite a bit and would hate to see it go.
I’d like to keep it per step but would also like optional automation for filter if possible. Alternatively, some kind of streamlining for multiple takes when bouncing would be good as that’s how I’ve been doing filter sweeps. My main concern is how it might affect saved projects using the current method.
I mean there’s no real downside to changing if there is an option to quantise automation per step/at note on and it makes the system way more powerful.
This is a tough one
The per step override is indeed quite handy and I’ve just got to grips with it in the workflow
However, if it’s making way for true automation, maybe it’s worth it? I’m assuming no room for both to co exist
I definitely agree a poll would be a good idea
I’ve gotten used to it but would let it go for automation for sure
I don’t understand completely.. can anyone please eloborate? But in any case please be careful about touching main options 
My vote is for automation all the way. However to please both sides, would it be easier from a coding/implementation standpoint to only allow the use of one at a time? Like having to turn one on at the beginning of a project, or if you tried to switch to automation after making changes in parameter override mode those said changes would be erased (with a warning message beforehand) and vice versa. Either way my vote is still heavily in favor of automation.
I’m not sure I entirely understand the question, but I regularly edit volume per-step in the sequencer. Sometimes for effect, sometimes for choking a sample that would otherwise hang over into another pattern. As long as I can keep doing that, I’m happy.
Automation would be cool but I edit pad sounds (filter, level, pitch, etc.) a lot after being played in/recorded initially. This comes with some disadvantages (like having the original sound being played when recording, instead of the sound after the edits) but it’s what works for me. Having a change that would heavily affect this would be problematic for me, especially for previous projects.
But automation could open doors for sure. A seperate option for this would be perfect.
I’d say automation would be cool. But if I’m not sure to understand correctly your proposal: does it means the properties of filter for example would disappear from the events properties in the sequencer like they are currently?
As if I understand correctly (no native speaker) its ‘Parameter override’ (A or B + Pad) against a ‘DAW like automation curve’? I hated that odd method at first, but now love it as it makes the machine unique full of character (dont know the SP)
I personally really appreciate to try getting the machine to next level, but man there are other things to do: more easy nudging/microtiming, more easy parameter locks, more advanced stepseq all in all, showing offgrid steps in stepsequencee, get rid of the running sequencer muting steps of random single pads when turning the filter knob too fast (CPU overload?) a drummachine first goal has to run the sequencer tight at all circumstances! That has to change please!
I really love the machine, but perfecting its current state seems much more important than adding new stuff to me. Okay, beside the long awaited analog filterboard of course, that definitly must happen, please 
It’s a show of hands post for future planning/roadmapping , not a ‘this is what we are doing next’ announcement.
The next firmware update is purely a bug-fixing, stability update. nudging/microtiming is a feature request. Have you posted one in the appropriate forum? (or +1’d an existing post on the subject)
I feel like the parameter override function is pretty useful in a performance/fill kinda way - would be a shame to lose it completely.
Thanks for your reply, appreciate it.
No, havent really posted it, mainly due to language barrier (esp technical things are hard to explain correctly) and i just hoped im not the only one with those requests and some advanced nativ speakers will handle it for me. Then the forum was off and i wasnt able to log in til yesterday…
The ‘dropout problems’ in the sequencer when turning filter knobs too fast is something i havent found in the forum yet (dont know what terms to use in the search option). Still, for me it feels to hard to explain in correct terms to open an official bug report for it. Wondering why this behaviour dont feel annoying for others too. My music is mostly livejams, i dont use automation stuff much, its mostly pure hands-on on the fly. In a live Situation its a real pain in the ass when the Kicks mutes for one hit when playing with the filters on a chord sound f.e.. At least the overall timing isnt influencde by this behaviour, which is of course much more important when the S2400 is master.
But all in all i really love the machine, its unique approach, its feel, its sound, groove… So, no rant from my side. Ill stop to not mess up the thread even further.
EDIT: Track 1 is the first that gets muted when CPU overloads is my current suspicion.
I have the same issue regarding the ‘dropout problems’ using filter knobs, esp on a few channels.
Automation would be way preferable. Would it editable or require a re-input for changes? Either way, i’d prefer it.
If one gives us PitchWheel and ModWheel Automation, then I vote for that.
I do use the per step edit a good amount to sorta automate my way through and honestly that’s where the s2400 shines. It’s really quick, so if that were lost it would be a shame.
Can we not have both and just have a global setting option? Or is it that volatile on a project file?