i@like.audio

Anthony P. Kuzub

i@like.audio

Category Archives: Science

Twist.Like.Audio

Posted on by

TwistRouting — Anthony’s Media Workflow Matrix

A browser-based broadcast signal routing visualizer, dressed in full LCARS regalia.

TRY IT HERE


It maps the living signal flow of a multi-floor production facility — every stage box,
every camera, every audio channel — onto destinations like control rooms, edit suites,encoders, and floor rooms. You drag a source onto a destination’s input, and the patchcomes alive as a twisting strand of DNA.

The “twist” is the metaphor and the mechanic: each routing point is a twist, and thesignals you braid into it are rendered as an animated double helix — two strands (cyan and magenta) spiraling around each other, the way two feeds wind together into one production.
Route a healthy source and the helix flows clean; route a faulted one and the strand corrupts, flickering red.

What it does

  • Sources (left ingress panel) — draggable signal nodes, discovered dynamically from the
    Sources/ tree:

    • Video stage boxes, organized by floor
    • Audio stage boxes (channel banks), organized by floor
    • Productions — finished program outputs exposed as re-routable sources
    • Shape encodes category at a glance: video reads as a trapezoid, audio as a rounded
      pill      , multiplex/group containers stay square.

  • Destinations (footer tabs) — consumers of signal, discovered from the Destinations/
    tree. Each category (Control Rooms, Edit Suites, Encoders, Floors…) becomes a tab group;
    each room is a tab full of twists:

    • Video Mixers, Audio Mixers, Multi Viewers, Intercoms
    • Monitors (single-feed)
    • ISO recorders with working RECORD / STOP arming and a pulsing REC indicator

  • Patching — drag a source onto a twist. The twist’s helix grows to show what’s braided
    in; click the LCARS lip or the left bar to fold/unfold the strand. Open a twist to get a
    matrix modal where you drag rows to reorder priority and switcher-input assignments.

  • Fault propagation — any source whose status isn’t OK (e.g. LOST CLOCK) pulses red.
    Route it anywhere and the destination inherits the alarm: the room’s LCARS L-bar pulses red
    and the twist’s DNA strand corrupts. Faults are visible end-to-end, the way they should be
    in a real plant.

  • Zero-backend discovery — the whole source/destination tree is just folders of JSON.
    Drop in a new stage box or a new control room and it appears in the UI; no code change.
    Discovery prefers an index.json manifest in each folder (so it works on any static
    host), and falls back to parsing autoindex HTML when none is present.

GIT HUB REPOSITORY

Data model

Everything is plain JSON under two roots:

Sources/        # draggable signals
  Audio/<Floor>/<box>.json
  Video/<Floor>/<box>.json
  Productions/<program>.json
Destinations/   # twists that consume signal
  Control Rooms/<tier>/<room>.json
  Edit Suites/<suite>.json
  Encoders/<encoder>.json
  Floors/<floor>/<room>.json

A source declares its channels, a colour class, a floor, and a status:

{ "id": "stagebox-101", "name": "STAGEBOX 101", "prefix": "S101-", "count": 12,
  "extraClass": "audio-studio", "floor": "1st Floor", "items": ["CH 1", "…"],
  "status": "LOST CLOCK" }

A destination declares its twists, each with what it accepts (video / audio /
both), its switcher inputs, and limits like maxVideo / maxAudio:

{ "id": "prod3", "name": "PROD 3", "color": "#646DCC",
  "twists": [ { "name": "Video Mixer", "accepts": "video", "inputs": ["SW IN 1", "…"] } ] }

Running it

Local, no dependencies (uses Python’s stdlib server, which provides the autoindex fallback):

python3 start.py        # serves the UI and opens your browser on a free port

Deploy to a static host over FTPS:

python3 uploadftp.py    # regenerates every index.json manifest, then uploads only the git diff

