• Date
    thomasrrh
  • Date
  • Replies 3 replies
  • Subscribers 87 subscribers
  • Views 1390 views
  • Users 0 members are here

LTC + MTC Into ETCNomad (and in theory any console, yet to test) Without the use of response gateways

After doing some digging, turns out that EOS supports any usb midi device providing it uses the built in windows drivers, which 99% of them do, my goal was to send MTC Timecode between a laptop rubbing reaper, and another device running ETCNomad, I also later tried this on an Ion XE.

First step was to buy two USB to MIDI adapters and couple them together using some female to female adapters, I did manage to receive Timecode on the Ion XE however it was very tempormental as when I stopped the playback on reaper, the adapters IN indicator refused to light up, and the console wouldn’t receive Timecode unless I reached behind the desk and unplugged the adapter and plugged it back in.

So that was attempt one, but after doing some more digging I came across this company called DOREMIDI which make tons of usb midi devices like splitters and stuff. They also happened to make a MIDI to LTC BOX, and after watching a YouTube video about it, this device has the ability to translate USBMIDI/MIDI/LTC to USBMIDI/MIDI/LTC at the simple push of a button, not only could it take the input from my USB to MIDI adapter, but it could also take LTC which is a lot more ideal for my use case, as it’s much easier to just run LTC out of qlab and run it through my theatres patch bay. This also allowed me to have  my laptop plugged into the midi inputs, so when doing notes for Timecoded dance shows, etc I am able to output Timecode locally from reaper at the exact points needed. And it also allows me to playback in stereo audio, which can be crucial for certain tracks.

 Now you might be wondering how EOS is compatible with this device over USB, and it’s quite simple. The device when plugged into any computer uses windows standard USB MIDI drivers, meaning EOS recognises the device and can be used to input Timecode. 

You can only purchase DOREMIDI’s MIDI to LTC BOX from their website, it cost me 81USD and shipped from china, and arrived in the uk just a week and a few days later. I am certainly not disappointed with my purchase, I have yet to test it on a physical console, but I am 95% confident it will work flawlessly

.

*Quick extra, it also outputs the protocol you are inputting in, I.e if you send LTC into the device it also sends it back out through the LTC out port, Same goes for midi and usb.

Parents

  • I think there might be an easier solution if we're only integrating timecode into Nomad. Mac has built-in MIDI over network drivers that allow you to connect different devices. We can configure the show control machine (outputting timecode and audio) and the Nomad machine to be on the same network. This setup is potentially costless (if you have an ethernet cable and a show control software).

    The setup I used has two pieces of software. I use QLab for show control, outputting MTC through the MAC built-in IAC driver. Keep in mind that QLab only runs on Mac, and you'll need a pro license to enable timecode, but you can rent a license for 4 USD per day. Other free options like Reaper also exist, but you'll still need to pay after the free trial period.

    I found this tutorial on how to set up QLab with ChamSys. https://www.youtube.com/watch?v=jK_acdzj3bE&t=730s&ab_channel=ChamSysRus. The only thing you can change for better functionality is to change the group cue mode to timeline mode. You just need an audio cue and a timecode cue inside the timeline group. Change the length of the timecode cue to the length of the soundtrack, so you can drag the timeline of the whole group in active cues to sync up the audio and the outputted timecode (and later using external in EOS).

    With a different tutorial on Reaper + EOS, I was able to adapt the ChamSys tutorial to EOS. https://www.youtube.com/watch?v=8By9TrLpw9w&t=335s&ab_channel=Benjermon

    I've tested this setup on my Mac running QLab and EOS at the same time, and it's worked for me. Based on the first tutorial, I'd assume that this would work for a multi-laptop/computer setup. Not sure how this would work on a console because I don't currently have access to one.

Reply

  • I think there might be an easier solution if we're only integrating timecode into Nomad. Mac has built-in MIDI over network drivers that allow you to connect different devices. We can configure the show control machine (outputting timecode and audio) and the Nomad machine to be on the same network. This setup is potentially costless (if you have an ethernet cable and a show control software).

    The setup I used has two pieces of software. I use QLab for show control, outputting MTC through the MAC built-in IAC driver. Keep in mind that QLab only runs on Mac, and you'll need a pro license to enable timecode, but you can rent a license for 4 USD per day. Other free options like Reaper also exist, but you'll still need to pay after the free trial period.

    I found this tutorial on how to set up QLab with ChamSys. https://www.youtube.com/watch?v=jK_acdzj3bE&t=730s&ab_channel=ChamSysRus. The only thing you can change for better functionality is to change the group cue mode to timeline mode. You just need an audio cue and a timecode cue inside the timeline group. Change the length of the timecode cue to the length of the soundtrack, so you can drag the timeline of the whole group in active cues to sync up the audio and the outputted timecode (and later using external in EOS).

    With a different tutorial on Reaper + EOS, I was able to adapt the ChamSys tutorial to EOS. https://www.youtube.com/watch?v=8By9TrLpw9w&t=335s&ab_channel=Benjermon

    I've tested this setup on my Mac running QLab and EOS at the same time, and it's worked for me. Based on the first tutorial, I'd assume that this would work for a multi-laptop/computer setup. Not sure how this would work on a console because I don't currently have access to one.

Children
No Data
Related

www.etcconnect.com