ADVANCED PRODUCER SYSTEMS

HyperDeck scheduling, control-panel checks, and troubleshooting

This section is for back of house producers handling recording automation, local control systems, and live troubleshooting in the room. It is intended as an advanced reference, not an entry-level checklist.

Back to TrainingOpen Resources
OverviewCron SetupExamplesControl PanelTroubleshooting

Quick Reference

Use this page when the producer is responsible for automated recordings, HyperDeck connectivity, or system-level troubleshooting during a weekend or special event.

Open cron editor

crontab -e

Start MAMP from Terminal

/Applications/MAMP/openMAMP.app/Contents/MacOS/applet ; exit;

Local HyperDeck interface

http://localhost/

HyperDeck SSD Recording Schedule

This workflow is for scheduling automated HyperDeck recording starts and stops from the ControlBoH computer.

To set the recording schedule

  1. 1Open Terminal.
  2. 2Type `crontab -e`.
  3. 3Type `i` to enter insert mode.
  4. 4Edit the crontab schedule.
  5. 5Press `Esc`.
  6. 6Type `ZZ` (Shift + Z twice) to save and exit.

What the cron job is doing

  • Each line schedules a `curl` command at a specific time.
  • The command hits the local HyperDeck control site on the ControlBoH machine.
  • The query string sends `rec` or `stop` to the configured deck.
  • Use recurring day-of-week schedules for standard weekends and date-specific schedules for holidays or special events.

Example Weekly Cron Job

20 13 * * 6 /Applications/MAMP/Library/bin/curl --silent 'http://localhost/?deck=1&cmd=rec'
55 14 * * 6 /Applications/MAMP/Library/bin/curl --silent 'http://localhost/?deck=1&cmd=rec'
30 16 * * 6 /Applications/MAMP/Library/bin/curl --silent 'http://localhost/?deck=1&cmd=stop'
55 16 * * 6 /Applications/MAMP/Library/bin/curl --silent 'http://localhost/?deck=1&cmd=rec'
30 18 * * 6 /Applications/MAMP/Library/bin/curl --silent 'http://localhost/?deck=1&cmd=stop'
25 8 * * 0 /Applications/MAMP/Library/bin/curl --silent 'http://localhost/?deck=1&cmd=rec'
50 9 * * 0 /Applications/MAMP/Library/bin/curl --silent 'http://localhost/?deck=1&cmd=stop'
55 9 * * 0 /Applications/MAMP/Library/bin/curl --silent 'http://localhost/?deck=1&cmd=rec'
20 11 * * 0 /Applications/MAMP/Library/bin/curl --silent 'http://localhost/?deck=1&cmd=stop'
25 11 * * 0 /Applications/MAMP/Library/bin/curl --silent 'http://localhost/?deck=1&cmd=rec'
30 13 * * 0 /Applications/MAMP/Library/bin/curl --silent 'http://localhost/?deck=1&cmd=stop'

Example Special Event Cron Job

Christmas Services Schedule - December 2024

See cron expressions reference
# Christmas Services Schedule - December 2024

# SATURDAY, DECEMBER 21, 2024
55 16 21 12 * /Applications/MAMP/Library/bin/curl --silent 'http://localhost/?deck=1&cmd=rec'
20 18 21 12 * /Applications/MAMP/Library/bin/curl --silent 'http://localhost/?deck=1&cmd=stop'
25 18 21 12 * /Applications/MAMP/Library/bin/curl --silent 'http://localhost/?deck=1&cmd=rec'
00 20 21 12 * /Applications/MAMP/Library/bin/curl --silent 'http://localhost/?deck=1&cmd=stop'

# SUNDAY, DECEMBER 22, 2024
25 15 22 12 * /Applications/MAMP/Library/bin/curl --silent 'http://localhost/?deck=1&cmd=rec'
50 16 22 12 * /Applications/MAMP/Library/bin/curl --silent 'http://localhost/?deck=1&cmd=stop'
55 16 22 12 * /Applications/MAMP/Library/bin/curl --silent 'http://localhost/?deck=1&cmd=rec'
20 18 22 12 * /Applications/MAMP/Library/bin/curl --silent 'http://localhost/?deck=1&cmd=stop'
25 18 22 12 * /Applications/MAMP/Library/bin/curl --silent 'http://localhost/?deck=1&cmd=rec'
50 19 22 12 * /Applications/MAMP/Library/bin/curl --silent 'http://localhost/?deck=1&cmd=stop'

# MONDAY, DECEMBER 23, 2024
55 16 23 12 * /Applications/MAMP/Library/bin/curl --silent 'http://localhost/?deck=1&cmd=rec'
20 18 23 12 * /Applications/MAMP/Library/bin/curl --silent 'http://localhost/?deck=1&cmd=stop'
25 18 23 12 * /Applications/MAMP/Library/bin/curl --silent 'http://localhost/?deck=1&cmd=rec'
50 19 23 12 * /Applications/MAMP/Library/bin/curl --silent 'http://localhost/?deck=1&cmd=stop'

