Tutorials

[Title card: "Tutorial 2: MIDI Setup & First Performance"]

"In this tutorial we're connecting a real MIDI controller. I'm using a 25-key USB keyboard — any class-compliant MIDI device will work the same way."

Section 1 — Connecting the device (0:30)

[Camera on hands plugging USB cable into keyboard, other end into laptop]

"Plug your controller in via USB. On macOS, Windows, and Linux, class-compliant MIDI devices are plug-and-play — no drivers needed."

[Screen: Chrome, navigate to the HazR app]

"Open the HazR app. Watch the MIDI status in the top left."

[Status changes from "Waiting..." to "MIDI Input Connected"]

"There it is — 'MIDI Input Connected.' Your device is live."

Section 2 — Understanding MIDI messages (1:45)

"Every note you play sends two values: the note number — which key you pressed — and the velocity — how hard you pressed it. HazR uses both."

"The note number selects the colour scheme — lower notes lean towards the beginning of the palette, higher notes towards the end, cycling every 12 semitones. The velocity controls the density and brightness of the pattern."

Section 3 — First performance (3:30)

[Full screen: HazR app, pattern slider at 0]

"Let's play. I'll start with slow, deliberate single notes — watch how each one shifts the colour field."

[Play slow single notes — visuals respond with clear colour changes]

"Now I'll play a chord — three notes at once."

[Play chord — multiple visual layers]

"And now something fast — a rapid run up the keyboard."

[Play rapid ascending scale — patterns shift quickly]

Section 4 — Experimenting with the controls (5:30)

[Move pattern slider]

"While playing, you can change the pattern with the Patterns slider. Try different values — each one changes the algorithm used to build the particle grid."

[Adjust speed X]

"Speed X and Y scroll the field. Setting both to zero freezes it. For a hypnotic loop, set X to 0.3 and Y to 0.1."

[Click Fullscreen]

"And hit Fullscreen. This is what your audience sees."

Closing (7:30)

"That's your first real performance. In the next tutorial we go deeper into visual patterns — including the ten AI-generated patterns available to Artist subscribers."

[Title card: "Tutorial 3: Visual Patterns & Controls"]

"This is where HazR gets deep. We're going to walk through every control in the app, understand what's happening mathematically behind each pattern, and then unlock the AI-powered patterns available on the Artist tier."

Section 1 — The 10 local patterns (0:30)

"The first 10 patterns — models 0 through 9 — run entirely in your browser using JavaScript. They are instant. There is no network round-trip."

[Slider to 0]

"Pattern 0 — Random. Every trigger generates a completely fresh layout — widths and margins are randomised on each MIDI event."

[Slider to 7]

"Pattern 7 — Spiral. Particles spiral outward from the centre, with density modulated by angle. The geometry rotates slightly with each trigger."

[Slider to 9]

"Pattern 9 — Circular Field. Particles cluster densely at the centre and fade toward the edges. The full set: 0 Random, 1 Checkerboard, 2 Vertical Bars, 3 Symmetric Triangle, 4 Cascading Waves, 5 Alternating Stripes, 6 Noise Field, 7 Spiral, 8 Stacked Clusters, 9 Circular Field."

Section 2 — Shape, size, and speed in detail (3:30)

"Shapes selects the geometry of each particle from 10 distinct forms. At 0 — Rectangle. Then Circle, Triangle, Pentagon, Hexagon, Heptagon, Octagon, Parabola, Hyperbola, and at 9 — Star."

"Size is camera zoom. Lower numbers zoom out — you see the full grid, small and precise. Higher numbers zoom in — the grid fills your vision and becomes abstract. For projection, I usually sit around 15 to 25."

Section 3 — Artist patterns (10–19) (5:30)

[Switch to Artist-tier account. Slide pattern to 10 — badge appears.]

"If you're on the Artist or Venue plan, you get ten additional patterns — models 10 through 19. These patterns are generated on the server by a Python engine for every single MIDI note you play."

[Slider to 12]

"Pattern 12 — Reaction Diffusion. This is a Gray-Scott simulation — the same mathematics used to model animal skin patterns. Feed rate responds to your velocity. Kill rate responds to the note."

[Slider to 19]

"Pattern 19 — Gravity Wells. N-body field strength. The note determines how many wells exist; velocity sets their mass. Play a chord and the wells multiply, creating complex gravitational topographies."

Closing (9:30)

