Looper oddity

Home Forums Products Stompboxes Looper oddity

  • This topic is empty.
Viewing 3 reply threads
  • Author
    Posts
    • #114678
      question
      Member

      Hi,

      I have started to see another strangeness.

      When H9 is not connected to any device (Bluetooth or not). I make a looper preset with the ‘resolution’ set as ‘chromatic’. When I hit the record button (on the device), I momentarily see the word ‘octave’ on the H9 display and when recording ends if I try to change the playback speed it jumps as if it was set to ‘octaves’. Same thing happens if I repeat whole steps via H9 control software.

      Briefly, H9 does not remember the ‘resolution’ setting and insists in the ‘octave’ option.

      I hope I’m just overlooking something : )

    • #148857
      question
      Member

      Well… obviously I have overlooked the “During loop recording, Resolution will always return to OCTAVES.  This guarantees that the immediate playback speed occurs at the recorded speed” section in Looper manual, which I’m not quite sure about the meaning.

      Why would the immediate playback speed occur at any different rate if the Resolution stays at where I set it at the first hand? Why the “octaves” is suitable and not the others. This makes the speed changes rather cumbersome especially when used live. On a H9 You need multiple button presses or you’re dependent on the control software (ie., your PC or tablet).

    • #148866
      Bodde
      Participant

      Yes that not saving the resolution and jumping back to octaves is a strange choice Eventide made. There was a reason behind it but I forgot what it was. But it is not very practical.

      • #148869
        brock
        Participant
        bodde wrote:
        Yes that not saving the resolution and jumping back to octaves is a strange choice Eventide made. There was a reason behind it but I forgot what it was. But it is not very practical.

        Here was the explanation from Russ:

        https://www.eventideaudio.com/comment/24756#comment-24756

    • #148873
      question
      Member

      Few comments like the one in https://www.eventideaudio.com/comment/24756#comment-24756

      wedelich wrote:

      We found everyone wants to use Loopers in very different ways, and we did this because most people prefered their immediate playback to be at the pitch/speed they recorded it in (more standard Looper usage).  

      or in https://www.eventideaudio.com/comment/21126#comment-21126

      wedelich wrote:

      That is actually how it was intended to work (it’s in the user Looper Help file).  It was actually a hard decision to come by, choosing between having an auto Octave switch back or not, but here is why: 

      Show More...

      Each way ( 1. auto Octave swtich back, 2. no auto Octave switch back) will always require an extra user step to change the Resolution in the situation where you want to record a new loop and have it playback at the speed you recorded (which I’m assuming is the majority of cases for a Looper in a guitar pedal).  For 1, it the extra user step always occurs after you create a new loop and have to adjust the Resolution to something else.  For 2, the extra step occurs before you want to record a new loop, i.e. put the Resolution back to Octaves, or at least make sure you put the Speed back to 100 or 50, etc.  

       

      could actually be the explanation of why it does not automatically return to your original choice after the first recording is finished (obviously that might cause an undesired pitch shift). But imho it doesn’t really clarify the mysterious : ) jump to ‘octave’ mode which occurs at the first hand when record button is pressed.

      Immediate playback at the pitch/speed of the first recorded material should occur with any arbitrary resolution/speed setting unless the user manually changes something in between (ie. between the first recording and the playback).

      I might think that for some technical reason, it can only record at the multiplies of a 25% rate. But since this limitation only exist during the first recording, and it can dub at any speed afterwards, this would be unlikely cause.

      Cheers

      Q

      Show Less...
Viewing 3 reply threads
  • You must be logged in to reply to this topic.