admin

[admin]

Can you open up mr. datalooper, remove the switch and email a photo & your address to info@datalooperpedal.com? It sounds like you need a replacement switch sent out. We’ve gone through a few manufacturers, so I just want to verify which switch type you have.

[admin]

Hi Jon, if you’re using the default .als template, there is a mapping on the looper device itself which you can remove. That mapping was intended to bring focus to the looper you’ve just recorded on for beginners to have a secondary visual aid, but it’s not necessary. Outside of that, there’s nothing in the script that changes focus. I don’t personally own a push, but I know the Push script does some pretty crazy stuff, so, yeah, there may be a bit of investigation necessary to see if there’s anything conflicting. I’m happy to make modifications to my script if there’s something overtly off.

[admin]

Hi Jeff, I believe we spoke on the phone. The template was updated to put undo controls on the top row of the unit. 9-11 having the ‘command if looper playing’ set to none is also correct.

[admin]

Hi Ernesto, any phone charger or power bank that’s meant to work with a USB device should work just fine.

[admin]

Hi guys, it sounds like maybe there are a few things going on. 1. Currently, there’s no way to read current presets; the config software is one way, from Chrome to the pedal. 2. It sounds like there’s some issue flashing configs if it’s hanging on red lights; the expected behavior is that the lights all turn red while flashing, then turn green. I’ve just updated the default config file; try uploading the new one (on the resource page) and see if you still get that issue. Regarding not being able to log in, are you visiting this page? (https://www.datalooperpedal.com/config/).

There are some issues with backwards compatibility on the config software that are real tricky to pin down, but everything should work with the latest config files. If you still have issues, feel free to email me directly at info@datalooperpedal.com.

[admin]

This was due to a change in the way ‘command if looper playing’ functioned. There was an option for ‘stop immediately’ added, which caused config files written with an older version to be misread (stop quantized got read as a clear). I put a fix in place on the new config software (2.72) that checks for this inconsistency and applies a fix. You will have to re-flash the config, but it should apply the fix as soon as you load the file. My apologies for this inconvenience. I sometimes miss these forum posts, so if there’s an issue like this that prohibits your use, please email me and i’ll take care of it immediately (info@datalooperpedal.com)

• This reply was modified 3 years, 3 months ago by admin.

[admin]

Hi, yes you can definitely use Datalooper as just a MIDI controller, just know that it won’t have the same LED feedback. You can use the Datalooper Config software to program whatever CC messages the Boss RC505 expects to receive. Check out the RC505 manual, and they should have a MIDI implementation chart somewhere in there.

[admin]

Hey guys, I think I have a fix for you. Try out the new config and 3.1 beta remote script (also update the firmware). This was a fairly complicated problem, and had to do with the default vertical config sending out multiple commands depending on the press/release state. This update adds a few things:

1. You can now save your config files from the config software without having to re-download a new file.
2. There is now a ‘none’ action in looper actions, allowing you to only trigger an action when the looper is playing
3. Fades work more reliably, and don’t require a utility device on the track any more.
4. CL tracks should be fully working again, with this template.

One issue I haven’t solved yet (it’s complicated) is that after getting a new clip slot, the main recording button will trigger a stop if it’s an audio track. The workaround is to just not use ‘get new clip slot’ with a CL audio track, and just record into a new slot using the overdub command. I’ll try to work out a better fix for this soon. Thanks for your patience. It’s been a busy busy few months with my other work.

• This reply was modified 3 years, 8 months ago by admin.

[admin]

Hmm, it’s possible there’s a hardware error with the Datalooper board. There were a few units right when V2 was introduced that had an issue with the wrong voltage going to the EXP jacks (5v instead of 3.3v). I believe the symptom of that though was that the pedal would send out 127 at the halfway mark, rather than the full range. If you want, you can ship me the pedal and I can take a look and see if that’s what’s going on, or you can open the box up and send me a photo of the main board (vince@datalooperpedal.com) and I can tell you if that’s what the issue is (I can visually see if the 5v line is connected wrong).

If that’s the issue, you can ship it in for repair or I can guide you through how to repair it if you’re handy with a soldering iron.

[admin]

Hi Dave, can you check that the expression pedal range is set correctly? Most expression pedals have a little range knob.

[admin]

I’ll send you guys an updated script shortly. I believe I found the issue and have fixed. So sorry I missed this original post until now.

• This reply was modified 3 years, 9 months ago by admin.

[admin]

Hi, I believe we got you sorted via email, lemme know if you still need help!

[admin]

Hmmm, are you certain you’ve flashed the correct firmware? I haven’t had any issues on 11.1. Also, does the Datalooper blink when transport is running (indicating the remote script is connected)? Also…is the remote script showing up next to input + output in the Ableton midi prefs?

[admin]

Hi! It’s possible your config had a different channel configured than the default config. By default, the Datalooper template is linked to MIDI channel 14. Unless there’s an Ableton bug I’m not aware of, there should be no reason that the template would not link the MIDI mappings. Can you confirm you were on channel 14?

[admin]

Hmm what version are you on? This will work with 2 DL instances but I haven’t tested with a CL and DL simultaneously. You can try putting LED in the name, like “DL#1 LED” and the other track just named “CL#1”. This may help, but I’ll have to test on my own to see if there’s something else going on.

[Author]

Posts