"That's the full visual toolkit. In Tutorial 4, we put everything together for a live performance context."

[Title card: "Tutorial 4: Live Performance Tips"]

"This tutorial is about performance. Everything we've built so far is now in service of one thing: a live show."

Section 1 — Display setup (0:30)

"For live performance, you want HazR running on a separate display — a projector, a large LED panel, or a second monitor. Set your monitors to Extended Desktop, not Mirror. Then move the HazR browser window to the output display and press the Fullscreen button."

Section 2 — Pre-show checklist (2:00)

"One: confirm MIDI Input Connected before the show starts. Two: set your starting pattern — start with a local pattern (0–9) for instant response. Three: set Speed X and Y to your preference. Four: set the Size for your projection distance — lower zoom for large projectors. Five: check the browser audio against the venue PA."

Section 3 — Building a set (3:45)

"Think of a HazR set in three movements. Opening: slow pattern, light velocity, let the audience settle. Middle: introduce speed, switch patterns mid-phrase. Peak: Reaction Diffusion or Interference, play hard, dense chords. Resolution: pull speed back, reduce velocity, let the field come to rest."

Section 4 — Managing your session (5:30)

"If the network drops during a set, the local patterns — 0 through 9 — continue working perfectly. Only the Python-generated patterns (10 through 19) require the server connection. Your core performance is always robust."

Closing (6:45)

"You're set up, you know your instrument, and you know how to perform with it. Everything else is practice."

[Title card: "Tutorial 5: Live Streaming — Venue Feature"]

"If you're on the Venue plan, your HazR performance can go live — simultaneously — on Facebook, YouTube, Instagram, TikTok, Twitch, X, and any custom RTMP destination you choose. One session, every platform, at the same time. You can push from OBS using either RTMP or SRT — we'll cover both."

Section 1 — The Stream Management Page (0:45)

[Screen: HazR dashboard → click "Live Stream"]

"From your dashboard, open Live Stream. The page has two endpoint sections: RTMP Endpoint and SRT Endpoint. Both use the same stream key — you choose which protocol to push with based on your setup and network conditions."

Section 2 — Configuring Platform Destinations (2:00)

"Facebook Live: paste just the stream key starting FB- from Professional Dashboard → Go Live. YouTube: combine the Server URL and Stream Key from YouTube Studio into one string. Instagram: paste the full rtmp:// URL from the mobile app. TikTok: paste the full RTMP URL from TikTok Live Studio. Twitch: paste just the stream key starting live_. X: combine server and key into one URL. Custom RTMP: paste any standard RTMP endpoint."

[Click Save Destinations]

"Click Save Destinations. Your settings persist across sessions."

Section 3 — OBS with RTMP (5:30)

"In OBS: Settings → Stream → Service: Custom. Server: rtmp://nxprm.io:1935/hazr. Stream Key: paste your personal key. Set up a Window Capture source targeting the HazR App tab. Click Start Streaming — the server detects the stream and relays to every configured platform."

Section 4 — OBS with SRT (7:30)

"SRT is more resilient than RTMP over unstable connections — it handles packet loss and variable latency far better, making it the better choice for venue networks or cellular connections."

"In OBS 30 or later: Settings → Stream → Service: Custom. Server: paste the SRT URL from the SRT Endpoint section — it includes your stream key embedded in the URL as the stream ID. No separate stream key field is needed. Click Start Streaming. The server receives the SRT stream, converts it, and relays it to your configured platforms — exactly as with RTMP."

[Show the SRT URL field on the stream page — reveal and copy]

"The SRT URL is hidden by default since it contains your key. Click Show, then Copy, then paste into OBS."

Section 5 — Browser Streaming Mode (10:00)

"Click Start Browser Stream on the stream page. Select the HazR App tab from the screen-share picker. The Live badge appears — your browser captures the tab, encodes it, and sends it to all your configured platforms. No external software required."

Section 6 — Regenerating your stream key (12:00)

"If you need to rotate your key, click Regenerate Key. Both the RTMP and SRT URL fields update immediately. Any active OBS session using the old key will disconnect — update OBS before streaming again. Platform destinations are unaffected."

Closing (12:45)

"Your HazR session — live, everywhere, at once. Use RTMP for reliable studio setups, SRT for venues and unstable networks."

[Title card: "Tutorial 6: Presets & MIDI CC Mapping"]

"Presets let you snapshot any visual configuration and recall it instantly. MIDI CC mapping lets you bind any slider to a physical knob or fader on your controller."

