question about Recycle's MIDI sequences

I've been using recycle for a year, admittedly this is the first time I ever used it's MIDI sequence function. It worked perfect for what I wanted: the sequence that will get the slices to sound as closely possible to the unsliced version.

I don't see any parameters regarding the MIDI files so I'm just confused as to why it worked. How did it know I would be sequencing 96 ticksper beat? Would the sequence still play correctly on a machine that has 480 ticks per quarter?

Harmoncj wrote:I've been using recycle for a year, admittedly this is the first time I ever used it's MIDI sequence function. It worked perfect for what I wanted: the sequence that will get the slices to sound as closely possible to the unsliced version.

I don't see any parameters regarding the MIDI files so I'm just confused as to why it worked. How did it know I would be sequencing 96 ticksper beat? Would the sequence still play correctly on a machine that has 480 ticks per quarter?

In almost a decade of using Recycle I never even thought about it. The MIDI files exported with a sliced loop (Individual WAVS with "export as one sample" disabled) always work in whatever I put them in 480/960PPQN no issues.

I see people forget that the MIDI file doesn't "know" the actual pitches/notes of the samples, only triggers the slices, but never saw an issue with different PPQN's in any hardware of software.

I believe MPCs adjust the resolution accordingly, this may even be a requirement of MIDI specification. So basically the MPC shifts notes to the nearest possible tick.

Ok that makes a lot more sense than what I was thinking. Thanks for the help!