Model:Cycles Q & A with Ess

[tallrobphilp]

The dual LP/HP filter on the M:S potentially has the same issue but I think it’s just part of the experimental nature of control all. I could live with it!

[darenager]

Yeah maybe but as @tallrobphilp says experimental could be fun, plus if it gets too out of hand hit reload.

Another idea might be to limit on a per pattern basis which track/params ignore ctrl-all.

[pselodux]

how would you then parameter lock it? And it would be missing from the panel - it’s a lot to consider in the end. (Also the design principles of the Model:Series goes against secondary functions for the most part)

A “slow” switch in the TRK menu maybe? Switching it on makes the envelope symmetrical, with equal time for attack and decay.

[Seta]

I replied in the same thread, to me just 2 or 3 settings DFAM like via menu (FAST/MEDIUM/SLOW, which could be shared with the LFO Menu) would be the easiest and maybe less DSP resource intensive. Could also be p-locked like all other LFO parameters.

In DFAM there is just two settings and that already makes a big difference sound design wise…

[AdamJay]

For some reason the attack conversation has been brought over into this thread, when all I was doing was linking the post with the workshop recording link for @Anfim
Use THAT thread for that conversation.

Let’s all collectively get back to the intent of this thread, Q&A for Ess, and limit our own break off conversations.

The forum software hasn’t been cooperative lately with regard to moving posts into other more appropriate threads, so us mods need the help of everyone in this thread to keep it tidy.

Thanks!

[Drumunkey]

Hope I didn’t miss this question… @Ess, Considering that via the side port you can power the M:C with 5v USB, why can’t it be powered via the actual USB port? Would save cables when plugged into say an iPad that’s using the CCK with power charging.

As it is now, there’s like 3 mutually explusive ports… Main power, side battery power, and a USB port… Seems odd.

[pselodux]

why can’t it be powered via the actual USB port?

Probably due to ground loop noise, see OP-Z/OP-1 sharing data and power over USB. Keeping them isolated from each other means no background whine when plugged in.

[Seta]

@Ess I have a question regarding how lfos are implemented inside M:C, are they part of the machines or part of the track/sequencer?

I ask this to see if (at least theoretically, not as a feature request which I already made ) LFOs from one track could be sent to other tracks; maybe very difficult to implement if they are part of the machines but maybe not so difficult if LFOs are part of the sequencer/tracks. I have no idea about coding so I am just asking.

In the studio I am using it as a two part monophonic synth with individual outputs (dry, no reverb or delay), that way is easier to multitrack from it, at least for me.

Right now I am using a tone machine as a drone machine with lfos sent from ableton (great fun) and I wonder if something like that could be accomplished within M:C, two part/2 outs drone machine with 3 lfos each.

As I said I can easily accomplish this in the studio but for live performances it could be a nice feature to have…

Thanks

[Drumunkey]

Excellent point! I returned the Uno because of the horrible usb buzz/hum.

[Seta]

@Ess As M:C was designed with Max, is there a M4L editor or could be one released in the future? Would be nice to have one to control and design sounds via push 2 …and my M4L knowledge is close to 0…

[pselodux]

From what I’ve heard/read, it was prototyped with Max, and then Elektron’s DSP guy remade it in assembly for the final product, so it’s not actually using the original Max patch.

edit:

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!

[Seta]

Ok, thanks. There is already a M:S m4l device around, I guess is a question of time for someone to make something similar for M:C

[captain8]

Hi Ess, I’d like to know what your thoughts are surrounding sampling and the model Samples, do you like the idea of things like internal resampling and sample slicing that would place slices on the pads etc… this is not a feature request just wondering how you view such concepts…

also what are your thoughts on intelligent randomizers in instruments like the model cycles and model samples ?.. Regards

[iskin]

I have the same problem with pads! Sensivity is very very poor! I dont want to beat off my fingers. it is really not usefull! Do yo know, are all devices go with these pads?

[craig]

I find no one needs 127 different velocities for the pads, especially on drums, so have you tried reducing VDep in the Pad menu? I set mine between 30 and 50 and it makes them very useable

[Soarer]

Model:Cycles

Glad you guys enjoy it, looking forward to what the Model:Cycles music will sound like a year down the road - I promise you that it will be completely different in sound.

Because of the sound design actually possible or because more machines will be added?

[craig]

Interesting! Possibly a bit of both? In the original context of the post, it seems to be that once you discover little tricks and certain settings it really opens up compared to what you thought you could do with it when you first got it. Let’s ask @Ess for clarification!

[cold_fashioned]

I always took that comment to mean that as you spend more time with the box, you learn more of the nuances and ways to play with the “limitations” to coax more and more out of the machine. And perhaps it’s the answer to the riddle “when is a drum machine not a drum machine?”