Section 1 — Saving a preset in-app (0:45)

"In the app, open the Presets panel. Click Save Current as Preset and give it a name. The preset captures every slider position — pattern, shape, size, speed, color mode, opacity, logo position — everything. It's saved to the server immediately and persists across sessions and devices."

Section 2 — Recalling a preset (2:00)

"Click the preset name. Every slider snaps to the saved positions in one instant transition. You can also manage your preset library from the Presets page in the dashboard."

Section 3 — What is MIDI CC? (3:30)

"CC messages — Control Change — are what your knobs, faders, and expression pedals send. Every physical control generates a CC number between 0 and 127 and a value between 0 and 127 when you move it. HazR can intercept those CC messages and route them to any visual parameter."

Section 4 — Creating a mapping (4:30)

"Go to the MIDI Mapping page in your dashboard. Choose the parameter — for example Color Mode. Enter the CC number your knob sends. Choose the MIDI channel or leave it on All Channels. Click Add Mapping. Go back to the app and turn your knob — the Color Mode slider moves in real time."

Section 5 — Useful mappings for live performance (6:00)

"A practical live setup: one fader for Size, one for Speed X, one for Speed Y, one for Color Mode, and a button mapped to Opacity so you can black out the visual with a single key press."

Closing (7:30)

"With presets and CC mapping, HazR becomes a hardware instrument. Your controller is no longer just playing notes — it's conducting the entire visual score."

[Title card: "Tutorial 7: Setlist, Custom Generators & Custom Modes"]

"This tutorial covers three features that unlock the full creative depth of HazR. Setlists let you pre-script your entire performance as a sequence of cues. Custom Generators let you write your own Python pattern algorithms. And Custom Modes let you write logic that reacts to every MIDI note in real time, controlling any visual parameter dynamically."

Section 1 — Creating a Setlist (0:45)

"Open the Setlist page from the dashboard nav. Click Create Setlist and give it a name. Add your first cue — fill in the parameters for your opening visual and label it 'Intro'. Add as many cues as you need. Each row represents one scene. Reorder by dragging."

Section 2 — Triggering cues live (2:30)

"In the app, open the Setlist panel, load your setlist. Click Next Cue — every slider jumps to the values you saved for that cue instantly. One finger advances the entire visual state. You composed the performance in advance."

Section 3 — Custom Generators (4:00)

"Custom Generators let you write a Python function that receives note and velocity data and returns a 40-by-30 grid of values. The template function receives note (0–127) and velocity (0–127) and returns a list of columns with 'value' keys between 0 and 1. Click Test to preview the output, then Save. Back in the app, activate it from the Custom Generator panel."

Section 4 — Custom Modes (7:00)

"Custom Modes control HazR's visual sliders directly. Write a respond() function that receives note, velocity, and the list of all currently active notes — and returns a dictionary of parameter names and their new values. Available parameters: mode, pattern, shape, color_mode, particle_size, speed_x, speed_y, speed_z. Your function runs server-side on every MIDI input."

Closing (9:30)

"Setlists, Custom Generators, and Custom Modes take the instrument from reactive to compositional. In Tutorial 8, we cover multi-display mirroring, branded logo overlay, and the external API."

[Title card: "Tutorial 8: Multi-Display, Logo Overlay & External API — Venue Features"]

"The Venue plan is built for installation, events, and professional performance. This tutorial covers three features that extend HazR beyond your single screen."

Section 1 — Multi-Display Mirroring (0:45)

"In the app, open the Mirror Screen panel. Click Go Live. A unique display URL is generated — a full-screen visual canvas that mirrors everything happening in your app in real time. Open it on any device with a browser: a projector laptop, a TV backstage, a tablet at the venue entrance. Every slider change you make is broadcast to all connected screens within milliseconds."

Section 2 — Logo Overlay (2:30)

"The Logo panel lets you overlay a transparent PNG on the visual canvas. Click Upload PNG and select your image. The Size slider controls the width in pixels (10–1000). Position X and Y move it anywhere on screen. The Opacity slider lets you ghost the logo — a setting around 0.2 to 0.4 gives a clean watermark effect. Logo parameters are saved with presets."

Section 3 — External API (4:30)

