Model:Cycles Feature Requests Thread

Agreed - I think this is more about resetting the clock though?

Of course it does I use it all the time. It saves your pattern.
Oh - what do you mean by remove the confirmation and how would that make sense?

I think it’s good to have a confirmation. The shortcut doesn’t need FUNC held down so it’s possible to accidentally trigger it if you hold the settings button for too long.

Pattern change options would be cool.

My problem is I try to change a pattern in time but fail. And wait for the next cycle.

Since we cannot update pad sensitivity, haha, how about a global option allowing instant pattern change. Yeah? Thanks.

  • Global & Pattern Mutes
  • Faster Project Save
  • Proper Octave Up/Down
1 Like

Can we please have the ability to take selected tracks out of the control all ?
like I want to mangle my pattern but I don’t want my kick for instance to be changed, I found this to be a big limitation for live jams and it seems easy to fix with an update (unlike the usb-c, alright I won’t go there)

2 Likes

Please, please, make that when in Settings->Midi->Sync when Clock Out is selected, the Clocks midi messages sending only starts when M:C receive a Play/Continue order.
AND let the output sound go to output when Clock in is On without receiving an external clock, Clock Out off and we press Play ??? It looks like a bug ?

While it would be nice to have a simple toggle for each track to manage this, you can still parameter lock anything you don’t want affected by Control-All. Actually it’s more creative this way, as you can leave certain parameter locks off for a small number of individual trigs. Only small parts of your tracks will be affected in that way.

3 Likes

Acid machine.
step recording.

1 Like

so for every pattern and on every track and on every trig and on very param you gonna go in and lock it? while playing live ?

Yep, it’s the only work around at the moment. And no, not live. Prepare it in advance :slightly_smiling_face:

1 Like

Unfortunately this doesn’t work that well since the sounds - especially the chord machine is still a bit affected by turning the knobs that are locked.

Really? That’s a bug then, right? Parameter locks should always override Control-All.

1 Like

Try it - it’s audible, and it’s not changing the locked parameter.

1 Like

That is contrary to the MIDI specification, so I don’t think that it’s a good idea.

1 Like

very much lack a filter or EQ especially for hats! I can’t create 808-like hihats, because hat’s need to be equalized or filtered in low and middle freqs!
Hats are to huge and retrigs are not nice at all!!

I would really love Fn+rightmost trig for octave up, Fn+leftmost for octave down…

9 Likes

Ok, I was not knowing about this. Problems are that:

  1. When Clock In is On and Clock Out Off, I get no sound from the model:Cycles ?
  2. I want to use an external midi controller to send clock on demand, so I don’t need the Model:Cycles clock being sent to Model:Samples and other flangers after it, but if I want some output from Model Cycles I must engage Clock Out ???
  3. But I also need to be in position to press the Play button on the Model:Cycles and have it send synch Clock to its followers ???
  4. This permanent and not always necessary Clock saturates my guitar pedal board midi with its flow of useless messages ? Even when my external controller send the main Clock.

Have you a link to this midi standard rule ?

Thanks

When the sequencer is running or when you are manually playing the tracks?

Do you mean other output (like Note messages) than clock messages?

What devices do you have, and what are the MIDI connections?

The MIDI 1.0 specification is here:
https://www.midi.org/specifications-old/item/the-midi-1-0-specification

1 Like

I see your point - a parameter lock on a track seems to be safe from glitching under CtrlAll knob movement (in this case the chord type) whereas the SoundLock is momentarily affected if the tweaking lands on its step - seems inconsistent, certainly undesirable - it’s necessary to parameter lock on top of a soundlock - but a ctrl all adjustment would ideally not affect the soundlock … especially as it’s fleeting and therefore glitchy - this may fall into a feature request category (make soundlocks immune to ctrl-all) or it may even be an oversight - i’d report it if i were you and see what’s advised

2 Likes