When I record MIDI to e.g. Dualchord Tracks the notes align well with the sequencer track steps.
However, when I record MIDI into the Sample tracks, e.g. 7/8 track the notes I play seem to get quantized differently: they usually are recorded/quantized one step late most of the time, so I have to shift them one step back manually.
I did not notice a Playback difference when playing via external MIDI, only when recording when the quantization is happening.
I did not do a proper test yet, I only played in via a MIDI keyboard via the MIDI Host connector, but found the difference quite noticable when comparing the dualchord track recording (which works OK) versus the Track 7/8 recording (which has an offset).
I am running V3.0, playback speed is normal.
Hey, I just did test this and I can't find any difference.
I set the record from Host Channel 1 to the destinations of Track 1 (modular), Track 2(Dualchord), Track 7(Audio1) and Track 8(Audio2) and record all at the same time. The notes are in all patterns at the exactly same step.
I couldn't think of anything that would cause your issue. Maybe you can share your project so I can find out if it is project related in any way.
Thanks for testing.
Did you also check how the notes are quantised if notes come in a bit early or late (up to 50% off the grid)?
I think if the notes are “spot on” it looked like it works, but playing via MIDI keyboard I noticed that Track 7 was harder to get the notes right in comparison to Dualchord.
I assigned “Track Select Record” to MIDI Host Ch1 for recording and assigned no other MIDI routing. Then I enabled Recording with SHIFT+Record while in the Pattern view.
I will try later (don’t know if I find time today) to feed the recording with a synced sequencer which can delay the notes off the grid and then share my project in case there really is a difference. I am not 100% sure because I just played by hand and it is subjective how well I hit the notes in time with the grid.
All Midi record is +- 50% quantized. So it should normally be fine to play manually, also for an untrained amateur like me :-)
Let me know. I am about to put a new release candidate online soon and if there is something hidden then it would be good of course if that would be fixed as well. For now I can't really see the difference. Audio tracks got their own double clock though since they are handled different than all other tracktypes, but that should not make any difference.
I tried again.
This time I synched the Westlicht Performer via analog clock and reset to the nerdseq and sent MIDI to the Nerdseq using the Performer as MIDI Host and the Nerdseq as USB MIDI Device on Port 1. I set the recording to record into the the track currently selected which was Track 7 with the pattern screen open during recording (I think this makes no difference).
I ran a simple sequence with hits on every beat, the first beat 1 octave higher to check sync.
Both sequencers run in sync nicely.
But when I record from the Performer into the Nerdseq Track 7 (Audio 1) I get a delay of one step (one line) in the sequencer.
When playback repeats, I can hear the 1 step delay between both sequencers when both trigger the same track (MIDI in plus the recorded pattern playing).
I have the project file attached. The last pattern on track 7 was recorded as described.
On the performer the note delay is set to 0, so all notes are excactly on each beat before recording, but not after recording, then it is delayed.
Maybe I got some strange setting? But there is no other mapping set up other than the MIDI recording.
Strange,
now I edited the track asignment again (not included in the uploaded file) to add DualChord in Track 3, to check if I get correct recording and now also DualChord recording if off one step.
Again I can hear the difference between the recorded track playing and the live MIDI input of 1 step, so the MIDI source is not offset.
Maybe there is a small offset of MIDI transmission of a few ms, but not much. The sync is pretty good (analog clock sync).
As a side note the project file was originally created in V2.x or earlier and I kept using it after updating the firmware. Maybe this makes a difference?
I could create a new project and check if the behavior is the same.
You got all your grooves set to 3 (your custom default groove).
The live recording is optimized to normal clock/groove options which is 6 ticks/step for the groove = 24ppqn.
The quantization is based on the ticks and so will work only as designed with 6 ticks per step.
Thank you for looking into it!
Ah OK, I did not know that the clock should be at 6 ticks per step and did not remember that I changed it, that was quite some time ago.
Downside is that I can not record at higher resolution that I have with 3 ticks per step which may be nice for drums, e.g. quick hihats. I know that I can add tables that run quicker manually (by editing) or could run at double tempo.
For basic stuff recording with 6 ticks per step will work for me.
I think I should add a feature request for quantized recording at 3 ticks per step?
(01-12-2026, 03:09 PM)48484B Wrote: [ -> ]Thank you for looking into it!
Ah OK, I did not know that the clock should be at 6 ticks per step and did not remember that I changed it, that was quite some time ago.
Downside is that I can not record at higher resolution that I have with 3 ticks per step which may be nice for drums, e.g. quick hihats. I know that I can add tables that run quicker manually (by editing) or could run at double tempo.
For basic stuff recording with 6 ticks per step will work for me.
I think I should add a feature request for quantized recording at 3 ticks per step?
I don't give that a chance. The resolution is actually lower, not higher in the first place. You just run twice as fast. 2nd, the 3 ticks groove can be different on every step. It is not 24ppqn then anymore which is used by Midi etc. 50% quantization is not possible anymore then since that would need 1,5 ticks both sides which is not possible cause of the internal resolution then.
Changing your ticks or clocks for your tracks is of course a nice flexible thing to do but it comes also at a cost for other situations.
I think I understand. By using 3 ticks instead of 6 I just get to see the steps in between for easier editing, but the tick resolution is still as it was before. I guess for 4 ticks, it would be possible to quantize +-2 ticks, but I do not need 4 tick step resolution (I guess that is some triplet timing). At 2 ticks per step it would be +-1 tick. But as you say, 3 ticks per step needs 1,5 steps for 50% quantization, it is not possible.
So for recording that probably means that the groove setting is also ignored when the recording is quantized +-50% to the steps?
I think all of this is not really an issue for me, I can also work at 6 ticks default step length and then edit to get higher note resolution manually if needed. I was just wondering if the recording function is defective but its all OK!
Thanks for the clarification!