Category Archives: Truth

SAMPLER.LIKE.AUDIO Bringing Hardware Sampler Soul to the Web Browser

Posted on by

SAMPLER.LIKE.AUDIO

Bringing Hardware Sampler Soul to the Web Browser

The Web Sampler & Sequencer is a fully-featured, open-source drum machine designed to run entirely within a modern web browser. By bridging the tactile workflow of classic beat-making hardware with the accessibility of modern web APIs, it offers a robust music production experience directly from a web browser.

Here is a breakdown of what makes this project technically unique and how it faithfully honors its hardware roots.

What Makes It Unique

The application stands out due to its radical approach to software architecture and browser integration, prioritizing transparency and local execution over cloud dependencies.

  • Zero-Dependency Architecture: The app requires no backend server, no Node.js environment, and no build tools like Webpack.

  • Direct Local File Access: It utilizes the File System Access API on Chromium-based browsers to let users browse and load samples directly from a local computer folder.

  • Absolute Privacy: Because it runs entirely client-side, the app never uploads a user’s audio files or patterns to a remote server.

  • Custom Legacy Audio Decoding: Alongside standard native Web Audio API formats (WAV, MP3, OGG, FLAC), it features a custom pure-JavaScript decoder for AIFF/AIFC files, which are common in vintage sample libraries.

  • Offline Independence: A built-in service worker caches the application shell and libraries, allowing the sampler to function completely offline after the initial load.

  • Transparent Codebase: The source code adheres to a strict philosophy where no individual file exceeds 200 lines.

  • No Compilation Needed: The app runs React natively in the browser via standalone Babel, meaning anyone can “View Source,” edit the code in a text editor, and refresh the page to see changes immediately.

Faithfulness to Hardware Samplers

Despite running in a web browser, the application meticulously recreates the physical feel and workflow limitations that made classic hardware samplers so intuitive.

  • Classic MPC Layout: The interface is built around a traditional 4×4 grid of 16 drum pads.

  • Mouse-Based Velocity: It simulates physical velocity sensitivity by calculating how close the user clicks to the exact center of a pad.

  • Plug-and-Play MIDI: The Web MIDI API allows users to plug in class-compliant USB controllers (like an Akai MPD) to finger-drum immediately with real velocity capture.

  • Tone Mode: By holding CTRL and clicking a pad, users can map a single sample chromatically across all 16 pads to sequence melodies and basslines.

  • Advanced Step Sequencing: The sequencer mimics classic hardware parameters, offering granular, per-step control over velocity, panning, pitch, and swing (shuffle).

  • Analog-Modeled Synthesis: When no sample is loaded on a pad, the app falls back on custom synthesis engines designed to strip acoustic percussion down to its physics—such as modeling the thump of a kick drum or the high-pass filtered noise of a snare wire.

Feature Translation: Hardware vs. Web

Hardware Concept Web Sampler Implementation
Internal Memory

Saves kits, favored samples, and patterns locally using browser localStorage and IndexedDB.
Sample Browsing

Recursively scans local directories to build a searchable, visual waveform grid.
Pattern Chaining

Provides 4, 8, 16, 32, and 64-step pattern options that can be managed in a dedicated Song tab.
Mixer Console

Features a dedicated mixer view with per-track volume, panning, and a shared reverb bus.

The Illusion of Brotherhood: Why the Local Music Scene is Drowning in Pettiness

Posted on by

The music business suffers from a severe branding problem. While the industry sells a romanticized image of “bandmates” as a tight-knit, passionate crew, the reality is often a hyper-competitive space where ego consistently supersedes compassion. Many adults in bands demand professional recognition while handling conflict with the maturity of children on a playground.

The Facebook Court of Petty Grievances

This unaccommodating culture is most visible on social media, where petty, toothless trolls use public pile-ons to inflate their sense of importance. Rather than managing logistics with grace, these individuals weaponize their local networks.

Consider the recent public saga involving Christopher Kathleen, Mellisa Mils (Names Changed) and his associates. The conflict began with a situation requiring basic empathy: a drummer needing to excuse himself from an engagement to undergo surgery. In a functional environment, this would be met with understanding; however, this situation devolved into public mudslinging. Christopher utilized Facebook to “publicly warn” other musicians against working with the drummer, citing a separate grievance post to bolster his position.

Missing the Forest for the Trees

