jamstream recordings

List and fetch the takes a session recorded to a bucket.

Usage: jamstream recordings [OPTIONS] [COMMAND]
       jamstream recordings get [OPTIONS] <SESSION>

A cloud session records into your own bucket, because the machine deletes itself at the end and a take on its disk goes with it. This is how the takes come back out.

Local sessions need none of this: their takes are already on this computer, in the directory jamstream host printed.

Both forms read the bucket details jamstream host saved beside each session record when the session was launched with a bucket, and the storage key from the environment.

Options

Flag	Default	Meaning
`--json`	off	Emit a JSON array instead of a table.

jamstream recordings get

Flag	Default	Meaning
`<SESSION>`	required	Session id prefix of the session whose takes to download. Any unambiguous prefix works.
`--out <OUT>`	current directory	Directory to write the takes into.
`--yes`	off	Skip the download confirmation, which is where the egress cost is shown.

Listing

$ jamstream recordings
SESSION    TAKE                                           SIZE  MODIFIED
3f2a9c01   jamstream-2026-07-28-1930-mix.flac          1.38 GB  2026-07-28 19:30
3f2a9c01   jamstream-2026-07-28-1930-Ana.flac         691.2 MB  2026-07-28 19:30
3f2a9c01   jamstream-2026-07-28-1930-Bo.flac          691.2 MB  2026-07-28 19:31
5aed5593 has no takes in my-jams (aws/eu-west-1).
5aed5593 has 1 take on this computer, found in /Users/you/Music/JamStream/5aed5593.

Fetch a session's takes with: jamstream recordings get <session>

A take is named for the minute it started, in UTC: jamstream-YYYY-MM-DD-HHMM-mix.flac for the mix, and one jamstream-YYYY-MM-DD-HHMM-<name>.flac per musician when the session recorded stems. They all sit side by side under the session's own prefix; there is no stems folder.

A session that recorded nothing says so on its own line rather than showing an empty table.

The last line is the app's own download folder, a JamStream folder in your music directory with one folder per session, which this command reads as well as the bucket. So a take the retention rule has already deleted still shows as being here.

Nothing is left to check those files against, so no size stands beside them.

Fetching, and what it costs

Downloading is the one part of recording that costs money after the session has already been paid for: the bucket bills egress on every byte that leaves it. So the size and the price come first, and nothing moves until you say yes.

$ jamstream recordings get 3f2a9c01 --out ~/takes
Session 3f2a9c01 recorded 3 takes in my-jams (aws/eu-west-1), delete after 30 days.
Download 2.76 GB at $0.09/GB                    $0.248832
Egress is billed on the download, not on the recording.
Your plan includes 100 GB/month of free download, so this is an upper bound.
Billed to your own cloud account at list prices; JamStream never sees it.
Download these takes? [y/N] y
  jamstream-2026-07-28-1930-mix.flac       100%
  jamstream-2026-07-28-1930-Ana.flac       100%
  jamstream-2026-07-28-1930-Bo.flac        100%
3 takes in /Users/you/takes, 2.76 GB.
Egress for this download: $0.248832.

Pass --yes in a script. Progress is whole lines at fixed percentages, so a log reads the same as a terminal.

The storage key

The object stores want an access key pair, which is not the credential that launches machines. It goes in two variables of its own:

$ export JAMSTREAM_RECORDING_ACCESS_KEY_ID=...
$ export JAMSTREAM_RECORDING_SECRET_ACCESS_KEY=...

In PowerShell: $env:JAMSTREAM_RECORDING_ACCESS_KEY_ID = '...' and $env:JAMSTREAM_RECORDING_SECRET_ACCESS_KEY = '...'.

JAMSTREAM_RECORDING_ACCESS_KEY_ID and JAMSTREAM_RECORDING_SECRET_ACCESS_KEY are read on every provider. Some providers also read their own pair, since neither is a launch credential there:

Provider	Also reads
AWS	nothing extra. `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY` are deliberately not read here, because that pair launches instances and gets written into a machine's user data
DigitalOcean	`SPACES_ACCESS_KEY_ID`, `SPACES_SECRET_ACCESS_KEY`
GCP	`GCS_ACCESS_KEY_ID`, `GCS_SECRET_ACCESS_KEY`

Scope this key to writing the recordings prefix of one bucket; the last section of your provider's page creates it.

The app keeps the same key in your system keychain instead, and its Takes screen fetches from there. This command does not read that keychain, so export the pair here even when the app already has the key.

The key is never written to disk: only the bucket, region, and retention are kept beside the session record.

Notes

Takes outlive the session. A session ended weeks ago still lists, until the bucket's retention rule deletes the objects, and a copy already on this computer outlives those too.
get on a session the rule has emptied still fails, because there is nothing left to fetch, but it names the folder the copies it found are in.
What lands is checked against the size the bucket listed, and a file that arrives short is deleted rather than left looking like a recording.
A take already in the output directory at the right size is skipped and costs no egress. One at a different size stops the download instead of being overwritten.
If a bucket cannot be reached, that session's line says why and the other sessions still list, but the command exits nonzero.

Keyboard shortcuts