Skip to main content

Building a Smart Video Studio in 10 Days for the Meta Hackathon (TWOC Studio Hub)

For the Meta Global AI Developer Hackathon, I spent around 10 days turning my creative video space into a connected, controllable smart studio. The web application's code is hosted on GitHub as TWOC-Studio-Manager under the AGPL-3.0 license. It pulls together smart power plugs, studio lighting over three different control protocols, OBS Studio scene switching, a dedicated backdrop monitor with custom animations and audio beds, timed multi-device sequences, and an AI orchestrator powered by Meta's API. 

Watch my demonstration video on YouTube: 




To get everything working in 10 days use the $150 worth of API credits, I built the system using Meta's AI developer tools, mainly Muse Code (running the muse-spark-1.3-contributor model to conserve tokens, along with Muse Wonder Full) and the Meta Model API. Overall, Meta's tools were straightforward to use and felt like enhanced vibe coding, though my software development and technical background still came into play whenever I had to debug hardware, direct the AI to Bluetooth packet logs, or trace wiring with a multimeter.

Using an Android phone to open the Studio Hub web interface and view the Zones panel, with a wide shot of the studio space in the bottom-right corner.

Studio Architecture: Hub Computer, Web UI, and Smart Zones

Rather than tying everything directly to my primary editing and recording PC, I run the Studio Hub FastAPI server on a dedicated Hub Manager PC. The web UI runs locally on my network, which means I can open a browser on my main workstation or pull it up on my smartphone while walking around the room. 

The Studio Hub Dashboard in a desktop browser alongside multiple live studio camera feeds.

Most of the gear in the room is organized into zones controlled by TP-Link Kasa smart plugs (plug-1 through plug-6, using Kasa HS103 plugs), alongside two logical zones that do not use smart plugs:

Here's how it breaks down which might be helpful to understand it all: 

  • Hub Manager (no plug): Hub Manager PC, IR transceiver, and the KQC 15.6in backdrop screen.
  • Workstation | Computer (plug-1): Main workstation PC, with a checkbox to automatically launch OBS after boot.
  • Workstation | Content Creation (plug-2): Sony A6400 main camera, Andycine A6 Pro field monitor, WGR 15.6 inch 1080p Portable Monitor, and Weeylite Viltrox Ninja 10 COB light.
  • Workstation | Background (plug-3): Background LED Strip Light and Workstation GVM 1500D panel.
  • Hands-On (plug-4): Atomos Ninja V recorder, Hands-On GVM 1500D panel, and Ninja 20 Hands-On Key light.
  • Hands-On - Workstation Screens (plug-5): Workstation screens used during hands-on segments.
  • Ambient Mood Light (plug-6): Weeylite Viltrox Ninja 400 light.
  • Crew (no plug): Clamp light (5600K), CRAPHY PT-15B panel, and ceiling ambient light (5600K).

The Kasa smart plugs communicated with the Hub Manager PC over my local WIFI network. Getting them integrated took some time because of their communication protocol and by default being locked down. I would like to add a dedicated Wi-Fi dongle directly to the hub computer so the switches can communicate straight with it rather than riding on the main network. So far I haven't implemented that, or at least tried to see if it was possible and works well. 

Using the local website on my phone to power up the computer and screens.

IMAGE 0005 = 0:01:25.500

The Zones card on the Dashboard listing the Kasa smart plug assignments and equipment inside each studio zone.

Power-cycling zones works cleanly for lights, such as shutting off the Workstation | Background zone to turn off the background shelving strip, overhead panel, and background camera in one click. Though one camera in my studio still requires physically pressing a button to switch into webcam mode. In time, I will probably have to look into hacking the camera firmware or finding another workaround for that. Some for the Atomos Ninja V HDMI recorder an to a degree the Weeylite Ninja 20 and Ninja 400. 

Turning off the Workstation | Background zone cuts power to the background shelves, GVM panel light, and background camera while leaving the rest of the studio on.