The core of the dispute was financial, centering on unreturned deposits after the drummer cancelled a show due to surgery. The band accused the drummer of ghosting them, attempting to hire a cheaper fill-in to pocket the difference, and mobilizing “lackeys” to attack the band online.

Regardless of the contractual details, the reaction reveals the toxic nature of this scene. By dragging a private business dispute into a public feed, the band prioritized a “pile-on” over professional conflict resolution.

Why They Cannot Be Taken Seriously

This behavior explains why many local acts fail to advance their careers:

  • Zero Compassion: Treating band members as disposable assets creates a revolving door of burnt-out musicians.

  • Public Unprofessionalism: True professionals handle contract and deposit disputes privately or through legal channels; broadcasting grievances signals that the band itself is a liability.

  • Ego Over Art: Focusing energy on internet drama and claims of “slander” distracts from the music.

The “Peace” Paradox: Weaponized Performative Morality

A jarring hypocrisy defines this scene: the performance of the “reasonable victim.” Individuals who thrive on drama often frame their aggression as a noble pursuit of “truth” or “speaking peace,” using community protection as a mask for personal vendettas.

This is a form of professional gaslighting. By positioning themselves as the “righteous martyr” who was forced to speak out, the aggressor gains moral cover for a targeted character assassination.

The hypocrisy is evident in several ways:

  • The Facade of Civility: Invoking “speaking peace” is a tactic used to lend an air of maturity to a retaliatory strike designed to damage a peer’s professional reputation.

  • The Contradiction of Professionalism: These individuals demand to be treated as high-level business entities but lack the emotional regulation to handle financial friction without public shaming.

  • The Blackmail Dynamic: By threatening to “drag a drummer’s name through the mud” or blacklisting them, these individuals turn a standard disagreement into a hostage situation.

True professional resolution is found in private mediation and clear, signed agreements. When artists trade their integrity for the validation of a Facebook comment section, they are not protecting their brand; they are confirming that they are liabilities that no serious professional should trust.

Don’t let small minds make big impacts on your life

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.

The Power of the Baseline: Why Being the Calmest Person in the Room is a Project Manager’s Ultimate Weapon

Posted on by

The Power of the Baseline: Why Being the Calmest Person in the Room is a Project Manager’s Ultimate Weapon

In high-stress project environments—whether you are leading a team of AV professionals dialing in a massive live event or managing an elite squad of commercial installers on a tight construction deadline—the air is constantly thick with potential panic. Cable runs fail. Hardware arrives damaged. The client shifts the scope of work an hour before kickoff.
In these volatile moments, most leaders default to matching the room’s energy. They move faster, speak louder, and broadcast urgency.

But the most effective leaders do the exact opposite. They utilize a psychological mechanism known as pattern interruption by maintaining a baseline of absolute, unshakeable calmness. In face-to-face team management, moving slowly, speaking softly, and refusing to react to the chaos around you isn’t just a temperament—it is a deliberate tactical strategy.

Here is how controlling your baseline transforms calmness into an authoritative superpower on large-scale projects.

1. Setting the Room’s Thermostat
Human beings are hardwired for emotional contagion; we instinctively mirror the stress levels of those in authority. If a supervisor is pacing, shouting, or visibly sweating the details, the field technicians and installers will internalize that panic. Cortisol spikes, peripheral vision narrows, and mistakes multiply.

When you walk the floor slowly and deliberately—acting like a stabilizing cloud rather than a category-five storm—you rewrite the room’s psychological reality. Your presence sends a silent, authoritative signal: If the person carrying the responsibility isn’t panicking, there is no reason for me to panic. By regulating your own stress, you mechanically lower the collective heart rate of your team, keeping them in a headspace where they can actually solve problems.

 2. The Mechanics of Pattern Interruption
If your default management style is characterized by constant intensity, your team quickly develops a tolerance to it. When everything is treated like a five-alarm fire, urgency loses all currency. It becomes background noise, and your crew will eventually tune you out to protect their own sanity.
True power lies in the contrast.

By establishing a baseline that is methodical, cool, and slow-moving, you create a powerful asset. Because your norm is so predictable, the slightest deviation from it becomes incredibly loud. When a typically soft-spoken, relaxed manager stops, looks a technician in the eye, and gives a sharp, direct, single-sentence instruction, the team doesn’t just listen—they pivot immediately. You haven’t screamed or lost your temper; you have simply broken your own pattern. The team recognizes the shift instantly and intuitively understands: This specific task is critical.

