{"id":721,"date":"2020-07-20T16:10:48","date_gmt":"2020-07-20T16:10:48","guid":{"rendered":"http:\/\/techministry.blog\/?p=721"},"modified":"2020-07-20T16:10:48","modified_gmt":"2020-07-20T16:10:48","slug":"tally-arbiter-1-2-support-for-newtek-tricaster-gpo-output-and-tsl-3-1-protocol-conversion","status":"publish","type":"post","link":"https:\/\/techministry.blog\/?p=721","title":{"rendered":"Tally Arbiter 1.2 &#8211; support for newtek tricaster, GPO Output, and tsl 3.1 protocol conversion"},"content":{"rendered":"\n<p>A few weeks ago, I released some <a href=\"https:\/\/techministry.blog\/2020\/07\/01\/using-node-js-python-multiple-raspberry-pis-and-usb-lights-to-create-an-inexpensive-wireless-camera-tally-system-that-can-arbitrate-multiple-sources-simultaneously\/\">free tally light software<\/a> to the community. I&#8217;ve had people checking it out and I am excited to be able to offer some more features!<\/p>\n\n\n\n<p>Some highlights in the 1.1 release:<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>Overall performance improvements<\/li><li>Fixed an issue where Devices added during runtime did not obtain a proper initialization state and would not assign tally data properly until the server was restarted<\/li><li>Fixed an issue where Devices mapped to OBS Studio sources could not correctly be in both preview and program bus at the same time (when in Studio mode)<\/li><li>Better checking on Source connection states<\/li><li>TCP\/UDP ports are now verified as in-use or reserved to help eliminate user errors<\/li><li>More verbose logging in the server console<\/li><li>All tally data received by all Sources is now sent to the Settings page (while open) for logging and diagnostic purposes<\/li><li>New Producer page; allows users to view all device states (tally information) without having the Settings page open. Created in dark mode for in-service viewing<\/li><li>Documentation added to Settings page to assist in initial setup and learning<\/li><li>OSC added as a Source type to trigger tally states<\/li><li>OSC added as a Device Action type (supports multiple arguments)<\/li><li>&#8220;Python&#8221; client renamed to &#8220;blink(1)&#8221; in preparation of other types of listener clients that may also use Python<\/li><li>Version is now displayed on the Settings page for diagnostic purposes<\/li><\/ul>\n\n\n\n<p>Now, I am releasing version 1.2! The highlights:<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li><strong>Newtek Tricaster support<\/strong> now included as a tally source type<\/li><li>OBS can now properly discern whether it is in preview or program<\/li><li><strong>Support for TSL Clients<\/strong> &#8211; Tally Arbiter can now send all device states (derived and arbitrated from any source type) as TSL 3.1 (UDP or TCP) out by specifying a TSL Address for each Tally Arbiter Device. This can be used to drive UMDs and other tally receiving interfaces by acting as a protocol converter between all source types and TSL.<\/li><li><strong>New Python listening client &#8211; GPO Output!<\/strong> Now you can trigger just about anything using the GPIO ports on a Raspberry Pi.<\/li><li>Bug fixes and UI improvements<\/li><li>More documentation and upgrade instructions<\/li><\/ul>\n\n\n\n<p>The biggest feature in this release is the new TSL Clients functionality. Tally Arbiter can now send out TSL 3.1 data to any number of connected devices any time a device changes state within Tally Arbiter. So, you can have, for example, a multiviewer of one switcher dynamically show whether a camera is in use on that switcher or a switcher of an entirely different brand\/model by using Tally Arbiter as a protocol converter.<\/p>\n\n\n\n<p>Here&#8217;s a video to show how the new TSL Clients feature works within Tally Arbiter and how to integrate it with a switcher like the Ross Carbonite. In this example, tally data is coming from both a Carbonite and a Blackmagic ATEM and the Carbonite multiviewer reflects that in real-time.<\/p>\n\n\n\n<figure class=\"wp-block-embed-youtube wp-block-embed is-type-rich wp-embed-aspect-16-9 wp-has-aspect-ratio\"><div class=\"wp-block-embed__wrapper\">\n<div class=\"embed-youtube\"><iframe loading=\"lazy\" title=\"Tally Arbiter 1.2 - Protocol Conversion with TSL 3.1\" width=\"840\" height=\"473\" src=\"https:\/\/www.youtube.com\/embed\/iZd0_K21k6U?feature=oembed\" frameborder=\"0\" allow=\"accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share\" referrerpolicy=\"strict-origin-when-cross-origin\" allowfullscreen><\/iframe><\/div>\n<\/div><\/figure>\n\n\n\n<p>If you&#8217;d like to check out Tally Arbiter or learn more about it, check out the GitHub repository here: <a href=\"https:\/\/github.com\/josephdadams\/TallyArbiter\/\">https:\/\/github.com\/josephdadams\/TallyArbiter\/<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>A few weeks ago, I released some free tally light software to the community. I&#8217;ve had people checking it out and I am excited to be able to offer some more features! Some highlights in the 1.1 release: Overall performance improvements Fixed an issue where Devices added during runtime did not obtain a proper initialization &hellip; <a href=\"https:\/\/techministry.blog\/?p=721\" class=\"more-link\">Continue reading<span class=\"screen-reader-text\"> &#8220;Tally Arbiter 1.2 &#8211; support for newtek tricaster, GPO Output, and tsl 3.1 protocol conversion&#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":[10,15,29,40,50,51,53,67,70],"class_list":["post-721","post","type-post","status-publish","format-standard","hentry","category-uncategorized","tag-atem","tag-carbonite","tag-javascript","tag-nodejs","tag-production","tag-programming","tag-python","tag-tally","tag-tsl"],"_links":{"self":[{"href":"https:\/\/techministry.blog\/index.php?rest_route=\/wp\/v2\/posts\/721","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=721"}],"version-history":[{"count":0,"href":"https:\/\/techministry.blog\/index.php?rest_route=\/wp\/v2\/posts\/721\/revisions"}],"wp:attachment":[{"href":"https:\/\/techministry.blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=721"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/techministry.blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=721"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/techministry.blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=721"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}