@leo
Can you try the latest (currently 1.2.3-43) from https://builds.strawberrymusicplayer.org/debian/trixie/ and see if it fixes this crash.

@MrDowntempo Personally what I like about strawberry is that it just works. Foobar is too much work to setup for a casual user to make it look good and make it functional!

@Sharky-PI adding info to this thread: searching the collection by
genre:microhouse
does find the example track, as does searching by
genre:clownpenis
So manual search works for semicolon-separated-subgenres, just not the GUI dropdown system.

+1 for this

Wow! That's what I call service! Thank you!
Just tested lyrics with m4a files and the tag editing now works!
I also tested with an ALAC (Apple Lossless) file, which, confusingly (to me, anyway!) is also m4a. It works on that also!

This is great news. For what it's worth, I think that full compatibility with Apple sourced files is important if you want to develop Strawberry for the Mac platform. While I don't have any real evidence, I think a lot of audiophiles own Macs. I used to read Stereophile magazine, and they were always mentioning their Macs when the subject of computers in audio came up.

To this day, iTunes will not play FLAC files, so Mac users that use iTunes will most likely use ALAC, or lossy AAC. iTunes default decoding is 256 kbps AAC, and that is also what you get if you purchase music from Apple.

On a side note, there is a lot of dissatisfaction with Apple these days, even with long time users. I love my iMac, but I am using Linux more and more. It is wonderful that my iTunes collection works well with a player like Strawberry. For Mac expatriates moving to Linux, Strawberry could be a good fit. It could also be a nice alternative to iTunes on the Mac platform.

Cheers

@Antihero7038
Here you can download Chromecast Player Premium version for Free.

Visit here - https://blackapks.com/en/tv-cast-pro

High CPU usage on Mac is due to a macOS-specific QT5 problem with the Track/Playlist screen and scrolling/interacting with it when on a high resolution display (such as your Retina screen on your MacBook) - you should find that CPU usage will drop and performance will noticeably improve if you resize your Strawberry window to something very small.

I did have an issue ticket raised on this issue on the Strawberry GitHub page, which was closed as it was deemed to be unresolvable under QT5, and I'm trying to get it reopened/looked at again, now that QT6 has been released (which may have a fix for this CPU usage/performance issue).

@fruity Changing to playbackinfopostpaywall worked for me on Ubuntu 18.04 (bionic) after I installed gstreamer-plugins-bad e.g. sudo apt-get install gstreamer1.0-plugins-bad

Answer from taglib,
Hi Ton,

As far as I know, DSDIFF/DSF was never part of an official TagLib release.

It was merged into master (2018-10-27, d71398c9), but it was later
removed (2019-09-12, 074f30e3) with the commit message

Remove DSF and DSDIFF from master to a feature branch

These can be merged back into master once they're in a more mature state.

@Scott: Can you tell us what exactly were the problems which led to
this removal?

The code still exists in the taglib2 branch. It is not difficult to
include support for a new tag format in a project which is using
TagLib, that code does not have to be part of TagLib, so the
Strawberry Musicplayer could add DSF support to its source code. I did
this myself for https://invent.kde.org/multimedia/kid3/, but I used
another implementation from https://github.com/pekingduck/metadsf
(2015-03-11, 18687eb2), and I had to add a few fixes based on bug
reports from users, so an alternative to the stuff in the taglib2
branch could be the src/plugins/taglibmetadata/taglibext/dsf folder in
the Kid3 sources.

Jonas, was this helpful?

The gap may be inserted during compression/encoding: https://en.wikipedia.org/wiki/Gapless_playback#Compression_artifacts

@fenixfeniks Hi, I am new here & this is my first post.
I use Strawberry on Windows 10.
Can somebody help me getting Tidal to work in Strawberry on Windows 10 Pro.
Software & Drivers fully updated, if that means anything.

@threearmedcow
The rating in Strawberry is from 0.0 to 1.0. A half star is 0.1. So 5 stars would be 1.0.

There are no standardized tags for rating. How the rating are saved to tags depends on the audio file format and the software.
One software can behave one way, and another can behave very differently when it comes to ratings. Another software might use an entirely different tag, and save ratings differently.
So comparing software to see if the rating of stars is read correctly don't always expect to see the same result.

However, when I see you mention some numbers with "192" and "255" I'm only guessing that it could be the POPM tag popularimeter frame for ID3v2 which are not really ratings, but commonly used to store ratings. These are saved by Strawberry too but converted from the rating, 192 should be converted to 0.8 (4 stars), 255 should be 5 stars.
I think it's mostly the same as described by wikipedia. See: https://en.wikipedia.org/wiki/ID3#ID3v2_star_rating_tag_issue
Another software might convert these differently though. So might treat both 192 and 255 as 5 stars. But it's hard for me to answer for another software I have no knowledge of. And you don't even mention what audio file format it is. If you saved the rating with strawberry for both files, I'm not really sure how they could be saved with different values.
Other formats that use Vorbis comments uses very different tags, does not have standardized ratings tag either, and no POPM tag.

For MP3 ID3v2 Strawberry saves a "FMPS_Rating" with the 0.0-1.0 rating too.
I found that Strawberry was writing the FMPS_Rating for MP3 but not reading it back, so it was always converting the POPM tag. Should be fixed now, so if the FMPS_Rating frame exists, it will use that instead of the POPM for rating, which will be more accurate for use in Strawberry. But the database rating will take priority, so if a rating exists in the database for the song, it won't re-read it from the tags.

@jonas I change it and nothing.
Thanks

@jonas I upgraded to 1.0.1 this morning, but I can't see any change. I've rescanned the collection and try to "remove unavailable tracks from playlist", but nothing happens, even if I know that there are hidden tracks there. Do I have to flush the playlist and start over?

where do i put the file

I'm aware of the issue. The shuffle mode is somewhat broken.
Bug report here: https://github.com/strawberrymusicplayer/strawberry/issues/707
I will look more into it at some point.

@jonas Guess I'll have to stick to Clementine.

@jonas
gstreamer 1.20.3 on Arch Linux

@wengels464
I tried the CUE sheet idea with my collection. Didn't work. Seems like strawberry simply won't add DSF files to the library, even if it can read the metadata (which, at least on my system, it does perfectly if I try playing a tagged DSF file from my file manager).

Maybe there's some trick that I have yet to discover, though. If you have any luck with your own testing, do please post back here!

@jonas
I've always had cover JPGs in the folders (never auto-downloaded), and this is the only app this has happened on! The folder you've directed me to also doesn't have cached covers (I'd already turned off that tickbox), just "strawberry.db".

I can confirm that Cover Manager shows them separately with the correct covers in the big grid, so it really does seem to be the sidebar with albums as the list that has this issue -- see attached image (RSF are the top set of tracks):

Right Said Fred cover on REM.png