Studio Setup: Difference between revisions

← Older edit

Studio Setup (view source)

Revision as of 14:46, 6 December 2022

417 bytes removed , 6 December 2022

admin team group, administrators, computing team, computing team group, domain admins, domain users, livestream distribution, livestream technicians, old calendar, producers, stv admin

65

edits

@@ Line 3: / Line 3: @@
 SDI patches 91-94 are routed from the studio into cameras 1-4 on the ATEM Television Studio 4K in the control room.
 : The wire for camera 4 in the loom is dodgy and needs replacing, for now it's hard-patched. [[User:Marks.polakovs|Marks.polakovs]] ([[User talk:Marks.polakovs|talk]]) 11:21, 16 November 2022 (UTC)
+SDI 95 is patched to one of the ATEM's non-program outputs, for use with camera control and tally (there's a SDI splitter on the studio side that runs it into the cameras, to avoid needing to run four more SDIs from the studio).
 The ATEM's program out is patched into SDI 0 on edit2's DeckLink for broadcast (usually through OBS).
@@ Line 15: / Line 18: @@
 :* Audio onto SDI, into a de-embedder, into X32 - spenny money (the Decimator can do it, but it's a bit overkill and a waste of a decimator)
 : Further tinkering is required. [[User:Marks.polakovs|Marks.polakovs]] ([[User talk:Marks.polakovs|talk]]) 11:21, 16 November 2022 (UTC)
+:: Could also be that Caspar is configured to use too high a latency. Worth experimenting, but that path may end up futile - per the Caspar developers, [https://casparcgforum.org/t/5-1-audio-via-system-audio-or-asio/2702/5 system audio is intended for testing, and is "not in sync to the decklink"]. [[User:Marks.polakovs|Marks.polakovs]] ([[User talk:Marks.polakovs|talk]]) 12:06, 16 November 2022 (UTC)
+: More or less settled on using the [[Decimator]] MD-DUCC as an audio de-embedder, unless we decide at some point to get an actual de-embedder (which I'm not fully convinced is a valuable use of money). [[User:Marks.polakovs|Marks.polakovs]] ([[User talk:Marks.polakovs|talk]]) 14:37, 6 December 2022 (UTC)
-Caspar is controlled using a Stream Deck running BitFocus Companion. As a nice bonus, this can be set up to trigger the VT, transition the ATEM, fade up the X32, and trigger OnTime, all with one button press.
+Caspar is controlled using a Stream Deck running BitFocus Companion. As a nice bonus, this can be set up to trigger the VT, transition the ATEM, fade up the X32, and trigger [[OnTime]], all with one button press.
 == TV Graphics ==
-Currently it's been done using NDI: running NDI Screen Capture on one of the PCs (usually edit3) and Studio Monitor on one of the laptops, running into the TV - and also into OBS.
+The TV in the studio (usually on [[Tom Lee]]) is connected (via a Micro Converter) into SDI patch {{unsure|71}}, which is connected into the AUX output on the ATEM. This is usually set to show Media Player 2, but can be changed (press the AUX button on the top-right, under MENU, then select the output you want on the program row).
-: This is overkill, and requires three PCs. [[User:Beth.marsch|Beth]] suggested just using the ATEM's media players, aux'd into the TV. This is a good idea. Let's do that. [[User:Marks.polakovs|Marks.polakovs]] ([[User talk:Marks.polakovs|talk]]) 11:21, 16 November 2022 (UTC)
 = OnTime =
@@ Line 27: / Line 31: @@
 [[OnTime]] is the stage timer system we use to manage time for live shows with a specific running order. It is a piece of software that usually runs on edit1.
-A Streamdeck can be used to make it easier to control [[OnTime]], although it can be controlled using just a keyboard and mouse just fine. The Streamdeck can be connected using [https://bitfocus.io/companion BitFocus Companion] and the plugin [https://github.com/bitfocus/companion-module-getontime-ontime GetOnTime-OnTime], which should be pre-installed with BitFocus Companion (I need to double check that).
+The timer view for [[OnTime]] is displayed on the iMac on the control room monitor wall and the Mac Mini rigged in the studio lighting rig. This allows crew members to see the timings for the current production.
-The timer view for [[OnTime]] is displayed on the iMac on the control room monitor wall and the Mac Mini rigged in the studio lighting rig.
-The Macs should automatically display the [[OnTime]] timer view when they are powered on; this is currently achieved by a script which runs on startup and opens Firefox in kiosk mode to https://go.ystv.co.uk/signage. At the time of writing, this redirects to edit1's IP address on port 4001. This redirection can be changed by modifying the entry for "signage" on the [[URL Shortener]] admin page.
-The Mac Mini in the lighting rig will automatically boot on power; the iMac on the monitor wall will need to manually be powered on. Both Macs will also need to be shutdown manually - this can be done by pressing the power button once and they'll shutdown after 60 seconds.
+When the Macs are switched on, they should automatically display the timer view. See the [[OnTime]] page for more information on how this works and how it can be changed.
-Both Macs currently run Ubuntu. We still need to investigate a proper signage solution. We did attempt to use PiSignage, however it turns out trying to use something designed for a Raspberry Pi on Ubuntu on a Mac doesn't work very well (the main reason we're using the Macs for signage is because they were just lying around not being used and aren't really suitable to be used for anything else).
 [[Category:Tech]] [[Category:Tech/Vision Path]]