I wrote a piece detailing my set-up procedure awhile back with some updates:Hope this helps some folks out...Arch
Thanks for this informative set-up procedure. I have set up LMS on a RPi 3B+ and it is working well with a large USB drive. The motivating goal has been to implement BrutefirDrc in the LMS feed. I am not sure it is working, though I see no specific errors in the log file. The filter configuration files, when tested separately with brutefir on the command line, do not cause errors and 'filtering begins now'. This spawns multiple processes, visible via 'top'. However, when LMS is running I can see no instance of brutefir processes using 'htop'. Even though *I think* I hear the results of the filters in the music stream, it would be nice to confirm that brutefirDRC is running correctly! CPU usage is suspiciously light - about 5% on one core @ 44.1kHz. I am using a recent LMS nightly of 7.9.2, and am using filters generated in rePhase. I have tried both LPCM.wav and text formats for the filters within the bruteFIR configuration files. ...same behavior for each.Any suggestions would be greatly appreciated! Thanks in advance!
pi@raspberrypi:/ $ ls -l /etc/squeezeboxserver/BrutefirDrc/settings
total 28
-rwxr--r-- 1 root root 2763 Feb 16 00:18 DRC-176400.txt
-rwxr--r-- 1 root root 2763 Feb 16 00:18 DRC-192000.txt
-rwxr--r-- 1 root root 2768 Feb 16 16:55 DRC-44100.txt
-rwxr--r-- 1 root root 2760 Feb 16 00:18 DRC-48000.txt
-rwxr--r-- 1 root root 2760 Feb 16 00:18 DRC-88200.txt
-rwxr--r-- 1 root root 2759 Feb 16 00:18 DRC-96000.txt
lrwxrwxrwx 1 squeezeboxserver nogroup 13 Feb 15 23:27 filter-6c_ec_eb_67_6f_9f -> DRC-44100.txt
-rw-r--r-- 1 squeezeboxserver nogroup 3330 Mar 5 08:30 wisdom
I imagine that root is a problem, so I've tried other possibilities...
TIA,
Frank
--
You received this message because you are subscribed to the Google Groups "BrutefirDRC" group.
To unsubscribe from this group and stop receiving emails from it, send an email to brutefirdrc...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
pi@raspberrypi:/ $ ps xa | grep brutefir
771 pts/0 S+ 0:00 grep --color=auto brute fir
In all other respects LMS seems to be working normally so I suspect my own understanding and not Raspbian, or some technical/system issue.
I do see something I don't understand on the LMS plugin configuration page under the 'advanced' tab for BturefirDrc. For the 'BruteFIR filter link directory' I have "/etc/squeezeboxserver/BrutefirDrc/settings". (correct directory, I hope!) OK, there is a small information pop-up associated with that input and the popup says:
"The absolute path to the directory where the filters configured for each player can be saved to. It is the plugins working directory. If a filter is changed for a player a file for the player referencing the new filter will be created in this directory. Make sure that the directory exists and is writeable by the SqueezeCenter user. Files in this directory are overwritten without warning! If you want to be absolutely safe create a directory only for this purpose. If this directory is changed you have to enable DRC again for any player via the remote control (yes it states that it is enabled you have to do it nevertheless, after enabling it you need to restart SqueezeCenter)."
That folder (.../BrutefirDrc/settings) is now at 777. But what is the process of 'enabling DRC via the remote control'? What/where is this 'remote control' the popup is referencing? I'm playing LMS output through squeezelite 1.8 on a BBB with LMS control using either a) http to the :9000 port at my players IP address, or b) the iOS program iPeng. Using the :9000 port I see two things to 'enable': a) BrutefirDrc is checked in the 'active plugins' group under the 'plugins' tab, and b) under the tab 'Player->Squeezelite->Brutefir room correction' I see Template = FLAC and Filter = DRC-44100.txt. These are the only controls I know about to 'enable DRC'. If there is another control interface somewhere, that would be good to know about! ;-P
I'm hoping my problem is something almost silly. But like all software problems, trivial and profound problems are equally important until the program works!
TIA, again!
Frank
I had no idea that so much was going on behind the scenes, and that you had to disable file conversion pathways to make the BruteFIR wrapper the default for FLACs. Also, I didn't realize that you can't convert some file types to FLAC and then have them sent to the BruteFIR wrapper.