Keywords: sound media playback, playback software, audio software, audio playback software, show control software, video playback software, windows software play back sound, sound and media playback software archive,sound and media playback, theater sounds, the windows software to play back sound, video software windows
I have a Hoglet 4 light table. I use my light table with my computer windows 10 installed without any problems.
I have 1 mac m1 computer and the Qlab program is installed on this computer. I control the led screen on my stage with the qlab program on my Mac computer. And I have one HOG MIDI / TC controller. I want to synchronize qlab program with hoglet 4
Could you please tell me where to connect the cables of my midi controller and what settings to make on my mac and windows computers, step by step, please someone help me, I couldn't find a detailed video on this subject on the internet.
Hi there, It looks like you might be missing one piece of equipment. With the MIDI/LTC widget, you have the connection to the PC covered, but we still need to make sure MIDI is connected to the MAC. M-Audio makes a simple interface that works great, -audio.com/products/view/uno. Connect the Uno's out to the Hog widgets in, and the Uno's in to the widgets out.
The next step will be to make sure Hog PC and QLab are set to use their respective MIDI devices. Here is the page from the manual that covers selecting the proper Midi device. _MIDI/MIDINoteandCCoutput.htm?TocPath=21%2520-%2520MIDI%257C_____3 This page also covers how to send MIDI notes from the Hog PC. This is probably the easiest way to have both applications operate together.
Once you've configured the midi notes inside of the Hog PC, you can navigate to the triggers tab of the inspector in QLab. -triggers-tab Here you can manually enter the note information or simply select capture and play the note from Hog PC. Once this is set, when you play the cue on the Hog with the MIDI note macro, QLab will fire the cue associated with that note.
Hi Nicola,
Will the TCP MIDI Driver ever be ported to Windows? We have several windows computers that I would love to fire commands to from our S5000 using softkeys or scene changes. E.g., Virtual Sound Check Record/Play, lighting cues.
When I was mucking around building a Go Button box for QLab I just had the buttons send simple MIDI note on/off commands and reprogrammed the QLab functions to respond to those if you just want simple go/stop etc.
You could do the same with your soft keys and forget about SysEx and/or MSC.
we need to diy 10 motor ( i can use zigbee relays ) to control them. they are curtain motors running together with the curtains (like Aqara pre build motors)
and then i need to use window open/close sensors to give feeback signal for the motors to stop at the right positions.
Since we use Qlab a theatre software to run entire shows cue list we want to hubitat and qlab to "talk together" , qlab can output all kinds of protokols.. I hope to find a way to trigger scene in hubitat from script or ?
and recieve output signal from zigbee switch / windows sensors.. from hubitat back to trigger stuff in qlab
The simplest way to start may be to use Maker API. It allows you to expose devices via an HTTP interface. If you install the Built-In Maker API App, it will show you example HTTP calls at the bottom of the page, some for retrieving information about a device, but also the ability to call commands for a device. You could use this to trigger a device that either itself activates a scene, or if needed, setup a virtual device and some rules, whatever suits your needs.
Out of curousity I looked for "WTF is Qlab".
I did find out that it can trigger an Art-Net protocol message (what ever this is ).
Then I found this thread:
Any interest in Art-Net / DMX? - Developers - Hubitat
"Smart Stage"' I love it
Good luck
used this : Send Device Command (replace [Device ID] with actual subscribed device id and [Command] with a supported command. Supports optional [Secondary value]
[Device ID]/[Command]/[Secondary value]?access_token=eac74dc6-883a-4f39-b444-2f97847cac43
and modified to : Send Device Command (replace [Device ID] with actual subscribed device id and [Command] with a supported command. Supports optional [Secondary value]
_token=eac74dc6-883a-4f39-b444-2f97847cac43
StreamDeck assumes that the target application exposes MIDI ports. GP currently does not have that feature. On the Mac you just use IAC ports and on windows you can install (free) a virtual MIDI driver which does the same thing for Windows. The StreamDeck will then be able to communicate with GP via that virtual port.
b1e95dc632