"From the API Keys page in the dashboard, generate a key prefixed with syn_. To send a visual update, make a POST request to /api/external/visual with your API key in the Authorization header and a JSON body specifying the parameters — pattern, color mode, speed X, and so on. You can also start and stop streaming via the API: POST to /api/external/stream/start and /api/external/stream/stop. The /api/external/usage endpoint returns live session data."

Section 4 — Putting it together (6:30)

"A full Venue setup: your main laptop runs the HazR app. The Mirror URL is open on the venue projector and at the DJ booth. Your logo is overlaid at 0.25 opacity. Four knobs map to color mode, speed X, speed Y, and opacity. Your setlist has 12 cues pre-programmed. HazR is a complete visual production system, and you are the director."

Closing (7:45)

"That's the full Venue toolkit. Full documentation is at nxprm.io/hazr."

[Title card: "DiggR Tutorial 2: Building Patterns"]

"In this tutorial we go beyond the default kit. We'll load your own samples, control the velocity of individual steps, change the pattern length, and build a bank of patterns ready to switch between during a performance."

Section 1 — Loading samples (0:30)

[Click the track label "Kick" on the left. Sample loader panel opens.]

"Click any track label to open the sample loader for that track. Click Load Sample and select an audio file from your computer — WAV, AIFF, or MP3. The sample replaces the default kit sound for that track. The waveform preview updates to show your file."

[Load a drum loop sample onto a track]

"You can load any sound — a drum hit, a synth stab, a spoken word clip. DiggR treats every track as a sample slot. Your kit is entirely yours."

Section 2 — Per-step velocity (2:00)

[Right-click an active step. Velocity slider appears.]

"Right-click any active step to reveal a velocity slider for that specific step. Drag it down for a quieter hit, up for a harder one. A fully dark step plays at maximum velocity; a lighter shade indicates a softer hit."

"Use velocity variation to add groove. A kick at full velocity on beat 1, a slightly softer kick on the 'and' of beat 3 — that subtle difference is the difference between a mechanical pattern and something that breathes."

Section 3 — Pattern length (4:00)

[Pattern length selector in transport bar — change from 16 to 32 steps]

"The default pattern length is 16 steps — one bar at 4/4. Increase it to 32 for a two-bar phrase, or drop it to 8 for a fast half-bar loop. You can also set different lengths per track — the Kick track might loop every 16 steps while a percussion track loops every 12, creating a polyrhythmic offset."

Section 4 — Multiple patterns (6:00)

[Pattern bank buttons at the top — A, B, C, D]

"The pattern bank holds up to four patterns: A, B, C, and D. Click a pattern letter to switch to it — the current pattern keeps playing while you edit the new one. Program your intro groove in A, your main loop in B, and a break in C. During performance, one click shifts the entire sequence."

Closing (7:30)

"In Tutorial 3, we take these patterns live — BPM control, swing, mute/solo, and how to build a set from your pattern bank."

[Title card: "DiggR Tutorial 3: Performance Mode"]

"You have your patterns programmed. Now we take them live. This tutorial covers everything that happens in real time during a performance: tempo, swing, muting tracks, and the pad bank."

Section 1 — BPM and tap tempo (0:30)

"The BPM control in the transport bar sets the tempo. Click and drag up to increase, down to decrease. Or use the Tap Tempo button — tap it four times in rhythm and DiggR calculates the BPM from your taps. Useful when you're syncing to a DJ set or a live band."

Section 2 — Swing (1:30)

"The Swing slider adds a shuffle feel by delaying the off-beats. At zero, the pattern is perfectly quantised. Increase swing and the pattern starts to push and pull — even-numbered steps land slightly late, creating a groove that feels human. Start around 15 to 20 percent for a subtle groove, 50 percent for a heavy swing feel."

Section 3 — Mute and Solo (2:30)

[Click the M button on the Hi-hat track]

"Each track has a Mute button. Click it to silence that track without stopping the pattern. The steps are still programmed — muting is non-destructive. Use mutes to build and strip the arrangement: start with kick and bass, add hi-hats, bring in the clap, then mute the kick for a percussion breakdown."

[Click the S button on the Snare track]

"Solo isolates one track and silences everything else. Useful for checking a single element in isolation or for a dramatic solo effect during a performance."

Section 4 — Live pattern switching (4:00)

"The pattern bank — A, B, C, D — switches at the end of the current bar, not mid-step. This keeps the transition clean and on beat. Queue the next pattern during the last few steps of the current bar and it switches seamlessly. Build a full set narrative: pattern A for the intro groove, B for the main section, C for a break, D for a peak."

