Jump to content
Dataton Forum

Search the Community

Showing results for tags 'msc'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type



Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 4 results

  1. Hi, we discovered free way to send out MIDI/MSC from Watchout via Bitfocus Companion and the module Midi-relay. Midi-relay is a small java app which sends/receives MSC/notes from your midi-interface by getting http requests. For every command there is a button to program in companion, plus sending a String output http request "BANK-PRESS" from WO to trigger that button. It works flawlessly and being able to trigger sound and light is a big step. The detour over companion is quite time consuming, a direct string output would be nice. So far I had no luck sending a POST http-request with WO: MIDI-relay is running on WO-production, 127.0.0.1 port 4000 { midiport: 'MIDI Port Name', midicommand: 'msc', deviceid: 0, commandformat: 'lighting.general', command: 'go', cue: '10', cuelist: '13', cuepath: '' } So the string from WO would be: POST {...} $0D I tried monitoring with wireshark to see what the syntax in WO should be but did not get clear results. Is it possible to send a .json method as a string output at all? I was looking into the the bome-box / network before, but there is no way to send commands from WO production, as serial output is only available on a display PC or with a TCP/serial converter. Or am I getting sth wrong? https://github.com/josephdadams/midi-relay https://www.bome.com/products/bomenet
  2. Hi everyone, I'm programming a theater show that is largely controlled by external timecode coming from our sound playback system. There are gaps in the timecode which pull us around to different sections of the main timeline. All of that works well. In a few instances when timecode is suspended, we are also taking MSC cues from a GrandMA light board, also in the main timeline. Timecode must not be running for the MSC commands to take. There are two MSC cues that we'd like to place while timecode IS still running. We could make these short cues auxiliary timelines, but it seems like we need to choose to have MSC Cue Lists map to either the Main Timeline or to Aux Timelines. The GrandMA always sends a cue list number with the cue number. Any clever ways to make this work? Seaghan
  3. In the past, we've always had great luck triggering the main timeline using MSC from our ETC Ion (and before it our Obsession). On this show, I had an element that needed to be triggered on cue, while the rest of the timeline was still running. My solution to this withing Watchout was simply to put this extra element in an Aux Timeline. That's when I started to run into problems with the midi. If I set my "Midi Playlist" setting to "ignore", nothing happens. If I set it to "Map to Main Timeline" I can't trigger the aux timeline. If I set it to "Map to Aux Timelines" I can't trigger the main. My first try was to make a timeline called "1" that had all the midi triggers and it, in turn, trigged the main or aux timeline as appropriate. This was intermittently dropping cues, though. I tried putting all the content in timeline "1" and the extra element in timeline "2" but that was still inconsistent. Has anyone run in to this in the past? Ultimately, this became a convenient way to convince the director that this particular cue was a poor choice, but it is something I would like to be able to do in the future. We're running 5.5.1 on Windows 7sp1 Jim
  4. These are the settings that we always set up in the IOS or EON family of ETC lighting desks for successful Midi Show Control (MSC) of Watchout. SMPTE Time Code RX - Enabled MIDI Time Code RX - Enabled Resync Frames - 2 MSC Receive - Disabled (Unless you want to receive MSC from another device, but Watchout doesn't send MSC) NSC Receive Channel - 0 ACN MIDI RX ID - 1 MSC Transmit - Enabled MSC Transmit Channel - 0 ACN MIDI TX ID - 1 (Or whatever you have your device ID set to in Watchout.) Analog Input - Enabled Relay Output - Enabled Serial Enable - Enabled Serial Group ID - 1 A key setting to pay attention to is the TX ID. This is the device ID and it must match the device ID set in Watchout. After all of this is set, you should be able to just set your Control Cues to match the numbers of the cue stack in the lighting desk, and be successfully tracking Midi Show Control. Hope this is helpful.
×
×
  • Create New...