MIDI drums trigger daw and lemur

[Digital Drum]

The lemur iPad interface is a great extension to control bitwig from my electric drums(TD-20). I have working faders for click volume and every drum. It would be nice if my faders and objects could flash when the corresponding drum was hit or signal from a daw track including tempo from BW. This would allow me visual feedback for quick mixing. I absolutely see the advantage to scripting, though I've tried and tried to make this happen. So I'm asking two things.... 1. What is the best way to get to know the scripting process particular to midi, (reference materials), and 2. Will one of you teach me how to do what i want to achieve. Thanks.

[MrCorba]

The best way to learn scripting, for me, is checking uncompyled scripts from other devices. Those scripts do exactly what you want and then you "only" have to understand how those work.

I remember the LiveControl2 has a working input meter. If you've got Live 8, I could try and help you with that but if you've got Live 9 I can only give you the uncompyled scripts.

[Digital Drum]

Thanks for reply.
Through use of the monitor I now know midi variables coming from bitwig but how do I harness that into a blinking color script to the incoming midi ?
?? If midi args == 0 then color black else color red?
Here is what I have that's seriously flawed.

MIDI_ARGS=[0];
if (MIDI_ARGS==0),
setattribute(Fader,'color',RGB(x[1],x[1],x[1])),
else
setattribute(Fader,'color',RGB(x[0],x[0],x[0]));

Can you give me a shove in the right direction?
Thanks again

[MrCorba]

Ah, for some reason I assumed you were using Ableton, so ignore my previous remote script remarks.

About processing the incoming midi:

If bw sends midi notes MIDI_ARGS probably is probably constructed like this {p,nn,vel,ch} where p = Daemon port, nn= Note Number, vel = velocity and ch = channel

So if you create a script set to onMidi and filter to Midi Notes this should work:

Code: Select all

if(MIDI_ARGS[1] == 44){ //Check the midi channel
	if(MIDI_ARGS[2] == 127) { //Check note velocity
		setattribute(Fader,’color’,RGB(x[1],x[1],x[1]));
	}else{
		setattribute(Fader,’color’,RGB(x[0],x[0],x[0]));
	}
}

I've used some random values, you need to check them. I also haven't check the color attribute code, I'm trusting you on that.

[Digital Drum]

Thanks for the suggestion. The script didn't return any results so I've been trying to find out why. When I get a working model ill let you know. I'm close then before now. I'm thinking it needs some kind of 90- note on ,80 note off thing or some kind of receive statement ...

[MrCorba]

If you can post a example of a message BitWig is sending, I'll have a look at it;)

[Digital Drum]

The script below works fine for color on off in response to channel switching. How could it be set to MIDI_ARGS[0] == 48 and then color change to incoming notes from bitwig sequencer.
My iPad is connected to daw through MUSIC IO and working great.

if(MIDI_ARGS[0] == 48)
{
setattribute (MIDIargumentsINPUT, 'color',HSV(.51,1,1));}
else
{setattribute (MIDIargumentsINPUT, 'color',HSV(.51,1,.5));
}

Thanks

[MrCorba]

I think this is something you're looking for. Read the comments in the script to understand whats happening. Hopefully this gets you on the right track.

[Digital Drum]

YES,YES,YES....
it's like you opened up the jail cell. Thank you .
My wife makes the best chocolates. We will def send you some.
Now I can edit the note number in the editor to every fader drum number and I'm off....darn yeah.
Thanks so much for taking the time and I'm serious about the chocolate !

Sincerely , Chuck

[MrCorba]

Glad to hear this was what you were looking for!