Section 5 — The pad bank (5:30)

"The pad bank at the bottom of the interface lets you trigger any sample instantly — outside the step sequence. Tap a pad during performance for fills, one-shot accents, or to introduce a new sound before activating its track in the sequencer."

Closing (6:30)

"DiggR in performance mode is a full live instrument. Build your patterns in advance, then use mutes, solos, pattern switches, and the pad bank to create a set that evolves in real time — in front of an audience, from a browser."

[Title card: "PulsR Tutorial 2: Visual Modes & Controls"]

"PulsR has nine distinct visual modes — from particle physics to digital rain to a 3D halo ring. Each mode responds to the same set of controls but produces a completely different aesthetic. In this tutorial, we go through every mode and every slider."

Section 1 — The nine visual modes (0:30)

[Screen: mode selector tabs in the app — Canvas, Quadrat, Curvic, DOM, Particle, Matrix, Fusion, Vector]

"The mode tabs are at the top of the visual panel. Let's go through each one."

"Canvas — a continuous flowing particle field. The primary generative mode."

"Quadrat — the canvas divided into a grid of reactive cells. Each cell brightens and shifts independently."

"Curvic — a curved line system that warps and oscillates with the audio."

"DOM — a text-based mode. The visual is built from layered HTML elements — great for type-heavy brand identities."

"Particle — a full physics simulation. Particles burst and arc under gravity and wind, with eight different emission shapes."

"Matrix — digital rain. Streams of characters fall in real time, fully configurable with ten character sets from binary to katakana."

"Fusion — a 3D-projected halo ring rendered in a canvas with a nebula core. Motion and glow respond to audio intensity."

"Vector — an animated node network. Points connect with lines, driven by the slider values rather than audio."

