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

Home Forums Products Stompboxes Does the Time Factor quantize loop length to external MIDI clock?

  • This topic is empty.
Viewing 6 reply threads
  • Author
    Posts
    • #111726
      allochthon
      Member

      This has been asked by another poster four years ago, but they never received a response. It is not addressed anywhere in the manual of in the FAQ. Seems like a pretty simple question…

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

    • #126177
      nickrose
      Moderator
      Eventide Staff

      The current one does not. But we're working on it for the next version – this is one reason why it is delayed.

      Less anyone misunderstand this, the tracking will not handle tempo changes – for example it will not time-compress the loop if you speed up the tempo – it will instead cut a bit off the end.

    • #126202
      onlinemusic
      Participant

      This is a critical feature for many modern styles of production. Thank you for working on it. 

    • #136865
      entreat69
      Participant

      Sooo looking forward to the much anticipated eventual release of the FW update for Time Factor.

    • #148876
      onlinemusic
      Participant

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

    • #148881
      brock
      Participant
      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

      Show More...

      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.

      Show Less...
    • #148883
      onlinemusic
      Participant

      Great, thanks!

Viewing 6 reply threads
  • You must be logged in to reply to this topic.