uploadftp.py is the smart deployer: it walks Sources/ and Destinations/ writing fresh
index.json manifests, then uses git status to upload only what changed (handling
renames and deletions), falling back to a full upload when there’s no diff. FTP credentials
come from a local .env (FTP_HOST, FTP_USER, FTP_PASS). (deploy.py is the older,
simpler full-tree uploader.)

Front-end layout

The app is plain HTML/CSS/JS — no framework, no build step:

index.htm            # shell + all the LCARS styling
js/globals.js        # discovery (listDirectory/fetchJSON), folding, tabs
js/poolVideo.js      # render video source pools
js/poolAudio.js      # render audio source pools
js/visuals.js        # the DNA-helix SVG rendering
js/matrix.js         # twists, routing, the matrix modal, fault logic
js/dragDrop.js       # drag-and-drop patching
js/productions.js    # productions-as-sources
js/topbar.js         # destination tabs / groups
js/app.js            # boot: build the tree, wire everything up

Homage to the LCARS designers

This project is a love letter to LCARS — the Library Computer Access/Retrieval System — the operating-system aesthetic of the 24th century. None of this look would exist without the artists who invented it:

  • Michael Okuda, scenic art supervisor for Star Trek: The Next Generation, Deep Space
    Nine    , Voyager, and the films — the man who designed LCARS itself. The sweeping rounded
    “elbows,” the flat candy-coloured panels, the confident typography, the idea that a starship
    interface could be calm — that’s all Okuda. The fan community named the style the
    “Okudagram” in his honour, and this app’s palette is taken straight from an Okudagram
    colour reference.
  • Denise Okuda, scenic artist and video supervisor, Mike’s collaborator and co-author of
    the Star Trek Encyclopedia — half of the partnership that made the future legible.
  • Rick Sternbach, senior illustrator and technical consultant, who with Mike Okuda gave the
    hardware its grammar (the Technical Manual) so every readout felt like it meant something.
  • Gene Roddenberry, for the conviction that the future’s tools should look like they were
    built for people, not against them.

The colours here are credited to the Okudagrams Color Complete Set Ver. 4.1
(lcarsmania.com, Toshitin) and live in lcars-styleguide.json —
LCARS Orange, Lilac, Blue Bell, Tomato, Sunflower, Red Alert, and the rest — used exactly as intended: as flat, functional, beautiful blocks of information.

To Mike, Denise, Rick, and everyone who ever lined up a perfect LCARS elbow at 2 a.m. so a panel would read right on camera — thank you. We’re still trying to live up to the future you drew.

“Tea. Earl Grey. Hot.” — and a clean signal path.

Created by Anthony Peter Kuzub · www.like.audio

LCARS is a trademark/design associated with Star Trek and its rights holders. This is a non-commercial fan tribute and a working engineering tool; no affiliation or endorsement is implied.

TCPIP : Just a Fancy 1950s Switchboard

Posted on by

The Great “Speed Dial” Conspiracy: Why Your Computer is Just a Fancy 1950s Switchboard

For decades, IT professors have tried to explain networking using “post offices” and “envelopes.” They were wrong. They were boring. And frankly, they didn’t understand that the internet is actually just a massive, global version of a small-town rotary phone system operated by people with very short tempers.

If you want to understand why your Wi-Fi is acting up, stop thinking about “packets” and start thinking about Anthony’s Telecom Theory of Everything.

The Permanent ID: The MAC Address

In this world, your device’s MAC Address is its hardwired phone number. It’s unchangeable, etched into the soul of the machine. It’s like that one landline number your grandmother has had since 1964. It doesn’t matter if she moves to Mars; that is her number. If you want to find the actual hardware, you need this ID.

The Speed Dial: The IP Address

But calling a 48-digit hardware ID is a nightmare. Enter the IP Address, or as we now call it: The Speed Dial. When you walk into a Starbucks, the router hands you a temporary speed-dial code. You aren’t “User 00-B0-D0”; for the next hour, you’re just “Extension 4.” It’s fast, it’s temporary, and if you stay too long without paying for another latte, they’ll give your extension to a guy with a MacBook Pro named Tyler.

