Clip launch feedback for Bitwig???

[jbw]

I've created an iPhone template for launching clips in Bitwig and would like for it to show which clip is playing in Lemur. I've read manuals, forums, and even examined different Lemur projects and could not figure it out.

The template has custom buttons set to pad mode, which send midi notes, and it would be great to have those buttons indicate when a clip was playing.

If anyone can help out I'd appreciate it.

[jbw]

Figured out a way do to this, at least in theory:

1. Use custom buttons in switch mode.
2. Set a light color for "On" and a dark color for "Off".
3. Set it up so that when you switch one clip launch button "On" it turns all the others in the row "Off"

That way it would show what clip was on, and when you switched it on it would turn the others off.

Only problem is I have no idea how to code that!

Well, these forums are kind of slow, so don't know if I'll get help here.

I'll keep on digging, and try to grind it out. It should work, and it's a simple solution to show what clip was currently playing. Hopefully someone out there can help!

[MrCorba]

You could just use a switch object for that set to Radio Mode. Then only 1 button can be pressed at the time. This should solve all your problems;)

[jbw]

You could just use a switch object for that set to Radio Mode. Then only 1 button can be pressed at the time. This should solve all your problems;)

Thanks for the reply, but for whatever reason Bitwig is only reading the first switch when mapping. I've tried both "note on" and "control change" with the proper range set in the Lemur MIDI mapping section. When I go to map them in Bitwig, it reads the first note of cc message for the first clip, but won't read the next one for the second clip.

I tested a simple two column switch, with "note on" set from pitch 13-14, and the same for CC (range 13-14), and Bitwig only reads the first column. When I go to map the second clip by tapping the second switch nothing shows up in Bitwig.

[jbw]

This is frustrating, because the Midi Map button in the editor (the button in the upper right corner) shows the switch to be correctly mapped to Note On with the correct pitch range, it's just not mapping in Bitwig beyond the first one.

[jbw]

Okay so, I finally got it to read the second mapping, but it's really hit or miss. Sometimes it works sometimes it doesn't.

Then I tried turning the "Radio" function off and everything maps just fine.

Kind of annoying, to have to map everything, then go back and turn on the "Radio" and reload the template. Maybe I'll make two templates, one for mapping and one for playing.

Seems like it's probably a bug. Any place to report bugs? Edit: Bug report has been sent via the website.

[MrCorba]

I don't think it's a bug. Just everything you click the next switch the other switch get's turned off and also sends a cc message. The same problem would occur if you script custom buttons to act as radio switches. Can't think of a good solution to that at the moment....

[jbw]

Can't think of a good solution to that at the moment....

I created another page within the project, copied the switches and pasted them to that page, then turned off the Radio function on those, and then just use that page for mapping.