Jam Sessions: Synchronised Listening, Explained

A Jam is a room where everyone hears the same second of the same track. Here is what is actually going on underneath, and how to run one that does not descend into chaos.

Published Updated

A Jam is a listening room. One person creates it, other people join with a code, and from then on there is a single playback state that everyone follows — one current track, one position, one shared queue.

Creating and joining

  1. 1

    Create the room

    You become the host. The room gets a join code, and a session starts in a lobby state before playback begins.

  2. 2

    Set visibility

    A Jam can be public, unlisted or private. Unlisted is the usual choice — reachable by anyone with the code, not surfaced to anyone without it.

  3. 3

    Share the code or invite link

    Anyone with it can join. Joining mid-track drops you in at the correct position rather than at the start.

  4. 4

    Start playing

    The session moves out of the lobby and everyone follows the same playback state from there.

Roles

Host
Created the room. Always has full control of playback and queue, sets permissions for everyone else, can promote and remove participants, and can end the session.
Co-host
Promoted by the host. Has playback and queue control regardless of what guest permissions are set to. Worth having on any session long enough that the host will step away.
Guest
Everyone else. What a guest can do depends entirely on the two permission switches the host controls.

The two permission switches

The host sets these independently, and the combination determines what kind of session it is.

Yes

Guests can control playback
No
The result
The usual party setup. Everyone contributes, one person keeps the evening coherent.

Yes

Guests can control playback
Yes
The result
Fully collaborative. Works well with a few close friends, poorly at scale.

No

Guests can control playback
No
The result
Broadcast mode. Useful when the host has built a set and wants it played as built.

No

Guests can control playback
Yes
The result
Unusual, but valid for a fixed queue that anyone should be able to pause.

Skip voting

Skipping is the most contentious action in any shared session, because it overrides somebody's choice. A Jam can put it to a vote instead: participants vote to skip the current track, and it skips when enough of them have.

The threshold is a share of the people in the room, so it scales — the same setting behaves sensibly with three people and with twelve. It removes the awkwardness of skipping someone's contribution by making it a group decision rather than an individual one.

What keeps playback in sync

Sync is the part that is easy to get wrong. Melodius holds the authoritative playback state on the server: each state update carries a position and a server timestamp, and clients compute where they should be from that anchor rather than from their own idea of when playback started.

Clients that fall out of alignment correct themselves against the next anchor, and a client that has been disconnected long enough re-synchronises from scratch rather than guessing. The practical consequence is that a bad connection causes a brief correction rather than a session that quietly drifts apart.

Running a good session

  • Seed twenty tracks before anyone joins. An empty queue makes the first arrival responsible for the mood.
  • Turn on queue permissions and leave playback control with hosts. This is the setting that works for almost every group.
  • Promote a co-host early on anything running more than an hour.
  • Use skip voting rather than arguing about skips.
  • End the session deliberately when you are done, rather than leaving it running — an abandoned room is just a queue nobody is listening to.

When a Jam is the wrong tool

A synced room is built around everyone being present. If people are drifting in and out, or in different time zones, or just want to hear what each other are into without coordinating, a Blend does that job far better — it needs nobody to be online at the same time.

Frequently asked questions

What is a Jam on Melodius?

A synchronised listening room. One person hosts, others join with a code, and everyone hears the same moment of the same track from a shared queue. The host controls whether guests can add to the queue and whether they can control playback.

How do I join a Jam session?

With the join code or invite link from the host. Joining part way through a track puts you in at the current playback position rather than starting the track again.

Can guests skip tracks in a Jam?

Only if the host allows playback control, or if skip voting is used — in which case a skip happens once enough participants have voted for it, based on a share of the people in the room.

How does a Jam stay in sync across different devices?

The server holds the authoritative playback state, and every update carries a position with a server timestamp. Clients align to that anchor rather than to each other, and re-synchronise after a disconnection instead of drifting.

Do I need a paid plan to host a Jam?

No. Jams are available on a free Melodius account, for hosts and for everyone joining.

More on this topic

// Topic

Listening together

Synchronised sessions, shared queues and playlists built from two tastes.