[Constant High Stress] —> Team develops “Urgency Fatigue” —> Commands are ignored
[Calm Baseline] —> Sudden Shift to Direct Action —> Pattern Interrupted (Instant Focus)

3. Creating “Reserved Authority”
On a chaotic job site, field crews respect competence and predictability. When an installer watches a project manager calmly navigate a catastrophic system failure without breaking character, it builds an immense reservoir of professional credibility. The team assumes you have either solved this exact problem a dozen times before, or that you are entirely unbothered by the stakes.

This creates a sense of “reserved authority.” Your team trusts that you are conserving your energy for what actually matters. They know that you don’t micromanage minor hiccups, which means that when you do step in to redirect a process, your intervention carries the full weight of your accumulated respect.

4. Execution Over Emotion
Ultimately, large project environments do not care about your feelings; they care about execution. When a complex AV network deployment or a massive physical installation goes sideways, raging against the problem burns valuable cognitive bandwidth.

Moving slowly and deliberately allows you to observe the chessboard clearly. It gives you the space to ask analytical questions rather than throwing emotional reactions at a technical problem.

Staying cool isn’t about being passive or disconnected from the reality of a hard deadline. It is about understanding that in a high-stakes environment, the most disruptive thing you can be is entirely at peace. Move softly, speak with intention, and let your calm baseline do the heavy lifting for you.

The Live Sound “Gotcha”: When 48k AVB Fits the Amps, but Breaks the System Core

Posted on by

The Live Sound “Gotcha”: When 48k AVB Fits the Amps, but Breaks the System Core

Every system engineer knows that dangerous moment on a load-in day: the false sense of security. You’ve run your lines, your network switches are glowing with beautiful, stable activity LEDs, and the initial pink noise test passes with flying colors. You step away from the tech table to grab a cold coffee, entirely confident that the audio rig is rock-solid.

Then, you roll in the primary loudspeaker processor, and the entire house of cards collapses.

This is the story of a classic digital audio “gotcha”—a day where a perfectly innocent, standard-rate network conversion box works flawlessly with your amplifiers, only to hit a brick wall when plugged into the system’s central processing brain. It isn’t a hardware failure, and it isn’t the conversion box’s fault. It’s a clash of two entirely different architectural mindsets within modern professional sound systems.

Phase 1: The 48 kHz Honeymoon
The day starts simple. The venue or tour is built around a standard, reliable 48kHz digital infrastructure. To get those console channels out to the main PA over the network, you deploy a format converter to bridge your console’s protocol over to an AVB network stream. It effortlessly spits out a 48kHz AVB stream, pointing it straight down the network to your modern, network-native power amplifiers.

You open your system management software, route the AVB streams to the amps, and *boom*—clean audio.
Why does this work so beautifully? Because modern professional amplifiers are engineered with an “adaptable endpoint” ideology. Even though the internal DSP core of a high-end network amplifier almost always operates natively at 96 kHz,  manufacturers design these endpoints to be incredibly forgiving listeners. When the amplifier detects an incoming 48kHz AVB stream, its onboard network hardware automatically engages an internal Sample Rate Converter (SRC). It gracefully up-samples the 48 kHz network audio to 96kHz at the input gate without a single error or clock pop.
You walk away from the rack room smiling. The 48 kHz stream is happy, the 96kHz amps are happy, and the system sounds incredible.

Phase 2: Rolling in the System Brain
After lunch, the central system processor or immersive matrix engine arrives. This is the master brain tasked with handling complex distribution, time-alignment, tuning, or object-based spatial mixing for the entire venue. To maximize mathematical precision, filter accuracy, and the microsecond time-delays that modern sound system design demands, the configuration dictates that this core processor must be run at its native, premium 96 kHz mode

mode.

You re-patch the network. Instead of sending the conversion box’s 48kHz AVB stream straight to the amplifiers, you route those console tracks into the inputs of the loudspeaker processor first, intending to let the core brain do the heavy DSP lifting before handing the final mix off to the amps.
You click “Connect.”

Suddenly, the network status screen lights up bright red. Absolute silence fills the room. The system processor throws a massive clocking error and completely refuses to unlock the streams.

The Gotcha: A Tale of Two Ideologies
This is where the trap snaps shut. It is incredibly easy to assume that because manufacturers build seamless, automatic sample rate conversion into their *amplifiers*, they must have put that exact same capability into their flagship *central processors*.

