@rlkeeney @jonas thanks lads, sorry, only just saw these replies.

Ok so for MP3 ID3v2.4 I shouldn't need to do anything given I have those 4 options ticked, i.e.:

Once a track has finished playing in Strawberry
-- if I've rated it in Strawberry, Strawberry should save the rating to the file
-- Strawberry should increment the playcount +1 and save that to the file If I edit a track externally (for reference, I would only be saving other tag fields, never rating nor playcount) Strawberry will re-read the track... so if I listen to a track in Strawberry, rate it, the track ends and the rating and playcount are updated by Strawberry to the track's ID3, then I change the track's comment externally, Strawberry should subsequently re-read the track's info (when it does a full scan?) and see the updated comment, and the rating & playcount should still be correct?

I might need to do some testing on that last one. For some reason it seems I have LOADS of tracks I've definitely played countless times, which have playcount=0, and similarly loads I've played and rated which have blanks for both. In the meantime I've edited various ID3 details for those tracks, but as I understand it, that should never compromise the playcounts and ratings, so it seems something is behaving incorrectly...

@jonas fabulous stuff, sorted, cheers mate

@jonas Thank you

Little update. It appears even on non-exclusive outputs (such as WASAPI2) Strawberry does use the samplerate set by the Windows mixer.
I guess this causes forced resmapling in all playback cases, thus noticeably reducing sound quality.

@jonas ah shoot that sucks thank you

@Jellby I don't think it is related. The symptoms do not match.

Last night, it hard-locked. I could not click on anything, so I had to kill the process and restart. There was an error window, but instead of an error message, there was a chunk of a video that was playing in another window.

@mike_jones Update: after another 45 minutes, it's up to 5% so not completely stuck, just very slow.

I've found solution. After updating fedora 41 to 42, extension "AppIndicator and KStatusNotifierItem Support" stopped working because it has not been updated yet to support Fedora 42. This extensions is responsible adding the support for tray icons. After installing the newest version from another source and enabling it I'm able to run Strawberry in background.

@strawt
I notice that the appindicator is installed in /home/tony/.local/share/gnome-shell/extensions, maybe the extension needs to be updated or reinstalled after upgrading to Fedora 42 and a new Gnome version?
I suggest to ask Fedora or Gnome, they probably know this better.

@lvsunz3748
https://support.patreon.com/hc/en-us/articles/360005502572-Canceling-a-paid-membership

@Biod-x
You need to enable it under Tools / Settings / Notifications

@mini_bomba said in Hacking in PrettyOSD positioning on KDE Wayland:

I've been using strawberry on KDE for a few years now.
From the start I've loved the "pretty OSD" style of notifications. They're just so much better than native ones.
They work great under X11, but ever since I've moved to Wayland, the rough edges of that display protocol were apparent every time the OSD appeared... the OSD would always spawn in the middle of the screen, which is just sad.

Now while I understand that this is a shortcoming of the Wayland protocols, that probably won't be resolved anytime soon (even though it should) and that the strawberry project can do nothing to resolve the issue for every Wayland user out there... this doesn't stop individual users (like myself) from hacking in solutions for their own use cases.
So KDE has this neat feature called "window rules". It basically allows me to create sets rules for specific windows, provided that there's a way to select the desired window. These rules may include forcing a specific positioning of a window, which would be quite helpful in this case.

There's only one issue. I couldn't find a way to distinguish the main strawberry player window from the OSD "window". Having the whole player be stuck to the top right corner of my screen wouldn't be ideal.
That's why I've been running a patched version of strawberry for the past few months. One with literally just a one line patch that simply sets the title of the OSD window to "PrettyOSD". This makes it possible to match the OSD window by its new title.

Now while this is a change that I made only to enable a DE-specific hack, I think it's quite a sensible change to make outside of this hack context.
I'll attach the patch I use below as a reference, but keep in mind that I've got almost no C++ experience and this might be the worst way to implement my general idea. I didn't use any AI "help" though, if that makes anyone more confident about the quality of that hacky patch.

Thanks for sharing this! I really appreciate how thoughtfully you’ve tackled this limitation — especially considering the current state of Wayland’s window placement protocols.

You're absolutely right: while the core issue lies in Wayland’s constrained control over arbitrary window positioning, your use of KDE's window rules is a clever and practical workaround. Patching Strawberry to include a unique window title for the OSD is a lightweight and elegant solution, and I agree it’s a change that could benefit more users, even beyond this use case.

This is a great example of how user-driven micro-patches can solve DE-specific issues cleanly without bloating the main project. Honestly, small touches like this — that improve usability without breaking general behavior — should be easy candidates for upstream consideration.

If you’re into sharing insights like this, you might enjoy a recent post I read on digitaldriv , which discusses how user-side patches and desktop-level scripting can bridge gaps in compositors like Wayland. It’s focused on Norwegian developers but offers universal perspectives for niche problems like this one.

hello, I'm having the same issue where strawberry can't find the ipod database - using strawberry version 1.2.10, linux mint, and a 7th gen ipod classic. it's a new to me ipod that's never had music installed on it, and strawberry can interact with my 5th gen classic (which already had music on it) just fine.

It seems to be a taglib issue as well.
Is there anything we can do to add these columns to Strawberry?
It would be very helpful for many.