Supplemental Information: Kasa Local Protocols

Older TP-Link Kasa smart plugs used an unauthenticated XOR protocol on TCP/UDP port 9999, whereas newer hardware and firmware updates migrated devices to the authenticated KLAP protocol over HTTP port 80. Even when controlled strictly on a local network without cloud relays, KLAP performs a local handshake verified against credentials linked to the TP-Link account.


Booting OBS Over Audio Cables (DTMF) and Controlling Scenes

When setting up remote OBS startup on my main workstation PC, I intentionally avoided triggering commands over the network. I did not want a mechanism sitting on the local network that could execute programs remotely on my main computer. I was also thinking something unique would be fun. 

Instead, I wired two 3.5mm audio cables between the Hub Manager PC and the workstation (TX port cable A out, RX port cable B in). The two machines communicate using Dual-Tone Multi-Frequency (DTMF) tones, the touch-tone signaling system originally developed by Bell Labs for telephones. One cable sends commands out from the hub, and the other sends confirmation tones back in a ping-pong loop.

Waiting for OBS to launch using that DTMF technique on the main workstation monitor after Windows boots.

When the Workstation | Computer zone boots with automatic OBS startup enabled, or when I click Start OBS (workstation) on the Dashboard or Boot + OBS on the Test Bench, a listener running on the workstation hears the DTMF signal, opens OBS Studio, and loads my scene collection and starting scene.

The PC link section on the Test Bench tab showing the TX and RX audio wire port settings, ping/pong test controls, OBS boot trigger, and DMX light controls below.

Supplemental Information: What Is DTMF Signaling?

Dual-Tone Multi-Frequency (DTMF) signaling was developed by the Bell System and introduced commercially in 1963 under the Touch-Tone trademark. Each symbol pairs one frequency from a low-frequency group with one frequency from a high-frequency group simultaneously, making the tones straightforward to decode reliably over a standard audio channel.

Once OBS is running, the Dashboard gives me direct scene buttons (Face Full View, Back Camera Full, Face & Hands-on, Side-By-Side, Multi-Cam Screen, and others), scene collection switching, and Start stream / Stop stream buttons gated behind a confirm stream start/stop checkbox. Switching views from either desktop Chrome or my phone works quickly.


Controlling Studio Lighting Across Three Protocols

Because my studio combines COB lights, LED panels, and a cheap RGB strip light behind the shelves, Studio Hub had to speak three completely different lighting protocols: DMX, Bluetooth, and infrared.

1. Wired DMX Control and Fixing a Mismatched Adapter (Weeylite Viltrox Ninja 400)

The Weeylite Viltrox Ninja 400 in my Ambient Mood Light zone is controlled over a physical DMX cable. I have two lights that support both DMX and Bluetooth, and for the hackathon setup I kept the Ninja 400 wired on DMX while running the others over Bluetooth. From Studio Hub, DMX gives me 0-100% brightness adjustments, bi-color temperature control for warmer or cooler mood lighting, and timed fades on the Test Bench.

Getting the physical DMX wiring working took some troubleshooting. I bought an adapter to go from a 3-pin XLR DMX connector to an RJ45 jack, and the adapter arrived with the wrong pin layout for the light. I brought out a digital multimeter and used Muse Code to help map out where each pin should go, then built a custom network cable that worked.

Close-up of the RJ45-to-3-pin XLR DMX adapter that arrived with the wrong pinout for the Ninja 400.

Using a red digital multimeter and test leads on the desk mat to check pin continuity on the DMX adapter.

Supplemental Information: DMX512 and RJ45 Pinouts

