Hi,
my signal chain is this:
Lemur on iPad sends MIDI -> Roland UM-ONE Mk2 -> Enttec DMX USB Pro Mk2 -> QLC+ 4.11.2 (on OSX 10.13.6)
Steps to reproduce:
- Start QLC+ with an empty project
(- Select the Enttec's DMX1 Output in a clean universe) -- Not strictly necessary
- Select the Enttec's MIDI Input (as input) in a second clean universe
- Create a fresh input profile in the "Profile" tab
- Enable the "Auto add channels" wizard in the "Channels" tab of the input device
- Wiggle a few controls
Outcome:
- The Roland MIDI interface flashes the "Output" LED as expected when pressing a pad or wiggling a slider
- The Enttec device blinks white/green/purple (e.g. Status OK/DMX1 enabled/MIDI enabled)
- But no MIDI controls are registered when operating them on the tablet
Expected Outcome:
- MIDI controls are recognized as usual when wiggling them
And yes, I did connect the UM-ONE's "To MIDI Input" plug to the Enttec's "MIDI In" plug.
This setup works fine if I use the Lemur Daemon and an Ad-Hoc Wifi for MIDI-Over-Wifi, but I really don't want to trust in Wifi for live shows. (And it limits usage to my computer, not the theater's box.)
No MIDI input from Enttec DMX USB Pro Mk2 via Roland UM-ONE Mk2
- mcallegari
- Posts: 4711
- Joined: Sun Apr 12, 2015 9:09 am
- Location: Italy
- Real Name: Massimo Callegari
- Contact:
Lemur can send OSC directly into QLC+. You can use a thunderbolt to ethernet adapter.
I don't understand why such a complex chain to send simple triggers.
As for the specific issue. Can you see the joystick blinking in the IO panel ?
Are you using the same universe for MIDI in and DMX out ? Try different ones.
I don't understand why such a complex chain to send simple triggers.
As for the specific issue. Can you see the joystick blinking in the IO panel ?
Are you using the same universe for MIDI in and DMX out ? Try different ones.
-
- Posts: 3
- Joined: Sat Aug 04, 2018 9:21 am
- Location: GER
- Real Name: Marcel
Concerning the "complex chain to send simple triggers":
Mostly because I knew MIDI and that the Enttec could do it. I only learned about OSC when I already had the MIDI hardware. Thus I had also bought a Lightning-USB-Adapter for the UM-ONE instead of a Lightning-Ethernet adapter. (Which is physically different from the Thunderbolt-Eth-Adapter...) If the Midi setup proves to be problematic, I might consider switching to OSC to get my stuff running...
I checked the MIDI input with Enttec's PRO-Manager application that shows the raw data. I can't really judge the bytes, but (as long as I do nothing) it regularly shows the 0xfe idle message and a lot more bytes when I move a slider. I can copy something together if that helps.
(I couldn't find any precise info about Lemur's "Slave Clocks to MIDI" option, but changing it didn't produce differences so far either.)
From my developer perspective, this feels like a debugging nightmare. I hope you've got an idea.
Mostly because I knew MIDI and that the Enttec could do it. I only learned about OSC when I already had the MIDI hardware. Thus I had also bought a Lightning-USB-Adapter for the UM-ONE instead of a Lightning-Ethernet adapter. (Which is physically different from the Thunderbolt-Eth-Adapter...) If the Midi setup proves to be problematic, I might consider switching to OSC to get my stuff running...
I assume the joystick you're referring to is the one in the Channels tab of the Input Profile Editor? There I first didn't see the joystick at all. Now I tried again, a little harder this time. With the "wizard" mode turned on, I could get a few controls to pop up in an empty input profile by moving various sliders and pressing buttons like crazy. The resulting data looks a little mixed up to me, it has now got channel numbers 33282, 29186 and 0232 with all three showing up as a button. During that experiment, QLC went to ~118% CPU and stayed there. I took a process sample using OSX's Activity Monitor, the file is attached.As for the specific issue. Can you see the joystick blinking in the IO panel ?
Are you using the same universe for MIDI in and DMX out ? Try different ones.
I checked the MIDI input with Enttec's PRO-Manager application that shows the raw data. I can't really judge the bytes, but (as long as I do nothing) it regularly shows the 0xfe idle message and a lot more bytes when I move a slider. I can copy something together if that helps.
(I couldn't find any precise info about Lemur's "Slave Clocks to MIDI" option, but changing it didn't produce differences so far either.)
From my developer perspective, this feels like a debugging nightmare. I hope you've got an idea.
- Attachments
-
- qlc_sample.txt
- (208.99 KiB) Downloaded 70 times