Totally agree with it!
Yea, the time-out thing just seems like a weird thing to have there…
My main frustration is how wonky pattern changes can be even all by itself. I tried having it be master clock to my OT and eurorack and that’s very messed up when changing patterns
Easy feature request:
Default retrig length should be 1/16 (instead of 1/4). This is the length of one step (or one trig) and makes it much faster to program ratchets and triplets.
Easy feature request for the TONE machine.
When holding FUNC and adjusting COLOR, the incremented values should be integer powers of 2. IE, it should snap to [0.125, 0.250, 0.5, 1, 2, 4, 8]. These are octave ratios, and would be much more useful than whatever useless increments it currently does. (No offense, I you)
Also, the CONTOUR parameter should be inverted. Currently, lower values make a slower modulation envelope, and higher values make a snappier envelope. It should be inverted so it behaves more like the DECAY parameter. This is more intuitive. Coincidentally, CONTOUR sits directly below from DECAY, so that’s nice.
Expanding on that, perhaps CONTOUR should also behave like the LFO SPEED parameter, with positive values making a positive envelope, and negative values making a negative modulation envelope. Easy way to implement pseudo-attack.
A REALLY EASY, REALLY GOOD WAY TO IMPLEMENT ATTACK
Decay should act like the LFO SPEED parameter on the TONE and CHORD machines only. IE, positive values create normal, falling decay of volume. Negative values create a rising volume.
Perhaps the decay parameter should do this for perc machines too, but maybe not, since having more control over DECAY is more essential. Maybe you could offset the inversion value. IE, value 63 is usually the center, but make it like, 8 or 16 instead for perc machines. Great way to have reverse hits, without sacrificing much decay control.
I always thought the DECAY knob should also be an ATTACK parameter, accessed with the FUNC button. But I think this would be an easier way to code attack functionality.
EDIT:
I’m thinking more about this. Combined with the NUDGE parameter, you could achieve some pseudo-envelopes with this. This might be at the top of my wish list. So easy to do and so versatile.
For envelope additions maybe the gate button could be employed to offer different A/D profiles?
100% TRIG condition, right now it only goes up to 99% and I don’t really get why.
This would be different from having no TRIG condition because a TRIG with 100% would be always played regardless of the track’s condition value. In order to get this effect I find myself using the “not fill” condition but it’s just a hack (I might want to play that TRIG during a fill too).
because a trig with no conditions is 100%?
A trig with no condition will be affected by the CHANCE parameter…he wants to have a Trig that is always played, regardless of the CHANCE value.
right.
can you P-Lock chance? that might be able to be set to 0
Ahem.
Nah you can’t
oh well…toss it in the bin.
I explain the difference in the next sentence, it’s really not that long of a comment, you should read all of it
SORRY SORRY…went off. a little salty today.
there are werk arounds and diff ways of doing stuff. dont focus too long on what cant be done and get stuff done.
…Pan locks?
Would be cool to see ping pong or random playmodes on a per track basis, seeing as the model line doesn’t have master pattern length it seems like this sort of stuff would make sense on them.
Just want to go on the record and request no addition of attack.
My favorite drum machines, the DR-110 and TR-606 also have no attack parameter. Model Cycles is right in there with them, where distinct sound meets simplicity. I love it.
Please don’t sacrifice your design philosophy on this one, Elektron.
I do not understand all that “Anti-attack” movement and the “flags” that come with it, it …comparing a 35 year old drum machine (TR-606) with only level knobs to a modern FM synth, because it is a synth.
Tone and chord machines are pure synth engines which would benefit a lot from an attack setting, so would the drum synth engines IMHO …
M:S does not need that ( which could also be argued)as you can load samples with smooth attack.
It is not a crazy feature request like a multimode filter, or a wavetable machine, is as simple as it can get as a feature request.
Those of you who do not need Env attack are free not to use it if you wish so, but let the rest of us have the option to choose too…
So I insist to ask for an attack setting, I do not care the way is implemented, knob/menu as long as it is added
I’m sure attack can be done in a way that doesn’t ruin the design philosophy.
I have found the need for a softer attack many times already and used the LFO for it so I would welcome it. Not that necessary but a welcome help for sound design.