Model:Cycles Q & A with Ess

What was the rationale behind not giving the Model series a battery compartment and going for the handle instead? Regarding the handle - why the external cable connecting the battery compartment to the plug? I like the option to tilt the M:C, but I find the cable looks not very elegant.

Just theoretical pure for the sake of interest. Are there major differences between the DSP in the M:C and the Prozessor of the Rytm. Could the rytm theoretically run those Maschines you put in the M:C.
Just daydreaming about a rytm that is equipped with those 6 dream maschines in addition to the analog stuff and the samples :wink: But for now I´m ok to put them side by side.

As I understand it you developed the pure algos for the Maschines completly on your own in Max as prototypes, right? Was it always those 6 maschines and you polished each of them, or where there many others and those were the ones that were the keepers and just needed a little polish?

Did you have a prototyping hardware which resembles the interface of the hardware, or did you focus just on the sound and then make it controlable with those four macros?

I got one:

Currently its very hard to visually distinguish between actual sequencer trigs vs trigless locks. Is there some insider knowledge that can help here? The diff between a fully lit and not isnt very clear right now, due to how the trigless lock led indicators “flicker” - wouldnt it be better for them to blink steadily or something instead?

Another question: As there doesn’t seem to be a dedicated HPF setting for the reverb nor delay, is there some HPF applied to the internal wetpath by design? Using reverb/delay without any lowcut in the wetpath muddies up a mix fast…

Sorry, one more question: Is the optional MIDI THRU function handled like a MIDI soft thru? As in, not an electrical copy of the data sent to the MIDI IN terminal, but a new MIDI signal reconstructed by DSP? I ask this because IME MIDI soft thru has always been an inferior solution versus a “proper” hardware MIDI THRU port, which just makes an electrical copy of the MIDI IN

thanks

1 Like

@Ess Does the M:C have the same reverb algorithm as the M:S? If not, what are the major differences (if any)? To me, the M:S sounds like a kind of Hall reverb, but I could be mistaken, especially since it sounds kind of Plate-ish when fed cymbals and crashes.

@Ess : as stated in another topic, what’s the point of the “pattern save” function ?

Does a slow resetting random lfo produce a new unique value per key strike (details here) ?

Knowing before its arrival may prevent some honeymoon blues if nay, please say yay :loopy:

Yes it does change on every pad press but I can not asure you it does the way you want. Having lfo assigned to pitch will give a different one each time I hit the pad. Completely random? That I do not know

2 Likes

If it is set to reset the ‘shape’ and is slow enough to be near static and it is changing per strike then all is good for me - this is encouraging - as i mentioned in the other thread the A4 wasn’t doing this originally so it looks like this random behaviour is retained - it’s not a Hold mode, but it’s close enough for me - thanks for chiming in, in any case i am sure i will adapt if it’s not like that, and maybe breaking old habits is a good thing - but this sounds promising :thup:

I have been trying it a little bit more; with LFO velocity set to 0 random LFO behaves like Hold (the given random value stays for as long as pad is pressed no matter what LFO multi value is entered), pressing the pad again gives a new value each time.

How random the LFO is I can not say, I can not compare to other Elektron LFOs but I would not say it is as random as an analog sample and hold, sometime feels like if there was some kind of pattern to it, like sometimes it just goes up or down for a few times on a row but maybe that is me just going paranoid…:sweat_smile:

2 Likes

that’s what i wanted to hear - we’re definitely on track

1 Like

I would like to try and patch up some replicas of the machines in Audulus while I wait for my unit. Can you break down what sort of algorithms you were using and how you were mapping/scaling the modulations to the patch to the 4 macro controls?

Can tracks be nudged, a-la other boxes. All tracks or just one?
Or can you only nudge trigs?

you can nudge the tracks by holding TRACK and turning the main encoder

5 Likes

Can you Latch CTRL ALL? I found myself needing my two hands when using CTRL ALL.

If not, Feature Request.

Do the trigs have velocity, or are they fixed?

No

You can edit velocity per trig, standard beeing V100. Retrigs can fade in or out

