07-09-2021, 09:31 AM
(This post was last modified: 07-09-2021, 09:32 AM by Marizu.
Edit Reason: Improve clarity
)
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.
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.