Mono Sequencer, automated transposing & being a step behind

[Dom Murphy]

Hello

Been playing around with the Mono Sequencer and quite like what I see / hear

I've programmed in a set simple transpositions in a clip going from B to G# which trigger on the 1st bar, 5th bar so the Mono follows the tracks chords. However, when each clip triggers it's 1 beat behind what it should be, so the 5th bar plays 1 extra note from B before switch to G#. It's like latency but I can't figure out where I need to correct it. Equally, when I trigger the sequencer fresh it will play 1 note of whatever previous transposition was playing before correctly playing the right sequence.

If I play the transposition in manually it is fine, only when I want to use a clip sequence.

Any ideas? I've watched the videos for this device on YT and it doesn't happen there... so I'm guessing I have something set up wrong.

Any help is super appreciated.

Dom

[Machinate]

It's pretty simple; you just need to set the note just before the bar, instead of *on* the bar.

[pepezabala]

what machinate says. mono seq is great, but unfortunately does not look ahead. So:

- turn off grid in your midi clip (ctrl4)
- select all notes (ctrl a)
- drag all notes a bit to the left


then you're set.

[Machinate]

it's basically something about quantum space time, and the linearity of time in normal computer systems.

[Dom Murphy]

Thanks all for the answers and I was nudging the note slightly though I discovered the culprit.

For my default midi set up I have a bunch of Midi Effects that I commonly use (like Pitch, Scale, Chord). I have these grouped into a device and this is placed before any instruments. I recently added a small M4L device that allowed me to emulate a Mod Wheel (my keyboard doesn't have one) and this was the culprit, as soon as I removed that device the midi was back in sync. I'm guessing that this device was adding a very small delay in the pipe...?

Moving this (and the whole midi tools block) after the Mono Sequencer fixed the problem and still allowed me to have the ability to freak out with my virtual mod wheel.

Seems ok so far... though does get a bit funky still - but no where near as bad.

Dom

[Dom Murphy]

Well so much for thinking I'd fixed it. Turns out Mono Sequencer has a mind of it's own and getting it to play nice isn't so simple, at least that's how it feels.

What are your experiences with it?

D

[JuanSOLO]

I agree, the MonoSequencer acts really strange sometimes.
Not ideal for performance or predictably reliable.
Yet it's a lot of fun to play with in a spontaneous fashion.
I end up recording my sequences to midi clips, and sometimes chopping those up further.

After altering it for the APC40 controll, and fix some of the buggyness I gave up.
I have been trying to build my own.

[Dom Murphy]

Yeah I wish it was more stable - interesting that it's that buggy and sold as part of the Suite

Any recommendations for alternatives - there seems to be a bazillion sequencers on maxforlive.com - not sure where to start.

[JuanSOLO]

interesting that it's that buggy and sold as part of the Suite :

the MonoSequencer is an amazing device.
If you plan on using a lot of M4L stuff I would recommend getting used to the idea that they are DIY creations, ideas that people put forward.
There's so many ways to patch things, not everything is going to turn out perfect.


I'll try to find the link to this one monosequencer I found when I get home and post it for you.

[JuanSOLO]

http://www.hpsounds.com/octane-step-sequencer/

[Dom Murphy]

Thanks Juan!