Like all the other boxes. :+1:t6:
Struggling over here…the sounds are so sweet…uuuhhhggg!

1 Like

The CPU is a Coldfire MCF5441 with up to 385 dhrystone 2.1 MIPS @ 250 MHz … Same one as in our other current lineup of products sans the Octatrack. (But before anyone asks - no that doesn’t mean we can run anything on everything, it’s a general purpose CPU and it does very different things across all machines.)

All DSP is done in assembler. Our process for this project was that first I made prototypes in Max which I made Max4live Devices out of and sent out to all my colleagues. We then collectively tested them and improved the patches based on the feedback received. After we were happy with how they sounded we started translating the patches to run on hardware, and this was quite a long process where I worked closely with our amazing DSP engineer Oscar A who dealt with my stupidity for a few months until we had all of the machines running on hardware. Thanks Oscar!

4 Operators are a very good amount I think, it’s a perfect balance between easy to handle and versatility. Add different waveforms to the mix and some other tricks, not really necessary to go above unless you want to do some very specific things.

The FM is not FM at all; it’s phase modulation just like the Yamaha stuff etc. PM has many advantages, but the biggest one is the possibility of doing feedback without detuning the sound.

Not really, I was just messing around with some ideas. At the time I was obsessed with trying to make all parameters feel ‘smooth’, so I came up with the oscillator balancing thing. At first it was sort of a mix between additive synthesis and chord intervals, but we later as a team made it much more musical by introducing the idea of using chord inversions for the interval mixing.

The voice itself is simple - it’s just four oscillators that each play the same wavetable. I made the waveforms with a max patch which later turned into Hard/Softcore. All of the tables in the Cycles are made strictly with additive synthesis. Sorting them in the particular order took a long time, it was really hard to find an order that felt logical and nice to sweep through, hehe.

I would like to add graphs of all the waveforms in the manual, but I haven’t had the time to plot them out yet.

The Kick drum is inspired by classic drum machines but with some FM sprinkles. It started off a bit wilder, with a ratio control and stuff, but Tone is so much better for that and I wanted the Kick drum to be fool-proof and always sound fat and punchy. Plus, having the setup it currently has is super specific and allows for some very cool ticks. I think there is so much more to FM than what you would expect, so having the triangular waveform shaping that goes to feedback is kind of unique and something I think sounds really good. Can’t do that on the Digitone!

I hope so, I think it’s very necessary for live performance.

From what I understand it was to keep the form factor slimmer and the handle was an interesting design decision. The cable is quite stiff, so it doesn’t really pose any issues.

Theoretically yes, but in practice the Rytm does a lot of other stuff so it won’t have enough power to run it. So short answer: no. Long answer: nooope.

Yes. There were one patch that didn’t make the cut, but it was mostly due to time constraints and its structure being radically different to all the other patches. The system in the Cycles that Oscar (DSP engineer) put in place is quite ingenious. It’s a huge structure that can dynamically change, this is what allows us to swap machine per step. It’s wild!

No, it was all made in Max and we used Ableton Live to try the different machines out as Max4Live patches. (No, I can’t share the patches and they also sound worse than the final product, much clickier and less refined overall. But the sound is pretty much the same)

Yeah we should try to improve upon that, I also think it’s too hard to distinguish.

The Reverb does have a Tone parameter (Hold FUNC and turn Reverb Size), but the Delay has a fixed HP/LP setting that rolls of nicely.

Yes, it’s a soft Thru, but it’s done right so… Shouldn’t pose any issues. :slight_smile:

Yes, it’s the same. I think I’ve commented on this before, but it’s simply the material being put into the reverb that is different, and therefore the tone of the effect itself is perceived as different too.

Depends on how you want to use it. You can see it as a save point you can go back to in case you made a change to the pattern you disliked. Or, you can use it as a performance control, save current pattern status, mess with it and then reload to the point before.

Apparently yes, I had no idea. Really cool trick! Hehe.

No, the mapping and scaling is our secret sauce. The algorithms, maybe. :slight_smile:

38 Likes

That was gonna be my guess :joy:

1 Like