@hogthow said in Tidal account:

@kamilos_x I ran into the same problem with the latest version of the Tidal Android app. I had to uninstall the Tidal android app and load an older version (I used 2.3.7) and it worked fine.

Yes, it looks like something has changed.

In 2.3.7 (from APKMirror) the format is like this:

[REDACTED].0:X-Tidal-Token: [REDACTED/this is the part you need]

While in later versions it is:

[REDACTED].0:vary: x-tidal-sessionid,x-tidal-token,authorization

Anyway, finally got it to work.

I actually notice a problem now with Strawberry and GStreamer 1.18 on Windows where it periodically makes a small "pop" sound (possible jump), not exactly sure what to call it, it occurs circa 4 seconds into the track, but sometimes elsewhere too, similar problem occurs when unpausing consistently each time.
I have only tested with FLAC files, but see that problem only occurs with the FLAC codec, playing the same file works fine using libav codec from within Strawberry. I can't reproduce the problem with gst-launch with either codec.
The problem is gone when downgrading GStreamer to version 1.16.2. So I tried to compile gstreamer using the latest code from git too see if the problem has already been fixed, and the problem appears to be fixed. I can definitely tell it by unpausing. So I'm going to use that until the next stable version of GStreamer is released.
So hopefully this will resolve also the issues reported to by @warbaque and @kaiser_sosai.
The buffering issues are most likely a different problem.

@tibokan
I switched to Qt 6 now. 0.8.5.131 and newer are Qt 6 and should be working: https://builds.strawberrymusicplayer.org/macos
(The ones from yesterday are broken because of a problem deploying plugins after I switched to Qt6)

@jonas Sorry for the delayed response. Just downloaded the newest Catalina version and the covers are all showing up. Fun! Thanks a ton!!

@overcast451 said in Strawberry Crashing Since Last Update:

Updated Strawberry to strawberry-0.8.5-2.136.g87719119.fc32.x86_64.rpm on Fedora 32 (5.10.21-100.fc32.x86_64) - been running all day with no issues!

9 days with zero issues now using the above.

Again, thank you. I've changed my studio around a bit and basically taken this machine off line. I did learn somethings about using the command line and for that I am very appreciative. Don't worry, as the novice I am I'm sure I'll be back at some point.

Keep well and all the best!

@jonas said in upgrade 08.3?:

Check that you have ALSA and PulseAudio as options under Output.
Check that your soundcard is listed under device.
Try specifically selecting ALSA or PulseAudio and the device.

Working perfectly now, thank you enormously 🙂

@jonas Well in my experience all KDE-related theme stuff are generally behaves rather bad in other DEs, especially in gtk-based environment. And breeze is kde default theme, so it applies too, i guess.

But Qt themes not related to KDE usually behave ok everywhere from my experience. I'm personally using QtCurve configured to mimic my gtk3 Adwaita-dark theme under gnome shell, and it looks fine.

Anyway, what im trying to say is, as long as other qt themes work fine, and breeze works in kde, it should probably be fine. Compared to windows, at least.

p.s. Ok there qt6ct actually, but its only present in fedora and arch official repositories, and not others. For most users its as good as not present, as they probably wont bother trying to compile from github.

Strawberry has added compilation tag to the edit tag dialog in the new versions.

@jonas Yes, indeed. Thanks, all compiled just fine and playing nicely now as I write this. So appreciated, thank you again!.

I notice dsun above saying 'I'm running Manjaro ARM on it and Strawberry is in the software repository.' How do we get Raspberry Pi OS to include it too? - Strawberry is so much better than VLC for music. Nicer UI, album covers, remembers playlists etc etc. It would be a real 'plus' for the RPi community.

I'm running a different version of chromaprint which may br causing the issue.

chromaprint-fftw 1.5.0-2.

I can't change that at the moment, but it may be the cause.

Thanks again for the support

@jonas Thanks for the update, that sounds great. I have "Solsbury Hill" so I will use that to verify once the new build is available. I appreciate all of your hard work on creating a great app!

@peterb

Yes, this worked! Thanks!

Also, i believe it imported correctly the "bad" songs 🙂

Sorry @jonas, missed the notification that there's activity here.

Just tested https://builds.strawberrymusicplayer.org/macos/bigsur/strawberry-0.8.4.28.gfcd4e5ac-bigsur.dmg and it seems to work. Thanks!

@Hompacko Thanks

@adityasubathu

The transfer rate from the NAS to the computer is 11 mb/sec
The (Dell) laptop has an SSD, is an i5 and has 16Gb RAM
Since Friday its been "Updating collection"
Running from a terminal window, it gets to 84850 and then stops. JRiver shows there are 86998 tracks
I can play a track if I click on the file name, but cannot create any Smart Playlists

Don't want to keep bothering you with what seems minor problems

@jonas
I can confirm that version: 0.8.5.158.g5256d795-Qt6-x64 is unaffected and the library scan works normally!

Thank you for your work and the quick fix!

I've never tried the KDE connect thing but I'm guessing that it uses MPRIS2 to Strawberry and also have a service running which listens to a port which then function as a received on the computer which again the Android remote connects to.
All such remotes which uses standard MPRIS2 will function with Strawberry.
But they only have basic functionality: https://specifications.freedesktop.org/mpris-spec/latest/
The purpose of having a custom remote specifically for the Strawberry like Clementine does is to manage all features of the player, not just basic play/stop/pause, etc. It won't be compatible with other audio players.

Strawberry will scan every single file in the directory you add to the collection independent of filetype, so make sure you don't have other files than music in the directory.
But to get an idea of what it's doing it could be useful to run it from the terminal like already suggested.

@jonas It sounds like you are saying that the default settings of; Save album covers in album directory and use hash is broken in the case where files are not physically stored in album specific folders. If this is the case, then why bother to use a hash at all? I would have expected that whether using a hash or a pattern, whether stored in the album's (or more accurately file's) directory or located in a hidden directory in the user's home folder, that there is some database that associates a particular physical image file with a particular physical music file.

To do otherwise creates a hidden trap for any user that may choose to store their music files in any structure other than limiting folders to only containing the files of a single album. If someone were to put all of their Goo Goo Dolls files in a folder, or all their songs from the 80's, or as I have done with some of my folders, just collections of completely unrelated music files then Strawberry's current implementation is unable to correctly handle the situation.

thanks again for your work.