DMX512 (ANSI E1.11) transmits unidirectional EIA-485 differential serial data over a twisted pair plus a signal common, mapped on standard XLR connectors as Pin 1 common/shield, Pin 2 Data-, and Pin 3 Data+. Although the official standard specifies 5-pin XLR, 3-pin XLR is widely used as a de facto connector on lighting fixtures, while lights like the Weeylite Ninja 400 use RJ45 ports for DMX input and output. ANSI E1.27-2 defines a standard Cat5/Cat6 pinout for RJ45 DMX wiring, though non-standard manufacturer pinouts exist, so off-the-shelf adapters do not always match every fixture.

2. Reverse-Engineering Bluetooth Lights via Android (Weeylite and GVM 1500D)

My Weeylite Viltrox Ninja 10 COB key light and Workstation GVM 1500D overhead panel run over custom Bluetooth control, alongside the Hands-On GVM 1500D and Ninja 20 Hands-On Key in the hands-on zone.

Rather than guessing Bluetooth Low Energy commands manually, I connected an Android phone to my workstation PC running Muse Code over ADB. Muse Code automated tapping the interface in the Weeylite and GVM Android apps (adb shell input tap), pulled the phone's /sdcard/btsnoop_hci.log Bluetooth capture, and cleanly reverse-engineered the Bluetooth protocols for both light families using a clean room approach. 

Development setup showing Windows Terminal running Muse Code with muse-spark-1.3-contributor, automated ADB taps pulling btsnoop_hci.log, the Meta Global AI Developer Hackathon page, and the Android lighting app.

In the Studio Hub Control tab, I can power each Bluetooth light on or off, adjust brightness (protected by an "allow bright" (past the gentle 10%) checkbox so I do not accidentally blind myself at 100%), set Kelvin color temperature (such as 5000K or 5600K), and pick RGB hue and saturation values on the GVM 1500D panels.

The Control tab for the Weeylite Viltrox Ninja 10 COB showing Bluetooth brightness controls and the safety toggle for going past 10% output.


Turning up the Ninja 10 COB brightness over Bluetooth noticeably illuminates the workstation key light.


3. Infrared Control Over USB-to-Serial (Background LED Strip Light)

The background strip light behind my shelves (a Bytech-style RGB LED adhesive strip light) uses a basic infrared remote rather than Wi-Fi or Bluetooth. To wire it into Studio Hub, I bought an inexpensive infrared transceiver module and attached it to a USB-to-serial board plugged into the Hub Manager PC right next to the strip's IR receiver. I then used Muse Code to read the codes coming off the handheld remote and mimic the protocol. 

Close-up of the infrared transceiver module connected to a red USB-to-serial adapter board

On the Control tab, the LED Strip Light page gives me 16 quick color buttons. Since it is a very cheap RGB strip, "white" is not true-to-form, and brightness stepping along with the strip's built-in animated modes (like the breathing effect).

Clicking royal blue on the LED Strip Light Control page changes the shelving background light behind the workstation to blue.


Backdrop Screen Animations, Text Overlays, and Audio Beds

Behind my workstation sits a KQC 15.6in portable screen connected to the Hub Manager PC so I can change what appears in the background depending on the mood of a livestream or recording. I bought it for the hackathon on a whim and I was glad I did because it added a lot to the project. I'd actually like to get a second one so my background is more symmetrical. 

Using Muse Code, I generated custom animations for this backdrop display:

  • Fish tank
  • Underwater reef
  • Fireplace
  • Starfield (with shooting stars)
  • Galaxy (Hubble spiral)
  • Code rain (programming)
  • Circuit (tech news)
  • Arcade (gaming) and Dice (D&D)
  • Build bay (mecha / gunpla)
  • Audio studio (meters)
  • Bistro (food / drink)
  • Cosplay, Unboxing, 
  • Tinker (soldering / repairs)
  • Photon animation (Scotty Photon)

The Asset dropdown on the Control tab listing all configured lights, displays, monitors, and the Atomos Ninja V recorder with text on the back kiosk screen.

Setting the KQC 15.6in backdrop screen to the Fish tank animation with custom text and audio playback controls below.