The Contact List: DNS

Nobody remembers that Google is actually 8.8.8.8. That’s why we have DNS, the Global Contacts List. You type in “Mom,” and the system looks at the list and says, “Oh, you mean Speed Dial 8.8.8.8.” Without DNS, we’d all be carrying around tattered binders of numbers like it’s 1992 and we’re trying to order a late-night pizza.

The Phone Book Page: The Subnet Mask

This is where it gets tactical. The Subnet Mask isn’t a map; it’s a specific page in the phone book.

Your computer looks at the number you’re dialing and checks its current page.

Is the number on this page? Great! That’s a “Local Call.” Your computer just stands up and screams the name across the office until the other device hears it.

Is the number NOT on this page? Panic. This is a “Long Distance Call.” You can’t handle this. You need… The Operator.

The International Operator: The Default Gateway

The Default Gateway is that chain-smoking operator at the telco office. When you try to call someone not on your “Page” (Subnet), you dial 0. The Operator (Router) sighs, plugs a physical cable into a different switchboard, and sends your voice into the void of the World Wide Web.

The Apartment Extensions: The Ports

Finally, you reach the building. But you don’t just want the “Building” (IP). You want to talk to the guy in the mailroom.

Extension 80: The Web Receptionist.

Extension 25: The Mailroom.

Extension 443: The Secure Vault.

If you don’t dial the right Port, you’re just ringing the lobby phone while the person you want is sitting three floors up wondering why nobody ever calls.

The Verdict: The next time your internet goes down, don’t “reset your router.” That’s modern nonsense. Pick up your imaginary receiver, yell at the Operator to check the Page in the Phone Book, and make sure your Speed Dial hasn’t been reassigned to a refrigerator in Ohio.

The Clocking Crisis: Why the Cloud is Breaking Broadcast IP

Posted on by

The Clocking Crisis: Why the Cloud is Breaking Broadcast IP

The move from SDI to IP was supposed to grant the broadcast industry ultimate flexibility. However, while ST 2110 and AES67 work flawlessly on localized, “bare metal” ground networks, they hit a wall when crossing into the cloud.

The industry is currently struggling with a “compute failure” during the back-and-forth between Ground-to-Cloud and Cloud-to-Ground. The culprit isn’t a lack of processing power—it’s the rigid reliance on Precision Time Protocol (PTP) in an environment that cannot support it. Continue reading →

The Invisible Connection: Why Radio Waves and Photons Are the Same Thing (and Why It’s So Confusing)

Posted on by

It’s a question that gets to the heart of how we understand the universe: “Does radio frequency (RF) move over photons?” The intuitive answer, based on how we experience sound traveling through air or ripples on water, might be “yes.” It seems logical to imagine radio waves “surfing” on a sea of tiny particles.

However, the reality of quantum physics is far stranger and more counterintuitive. The short answer is no. Radio frequency does not move over photons. Instead, a radio wave consists of photons.

This concept is notoriously difficult to grasp. It challenges our everyday perception of the world and requires us to accept one of the most mind-bending ideas in science: wave-particle duality. Let’s break down why this relationship is so complicated. Continue reading →

Rescuing Your Old Tapes: A Guide to Cassette Tape Restoration

Posted on by

Rescuing Your Old Tapes: A Guide to Cassette Tape Restoration

For those with treasured audio recordings on old cassette tapes from the 1970s and 80s, discovering they no longer play correctly can be heartbreaking. A common issue is the tape slipping and dragging, which can manifest as a screeching sound or simply an inability to move past the capstan. This frustrating problem is often a symptom of a condition known as “sticky-shed syndrome”, and fortunately, it’s one that can be fixed. 

Understanding Sticky-Shed Syndrome

Continue reading →

The Center of Reverberation

Posted on by

The Center of Reverberation: From the First Pulse to the Intimate Decay

In the world of acoustics, we often talk about “space” as something we are in, but to understand the soul of a sound, we must look at where it begins and how it dies. If we combine the physical “Center of Mass” with the temporal “Center of Gravity,” we arrive at a concept we can call the Center of Reverberation.