They didn’t.

Unlike endpoint amplifiers—which only have to manage a handful of audio channels destined for a specific set of speakers—a core loudspeaker processor or matrix hub handles dozens or hundreds of simultaneous routing cross-points. Because of this massive processing scale, high-end system processors are designed with a strict “True Match” architectural ideology: the input streams must match the internal engine clock identically.

These heavy-duty central brains generally do not possess asynchronous sample rate converters across their primary network input cards. When you set that master processor to run at 96kHz, it completely blinds itself to 48kHz AVB streams. It cannot upscale them on entry the way the amplifiers did just an hour prior.

Not a Fault, But a Generational Shift
It is tempting to blame the conversion box in this scenario, but the box is doing exactly what it was asked to do: outputting a clean, stable 48kHz network stream. The breakdown occurs entirely because of a shift in engineering mindsets between different classes of DSP hardware.
An amplifier is designed to be a flexible destination; it adapts to whatever flavor of audio you feed it because it sits at the very end of the line. A core matrix processor, however, is designed to be the absolute master clock authority of a massive sound system; it demands total consistency across its inputs to maintain strict, deterministic processing latency and absolute mathematical accuracy

The Fix for the System Engineer
By the time the sun starts to set, the lesson is learned. To get out of this corner, you have two choices:

1. **The Compromise:** Force the central loudspeaker processor to drop its internal engine down to 48kHz to match your conversion box. You lose a tiny bit of high-sample-rate resolution on paper, but the network immediately locks, the audio flows, and the show goes on.

2. The Right Tool for the Job: Recognize that a 48 kHz console infrastructure and a 96kHz system processing core need a dedicated mediator. You introduce a heavy-duty, system-grade hardware network bridge—one specifically engineered with the massive asynchronous processing horsepower required to upscale a 48kHz world into a strict, pristine 96kHz network stream before it ever hits the processor’s input gate

the show must go on:

The Hybrid Infrastructure Compromise: If you are dealing with a permanent installation or a split system where some zones absolutely demand 96kHz networking but others are trapped in 48kHz, you start splitting lanes. You run an old-school, analog 2-wire copper lines straight into a handful of local amplifiers to bypass the network entirely, while simultaneously building an AES3-to-AVB hardware gateway elsewhere in the rack. By taking a 48 kHz AES3 feed and running it through a local gateway that handles the up-sampling to 96kHz AVB, you can feed the master processor exactly what it wants for the main array, leaving the copper to handle the rest.

In live sound, assuming that two pieces of gear from the same generation or ecosystem think the same way is the fastest route to a headache. Always look past the network jack on the chassis, check the clocking architecture under the hood, and remember that just because an amp can adapt, doesn’t mean the brain can.

“P.Y.T.H.O.N.” Why Your Best Code Belongs on a Coffee-Stained Serviette

Posted on by

Welcome to the era of P.Y.T.H.O.N.:
Prototype Your Thing Haphazardly On Napkins.

The Death of the Keyboard

For decades, we’ve been lied to. They told us we needed mechanical keyboards and 40-inch curved monitors to “disrupt the industry.” But as any seasoned Senior Architect will tell you between bites of a $14 artisan bagel, the most robust systems are actually conceived in the fleeting moments between ordering a latte and realizing you have no signal.

The P.Y.T.H.O.N. methodology embraces the chaos of the physical world. If your algorithm can’t fit next to a smudge of strawberry jam, is it even worth scaling?

Key Features of the Napkin Stack

The beauty of the Haphazardly phase is its inherent security. Traditional hackers can’t breach a firewall that is literally a piece of trash.

  • Biodegradable Backends: Unlike AWS servers, a napkin prototype can be destroyed in seconds by a spilled glass of water or an aggressive sneeze.

  • Zero-Latency Ink: There is no “loading” time for a Bic Cristal. The data transfer from brain to cellulose is instantaneous, though often illegible.

  • Variable Geometry: Napkins can be folded. Can you fold a GitHub repository? No. Folding allows for multi-dimensional data structures that would make a quantum physicist weep.

The “Haphazard” Advantage

Modern “Agile” workflows are far too organized. To truly innovate, one must be Haphazard. By writing code on a medium designed for wiping grease off a chin, you remove the “fear of failure.”

