I'm wondering now whether I should have made a post instead just about the error Run-time dependency gstreamer-1.0 found: NO (tried pkg-config and cmake). Given that that's the actual issue that's currently still relevant. Can someone confirm that gstreamer-1.0 is supposed to be included in gst-plugins-rs.git and that it shouldn't be missing after following the plugin instruction steps, or otherwise clarify where I've made a mistake following the wiki instructions?

I have the same problem. It can show up randomly but if I choose next in the playlist it will happen then. If I double-click the selected song it will resume. I use ALSA and have used both HW and PCM with no change between them.

I use Linux Mint Mate.

@silver-sun I've adjusted the headset volume and its helped. But the volume slider is directly connected to the application volume control so adjusting it on there adjusts the volume slider and vice versa. There is no other point on the chain besides those two. (I'm using pipewire for context)

Your pay grade is obviously higher than mine.

God I hope not I'm unemployed

Look for Menu -> Tools -> Settings... -> Playlist -> Use alternating row colors

@Sharky-PI this would be incredibly useful.

I'm pretty sure that Strawberry sorts by metadata. A song needs a track number, independent of the file name. The suggestion of renaming files numerically is a good idea. Organizing your album folders alphabetically, by song name, runs counter to the way albums are presented -- which is numerically, by track number.

Right click on a song and select "Edit track information". There should be a number in the "Track" field at the right. Don't change anything yet, until you figure out the root of your problem, but if there is no number, that might be of concern.

Hope that helps.

Following up on this — the moodbar workaround is a fair suggestion, but I think it is worth distinguishing because moodbar and a real waveform actually solve different problems/features. The moodbar shows the spectral "mood" of a track as a colour gradient, which is fine for a vibe, but the colour bands do not reliably correspond to where the loud parts, drops, breaks, or quiet sections are. As a DJ I find myself wanting to see the actual amplitude shape of the track — the peaks and troughs over time — so I can spot a drop, a build-up or a breakdown by eye in a few hundred milliseconds. Mixxx and most DJ-oriented tools display this as a horizontal waveform strip with a playhead, and it is hard to go back to scrubbing without one.

What I would propose for Strawberry is a proper waveform visualization that lives in the analyzer area above the progress bar, alongside Block, Boom, Turbine and the others, as just another option in the right-click "Analyzer" menu. Selecting it would render the loudness contour of the entire current track as a horizontal waveform, with a playhead moving across it as the song plays. It would not replace the moodbar (moodbar can stay exactly where it is, painted into the slider groove), and it would not replace the live spectrum analyzers either.

It would just be one more option in that menu, for the users who want it.

I had a look at the code and the feature seems quite feasible without adding any new dependency. The moodbar pipeline already handles the hardest part: running a GStreamer pre-pass over a track on a worker thread and caching the result. A waveform pipeline would essentially be the same pattern, but storing peak/RMS values instead of FFT-derived colours. Other parts of the engine (Chromaprint, EBU R128 loudness analysis) already extract raw PCM from GStreamer in the exact way a waveform would need.

I am planning to open a GitHub issue to gauge the maintainers' interest. Would anyone else here find this useful? Especially curious whether other DJs, or people working with mixes and live recordings, would back this up.