Reply To: Does the Time Factor quantize loop length to external MIDI clock?

[brock]

allochthon wrote:

… Does the loop length quantize to match an external MIDI clock????

onlinemusic wrote:

… Does anyone know if this feature was ever implemented? Thanks!

I believe this is what you’re looking for, from the updated Looper manual:

https://com-eventide-drupaluserfiles.s3.amazonaws.com/download/file/Looper.pdf

Manuel Looper wrote:

Tempo Mode Footswitch Quantization

MIDICLK is made up of a series 24 “ticks” per beat. Tempo Mode quantizes many of the Footswitch actions either to the next MIDI beat or the next MIDI tick. The quantization action of the Footswitches for each Looper State is as follows:

Empty ● – Starting a new recording syncs to the next beat ONLY if in MIDICLK Slave mode AFTER having received a MIDI Start command. Otherwise, this begins recording on the next tick. ►– No action. ■ – Only used for tap tempo

Recording ● – Record to Dub transition quantizes to the next beat. ► – Record to Play transition quantizes to the next beat. ■ – End recording and stop, quantized to the next beat

Dubbing ● – Dubbing in/out doesn’t do any footswitch action quantization. ► – End Dubbing and Start Playing from Loop Start. This action quantizes to the next tick. ■ – End Dubbing and Stop Playing. This action quantizes to the next beat.

Playing ● – Start Dubbing, no footswitch quantization. ► – Start Playing from Loop Start. This action quantizes to the next tick. ■ – Stop Playing. This action quantizes to the next beat.

Stopped ● – Starting a new recording quantizes to the next beat ONLY if in MIDICLK Slave mode AFTER having received a MIDI Start command. Otherwise, this begins recording on the next tick. ► – Start Playing from Loop Start. This action quantizes to the next tick. ■ – No action.