“I used to spend weeks on documentation,” says one convert. “Now, I just hand my lead developer a crumpled wad of paper I found in my pocket. If he can’t decipher my ‘for’ loop through the ketchup stain, that’s a communication bottleneck, not a bug.”

Comparison: Traditional vs. P.Y.T.H.O.N.

Feature Python (The Language) P.Y.T.H.O.N. (The Lifestyle)
Indentation Mandatory (Strict) Dependent on napkin wrinkles
Libraries Pip install Whatever is in the condiment caddy
Garbage Collection Automatic Performed by the busboy
Syntax Errors Stop the program Add “flavor” to the vision

The Verdict

If you want to build the next unicorn, stop staring at a blinking cursor. Go to a diner. Order the cheapest thing on the menu. Wait for that moment of frantic, grease-fueled inspiration and start scribbling.

Think Optionally – Why Apple’s Users Hate AI

Posted on by

In 1984, Apple introduced the Macintosh with a promise: we were here to smash the monolithic, droning conformity of Big Brother. We were the crazy ones. The misfits. The rebels. We bought computers not to balance spreadsheets or optimize logistics, but to write the great American novel in a coffee shop and edit films that would never make it into Sundance.

Apple sold us the “Bicycle for the Mind.” It was a tool that amplified human capability.

So, why is the company currently pivoting to sell us the “Uber for the Mind”—where you just sit in the back seat, drooling, while an algorithm drives you to a destination you didn’t choose? 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 →

How Listening Is the Story: Why Audio Paints the Truest Pictures

Posted on by

How Listening Is the Story: Why Audio Paints the Truest Picture

By Anthony Kuzub

In an age dominated by high-definition screens and viral video, it’s easy to believe that seeing is believing, and that the richest experiences are those delivered through our eyes. But what if the deepest, most personal narratives aren’t found in pixels, but in vibrations? What if, in fact, listening is the story, and the pictures we perceive are often secondary, mere echoes of the sound that truly brings a narrative to life? As it turns out, there’s always more to imagine when you listen.

For centuries, before the advent of the printing press, let alone cinema, stories were primarily heard. They were sung, chanted, whispered, and declaimed around campfires and in great halls. The power of these tales resided not in their visual depiction, but in the narrator’s voice, the cadence of the language, and the vibrant tapestry of sound effects conjured by the imagination. Our brains are wired for this primal form of storytelling, acting as a personal, infinitely adaptable cinema for the mind, always ready to fill in the magnificent gaps.

The Brain: Your Personal IMAX – And Director

When you listen, particularly to an audiobook, a podcast, or a radio play, your brain shifts from passive consumption to active co-creation. The storyteller provides the blueprint: the dialogue, the ambient sounds, the pace, and the tone. Your imagination, in turn, becomes the ultimate set designer, costume department, and casting director. The rustle of leaves described by a narrator becomes your forest, filled with your specific species of trees and the quality of light you envision. A character’s voice sculpts their face, their posture, their very presence in a way no director’s camera could ever universally achieve. This is where the “more to imagine” truly comes alive.

This isn’t a deficiency; it’s a superpower. The pictures generated by your mind are infinitely more personal, detailed, and emotionally resonant than any external image. They are tailored to your unique experiences, memories, and desires, making the story not just something you observe, but something you inhabit. Every inflection, every pause, every sound effect becomes a prompt for your inner world to expand, offering an endless canvas for your own creativity.

The Primacy of Sound: A World of Evidence

Consider the very nature of media, and how sound consistently takes the lead:

* Dialogue Drives Drama: In film and television, while visuals are undeniably important, the plot, character development, and emotional arcs are predominantly carried by dialogue. Without the spoken word, most visual narratives would collapse into confusing pantomimes. The picture provides context, but the audio delivers content, making you lean in, listen closer, and imagine the unspoken details.

* The Power of Foley and Score: A horror film wouldn’t be scary without the screeching violin, the ominous bass, or the subtle creak in the dark. A romantic comedy relies on a soaring soundtrack to punctuate its tender moments. These sounds don’t just accompany the visual; they create the emotional landscape that the visuals then inhabit. Try watching a gripping scene on mute—the impact is drastically reduced, proving how integral the audio experience is. There’s always more emotion to imagine when the sound tells you how to feel.

