Anyone using TCP Midi for anything interesting?

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 Profile photo of ThatComplicatedMidiGuy ThatComplicatedMidiGuy 4 years, 3 months ago.

Viewing 15 posts - 1 through 15 (of 18 total)
  • Author
  • #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?

    Profile photo of DanZ

    Yes. 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 value

    Another 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 app




    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.

    Profile photo of ddff_lv

    Is MIDI protocol document finally available for dLive? I know most is compatible with GLD, however dLive has much larger input/mix count.



    I 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.

    Profile photo of Jack_AH

    Hi all,

    dLive 1.5 midi spec is here.

    It is now a little different to the GLD one, but officially supported from v1.50!


    Sweeeeeeeeeeeet! Thanks Jack!!

    Profile photo of ea4bnm

    Hello !!

    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.

    Profile photo of TheMAXX

    Where 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.


    AFAIK Windows isn’t supported. You could use a BomeBox though:


    Profile photo of Mr.X

    The DAW-Control driver should allow MIDI communication to/from Windows to/from the dLive. Has nobody tried it?


    Theoretically 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??)

    Profile photo of Nicola A&H
    Nicola A&H

    DAW Control V1.50 added a ‘thru’ map (no HUI / Mackie Control translation) to expose the dLive MIDI on a Windows MIDI virtual port.


    Ooooo, 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.

    Profile photo of Zistan

    But TouchOSC don’t support MIDI NRPN for fader position, it’s bad…

Viewing 15 posts - 1 through 15 (of 18 total)

You must be logged in to reply to this topic.