Hey guys, apologies if this has been covered before, I can't remember if these have been addressed or not. Couple of issues...
1). Basically, I'm using my BASE controller alongside an APC40, but I'm not using the remote script for Base, I'm using it as a simple MIDI controller so that I can take advantage of all the LED lighting and using Live 9's MIDI learn to map all the FX I need that way.
Experiencing a weird issue when I try to map the left 16 pads on my controller to various FX I have in live (BeaT repeat On/Off). Since they just need to be in On/Off states essentially, I tried enabling toggle for each of those pads in the web editor (by the way I've tried using Mac and Windows, same result). No matter what I try though, I can only seem to get them to work in momentary mode (even when that mode is disabled). Whenever I have been able to get the pads to work in somewhat of a toggle mode, whenever I map an On/Off button in Ableton to a pad, I have to hit the pad like 4 times to enact a toggle, twice to turn it on, and twice to turn it off.
2) Minor issue, but the RGB controls for pads/faders seems to be backwards or inverted, i.e. R=blue, B=red, etc.
I'm using the web-based editor, and I have the most recent firmware for BASE, 1.3.
Comments
Ok so let me ask, are you trying to use a custom map with the BASE remote script for Live?? I have to preemptively say that Live doesn't like that...
Hey Jay, no I'm not using any Remote Script for Base, just utilizing it as a standard MIDI controller and using Live's MIDI Learn to map my effects (i.e. the left half rows of pads are used for beat repeats, the right-hand side is used as a standard 16-grid pad for drums/sampler, I've got my bank selector buttons mapped to an Instrument Rack chain selector range, etc). In the editor, I've also set my global channel to something other than 1 to try and avoid a bunch of conflicts with my APC40 that I'm using in tandem.
I'm doing it this way to take advantage of the LEDs on the BASE without having to resort to User Mode, which doesn't allow me use of the LEDs, and also to avoid MIDI conflicts with my APC40.
The red and blue being switched probably means that you have the wrong firmware. There is a batch 1 and batch 2 version. Try the opposite of what you are currently running.
As for the toggle mode problem, it sounds like there may be some double triggering happening. I'm not positive, but maybe you are turning the note on and off very quickly so you see it as nothing happening. Can you download a MIDI monitoring program or use the midi monitor in the editor? Then you can view the actual midi data and see what is happening when you press a button. In toggle mode, you should get a single note on the first time you press a pad, then a single note off the next time you press it.
Let us know your results and we can go from there.
Hey Mark, yeah on the website you have two options for selecting your firmware based on date, and I had purchased my BASE through Guitar Center after that date I think, but who knows when Guitar Center actually got it and had it sitting in their warehouse. Anyways, I just used the Original Firmware and that fixed my LED issue.
That is normal to send note on, then cc messages, then note off(momentary). If you are in toggle mode, then the note off shouldn't come until the next time you press the button. Can you verify if it is doing a note off when you release or the next time you press it?
The cc's that come after you press the button are for after touch and pressure sensitivity.
You can disable them, or map them to an effect like beat repeat.
Yeah looks like I'm getting a Note Off message whenever I hit the pad again. Here's a screenshot of me hitting that pad twice (I guess I'm hitting it pretty quickly so as to not get too many CC messages afterwards):

So is it possible then that when I use Live's MIDI learn to map an On/Off button to a Beat Repeat Device in Ableton that it's actually getting mapped to a CC message that happens after the note on/off? How can I disable that? I just want to be able to hit the pad once to activate the Beat Repeat, and then hit it a second time to turn it off. Right now, whenever I've been able to get it to map successfully in a toggle-like fashion, I've had to hit it 4 times to get that effect, twice to turn it on, twice to turn it off, and that's no good for me.
You can turn the CC's off in the editor. Look for "cc enable".
You can also turn "drum pad local control" on which will give you an LED indicator.
Try turning on the "fixed velocity" that will make the velocity 127 each time which will always turn on the device. I think before if you were register velocity under 64 it would not turn the control on.
Okay, so I seem to have it working now after a bit of testing.
Just as an FYI, Live doesn't send MIDI feedback when a device is turned on and off, which is why a MIDI learned action will not light up when it is toggled. Toggle mode with hypothetically fix this, but could screw up some of your other lighting functions as toggle is a global option.
Well, the LED feedback seems to work when toggle is disabled in the editor for those pads. As long as I'm not using the remote script, and I have toggle disabled for the pads I want, if I map a pad to a device On/Off I seem to get LED feedback on the Base.
You only need to change the ch. setting for the bank 1.
Having some trouble with this again. It seems like it started happening after I upgraded the firmware for my BASE I, I was able to resolve this issue at one point in time for a long time. It also could very well be an issue stemming from an update from Ableton perhaps? Not sure.
Here's a quick video of me trying to map the pad. Sorry for my mumbling and any shakiness in the video. I think the vid got a little compressed, but the Note it's getting mapped to is C3 once I've mapped the pad, if that makes any difference:
https://drive.google.com/file/d/0B0-6BqN_Be53bmlQdVlSMTVoR0c5YTlJdWUyT3dsdEJ3S3Jr/view?usp=sharing
Hey Moon, thanks for the reply!
Hey Moon, thanks again for your reply. I finally was able to get it working. I think there were some other MIDI ports that were enabled in my Preferences that were possibly interfering with my mappings for the Base.
There we go, just needed to enable "Remote" on my MIDI Output like you said and that did the trick! Thanks again!