* Closed Captions: The Ultimate Concession: Perhaps the most compelling evidence for the primacy of audio lies in closed captions. Why do they exist? Not because the visuals are insufficient, but because the audio, the actual spoken story, is sometimes inaccessible. Captions are a testament to the fact that even in a visually saturated world, the words, the sounds, the voices—the audio itself—remain the non-negotiable core of communication and storytelling. They are a visual representation of the audio, not the other way around, proving that even when we can’t hear, we still recognize that there’s more to imagine when you listen to the words, even if read.

In a society increasingly fragmented by endless visual stimuli, there’s a quiet revolution brewing: a rediscovery of the profound intimacy and imaginative freedom that comes from simply listening. Podcasts are soaring in popularity, audiobooks are challenging traditional print, and immersive audio experiences are pushing the boundaries of what stories can be. They all tap into that inherent human desire for richer, more personal engagement.

These formats don’t ask you to passively receive; they invite you to actively participate. They remind us that the most vivid images often aren’t seen with our eyes, but crafted in the unique, limitless theater of our minds, all thanks to the humble, yet powerful, act of listening. They affirm that there’s always more to imagine when you listen.

So, the next time you’re looking for a truly immersive experience, close your eyes, put on your headphones, and let the sounds paint the pictures. You might be surprised by the masterpiece your own mind can create.

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 →

Music Labels – Global market structure

Posted on by

Tier 1: The “Big Three” Global Conglomerates

These three companies collectively control the vast majority of the global music market share. Their subsidiaries and imprints are listed below them.

  1. Universal (Universal Music Group – UMG)
    • Description: The largest record label group globally, with the biggest market share and a vast catalog.
    • Wikipedia: Universal Music Group
  2. Sony (Sony Music Entertainment – SME)
    • Description: The second-largest global record company, with a rich history and extensive publishing assets.
    • Wikipedia: Sony Music Entertainment
  3. Warner (Warner Music Group – WMG)
    • Description: The third of the “Big Three,” with a significant history and diverse roster.
    • Wikipedia: Warner Music Group

Continue reading →

Schwartzkopf on Leadership

Posted on by

Schwartzkopf on Leadership

  1. You must have clear goals. You must be able to articulate them clearly. When the goal is clear and simple, it is easy to focus on success.
  2. Give yourself a clear agenda. Every morning write down the five most important things for you to accomplish that day. Whatever else you do, get those five things done. Insist that the people who report to you operate the same way
  3. Let people know where they stand. Everyone knows you do a disservice to a B student when you give them and A. This applies in life as well as in school. The grades you give people who report to you must reflect reality.
  4. What’s broken, fix now. Don’t put it off. Problems that aren’t dealt with lead to other problems. Besides, tomorrow something else will break and need fixing.
  5. No repainting the flagpole. Make sure all the work you are doing is essential to the organization.
  6. Set high standards. Too often we don’t ask enough of people. Schwartzkopf was at one point in charge of helicopter maintenance. When asked how many copters were available to fly on any given day, he was told 75%. He then raised the standard to 85%, which was met quickly. The moral is people generally won’t perform above your expectations, so it’s important to expect a lot.
  7. Lay the concept out, but let your people execute it. Yes, you must have the right people in place. But then step back and allow them to own their work.
  8. People come to work to succeed. Nobody comes to work to fail. It seems obvious. So why do so many organizations operate on the principle that if people aren’t watched and supervised, they’ll botch the job?
  9. Never lie. Ever. Schwartzkopf said there had been a big debate about whether to use disinformation to mislead the Iraqis during the Gulf War. “We knew they were watching CNN. Some people argued we could save American lives by feeding incorrect information to our own media”. Schwartzkopf vetoed the idea because he believed it would undermine the military leadership’s credibility with the American public.
  10. When in charge, take command. Leaders are often called on to make decisions without adequate information. As a result, they may put off deciding to do anything at all. That is a big mistake. Decisions themselves elicit new information. The best policy is to decide, monitor results, and change course if necessary.
  11. Do what is right. “The truth of the matter,” said Schwartzkopf, “is that you always know the right thing to do. The hard part is doing it.

The Name Kuzub

Posted on by

My Colleague Pavlo Kondratenko gave me some extra context to my name: According to one website (accuracy aside), there are around 1,600 people in Ukraine today with your last name. Most of them live in Kyiv and Poltava. In Ukrainian, it’s pronounced more like “Koozoob.”

The Meaning Behind “Kozub”: More Than Just a Name

