Sound Lexicon / Queue · all queues
Listening queue
Drag Suno, YouTube or Spotify links in from the browser, or paste them anywhere on the page. The
list lives in this browser only — nothing is uploaded. Playback is each source's own
embedded player, so a mixed queue is fine.
Drop Suno, YouTube or Spotify links here — or paste one anywhere on the page.
A Suno
/song/ , embed, share or bare id — a
youtube.com/watch ,
youtu.be or shorts link —
an
open.spotify.com/track/ link or a
spotify:track: uri —
or a YouTube (or YouTube Music)
playlist , or a Spotify
album or playlist , each of which
joins the queue as one row and plays all the way through.
Add
you are —
Change name
live
Open adding: off
Suno
YouTube
Spotify
Copy link
listed
Delete queue
New queue
Share this queue
This queue is private to this browser — no chat, and nobody else can see it.
Share this queue publishes it, gives you a link, and opens a chat on it.
⛶
COVER
next in
0:00
⏮
⏭
⛶
Nothing playing
Queue is empty
follow
auto
shuf
rep off
Up next
Take turns
Shuffle order
Clear
Nothing queued yet.
Already played
Reset
Nothing played yet.
Chat anyone with the link can talk here
Keys: shift +← → previous / next track · t player size —
theatre or full window · f a Suno track's cover (still or moving) full window ·
esc out of either.
Which sources guests may use. An owner can switch Suno , YouTube or
Spotify off for everyone else, from the three buttons beside Open adding . It
is a rule about the room rather than a promise to yourself — the owner can still add from
any source — and it only bites while open adding is on, since guests cannot add at all
otherwise. A blocked link posted in the chat says which source is off rather than quietly
offering nothing. Like open-adding, this is enforced by the database and not by hiding the
button: a guest who calls the API by hand is refused just the same. A queue that has never
been restricted allows all three, which is what every queue made before this does.
Listening together. On a shared queue, follow keeps a visitor on the owner's
track — and now at the owner's position in it, for the two sources that allow it.
YouTube and Spotify both publish a player API with a seek and a position, so
the owner's playhead is written to the queue whenever it changes and every follower is held
within a couple of seconds of it, starting, pausing and jumping when the owner does. The
position carried is "this second, at that moment", not a stream of ticks, so a visitor
arriving mid-track works out where to be rather than waiting to be told, and both ends use
the database's clock so nobody's own is trusted.
Suno cannot do this , and the page does not pretend otherwise. Its embed publishes no
player API, answers no message, and cannot even be started from outside — which is why the
countdown next to it is a timer rather than a playhead. A Suno row still follows to the same
track; where you are inside it is yours. On Spotify the thirty-second rule still applies: a
preview cannot follow a playhead past 0:30. Picking any row yourself steps out of following,
which is also how you take back the pause button.
Moving tracks between the columns. A row drags within Up next to reorder the
queue, and now also across to Already played and back. Dragged into the played
column it is recorded as heard without being played — the way to skip something for good
without deleting it. Dragged out of it, it is struck from that record and goes back into
the queue at the point you drop it, which is how you queue something again. Dropping onto
a row puts it in that row's place; dropping on the space past the last row puts it last.
Neither direction touches the player: what is playing keeps playing. Only the owner of a
shared queue can do this, because the history it writes belongs to the queue.
About auto-advance. It works two different ways, because the sources differ.
YouTube and Spotify publish player APIs, so this page is genuinely told when a
track ends and advances on that — exact, and it respects a pause. Suno's embed is a plain
cross-origin frame that reports nothing, and their audio stream is encrypted, so the track
cannot be played here and watched for its end either. For Suno rows auto is
therefore a timer over the track's known length, with the countdown kept on screen: right
when you listen straight through, and wrong if you pause inside the frame, which is the one
thing it cannot see. It starts when you press play rather than when the track loads — the
page cannot read inside the frame, but it can see the window hand focus to it, which is
the moment somebody pressed something. Only that first press is visible: once focus is in
the frame, further clicks there raise no event at all — measured, not assumed — so
pausing cannot be detected and the countdown keeps running while Suno's does not. That is
the one case it gets wrong, which is why it stays on screen rather than working silently.
Click it to start a clean run from the top.
Spotify, and the thirty-second problem. A Spotify row plays in Spotify's own embed,
which hands this page the playhead — so the queue moves on at the real end of the track,
the same as YouTube. What the embed plays, though, depends on who it thinks you are: signed
in to Premium in this browser it plays the whole track; otherwise it plays a
thirty-second preview and stops, and the queue moves on after thirty seconds because the
track did, as far as anything here can see. A row's length is the honest tell, and the only
one there is: a track showing 0:30 is a preview. Nothing here can ask the embed who it
thinks you are — a frame from another site tells this page nothing about its session — so
the queue never claims to know, and there is no button that could change it.
Two things have to be true for the whole track. You have to be logged in to Spotify in
this browser — the desktop app does not count, it is a different session and the frame
cannot see it. And the account has to be Premium ; Spotify gives a free listener
previews in an embed whatever anyone does. A third can get in the way: the player is a
third-party frame, so a browser set to block third-party cookies leaves Spotify unable to
see the session even when you are signed in. That is a browser setting rather than
something this page can request — Chrome allows them by default, private windows do not.
If the preview is what you get, the Spotify ↗ link on the row is the way out.
Spotify albums and playlists. They play, and they play all the way through, but the
embed reports only where it is in the CURRENT track — never which track of the list that
is. So the end of the last one is indistinguishable from the end of any other, and such a
row does not advance the queue by itself; it says so in the list. Press next when you are
done with it. Individual tracks are exact.
Dropping into the chat. A link dropped anywhere on the chat is posted as a message,
which is how a guest suggests something. If you own the queue it is queued as well —
suggesting a track to yourself and then pressing your own button is a step that does not
need to exist. Anything without a link in it is just posted.
A stream beside the music. Paste a YouTube live link into the small player
to the left and the room can watch while it listens. It is not a queue row: it never plays
in turn, never advances, and nothing syncs to it — the queue is a list of tracks, this is
a window. On a shared queue the owner sets it and everyone sees the same one; on a private
list it is yours and stays in this browser. Either way it is still there when you come
back. It is 356×200, which is the smallest 16:9 box that still clears YouTube's rule that
an embedded player be at least 200 by 200 — any narrower and the height would fall below
the floor. It does not start on its own, so it never talks over the track you are playing;
clear takes it down for everyone.
Covers that move. A few tracks have a video where the rest have a picture — the
creator replaced the cover with an uploaded clip, and Suno kept both halves of it: the
video, and a snapshot of its first frame, which is the still you see on the row and
everywhere else on this page. When one of those plays, the clip appears in its own panel
between the stream and the player, silent and on a loop, and the player shifts right to
make room. Eleven of the library's demos have one. Every other Suno track shows its still
cover in the same panel, square, so any song's artwork can take the window too; YouTube
and Spotify tracks leave the panel off, since their picture is already in the player. Press ⛶ on the picture — or the picture itself, or f — and the
cover takes the window, the same way t does it for the player: the browser window
and not the screen, so this is still a page and escape is still the page's own way out.
The song carries on, because the sound was never in this panel, and the keys carry on with
it — shift +← → walks the queue from here, and a track whose cover
also moves simply keeps the window. The two never share it: sending one full window puts
the other back.
It is a loop beside the music, not a video of it. The clip runs five or ten seconds
against a track of three minutes, so it cannot be in step with anything and does not
pretend to be: it starts when the track loads and repeats until the track ends. Pausing
inside Suno's player does not pause it, for exactly the reason the countdown keeps running
— nothing out here can see inside that frame. A browser asked to keep motion down gets the
still instead, and the clip runs only if you send it full window.
What was playing. A message carries a small cover of whatever was in the
owner's player when it was sent, so a remark months later still says which track it
was about. It is stamped at the moment of sending and never revisited — the playhead moves
on, the message does not — and it is the owner's player for everybody, which is what makes
the same icon mean the same thing on every screen. Messages sent while nothing was playing
carry none, as do any sent before this existed. A Spotify track nobody here has loaded
shows no icon rather than a broken one, because Spotify's cover address is a hash and
cannot be worked out from the link.
Hover the cover to ring the row it belongs to, and click it to scroll that
row into view — useful when the queue is long enough that the row is nowhere near the
message. It finds the row by the track rather than by where it sat, so a queue reordered
since the message was written still lights the right one. A track that has left the queue
has nothing to point at, and its cover says so rather than pretending.
Talking to someone in particular. Type @ and press Tab to complete a
name; Tab again cycles through the matches and Shift+Tab goes back the other way. A bare
@ then Tab offers everyone, which is how you find out who is here — there is no
member list, because the database knows who is present but not what they call themselves.
The names offered are everyone who has left one in this room: whoever has spoken, whoever
queued a track, and the owner, most recent first. Names may contain spaces, so
@ann m completes to @Ann Marie , and a
mention of the longer name is never mistaken for the shorter one. A mention of you is
highlighted where everyone else's is merely coloured. Nothing is verified and nothing is
notified — a name is a label, exactly as it is everywhere else here.
Album playlists. A YouTube Music album link (its id starts
OLAK5uy_ ) will not play here. The embedded
player refuses to unpack one — it loads a single track and then shows its own error
without telling this page anything, which is why such a row is marked in the list and
offers a link out. Ordinary playlists are fine. Individual tracks from the album are fine
too, if you would rather queue them one at a time.
YouTube Premium and ads. Whether the embed serves ads is between you, YouTube and
your browser; this page is not in it and cannot see the answer. The player is a frame from
another site, so it consults your account only if it can read its own cookies here — which
it can in an ordinary Chrome window, and cannot in a private one or in a browser set to
block third-party cookies. That is a browser setting, and only you can change it.
There used to be a sign-in button here that offered to ask on your behalf. It
could not: the API it used covers images and scripts rather than frames, and Chrome allows
it only between sites that have declared themselves related, which this page and YouTube
have not. So every press ended in "your browser did not allow it" — which sounded like a
verdict on your account, and was nothing of the kind. It is gone. If the embed serves ads
anyway, the fix is to open the track on YouTube itself.