You should be able to install it by just double clicking the DMG and drag the Strawberry folder over to "system". It's the same way similar dmg's are installed on macOS.
However we only provide experimental development builds for macOS since we don't have any developers with mac active in the project. You can download here: https://builds.strawberrymusicplayer.org/macos/

Hi.
macOS needs to some special tricks to receive media keys without iTunes receiving them (or maybe another application), we used SPMediaKeyTap for this but it was removed by a contributor. Unfortunately I don't have a mac so I can't look into or fix it.
A developer with macOS needs to fix this, I don't know of anyone.

It depends on what Linux distribution you run on it.
You might need to compile yourself from source unless strawberry is available for arm in their repository.
But it's pretty easy as long as you know what dependencies are required so you have the required development packages installed before you start.
Instructions are here:
openSUSE: https://github.com/strawberrymusicplayer/strawberry/wiki/Compiling-on-openSUSE
Fedora: https://github.com/strawberrymusicplayer/strawberry/wiki/Compiling-on-Fedora
Debian: https://github.com/strawberrymusicplayer/strawberry/wiki/Compiling-on-Debian
Ubuntu: https://github.com/strawberrymusicplayer/strawberry/wiki/Compiling-on-Ubuntu
Arch: https://github.com/strawberrymusicplayer/strawberry/wiki/Compiling-on-Arch

Most of the other Debian based distros should work with either the debian or ubuntu guide.

Then it looks like it stops on a directory level before it parses any files. It will skip any directory that is hidden, or has files named ".nomedia" or ".nomusic". Other than that, it's hard to tell what could be wrong. It's working for everyone else, so it must be something to do with your directory. Try a different directory.

This should be fixed in the newst builds: https://builds.strawberrymusicplayer.org/ and the next release.

@chrisc
Only audio files will be filtered.
You need to mount the NAS to a mountpoint.

@yelpspoon
Run strawberry from the terminal to see any output. Open a terminal and type:

/Applications/strawberry.app/Contents/MacOS/strawberry

Check that strawberry is enabled/allowed in the accessibility system settings.

@yahyah24
Could be unsupported audio filetypes.
It will also skip any directory that is hidden (.dot), or has files named ".nomedia" or ".nomusic".

@robyn

Make sure the desktop file is installed, normally it should be:

/usr/share/applications/strawberry.desktop

Make sure that strawberry is installed in PATH, and that it isn't a different version from the one you launch.

sudo find /usr -type f -name 'strawberry'

Make sure the "tidal" URL scheme is correctly registered to strawberry, run the following command in a terminal while strawberry is open:

xdg-open tidal://test

This should add "tidal://test" to the active playlist. If that works, then it means authentication with TIdal should be possible.

If it still doesn't work, then try close firefox and reopen, or set a different web browser as default.

@choobs
There was a bug when organizing songs and moving between different collection directories, it was duplicating the songs in the database. It is fixed now.
https://github.com/strawberrymusicplayer/strawberry/commit/fb634bc2d41d40e55ecfa23dc39094c007b8e621

@llucps I realize it won't work because all the libraries used from homebrew are compiled on Big Sur with no comparability.

@vonpolak Why is it impossible to use? Do the device appear in Tools / Settings / Backend / Device list?

I wonder if I can just build on Big Sur and set CMAKE_OSX_DEPLOYMENT_TARGET to 10.14
https://cmake.org/cmake/help/latest/variable/CMAKE_OSX_DEPLOYMENT_TARGET.html

@llucps
Yeah, that's why I made different releases for each macOS version now.
The only problem with that is that I can no longer update the sparkle updater, since that would update for those that have Big Sur to the Mojave or Catalina builds. But maybe there is a solution for that I'm not a aware of.

@llucps
The tagreader worker issue is fixed. The crash is probably the same as reported in https://forum.strawberrymusicplayer.org/topic/131/strawberry-for-macos-big-sur/3
Maybe some of the core libraries on Catalina and Big Sur are not binary compatible.
I don't have Big Sur to test on.
Does it show a backtrace?