# TUESDAY, DECEMBER 24, 2024
55 10 24 12 * /Applications/MAMP/Library/bin/curl --silent 'http://localhost/?deck=1&cmd=rec'
20 12 24 12 * /Applications/MAMP/Library/bin/curl --silent 'http://localhost/?deck=1&cmd=stop'
25 12 24 12 * /Applications/MAMP/Library/bin/curl --silent 'http://localhost/?deck=1&cmd=rec'
50 13 24 12 * /Applications/MAMP/Library/bin/curl --silent 'http://localhost/?deck=1&cmd=stop'
55 13 24 12 * /Applications/MAMP/Library/bin/curl --silent 'http://localhost/?deck=1&cmd=rec'
20 15 24 12 * /Applications/MAMP/Library/bin/curl --silent 'http://localhost/?deck=1&cmd=stop'
25 15 24 12 * /Applications/MAMP/Library/bin/curl --silent 'http://localhost/?deck=1&cmd=rec'
50 16 24 12 * /Applications/MAMP/Library/bin/curl --silent 'http://localhost/?deck=1&cmd=stop'
55 16 24 12 * /Applications/MAMP/Library/bin/curl --silent 'http://localhost/?deck=1&cmd=rec'
20 18 24 12 * /Applications/MAMP/Library/bin/curl --silent 'http://localhost/?deck=1&cmd=stop'
25 18 24 12 * /Applications/MAMP/Library/bin/curl --silent 'http://localhost/?deck=1&cmd=rec'
50 19 24 12 * /Applications/MAMP/Library/bin/curl --silent 'http://localhost/?deck=1&cmd=stop'

HyperDeck Control Panel

We use HyperDeck Control Panel to create a HyperDeck web interface. The local system turns the ControlBoH computer into a web server using MAMP and hosts the control page at `http://localhost/`.

  • We use HyperDeck Control Panel to create the HyperDeck web interface.
  • The ControlBoH computer runs MAMP and hosts the local website at `http://localhost/`.
  • That local web interface sends commands to the HyperDeck for record, stop, and status checks.
  • If something fails, isolate whether the issue is the web interface, MAMP, the HyperDeck itself, or signal routing.

Related site

http://hyperdeck.iamjeffamato.com/

Troubleshooting

Work from the simplest physical checks first, then move toward software, networking, and routing. The goal is to isolate the failure quickly without creating extra variables.

The HyperDeck won’t start recording

  • If the HyperDeck Control Panel web interface is not working, try the record button manually on the recorder itself. If manual recording works, continue through the system checks below.
  • Check that both SSDs are installed in the HyperDeck.
  • Make sure there is available space on the SSD drives.
  • If needed, format the SSDs from the HyperDeck menu: Menu > Format SSD > Format SSD # > HFS+ > Format SSD.

The broadcast program is not showing on the preview HyperDeck screen

  • Make sure the Program feed is actually being output. Verify on the top-right multiviewer monitor.
  • Press the `INPUT` button on the HyperDeck recorder and confirm the live input is selected.
  • Check the SDI lines.
  • Make sure routing is correct in both the router and the switcher.

The HyperDeck web interface is not loading at all

  • If MAMP is not running, the HyperDeck web interface will not load.
  • Check whether MAMP is running. If it is not, open Terminal and run `/Applications/MAMP/openMAMP.app/Contents/MacOS/applet ; exit;`
  • If that does not work, open `MAMP.app` manually from Applications and click `Start Server`.

The HyperDeck web interface is running, but cannot connect to the HyperDeck

  • From the HyperDeck menu, check the unit IP address.
  • From the web interface, open settings and make sure the saved IP address matches the unit.

Lyrics are not displaying on the LED wall

  • From CG2 in PVP, navigate to the `Startup` group and click the ProPresenter NDI source.
  • If that does not work, make sure Wi-Fi is turned on.
  • If Wi-Fi is on and still not working, toggle Wi-Fi off and back on, making sure the `Tech208` network is selected.
  • If that still does not work, ask the lighting operator, typically Jared.

Teradeks are not working

  • If nothing appears after 15 seconds with the cameras powered on in the room, ask operators to reboot their Teradek transmitters.
  • If restarting the transmitter does not work, ask the operator to reboot the receiver.
  • Receiver locations: Cam 3 on the stage-right wall under the multiviewer monitor; Cam 4 stage left next to the front curtain near the ADA hallway; Cam 5 mounted to the Camera 1 tripod.
  • If restarting the receiver does not work, check power to both the transmitter and the receiver.
  • If everything has power, open `Spectrum Analyser` on the receiver, pick a frequency with low activity, and wait up to 30 seconds for sync.
  • Make sure the receiver menu is closed afterward so it does not appear on the video output.
  • If needed, try another frequency.

Advanced systems still serve the same mission

Even when the task is highly technical, the goal stays the same: support the room, remove distractions, and help the message move clearly.

Back to Role TrainingBrowse Resources