Home › Forums › Help/Technical Questions › 22500 Looper: Trouble importing rhythm loops

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • January 3, 2019 at 6:28 am #85619
    kajitokenka
    Member

    I just got my 22500, and I’ve been trying to import some of my own audio files. Following the instructions in the manual, I was able to add a file as a Loop B in a bank folder I created. However, nothing I did with the rhythm loops worked. I followed the manual, but when I put my SD card back in the 22500 it didn’t recognize the new LOOP25 folder I created. I tried it a couple of times with a few different .wav loops (all stereo files), and I always made sure to name the .wav TRACKM and edit the tempo.txt file, but it wouldn’t work for me. Once, I tried copying one of my .wav loops into an existing loop folder (LOOP5), but then the 22500 stopped recognizing that folder too. I’m at a loss, and I’d appreciate some guidance! Thanks…

    January 3, 2019 at 9:19 pm #124681
    Flick (EHX Staff)
    Moderator

    The file that you added to Loop B in a bank folder, did that audio file playback?

    Make sure the audio file you are trying to import into the LOOPXX folders for the rhythm loops follow these rules:

    The audio file must be .wav format.
    The audio file must be 16 bit resolution.
    The audio file must be stereo.
    You have copied the tempo.txt file from an established rhythm loop folder and it is present in the new loop folder.

    If any of the above rules are not followed it will not playback.

    January 3, 2019 at 11:09 pm #124682
    kajitokenka
    Member

    Thanks for the quick reply! Turns out I was trying to use 24-bit files, which must be why the 22500 wasn’t recognizing them. I converted them to 16-bit and now I’m in business. Cheers!

    January 4, 2019 at 2:20 pm #124684
    Flick (EHX Staff)
    Moderator

    Great to hear. Thanks for letting us know and have fun with the 22500!

  • Author
    Posts
Viewing 4 posts - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.