XOR Userforum

I'm trying to record sequences from an Intellijel Metropolix. I am having mixed results.

If I record using "CV NOTE + GATE 1" option, then the NerdSeq doesn't seem able to record stages on Metropolix where two notes directly follow one another. So if I set the "Pulse Count" on Metropolix to more than 1 on a stage, the stage will output the same note (in a basic example) but multiple gates, however the stage records each gate as "FE" (gate on), then the next step in the NerdSeq records in the same fashion, so that I end up with a continually open envelope instead of the multiple gates that were output by Metropolix.

My guess is, based on the accurate recording in this mode of steps that don't have multiple gates selected (ie, stages where the NerdSeq records an FE followed by a [] on the subsequent step), is that this is simply the resolution at which the recording is made, and that if two consecutive steps both contain a note, the gates will record such that they slur together, have I got that correct?

My first workaround is that  I can get a pretty decent recording by using the "CV NOTE + TRIGGER 1" option, but now I'm not recording real gates, but at least the multi-pulse stages get recorded much more closely to what metropolix outputs. I can of course then edit the trigger column to customise gate lengths, but it's not as cool as it would be if I could record directly the gate lengths output by Metropolix.

Another workaround I could think of would be to run the nerdseq at a faster clock rate, say 240bpm, then run the metropolix at a half clock from that, which sounds like it could/maybe/might work to get a pulse on metropolix to be followed by a rest at the resolution of the Nerdseq with the higher clock rate (so it would record a [] on it's "extra" clock pulse after the metropolix gate had ended), but would be a pretty massive hack. 

Is there a better way to do this? Can I record with KILL commands so as to directly record this better? Perhaps I'm just being really dumb and it's much simpler than I am making it out to be, but so far, I just can't get it to "just work".

Also, when recording, it seems I can only overdub, so say I started with a 4-on-the-floor beat coming from metropolix, then swung it whilst recording (without changing the number of active steps, just moving them in swing), I would eventually end up filling all the steps in the pattern - so I would have beats on every step, not just the newly swung 4 beats. I have looked carefully in the manual but have been unable to find anything about this - how do I overwrite when recording instead of overdubbing?

[url=https://modwiggler.com/forum/viewtopic.php?f=16&t=177599&p=3562162#top][/url]

I was doing this last night and I saw the similar issues. All of my gate triggers had been recorded as FE. Like you say, I manually edited all of the FE (gate on) to a 10.

I haven't yet looked at how Metropolix handles swing (is the clock that it puts out swung, or is the clock straight, but the output gates are swung), but Nerdseq doesn't really have swing, so I would turn that off when you are recording the patterns.

My settings For input 1 record are CV Note+Gate 1 but I put ^ TR / GT DLY 3ms on input 2 record, as that's what I tended to use for Metropolis.

When you say that you can only overdub, what are you referring to? Are you talking about in the pitch or in the trigger columns?
I saw a load of FE triggers, as you describe, but they were interspersed with 00 triggers for steps that Metropolix didn't trigger.

I'm on the V1.25 RC1 firmware.

Regarding the massive hack, I might instead suggest changing track multiplier and/or groove from 6 to 3, at least before getting hacky with BPMs. Whichever minimal change or changes to have more resolution on the NerdSEQ side than you need for the Metropolix output. You’d end up down to two-bar or even one-bar patterns instead of four, but can make up for that somewhat by recording directly into an island of patterns rather than one.

That and there’s always fun to be had by playing existing patterns with their appropriate multiplier cut in half, especially on another track at the same time as the original is still playing.