{"id":525,"date":"2020-02-26T19:17:11","date_gmt":"2020-02-26T19:17:11","guid":{"rendered":"http:\/\/techministry.blog\/?p=525"},"modified":"2020-02-26T19:17:11","modified_gmt":"2020-02-26T19:17:11","slug":"walkthrough-setting-up-midi-relay-on-macos-to-control-chroma-q-vista-3-with-a-stream-deck-over-the-network","status":"publish","type":"post","link":"https:\/\/techministry.blog\/?p=525","title":{"rendered":"Walkthrough: Setting up midi-relay on MacOS to control Chroma Q Vista 3 with a Stream Deck over the network"},"content":{"rendered":"<p>I have had a few people ask if I could post another walkthrough with more precision on setting up <a href=\"http:\/\/techministry.blog\/2019\/06\/06\/controlling-chroma-q-jands-vista-with-midi-show-control-and-a-stream-deck-using-node-js-and-the-web-midi-api\/\">midi relay<\/a> to control Chroma Q Vista (formerly owned by Jands) with their stream decks.<\/p>\n<p><strong>What you will need:<\/strong><\/p>\n<ul>\n<li>MacOS running Vista 3 (Vista 2 will also work)<\/li>\n<li>Node.js installed, or you can download the MacOS binary release of midi-relay here: <a href=\"https:\/\/github.com\/josephdadams\/midi-relay\/releases\" target=\"_blank\" rel=\"noopener\">https:\/\/github.com\/josephdadams\/midi-relay\/releases<\/a><\/li>\n<li>Bitfocus Companion installed and running on a computer\/device (it can be the same computer running Vista, or another computer on the network)<\/li>\n<\/ul>\n<p><strong>To set it all up:<\/strong><\/p>\n<ol>\n<li>First, you will need to set up the loop-back MIDI port. Open\u00a0<em>Audio MIDI Setup<\/em>. It&#8217;s in Applications &gt; Utilities.<\/li>\n<li>In the\u00a0<em>Audio MIDI Setup<\/em> window, choose\u00a0<em>Window<\/em> from the top menu, then\u00a0<em>Show MIDI Studio<\/em>.<\/li>\n<li>This opens the\u00a0<em>MIDI Studio<\/em> window. You will see a few options here such as\u00a0<em>Bluetooth<\/em>,\u00a0<em>IAC Driver<\/em>, and\u00a0<em>Network<\/em>. Depending on how you may have configured MIDI ports in the past, the number of devices here can vary.<\/li>\n<li>Double click the\u00a0<em>IAC Driver<\/em> device. This will open the Properties window. The main thing you need to do is click the checkbox for &#8220;<em>Device is online&#8221;\u00a0<\/em>(if not already checked). You may also want to change the device name to\u00a0<em>Vista<\/em>.<\/li>\n<li>You can close out all of the\u00a0<em>Audio MIDI Setup<\/em> windows now.<\/li>\n<li>Now you need to start\u00a0<em>midi-relay<\/em> running. Open a\u00a0<em>Terminal<\/em> window and change directory to where you put the executable file for\u00a0<em>midi-relay<\/em>. I put mine in a subfolder within the\u00a0<em>Documents<\/em> folder.\u00a0<strong>It&#8217;s important that you run the executable while the Terminal window directory is the same folder the executable is in, or things may not work correctly.\u00a0<\/strong>Once you&#8217;ve changed directory to the correct folder, you can drag the executable file from\u00a0<em>Finder<\/em> to the\u00a0<em>Terminal<\/em> window, or you can type in the executable name manually. Hit enter to run it.<\/li>\n<li>When\u00a0<em>midi-relay<\/em> starts up, it will give you a read-out in the console of all the available MIDI in\/out ports. You should now have one that says\u00a0<em>Vista Bus 1<\/em>.<\/li>\n<li>Open\u00a0<em>Vista<\/em>. Go to the\u00a0<em>User Preferences<\/em> menu by selecting File &gt; User Preferences.<\/li>\n<li>Go to the\u00a0<em>MIDI<\/em> tab.<\/li>\n<li>Under the\u00a0<em>MIDI Show Control<\/em> section, set the\u00a0<em>Device ID<\/em> to 0 (zero).<\/li>\n<li>Under the\u00a0<em>External MIDI Ports<\/em> section, check the box next to the\u00a0<em>Vista Bus 1<\/em> MIDI port.<\/li>\n<li>Click OK.<\/li>\n<li>In Vista, right click on the cue list you want to use with MIDI control, and choose\u00a0<em>Properties<\/em>.<\/li>\n<li>Go to the\u00a0<em>MIDI\u00a0<\/em>tab.<\/li>\n<li>Now open the\u00a0<em>Companion Web GUI\u00a0<\/em>on the computer that is running Companion.<\/li>\n<li>Add a new instance by searching for\u00a0<em>Tech Ministry MIDI Relay<\/em>.<\/li>\n<li>In the instance configuration, type in the IP address of the computer running Vista and midi-relay. If you&#8217;re running Companion on the same computer, you can use IP address\u00a0<em>127.0.0.1<\/em>.<\/li>\n<li>Click\u00a0<em>Apply Changes<\/em>.<\/li>\n<\/ol>\n<p><strong>To Send a MIDI Note On and advance a cuelist:<\/strong><\/p>\n<ol>\n<li>Add a new button in Companion.<\/li>\n<li>Add a new action to that button, using the midi-relay action,\u00a0<em>Send Note On<\/em>.<\/li>\n<li>Under the options for this action, choose the <em>Vista Bus 1<\/em> for the MIDI port.<\/li>\n<li>By default, it will send channel 0, note A0 (21), with a velocity of 100. Vista does not look for a specific velocity value, only channel and note. Vista will listen to any channel by default, but if you set a specific channel in the Vista MIDI settings, you will need to make sure you send the correct channel from Companion.<\/li>\n<li>Go back to Vista and in the\u00a0<em>Cuelist Properties<\/em>,\u00a0<em>MIDI\u00a0<\/em>tab, click <em>Learn<\/em> next to the\u00a0<em>Play<\/em> item. The\u00a0<em>Play<\/em> command is what advances a cuelist. The\u00a0<em>Learn<\/em> function will listen for incoming MIDI notes and makes setting the MIDI note slightly easier (and it proves that it works). You can also just set the note manually if you want.<\/li>\n<li>Go back to Companion and click\u00a0<em>Test Actions<\/em> (or press the physical button on your stream deck if you are using one), and the\u00a0<em>Learn<\/em> box in Vista will go away, and you&#8217;ll see that the note you sent from Companion is now populated in the Vista settings.<\/li>\n<li>Now every time you press that button in Companion, it will advance that cuelist. If you have multiple cuelists, you will need to use different MIDI note values.<\/li>\n<\/ol>\n<p><strong>To Send a MIDI Show Control message to go to a specific cue in a cuelist:<\/strong><\/p>\n<ol>\n<li>Add a new button in Companion.<\/li>\n<li>Add a new action to that button, using the midi-relay action,\u00a0<em>Send MSC Command<\/em>.<\/li>\n<li>Choose\u00a0<em>Vista Bus 1<\/em> for the MIDI port.<\/li>\n<li>The default Device ID is 0 (zero) but if you changed that in Vista, make sure it matches here.<\/li>\n<li>The Command Format should be\u00a0<em>Lighting &#8211; General<\/em> and the Command should be\u00a0<em>Go<\/em>.<\/li>\n<li>The\u00a0<em>Cue<\/em> field should be the specific Cue Number in Vista of the Cuelist you want to control.<\/li>\n<li>The\u00a0<em>Cue List<\/em> field should be the specific Cuelist Number in Vista.<\/li>\n<li>Now every time you press that button in Companion, it will go to that specific cue in that specific cuelist.<\/li>\n<\/ol>\n<p>Here&#8217;s a walkthrough video of these steps:<\/p>\n<p>[wpvideo HZriRGlS]<\/p>\n<p>I hope this is helpful! If you&#8217;re using MIDI relay, feel free to drop a comment and share how it is working for you!<\/p>\n","protected":false},"excerpt":{"rendered":"<p>I have had a few people ask if I could post another walkthrough with more precision on setting up midi relay to control Chroma Q Vista (formerly owned by Jands) with their stream decks. What you will need: MacOS running Vista 3 (Vista 2 will also work) Node.js installed, or you can download the MacOS &hellip; <a href=\"https:\/\/techministry.blog\/?p=525\" class=\"more-link\">Continue reading<span class=\"screen-reader-text\"> &#8220;Walkthrough: Setting up midi-relay on MacOS to control Chroma Q Vista 3 with a Stream Deck over the network&#8221;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[32,35,37,38,50,66,68,75],"class_list":["post-525","post","type-post","status-publish","format-standard","hentry","category-uncategorized","tag-lighting","tag-mac","tag-midi","tag-ministry","tag-production","tag-stream-deck","tag-technology","tag-vista"],"_links":{"self":[{"href":"https:\/\/techministry.blog\/index.php?rest_route=\/wp\/v2\/posts\/525","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/techministry.blog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/techministry.blog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/techministry.blog\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/techministry.blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=525"}],"version-history":[{"count":0,"href":"https:\/\/techministry.blog\/index.php?rest_route=\/wp\/v2\/posts\/525\/revisions"}],"wp:attachment":[{"href":"https:\/\/techministry.blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=525"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/techministry.blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=525"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/techministry.blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=525"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}