The word Kozub has deep roots in Ukrainian culture, both linguistically and practically. Originally, a kozub referred to a small woven basket—typically made from bast (a type of tree fiber), birch bark, or vine—used mainly for collecting berries. Diminutives and dialectal variants include kozuben, kozubenka, kozubets, and kozubka.

In some regions, a similar basket was known as a stuga, or in its diminutive form, stuzhka. These bast or vine baskets were sometimes coated in clay and used to store grain or flour—highlighting their practical role in traditional rural life.

Etymology and Origins

The word kozub is believed to derive from the Proto-Slavic kozubъ, which may be related to koza (goatskin bag) or koža (skin). While the shift in meaning from “skin bag” to “woven basket” isn’t entirely clear, it reflects the fluidity and adaptation of language through time.

Cultural Footprint

The term kozub has left its mark not only on tools and traditions but also on Ukrainian surnames and place names—such as Kozub, Kozubenko, Kozubnyak, Kozubov, and even the village Mali Kozuby. These names serve as living reminders of everyday objects that once played central roles in agrarian life.

Folk Language and Expressions

The legacy of kozub extends into Ukrainian idioms and proverbs. For instance:

  • Kozubaty means “bellied” or “pot-bellied.”
  • To become a kozub describes something becoming stiff or hardened by frost—like bark or frozen wet clothes.
  • And an old saying, “If it’s not a mushroom, don’t climb into the chimney,” recorded by folklorist M. Nomis, captures the whimsical, metaphor-rich spirit of Ukrainian rural expression.

Whether as a humble berry basket or a family name passed down through generations, kozub is a small word with a big cultural story.

—

Google Translate didn’t quite hit the mark—particularly with translating “kozub” as “chimney,” which is puzzling. It also mistranslates the phrase “if you are not a mushroom” when it should be “If you are not a mushroom, don’t get inside the basket.” There’s some cultural nuance here, and the full proverb is: “Коли ти мені муж, то будь мені дуж; а як не гриб, то не лізь у козуб.” This roughly means, “If you’re my man, be strong; and if you’re not a mushroom, don’t crawl into the basket.” Some interpretations, like the one on Wikipedia, simplify the second part to mean “Mind your own business.” But there’s a deeper layer—one that folklore researchers are only recently starting to unpack. Apparently, in 19th-century folk songs and sayings, euphemisms were common: a horse might symbolize a penis, a bucket a vagina, and yes—a mushroom and a basket carried similar meanings. So in that context, the phrase takes on a more suggestive undertone.

 

Disagree well – Why do you want to believe that?

Posted on by

To disagree well, it’s essential to approach conversations with epistemic humility—acknowledging that you could be wrong. This mindset opens the door to understanding, not just winning the argument. By asking “Why do you want to believe that?”, you invite the other person to reflect on their beliefs, fostering a deeper dialogue rather than a debate.

Key Points for Disagreeing Well:

  • Start with humility: Recognize your own limits and uncertainties.
    “I see your point, and I could be wrong, but here’s how I see it.”
    “I’m not entirely sure, but I think there’s another way to look at this.”
  • Invite Dialectic Sialogue, not debate: Shift from winning to understanding.
    “I’m interested to hear your thoughts on this. Maybe we’re both missing something.”
  • Listen actively: Engage with the other person’s perspective, not just preparing your rebuttal.
    “That’s a good point. I hadn’t considered that angle before. Here’s how I’m thinking about it…”
  • Stay open to revising your view: Be willing to change your mind if presented with compelling evidence or new insights.
    “You make a solid point. Let me think about that and see if it changes how I view things.”
  • Avoid personal attacks: Focus on ideas, not individuals.
    “I understand your perspective, but I think this approach might have some flaws.”

In any discussion, it’s important to ask “Why are we here together?”—to understand the purpose of the conversation—and “What is our goal?” This helps guide the dialogue toward constructive outcomes. Ultimately, how we get from the purpose to the goal is through humility, active listening, and an openness to growth. By focusing on these principles, we foster meaningful, respectful exchanges that can lead to shared understanding or even change.

Dialectic is more than just a method of argument—it’s a disciplined way of seeking truth through the structured tension between opposing ideas. Whether in philosophy, politics, or everyday conversation, it emphasizes that progress often comes not from avoiding conflict, but from engaging it thoughtfully to reach deeper understanding.

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.