I can also pick a theme, push custom text (for example, Tonight: co-op night), specify a display duration in seconds, or clear the screen. There is still a slight quirk where I sometimes have to hit Clear before pushing a new animation cleanly.

Pushing the Underwater reef animation to the backdrop screen from the zoomed-in control view.

Below the screen controls, there is an audio player with looping background beds (such as Eurobeat and Piano, plus a lo-fi track that Muse Code made) and sound effects (stinger), complete with a volume slider and Play bed / Stop bed buttons. The audio plays directly out of the Hub Manager PC, though in my unedited test recording I did not pipe that machine's audio feed into my screen capture.

Running the Code rain (programming) animation alongside the Eurobeat audio bed in the backdrop screen controls.

Equipment Metadata, Modality Manager, and Test Bench

Alongside single-device controls, Studio Hub includes three management and testing pages:

Equipment Tab

The Equipment tab lets me add or remove studio gear, manage multiple studio profiles (Home Studio and Example Studio), and move devices between smart plug zones. Each item also includes descriptive metadata fields (Role, Position, Distance to subject (m), Power, Est. watts, Modifiers, and Visual JSON) that get fed to the AI orchestrator so it has context on what each device does and where it sits in the room.

The Equipment tab displaying datapoints for the Hub Manager PC and the multi-studio selector dropdown.

Equipment metadata fields for Hands-On GVM 1500D and the Zones management controls at the bottom of the page.

Modality Manager

The Modality Manager combines modes, presets, and timed presentations into step-by-step sequences called "beats." Each beat can trigger an OBS scene change, individual or zone light JSON settings, backdrop screen changes (kiosk screen JSON), smart plug power commands, and a hold timer. 

I tested sequences like GVM Showcase (21 beats stepping and flashing the overhead GVM panel through different brightness and color states), workstation chill (which brings up the fish tank backdrop and dims the lights), and workstation light showcase. Several of the saved modalities still contain older test data, and there are a few UI quirks left to polish, but it demonstrates how automated lighting cues could work during a stream.

The Modality Manager.


Test Bench

The Test Bench page holds low-level hardware controls used during development and debugging, including raw Kasa plug toggles, IR strip brightness stepping and built-in animated modes, direct Bluetooth sliders, DMX fade testing (such as 0.5-second fade steps on the Ninja 400), and the TX/RX audio link configuration.


The AI Look Orchestrator (Meta Model API)

On the Dashboard, the AI look panel connects Studio Hub to the Meta Model API so I can adjust lighting and the backdrop display from plain text or voice prompts. I can type a request (like cozy interview), check which zones are included, toggle between lights+screen or Direct modes, or click Mic with auto-direct on hear checked to speak a prompt directly. This has been reworked since the hackathon to revise how it works. I had deleted the API key and swapped to a local Gemma-4 model running on the old Hub computer. It works surprisingly well, but is somewhat slow given the PC has a GTX 1060 6GB GPU and I'm trying to get it to run a ~4.5 GB model. 

The AI look orchestrator panel on the Dashboard showing the text prompt box, microphone controls, zone checkboxes, and hardware summary.

Studio lighting and the backdrop screen update after the Meta API processes the cozy gaming prompt.

For the hackathon, the Studio Hub sends my zone layout and equipment metadata to the Meta cloud API and applies the returned adjustments. 


Source Code and Post-Hackathon Updates

The full project source code is published on GitHub at TheWayOfCoding/TWOC-Studio-Manager under the AGPL-3.0-or-later license.

Since the hackathon wrapped up, I have continued updating the repository beyond what is shown in the demo video. 

As of this article: newer updates include a local GPU model option (llama-server) alongside the Meta API so looks can run without a cloud round trip, named default equipment snapshots (defaults.json) for one-click resets, a /datamap health check view, dual BLE/DMX interface switching on both the Ninja 20 and Ninja 400 that support both, and a lot more. 

Supplemental Information: Meta Global AI Developer Hackathon and Muse Tools