This isn’t just a spot on a map; it is the mathematical and emotional balance point between a raw explosion of energy and the intimate whisper of a room.

1. The “Zero Point”: The Place Without Reverberation

Every sound begins at a First Point of Sound. Imagine a bomb detonating in a total vacuum or an anechoic chamber. In this “Zero Point,” there is no reverberation. There is only raw, directional energy moving outward at approximately 343 meters per second.

This is the “Center of Source.” It is pure, violent, and clinical. Because there are no reflections to give the sound context, your brain cannot tell how large the space is. Without reverberation, the sound has no “size”—it only has intensity.

2. The Early Energy Trail: The Birth of Shape

As that initial energy leaves the center, it strikes the world. The “Center of Reverberation” begins to form the millisecond that energy hits a boundary.

The Early Energy: These are the first reflections to return to your ears.

The Reflective Filter: The early energy “trails off” or holds strong based on the surfaces it hits. Hard marble preserves the energy; heavy velvet consumes it.

If the proximity of early reflections is close and the signal is strong, the sound feels “present.” This is the foundation of the Center of Reverberation: it is the point where the raw energy of the “bomb” meets the character of the room.

3. The Intimacy Gap: Creating the Space

In acoustics, Intimacy is defined by the time gap between the direct sound and the first reflection.

If the Center of Reverberation is “tight”—meaning the reflections follow the source almost instantly—the space feels small, private, and safe. If the center is “wide,” the space feels cathedral-like and distant.

The Paradox of Intimacy: To feel “close” to a sound, you actually need the room to talk back to you quickly. Without those early reflections, the sound feels “dead.” With them, the space itself becomes an instrument.

4. The Passive Shift: From Source to Field

As the sound continues to bounce, it moves from “active” energy (the source) to “passive” energy (the decay). The Center of Reverberation is the pivot point where the listener stops hearing a “thing making noise” and starts hearing “a room that is noisy.”

This is where the physics of mass and the physics of sound align:

Center of Mass tells us where an object is balanced in space.

Center of Reverberation tells us where the sound is balanced in time.

Conclusion: The Balance of the Pulse

The Center of Reverberation is the bridge between the Explosion and the Echo. It is the specific density of energy that allows a listener to feel the power of the first point of sound while being wrapped in the warmth of the environment.

Whether it is the crack of a drum or the boom of a firework, we don’t just hear the source; we hear the way the energy finds its center in the 3D world around us.

Production Offsets – Delay is dead, latency is lame

Posted on by

Production Offset (noun):

The accumulated timing differences within a production process caused by variations in signal transportation time, processing speed, or media transfer over IP networks. These offsets occur when different elements of a production pipeline experience inherent latency due to the nature of their processing paths.

A production offset specifically applies when synchronization between signals is required to maintain a cohesive output.

Examples of Production Offsets:

  • Audio-to-Video Delay: When video encoding and transmission take longer than audio, causing lip-sync issues.

  • Program Audio vs. Video Delay: A mismatch between broadcast-quality audio and video paths, requiring realignment.

  • Media Transfer Delays: Timing mismatches when files, streams, or packets arrive at different times due to network transport latency.

Control Audio vs. Program Audio – Is It a Production Offset?

  • Control Audio (Intercom, IFB, Coordination): Must be as close to real-time as possible to minimize awkward pauses in live communication.

  • Program Audio (Broadcast, Recorded Content): May have additional latency due to processing, mixing, and distribution.

  • Since these serve different functional purposes, their latency differences are generally not considered a production offset unless they must be synchronized for a specific use case (e.g., when coordinating live feeds with talent responses).

Managing Production Offsets Involves:

  • Measuring transport and processing delays across different signal paths.

  • Collating and analyzing timing discrepancies.

  • Applying delay compensation or synchronization techniques.

  • Optimizing network and processing paths to reduce unnecessary latency.

