Forums › Forums › dLive Forums › dLive General Discussions › Anyone using TCP Midi for anything interesting?
This topic contains 17 replies, has 9 voices, and was last updated by ThatComplicatedMidiGuy 5 years, 10 months ago.
-
AuthorPosts
-
2017/06/26 at 4:31 am #64007
I’m building a Touch OSC template that uses Osculator to communicate with like four different systems at once. (dLive being one of them.) Currently trying to wrap my brain around the TCP Midi values and interpolate that data into something useful. So far – cue recall is easy = program changes. Fader movements are… somewhat more complex.
Just curious if any of you guys are doing interesting stuff with TCP Midi yet?
2017/06/26 at 8:06 am #64010Yes. I have created a very useful program for my band with the A&H QU-PAC.
With 2 pedals, the 2 singers can transform their microphones into talkback microphone to talk to the band into their IEM
Basically, it remote the sounds from the LR and floor speakers so the mics are not going out , and send them only to the IEM aux
While releasing the pedal, it set it back to the original valueAnother thing I will add is : one button per IEM aux with the name of the AUX
When pressing this button, it also PAFL it, o I can hear what the musician is actually listening in its IEM
And maybe add 32 channels faders too, so I can edit them more easily than on the QU appDan
2017/07/01 at 5:20 pm #64097Nice!
I hadn’t thought about using it for talkback in that way.
I finally got my touchOSC template going that has scene recall + 8 faders and controls for lights/media all on one page. (With full back-mapping so you can see where you’re currently at in lighting/media cues.) Took me a minute to parse out the midi messages in Osculator for the dLive, but it seems to be working fairly well.
One odd thing I’ve run in to: If I do a scene recall my faders Don’t jump to position in Touch OSC, but they DO move any time I move a fader on the desk or in director, or on an ipad etc. So the console is reporting the movement. Stranger still, they started working properly on scene recall for a few minutes, then stopped again. Have to dig a bit deeper into that one.
2017/08/02 at 1:29 pm #64617Is MIDI protocol document finally available for dLive? I know most is compatible with GLD, however dLive has much larger input/mix count.
ddff
2017/08/02 at 11:07 pm #64623I haven’t seen anything. GLD spec seems to cover it though yeah? I’ve had really good luck just sniffing input messages from the desk in Osculator, but you could do that with any midi monitoring software.
2017/08/07 at 1:58 pm #64692Hi all,
dLive 1.5 midi spec is here.
http://www.allen-heath.com/media/dLive-MIDI-TCP-Protocol-1.50.pdf
It is now a little different to the GLD one, but officially supported from v1.50!
2017/08/08 at 3:40 am #64710Sweeeeeeeeeeeet! Thanks Jack!!
2018/06/07 at 4:41 pm #71585Hello !!
I am interesting in the useful program of Dam… It is the utility that I need: a pedal to activate via MIDI TCP my GLD some things of the console.
Dam, can you tell me more info about it… what kind of pedal and software for this operation.
Thank you for all.
José2018/06/10 at 1:34 pm #71690Where can I find the TCP/Midi driver for windows computers? There is one for the Mac on the A&H website in the dLive section but no windows version that I can find.
2018/06/11 at 3:58 pm #71719AFAIK Windows isn’t supported. You could use a BomeBox though:
2018/06/24 at 4:25 pm #72023
AnonymousThe DAW-Control driver should allow MIDI communication to/from Windows to/from the dLive. Has nobody tried it?
2018/06/24 at 9:53 pm #72030Theoretically yeah, but as far as I’m aware that’s Mackie only; which means you’d *still* have to interpret the Mackie data into something useful, with like a windows version of Osculator. (Does that exist??)
2018/06/25 at 11:57 am #72055DAW Control V1.50 added a ‘thru’ map (no HUI / Mackie Control translation) to expose the dLive MIDI on a Windows MIDI virtual port.
2018/06/25 at 4:16 pm #72070Ooooo, I didn’t know that! I know what I’ll be doing later!
Does it automatically establish connection now like TCP midi does? That was a real nonstarter for me in terms of usability.
2018/06/25 at 4:56 pm #72071But TouchOSC don’t support MIDI NRPN for fader position, it’s bad…
-
AuthorPosts
You must be logged in to reply to this topic.