The Meta Global AI Developer Hackathon ran virtually for 10 days from October 26 to November 4, 2026, with developers building projects using the Meta Model API alongside Meta's Muse models and developer tools. Within that lineup, Muse Code is Meta's coding agent, Muse Wonder is Meta's flagship agent model, and the Muse Spark series includes models such as Muse Spark 1.3 for coding and multimodal tasks.

Working with Muse Code (muse-spark-1.3-contributor and Muse Wonder) was straightforward and felt like enhanced vibe coding. That said, I do think actual software development experience still matters a lot with making complex systems.

Triggering the studio shutdown turns off the lights across the room at once.

For 10 days of work, I am happy with how much came together, and it is a project I plan to keep refining and debugging over time. If you want to see the lighting changes, backdrop animations, audio playback, and DTMF OBS boot sequence in motion, watch the full hackathon walkthrough video.


Here are most of the products I bought for this hackathon project: 

As an Amazon Associate, I earn from qualifying purchases!


Popular posts from this blog

Reviewing the Thermalright TL-G12 and TL-C14 Fans

I recently picked up a bunch of Thermalright fans for a new PC build, specifically the TL-G12 (120mm) and the TL-C14 (140mm). At the time, they were pretty inexpensive, and the promise of fluid dynamic bearings (FDB) along with PWM control sounded like a great deal on paper, so I bought quite a few of each. In this article and related video I go into detail about their installation and use.  Boxes for the Thermalright TL-G12 and TL-C14 fans. Specifications listed on the TL-G12 fan box. Specifications for the 120mm TL-G12: Speed: 1500 RPM (+/- 10%) Noise: Rated 23.6 dBA or greater. Airflow: Up to 62.6 CFM Connector: 4-pin PWM with a daisy-chain feature. Extras: Includes rubber pads on the corners for vibration dampening and standard case screws. One thing I noticed on the G12 frame is the lack of an airflow direction indicator, but it's a standard fan design, so it's easy enough to figure out. Specifications shown on the TL-C14 fan documentation. Specifications of the 140 mm TL-...

Upgrading from GTX 1060 to RTX 4060: Performance Gains in an Older System

(I used Claude AI to generate this article based on my video's transcript, so keep that in mind it might not be perfect even though I've gone through it to correct any issues I see. Also keep in mind that I've done further testing with an ASUS Proart 4060 compared to the MSI 1060 on my old PC and noticed a few situations where the CPU was limiting performance such as FFXIV minimum framerates.) I recently decided to take a look at the GIGABYTE RTX 4060 low profile version. This was the cheapest RTX 4060 card I could find as an Amazon Warehouse Deal, and I was curious to see if my old computer would benefit from upgrading from a GTX 1060 6GB to this new card. Low profile! My current system is built around an Intel i7-6700 CPU, which is likely to be the main limitation in this comparison. I was particularly interested in the sound profile of this card given its tiny size. I don't take a look in the video, but potential benefits of AV1 encode/decode are one reason I wanted...

SanDisk Ultra 128GB USB 3.0 Flash Drive and Tests

Today I'm taking a look at this 128GB SanDisk Ultra USB 3.0 flash drive. To see how it performs, I will be comparing it to a bunch of older drives that I have on-hand. The SanDisk Ultra USB 3.0 128GB flash drive in its retail packaging. Unboxing and First Impressions This is a USB 3.0 compatible drive. One negative of this package is you're going to have to cut it open with scissors. If you do, be careful not to cut too far down and damage the slip for the RescuePRO software offer inside. The  RescuePRO information and activation code inside the package. The drive itself is very lightweight. You have a spot for some type of key loop or strap. In the center, there is a slider that you push down and out to extend the USB port. It's a retractable design, which means there's no cap to lose.  Here you can see the hole for a keychain and the button to extend the USB port.  A key feature is the USB port itself. It has the classic blue plastic inside, which is a common indicato...