The MIDIin CHOP’s sample rate parameter does not seem to have any effect on the resolution of the MIDI input and the number of samples remains at 1 per frame. I’ve outlined what the issue seems to be in this thread: Match MIDIin CHOP number of samples to that of other operators but have also recorded a video which further demonstrates the issue.
Would you mind going into a bit more detail about the improvements to the MIDI in CHOP in the new experimental build?
I’ve been trying it out this morning and the set-up from the previous video yield the same results.
The reason I can’t switch over the MIDI in DAT for some applications is that MIDI input is being used to drive a CHOP based audio network and needs to be converted into CHOP triggers at some point.
I’ve recorded another video which demonstrating this.
Sorry for the delay, some issues with the previous version have been fixed causing random values in the CHOP output. These are now fixed in builds 2022.22770 and later.
In addition there is now a new option “Preserve Pulses” which better handles high frequency pulse information.
Cheers.
I hate to be a downer again but the “preserve pulse” parameter doesn’t accomplish what this bug/RFE thread pertains to: input timing accuracy at higher sample rates.
From what I can tell “preserve pulse” adds a single sample with a maximum velocity value followed by a 0 value input followed by the actual velocity value. The timing of this pulse is however still constrained to the first sample regardless of the sample rate.