The engine
Fixed 32-sample block, Plugin Latency Tolerance with per-slot blocks, AU + CLAP + VST3 in one chain, ten built-in plugins, rack macros.
Roadmap
Where this is going
What's in the beta today, what's on the bench, what comes after, and the one thing that's waiting on someone else. Dated where we can be, so you can hold us to it.
Capture
Multitrack audio and multiple cameras on one clock, Performance Record for the whole set, camera cuts recorded as editable timeline data.
The stage
DMX lighting on tracks (Art-Net and USB-DMX), looper station with FCB1010 support, phone remote with per-player IEM mixes, RTMPS streaming.
Writing
Tabs and notation on the MIDI engine, Guitar Pro export, vocal synthesis, the .jam song format and setlists.
Capture your gear
In-app Neural Amp Modeler training, impulse-response capture from a swept sine, drag-and-drop profiles onto racks.
Interop
Export to REAPER, Final Cut Pro (FCPXML) and OpenTimelineIO; import of every common audio container.
On the bench
In development
Code exists and is being tested. Not in testers' hands yet.
Session sharing between players
Peer-to-peer sessions on one shared transport and clock. TOAST already links machines across a local network; sharing whole sessions between bandmates comes first, then the same thing across the internet.
Freeze the rig
Distill a whole plugin chain into a captured NAM profile plus IR that plays back at a fixed, known latency. Unfreeze to get the chain back.
Portable core
The engine, clip store and session format extracted from the macOS shell so the same code runs on Linux and on phones.
After the beta
Next
In roughly this order. Each one is scoped; none is started.
Record direct to cloud
Takes upload while you're still recording them, behind the disk write, so a crashed laptop at minute 47 has already saved minutes 0–46. Optional, and off by default. Pricing.
Band pages and the practice room
A page per band, created from inside the app. Bandmates open the material in a browser, practice against the band minus their own part, and leave a take for review. Free to host from your own studio; always-up on the subscription.
Linux
Ubuntu Studio on affordable mini-PCs: the same engine, the same fixed 32-sample block. A build guide and a first-boot installer come with it.
Phone app, standalone
Record with the phone's mic and camera into a session, then sync it back to the studio. Same engine, same 32-sample core.
DAWs without borders
The DAW you already use isn't a place you have to leave
JNS4Live and JAMNetStudioRPP put JAMNet Studio's engine inside the DAW you already open every day. Project Rosetta is what makes the trip between them lossless.
JNS4Live
JAMNet Studio as an extension inside Ableton Live: the same 32-sample engine, tracks and racks, running alongside Live's own on one clock.
JAMNetStudioRPP
Run JAMNet Studio from inside REAPER: the same engine reachable without leaving REAPER's own session.
Project Rosetta
The session converter, extracted and open-sourced: OpenTimelineIO in the middle, a faithful translation into each DAW and editor format, and a list of exactly what carried over. What it means.
Further out
Later, and one thing we're waiting on
Playing together over the internet
Three rungs, each with a benchmark: wired-LAN sessions with under a millisecond of added latency; internet sessions on Network Latency Tolerance, where every player is aligned to the same negotiated delay; and a shared-looper mode for any distance, where players layer against each other's previous pass.
Network Latency Tolerance
Your brain already compensates for a fixed delay: with headphones on, fingers adjust to it within minutes, up to a threshold that's different for everyone. A wired connection can generally hold that under 30 ms end to end, comfortably inside it. Network Latency Tolerance shares one delay-compensated mix across every player, so you're both adjusting to the same offset instead of two different ones, which is what actually keeps a pocket together at a distance. Turn it off for the lowest latency to your own monitor, and a looser feel against your bandmate.
Hardware guide and starter kits
A build guide for a barebones mini-PC that runs the Linux version, then small batches of sealed-component kits with the installer, then a validated configuration with a vendor.
Windows
The engine goes where the OS can keep a fixed 32-sample buffer on any class-compliant interface. Microsoft has announced an in-box low-latency USB audio stack; when it ships and holds that contract, a Windows build is on the table. Undated on purpose.
How the order gets decided
Three rules
- The latency contract is never traded away. A feature that needs the audio thread to wait doesn't ship, however popular.
- One clock, one timeline. Anything new (a camera, a lighting fixture, a bandmate's laptop) joins the same clock or it doesn't join.
- Free things stay free; paid things have a server bill. The app is the instrument. The subscription is the cloud that holds things for you. Nothing is held back from the app to sell it later.