push!
many audio tracks are too slow...

with the mixxx audio player
i can timestretch to a specific BPM value

somehow i like multiples of 12 BPM...

examples:

156 BPM = 13 x 12 BPM
https://soundcloud.com/mila-nautikus/distance-new-outlook-156bpm

96 BPM = 8 x 12 BPM
https://soundcloud.com/mila-nautikus/the-dust-brothers-this-is-your-life-with-intro-96bpm
https://soundcloud.com/mila-nautikus/die-toten-hosen-unsterblich-96bpm

84 BPM = 7 x 12 BPM
https://soundcloud.com/mila-nautikus/scars-on-broadway-they-say-its-all-about-to-end-84bpm
https://soundcloud.com/mila-nautikus/snak-the-ripper-nothing-lasts-forever-84bpm
https://soundcloud.com/mila-nautikus/rakede-sonne-84bpm

72 BPM = 6 x 12 BPM
https://soundcloud.com/mila-nautikus/kummer-schiff-72bpm

@jonas after a reinstall it is now working, just rightclicking the progression bar
thanks for your help/your replies

@uberblatt
There is, if you go to tools / "Update changed collection folders"

@appson
It was an issue with the flatpak runtime, it should be fixed if you do an update.

@Kisequé
It doesn't support multi-tags. It might be something we can implement at some point, but it's a huge job.

@materpris23
The desktop file has been renamed since the previous reply, normally should be /usr/share/applications/org.strawberrymusicplayer.strawberry.desktop

Maybe there is an issue with Tidal authentication when using flatpak, try a native package.

@Devilishly_Jaded
You can't use a client ID from https://developer.tidal.com/dashboard, if that's what you've tried, that's not compatible. You need to use a client ID from a registered application that Tidal allow to get stream URL's without unencrypted.

@breversa
Tagging using inline editing in the playlist for files outside the library was broken, I've just fixed it.
If you are on linux you can try the latest from https://builds.strawberrymusicplayer.org/

Just tested and it seems to be working again in Linux Mint.

@jonas the tidal://test pops up but still wont work, goes to tidal then there error screen

@jonas Apparently it was fixed by yesterday's GNOME/KDE update.

@silver-sun Well, if anything, it means it'll be worthwhile for me to downgrade to a previous version until this gets a fix.
It's such an odd omission.