By properly managing production offsets, teams ensure seamless synchronization where required, while also prioritizing real-time communication for control audio.

Example: The team compensated for the production offset between program audio and video while ensuring control audio remained as real-time as possible for smooth coordination.

 

Metric Frame Rates: Banishing the Bizarre

Posted on by

Metric Frame Rates: Banishing the Bizarre

In a digital world governed by binary precision, there is a ghost in the machine. It appears in the settings menus of our cameras and the export windows of our editing software. It is the spectral presence of fractional math: 23.976, 29.97, and 59.94.

These numbers are messy. They are relics. It is time we fully embraced a concept that brings sanity back to video: Metric Frame Rates.

Defining the Metric Frame Standard

What are Metric Frame Rates? They are the clean, integer-based measurements of time that align perfectly with the way we count seconds. They are the logical progression of temporal resolution:

* 25 fps: The cinematic baseline.

* 50 fps: The standard for smooth, lucid motion.

* 100 fps: High precision and clarity.

* 200 fps: Extreme fluidity and slow-motion capability.

Unlike the fractional legacy standards, these rates—25, 50, 100, and 200—do not require a calculator to determine how many frames exist in an hour of footage. They are absolute.

The NTSC Hangover: Where the “Weird” Came From

To understand the beauty of Metric Frame Rates, you have to look at the chaos they replace.

For decades, North America and parts of Asia have been stuck with the “NTSC” standard. Originally, black and white television ran at a clean 30 frames per second. But when engineers added color in the 1950s, they hit a snag: the color signal interfered with the audio signal.

Their solution? Slow the video down by exactly 0.1%.

Suddenly, 30 fps became 29.97 fps. 60 fields per second became 59.94. Cinema’s 24 fps was slowed to 23.976.

This “fractional frame rate” created a nightmare for editors and engineers. Timecode became a headache (Drop-Frame vs. Non-Drop Frame). Audio drifted out of sync over long durations. We have been carrying this baggage for over half a century, long after the analog cathode-ray tubes that required it were thrown into landfills.

The Elegance of the Metric System

Metric Frame Rates (rooted historically in the PAL/SECAM regions and 50Hz power grids) bypassed this absurdity. They stuck to the integers.

1. The Mathematical Harmony

Metric rates scale perfectly.

* 25 fits into 50 exactly twice.

* 50 fits into 100 exactly twice.

* 100 fits into 200 exactly twice.

This base-2 geometric progression makes frame-rate conversion, math, and compression algorithms significantly more efficient. If you shoot at 100 fps and want to slow it down to 25 fps, the math is flawless: play every frame for 4x slow motion. No “pulldown” patterns, no jitter, no ghost frames.

2. 25 fps: The Aesthetic Sweet Spot

While Hollywood clings to 24 (or the dreaded 23.976), 25 fps offers a nearly identical aesthetic experience with a slightly higher temporal resolution. It retains the “dreamlike” quality of film without the fractional headache.

3. 50 fps: The Reality Standard

50 frames per second is the metric answer to the “soap opera effect,” but used correctly, it provides the “being there” feeling required for news, sports, and documentation. It captures reality with fluid precision, free from the flicker of lower rates.

4. 100 and 200 fps: The Future of Clarity

As we push into high-refresh-rate displays (120Hz, 144Hz, 240Hz), Metric Frame Rates like 100 and 200 are becoming vital. They offer a hyper-real smoothness that 29.97 can never achieve. Furthermore, 100 fps serves as the perfect “universal donor” for slow motion—fast enough to capture high-speed action, but mathematically simple enough to conform down to 50 or 25 for delivery

We no longer live in an analog world of interfering radio frequencies. We live in a digital world of absolute values.

There is no technical reason for a modern digital creator to be forced to use 29.97 unless they are broadcasting to legacy television networks. For the rest of us—creating for the web, for streaming, and for the future—it is time to reject the bizarre numbers of the past.

It is time to standardize on the clean, logical, and precise integers of 25, 50, 100, and 200.