[Pause on each mode briefly as it's named]

Section 2 — The parameter sliders (3:00)

[Screen: parameters panel with all sliders visible]

"Every mode shares the same set of sliders — their effect is different in each mode, but the layout is consistent."

"Particle Size — controls the scale of the primary visual element. In Canvas mode this is the particle radius. In Matrix it's the font size. In Fusion it's the ring radius."

"Velocity — in audio-reactive modes, this sets the burst strength when audio triggers. In non-reactive modes it controls overall motion speed."

"Speed X and Speed Y — horizontal and vertical drift. In Particle mode these become wind direction. In Matrix they control horizontal drift of the streams."

"Speed Z — the third axis. In 3D modes like Canvas this is depth movement. In Matrix it controls trail intensity."

"Emission — the density of the effect. In Canvas this is particle count. In Matrix it's stream density. In Fusion it sets amplitude and glow width."

"Opacity — overall canvas transparency. At zero the canvas is invisible. At one it's fully opaque. Partial opacity lets you layer PulsR over other content."

"Colour Mode — fifty-one preset colour palettes. Scroll through them to find the one that best matches your brand."

Section 3 — Audio input (6:00)

[Screen: audio input section]

"PulsR can read from a microphone or from your system's audio output — depending on your browser and OS permissions. On Chrome with the right system audio permission, you can route your DAW directly into PulsR."

"The sensitivity slider in the audio section controls how aggressively the visual reacts. In a quiet environment, raise it. In a loud venue with a strong signal, lower it to prevent the visual from clipping at maximum intensity on every beat."

Section 4 — Launch Multi (7:00)

[Screen: Launch Multi app with four canvas panels]

"Launch Multi opens a four-canvas layout — each panel shows a different visual mode simultaneously, all reacting to the same audio input. This is useful for event display walls, multi-screen rigs, or clients who want to see a range of visual options running in parallel."

Closing (7:45)

"In Tutorial 3, we configure the brand-specific elements — colours, logo, text overlay, and camera — and save everything as a named brand template."

[Title card: "PulsR Tutorial 3: Brand Templates & Overlays"]

"PulsR is a brand tool first. In this tutorial, we configure the visual identity layer — your brand's colours, logo, and typography — then save it as a reusable template."

Section 1 — Brand colours (0:30)

[Screen: Brand section in the control panel — three colour pickers]

"The Brand section has three colour inputs: Primary, Secondary, and Accent. Primary drives the dominant visual elements — the particles, lines, or characters depending on your mode. Secondary fills the supporting geometry. Accent fires on high-intensity audio moments — a beat hit, a transient peak."

"Click any swatch to open the colour picker, or type your hex code directly. The canvas updates in real time."

[Type a hex code — canvas recolours]

Section 2 — Logo overlay (2:00)

[Screen: Logo section — upload button and sliders]

"Upload your logo as a PNG with a transparent background. Use the Size slider to scale it. X and Y position sliders move it anywhere on the canvas — top-right corner for a subtle watermark, centred for a bold brand statement. The Opacity slider lets you ghost the logo over the visual without obscuring the animation."

"The logo is composited above the visual canvas at all times, even during audio peaks."

Section 3 — Text overlay (3:30)

[Screen: Text overlay section]

"The Text Overlay section lets you add a single line of text over the canvas — an event name, a brand tagline, a call to action. Choose a font from the selector — there are several typefaces available. Set the colour, size, opacity, and X/Y position independently from the logo."

"This is useful for live event lower thirds, presenter name cards, or social content captions."

Section 4 — Camera overlay (4:30)

[Screen: Camera section — device selector and enable toggle]

"The Camera section adds a live webcam feed as a layer above the visual canvas. Select your camera device from the dropdown and click Enable Camera."

"You can choose between 16:9 landscape or 9:16 portrait aspect ratio. The Fill options let you contain the camera feed inside the canvas or stretch it to fill the full frame."

"The Background Removal toggle activates AI-powered background keying using MediaPipe — the presenter stays visible while the background is replaced by the visual. This works entirely in the browser, with no server processing."

[Toggle background removal — presenter isolated over visual]

Section 5 — Saving and loading templates (6:30)

[Screen: Brand Templates section in control panel — save button]

"Once your visual is configured, open the Brand Templates panel and click Save. Name the template after your client or event. The template stores every setting: mode, all slider values, brand colours, logo, text, and canvas aspect."

[Screen: Brand Templates dashboard page at nxprm.io/pulsr/templates]

"Your saved templates are also accessible from the Templates page on the dashboard. Here you can edit every parameter directly — without opening the app — and click Open in App on any template to launch the visual engine with that configuration pre-loaded."

Closing (7:45)

"In Tutorial 4, we connect PulsR to external platforms — live streaming to Facebook, YouTube, TikTok, and mirroring the visual to a second display over the network."

[Title card: "PulsR Tutorial 4: Live Streaming & Multi-Display"]

"Agency subscribers can broadcast PulsR visuals live to Facebook, YouTube, Instagram, TikTok, Twitch, X, or any custom RTMP destination — directly from the browser or via OBS. In this tutorial we'll configure both modes and set up a mirror screen."

Section 1 — The Stream dashboard (0:30)

[Screen: nxprm.io/pulsr/stream]

"Open the Stream page from the dashboard. You'll see two sections: Browser Streaming and RTMP Endpoint. Below both, Platform Destinations — where you configure your target platforms."

Section 2 — Platform destinations (1:00)

[Screen: Platform Destinations form]

"Fill in your stream credentials for each platform you want to reach. Facebook Live and Twitch take just a stream key — grab these from your Facebook Live dashboard or Twitch Settings respectively. YouTube, Instagram, TikTok, and X use a full RTMP URL that combines the server address and stream key — your platform's live settings page will show you both."

"Leave any platform blank to skip it. PulsR relays to all configured platforms simultaneously from a single stream."

[Click Save]

Section 3 — Browser streaming (2:30)

[Screen: Browser Streaming section — Go Live button]

"Browser streaming captures the PulsR canvas directly from your tab and encodes it server-side. Click Go Live in the Browser Streaming section. Your browser will ask permission to share your screen or a tab — select the PulsR app tab."

"The stream begins immediately. PulsR encodes and relays to all your configured platform destinations. The Go Live button turns to a Stop button — click it to end the broadcast."

"Browser streaming works without any additional software — the only requirement is an Agency account and a stable internet connection."

Section 4 — OBS with RTMP (4:30)

[Screen: RTMP Endpoint section — server URL and stream key]

"For encoding control — resolution, bitrate, frame rate — use OBS. Copy the RTMP server URL and stream key from the RTMP Endpoint section. In OBS: Settings → Stream → Service: Custom. Paste the server URL and stream key. Click Start Streaming. OBS pushes to the PulsR server, which relays to all your configured platforms."

Section 5 — OBS with SRT (5:45)

"SRT is an alternative to RTMP that handles packet loss and latency spikes better — ideal for venue networks or cellular connections. In the SRT Endpoint section, click Show on the SRT URL field and copy it. The URL has your stream key embedded as the stream ID."

[OBS 30+: Settings → Stream → Custom → paste full SRT URL into Server]

"In OBS 30 or later: Settings → Stream → Service: Custom. Paste the full SRT URL into the Server field — no separate stream key is needed. Click Start Streaming. The server receives the SRT stream, converts it, and relays it to all configured platforms."

"If you need to rotate your key, click Regenerate Key. Both the RTMP and SRT URL fields update immediately."

Section 5 — Multi-display mirror (5:45)

[Screen: Mirror Screen section in the app panel → Go Live toggle]

"The Mirror Screen panel inside the app sends your visual state to a second browser at a unique URL. Toggle Go Live, copy the mirror URL, and open it on any screen — a second monitor, a projector, a tablet — connected to the same or a different device on the network."

"Every slider change, mode switch, and audio peak is mirrored in real time. The mirror screen requires no login — share the URL with your AV team and they can display it on any device."

Closing (6:45)

"In Tutorial 5, we look at the API — how to control PulsR programmatically from show control systems, scripts, or any MIDI-to-HTTP bridge."

[Title card: "PulsR Tutorial 5: API Keys & External Control"]

"Agency subscribers can control PulsR entirely over HTTP — triggering visual changes, starting and stopping streams, and reading usage data from any system that can make a web request. This means show control consoles, custom scripts, MIDI-to-HTTP bridges, or automation pipelines."

Section 1 — Generating an API key (0:30)

[Screen: nxprm.io/pulsr/api]

"Open the API Keys page from the dashboard. In the Generate New Key form, enter a descriptive name — something that identifies the system this key will be used by. 'Live Show', 'Studio Controller', 'Automation Script'. Click Generate."

[Key appears in amber reveal box]

"The full key appears once — copy it now. PulsR stores only a hash of the key, not the key itself, so it cannot be recovered after you close this panel. If you lose it, generate a new one and delete the old entry."

"Generated keys appear in the table below with their name, creation date, and last-used date. Delete any key from this table to immediately revoke its access."

Section 2 — Authentication (1:30)

"Every API request requires a Bearer token in the Authorization header:"

[Show: Authorization: Bearer syn_xxxxxxxxxxxx]

"The key format is syn_ followed by a hex string. Include it exactly — the API returns a 401 Unauthorized response for any request with a missing or invalid key."

Section 3 — Setting visual parameters (2:00)

[Screen: API reference — POST /api/external/visual]

"POST to /api/external/visual with a JSON body containing any combination of visual parameters — model_index to change the visual mode, shape_index to change the pattern within a mode, particle_size, speed_x, speed_y. All parameters are optional; only the ones you include are updated."

[Example: curl -X POST with JSON body]

"For example, to switch to Matrix mode — model_index 5 — and set a slow fall speed, send model_index 5 and speed_y 0.3. The visual in the app updates within a fraction of a second."

"This endpoint is the core of show automation — a lighting desk with a macro processor can call this API on every scene change, keeping the PulsR visual in sync with your show state without any manual operation."

Section 4 — Stream control (4:00)

"Two endpoints control streaming: POST to /api/external/stream/start begins relaying to your configured platforms, and POST to /api/external/stream/stop ends it. Both require only the Authorization header — no body needed."

"This lets you automate your broadcast schedule — a cron job or show controller can start the stream at the top of the set and stop it at the end, without manual intervention on the dashboard."

Section 5 — Usage data (5:00)

[Screen: GET /api/external/usage]

"GET to /api/external/usage returns your session history and statistics in JSON — session count, average duration, total event triggers. Use this to build custom reporting dashboards or feed data into your client billing systems."

Closing (5:45)

"The API gives you full programmatic control over PulsR. Combined with a show control system or a simple script, you can automate every aspect of your visual workflow — from first cue to final fade — without touching the browser interface."

[Outro card: "Full API documentation at nxprm.io/pulsr/api"]

[Title card: "Loopback Mixer 16x2 — Tutorial 2: DAW Setup"]

"Loopback Mixer is installed. Now we route our DAW's audio output through it. I'll demonstrate in Ableton Live, then Logic Pro, then briefly cover other DAWs."

Section 1 — Ableton Live (0:20)

[Screen: Ableton Live. Open Preferences with Command + comma.]

"Open Ableton Live and go to Preferences — Command comma on Mac. Click the Audio tab."

[Audio Output Device dropdown. Select Loopback Mixer 16x2.]

"Set the Audio Output Device to Loopback Mixer 16x2. Below that, you'll see the Output Config — click it to open the channel configuration window."

[Channel configuration window. Enable outputs 1/2.]

"Enable the output channels you need. For a standard stereo setup, enable outputs 1 and 2 — these are your Master L and R. For multi-channel setups with multiple outputs, enable additional pairs."

[Close preferences. Play a track. Audio comes out of speakers.]

"Close preferences and play a track. Audio comes out of your speakers or headphones immediately — Loopback Mixer is passing it through transparently."

Section 2 — Logic Pro (2:30)

[Screen: Logic Pro. Logic Pro menu → Settings → Audio.]

"In Logic Pro, go to Settings → Audio. Under Output Device, select Loopback Mixer 16x2. Logic will briefly reload its audio engine — this is normal."

[Play a track. Audio plays through speakers.]

"Play your project — audio comes through your speakers or headphones as expected. Logic's output is now routed through Loopback Mixer."

Section 3 — Other DAWs (4:00)

"For any other DAW — Pro Tools, Reaper, Bitwig, FL Studio on Mac, GarageBand — the process is the same: find the audio preferences or output device setting and select Loopback Mixer 16x2 as the output. Every DAW follows this same pattern. If your DAW uses Core Audio, Loopback Mixer will appear in its device list."

Closing (5:30)

"Your DAW is now configured. In Tutorial 3, we look at multi-channel routing for complex setups, and cover the most common troubleshooting issues."

[Title card: "Loopback Mixer 16x2 — Tutorial 3: Multi-Channel Routing & Troubleshooting"]

"In this tutorial, we go beyond the basic stereo setup. We'll look at how Loopback Mixer handles multi-channel output, how headphone switching works, how to tune the buffer size, and how to diagnose and fix common audio issues."

Section 1 — Multi-channel output (0:30)

"Loopback Mixer 16x2 provides 16 output channels — 8 stereo pairs. In Ableton, you can route different tracks to different output pairs: your master to outputs 1/2, a headphone cue mix to outputs 3/4, a stem group to outputs 5/6, and so on. This is the same workflow as a professional audio interface — Loopback Mixer maps each pair to your physical output transparently."

[Ableton audio preferences — Output Config — multiple pairs enabled]

"Enable the additional output pairs in Ableton's Output Config. Each pair appears as a hardware output in your session mixer — route tracks to them using the output selector on each channel strip."

Section 2 — Headphone switching (2:00)

"Headphone switching is fully automatic. When you plug in headphones, macOS switches the physical output target — Loopback Mixer detects this and routes all audio to the headphones. When you unplug, it switches back to speakers. There is no interruption, no click, no dropout. This is handled at the driver level."

"If you use a USB audio interface as your headphone output, set that interface as your Mac's default output in System Settings and leave Loopback Mixer as your DAW's output device only. Loopback will route DAW audio to your interface transparently."

Section 3 — Buffer size and latency (3:30)

"Buffer size controls the trade-off between latency and stability. A smaller buffer — 64 or 128 samples — means lower latency: what you play in your DAW is heard almost instantly. A larger buffer — 256 or 512 — is more stable on busy projects with many plugins."

"Change buffer size in your DAW's audio preferences — the same Audio settings where you selected Loopback Mixer. If you hear crackling, increase the buffer size one step at a time until it stops. If latency is too noticeable during monitoring, reduce it one step at a time."

Section 4 — Common issues (4:30)

"No audio from DAW: confirm Loopback Mixer 16x2 is selected as the output device in your DAW's audio preferences, and that the correct output channels are enabled in the Output Config."

"Loopback Mixer not appearing in device list: restart your Mac. If it still doesn't appear, re-run the installer package — it will repair the driver without affecting your settings."

"Crackling or dropouts: increase the buffer size in your DAW preferences. If the issue persists, open Activity Monitor and check if any background process is causing high CPU usage."

"Audio after uninstall: after running Uninstaller.pkg and restarting, Loopback Mixer will be removed from your device list. If your DAW shows an error about a missing device, open its audio preferences and select a different output."

Closing (5:45)

"Loopback Mixer 16x2 is designed to stay out of your way — install it once, set it as your DAW output, and forget about it. The full compatibility list and system requirements are on the Downloads page at nxprm.io/downloads."