UPDATE: This tutorial has been updated for buster installations now
I managed to get MusicIP (headless), sugarcube, and the MusicIP plugin on raspberry pi LMS working with the help of Qemu. This is a inexpensive and simple setup without requiring an intel processor architecture.
For my 25k track collections, a new mix keeps one core of the raspberry pi 4 busy for approximately 2 seconds, while LMS continues to play in the background, thus no issue concerning processing power (in contrast to the old raspberries).
Basically all is working so far. I have not tested validation of music, as all my tracks have been validated and fingerprints archived using the Windows version of MusicIP. Scanning / adding 25k tracks to MusicIP takes approximately 30 minutes
High Level tutorial (I used a Max2Play installation of LMS):
We need to add the i386 architecture:
sudo dpkg --add-architecture i386
You have to edit your /etc/apt/sources.list file and every file in /etc/apt/sources.list.d, adding [arch=armhf] behind each occurence of deb.
So for example the line
deb http://archive.raspbian.org/raspbian buster main contrib non-free
would become
deb [arch=armhf] http://archive.raspbian.org/raspbian buster main contrib non-free
In my case only following two files were modified:
sudo nano /etc/apt/sources.list
sudo nano /etc/apt/sources.list.d/raspi.list
sudo apt-get update
sudo apt-get dist-upgrade
sudo apt-get install qemu binfmt-support qemu-user
The libc6:i386 Deb Package needs to be modified to match the version of its Raspbian equivalent (which has an additional +rpi1)
Check the current libc6 version of the Raspberry: dpkg -s libc6:armhf
Find the equivalent version of the i386 libc Debian package from https://packages.debian.org/buster/i386/libc6 (currently libc6_2.28-10_i386.deb)
Adapt the lines below with the current version:
cd ~
wget http://ftp.us.debian.org/debian/pool...28-10_i386.deb
mkdir -p newpack oldpack/DEBIAN
dpkg-deb -x libc6_2.28-10_i386.deb oldpack/
dpkg-deb -e libc6_2.28-10_i386.deb oldpack/DEBIAN
nano oldpack/DEBIAN/control
Set the version to the Rasbian version (add +rpi1) and remove the dependency of libgcc1 and save the file
rm oldpack/usr/share/doc/libc6/changelog.Debian.gz
nano oldpack/DEBIAN/md5sums
Remove the line with the MD5 Sums for changelog.Debian.gz
dpkg-deb -Z xz -b oldpack/ newpack/
The new package is now in the subfolder newpack, with the name of the new version (e.g. libc6_2.28-10+rpi1_i386.deb)
Install the new package:
sudo dpkg -i newpack/libc6_2.28-10+rpi1_i386.deb
Please note:
If you update the libraries with sudo apt dist-upgrade and a new version of libc6 will have been published in the meantime, the upgrade will fail due to version mismatches.
In this case remove the libc6:i386 version (sudo apt-get purge libc6:i386) re-run the distribution upgrade and then follow the steps of re-packaging and installing the new libc6:i386
Also please note:
If you are using an ubuntu-based OS, the appropriate library might be (at the time of writing): http://de.archive.ubuntu.com/ubuntu/...untu4_i386.deb
Unpack MusicMixer into your home directory (you can download it at https://www.spicefly.com/article.php...sicip-software )
gzip -dc MusicMixer_x86_1.8.tgz | tar -xf
/home/pi/MusicIP/MusicMagicMixer/MusicMagicServer start
ignore warnings about ERROR: ld.so: object '/usr/lib/arm-linux-gnueabihf/libarmmem.so' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored.
It should be accessible via http://localhost:10002/server
/home/pi/MusicIP/MusicMagicMixer/MusicMagicServer stop
You can start the MusicMagic server (in my case installed in the pi home-directory):
/home/pi/MusicIP/MusicMagicMixer/MusicMagicServer start
It should be accessible via http://localhost:10002/server
ignore warnings about ERROR: ld.so: object '/usr/lib/arm-linux-gnueabihf/libarmmem.so' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored, the server runs anyway.
Stop the server via:
/home/pi/MusicIP/MusicMagicMixer/MusicMagicServer stop
Copy mmm.ini from the /home/pi/MusicIP/MusicMagicMixer folder to /home/pi/.MusicMagic/
or download a stripped version from http://spicefly.com/files/mp/mmm.ini to /home/pi/.MusicMagic/
Make it editable:
sudo chmod a+rw /home/pi/.MusicMagic/mmm.ini
edit mmm.ini and adjust the path for the cache, in my case to /home/pi/.MusicMagic/default.m3lib then save the file
Autostart:
To start the sever every time when the raspberry boots:
sudo nano mmserver
Edit the file and add the header for the init daemon, adapt the paths. My version looks like:
------------
#! /bin/sh
### BEGIN INIT INFO
# Provides: mmserver
# Required-Start: $remote_fs $syslog
# Required-Stop: $remote_fs $syslog
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: Start MusicIP daemon at boot time
# Description: Enable service provided by daemon.
### END INIT INFO
# NON-PRIVIELEGED USER TO RUN MUSICMAGICSERVER.
USER=pi
# PATH TO THE MUSICMAGICMIXERSERVER
export MUSICHOME=/home/pi/MusicIP/MusicMagicMixer/
case $1 in
start)
# next line was original
# su - $USER -c $MUSICHOME"MusicMagicServer start & > /dev/null"
sudo -u pi /home/pi/MusicIP/MusicMagicMixer/MusicMagicServer start & > /dev/null 2>&1
echo "Running MusicMagicServer"
exit
;;
stop)
# next line was original
# su - $USER -c $MUSICHOME"MusicMagicServer stop & > /dev/null"
sudo -u pi /home/pi/MusicIP/MusicMagicMixer/MusicMagicServer stop & > /dev/null 2>&1
echo "Stopped MusicMagicServer"
exit
;;
*)
echo "Usage: /etc/rc.d/init.d/mmserver { start | stop }"
exit
;;
esac
--------
sudo cp /home/pi/MusicIP/MusicMagicMixer/mmserver /etc/init.d
cd /etc/init.d
Then register the start script and reboot:
sudo update-rc.d mmserver defaults
sudo reboot
There is a Memory Leak in the Quemu emulation of Music IP and will lead to high memory consumption over few weeks.
Best way is to restart MusicMagic Server due to memory leak ever night, in my case I chose at 4:00.
quick instructions using crontab:
At shell:
crontab -e
Add following lines:
0 4 * * * /home/pi/MusicIP/MusicMagicMixer/mmserver stop
1 4 * * * /home/pi/MusicIP/MusicMagicMixer/mmserver start
save and exit and check if in crontab saved:
crontab -l
Reboot and musicIP should be restarted every night. this way it should consume only single digit percentage of your raspberry pi memory.
Set Timeouts for the LMS MusicIP Plugin to higher values to account for the slow speed of the Raspberry - I386 Emulation:
- shut down LMS
- open plugin/musicip.prefs from your Prefs folder
- add "timeout: 120" to the end
- restart LMS
to use recipes, copy recipes.xml to your/home/.MusicMagic directory
The next steps might be outdated and thus not required unless you run into memory issues:
Also ensure that while scanning new music you set in the LMS GUI settings - preferences - Database Memory Config to "normal", not high or max. Otherwise you might run out of memory or you need to create large swap files to cope with 1-2 GB memory consumption while importing MusicIP info during the scan process.
If you have very large libraries, please update the swap partition and reboot (this is primarily for a Pi with 1 or 2GB, a 4GB pi should be fine without modifications):
sudo nano /etc/dphys-swapfile (change conf_swapsize to desired value-- 4096)
sudo nano /sbin/dphys-swapfile ((change conf_maxswap to desired value -- 4096)
I managed to get MusicIP (headless), sugarcube, and the MusicIP plugin on raspberry pi LMS working with the help of Qemu. This is a inexpensive and simple setup without requiring an intel processor architecture.
For my 25k track collections, a new mix keeps one core of the raspberry pi 4 busy for approximately 2 seconds, while LMS continues to play in the background, thus no issue concerning processing power (in contrast to the old raspberries).
Basically all is working so far. I have not tested validation of music, as all my tracks have been validated and fingerprints archived using the Windows version of MusicIP. Scanning / adding 25k tracks to MusicIP takes approximately 30 minutes
High Level tutorial (I used a Max2Play installation of LMS):
We need to add the i386 architecture:
sudo dpkg --add-architecture i386
You have to edit your /etc/apt/sources.list file and every file in /etc/apt/sources.list.d, adding [arch=armhf] behind each occurence of deb.
So for example the line
deb http://archive.raspbian.org/raspbian buster main contrib non-free
would become
deb [arch=armhf] http://archive.raspbian.org/raspbian buster main contrib non-free
In my case only following two files were modified:
sudo nano /etc/apt/sources.list
sudo nano /etc/apt/sources.list.d/raspi.list
sudo apt-get update
sudo apt-get dist-upgrade
sudo apt-get install qemu binfmt-support qemu-user
The libc6:i386 Deb Package needs to be modified to match the version of its Raspbian equivalent (which has an additional +rpi1)
Check the current libc6 version of the Raspberry: dpkg -s libc6:armhf
Find the equivalent version of the i386 libc Debian package from https://packages.debian.org/buster/i386/libc6 (currently libc6_2.28-10_i386.deb)
Adapt the lines below with the current version:
cd ~
wget http://ftp.us.debian.org/debian/pool...28-10_i386.deb
mkdir -p newpack oldpack/DEBIAN
dpkg-deb -x libc6_2.28-10_i386.deb oldpack/
dpkg-deb -e libc6_2.28-10_i386.deb oldpack/DEBIAN
nano oldpack/DEBIAN/control
Set the version to the Rasbian version (add +rpi1) and remove the dependency of libgcc1 and save the file
rm oldpack/usr/share/doc/libc6/changelog.Debian.gz
nano oldpack/DEBIAN/md5sums
Remove the line with the MD5 Sums for changelog.Debian.gz
dpkg-deb -Z xz -b oldpack/ newpack/
The new package is now in the subfolder newpack, with the name of the new version (e.g. libc6_2.28-10+rpi1_i386.deb)
Install the new package:
sudo dpkg -i newpack/libc6_2.28-10+rpi1_i386.deb
Please note:
If you update the libraries with sudo apt dist-upgrade and a new version of libc6 will have been published in the meantime, the upgrade will fail due to version mismatches.
In this case remove the libc6:i386 version (sudo apt-get purge libc6:i386) re-run the distribution upgrade and then follow the steps of re-packaging and installing the new libc6:i386
Also please note:
If you are using an ubuntu-based OS, the appropriate library might be (at the time of writing): http://de.archive.ubuntu.com/ubuntu/...untu4_i386.deb
Unpack MusicMixer into your home directory (you can download it at https://www.spicefly.com/article.php...sicip-software )
gzip -dc MusicMixer_x86_1.8.tgz | tar -xf
/home/pi/MusicIP/MusicMagicMixer/MusicMagicServer start
ignore warnings about ERROR: ld.so: object '/usr/lib/arm-linux-gnueabihf/libarmmem.so' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored.
It should be accessible via http://localhost:10002/server
/home/pi/MusicIP/MusicMagicMixer/MusicMagicServer stop
You can start the MusicMagic server (in my case installed in the pi home-directory):
/home/pi/MusicIP/MusicMagicMixer/MusicMagicServer start
It should be accessible via http://localhost:10002/server
ignore warnings about ERROR: ld.so: object '/usr/lib/arm-linux-gnueabihf/libarmmem.so' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored, the server runs anyway.
Stop the server via:
/home/pi/MusicIP/MusicMagicMixer/MusicMagicServer stop
Copy mmm.ini from the /home/pi/MusicIP/MusicMagicMixer folder to /home/pi/.MusicMagic/
or download a stripped version from http://spicefly.com/files/mp/mmm.ini to /home/pi/.MusicMagic/
Make it editable:
sudo chmod a+rw /home/pi/.MusicMagic/mmm.ini
edit mmm.ini and adjust the path for the cache, in my case to /home/pi/.MusicMagic/default.m3lib then save the file
Autostart:
To start the sever every time when the raspberry boots:
sudo nano mmserver
Edit the file and add the header for the init daemon, adapt the paths. My version looks like:
------------
#! /bin/sh
### BEGIN INIT INFO
# Provides: mmserver
# Required-Start: $remote_fs $syslog
# Required-Stop: $remote_fs $syslog
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: Start MusicIP daemon at boot time
# Description: Enable service provided by daemon.
### END INIT INFO
# NON-PRIVIELEGED USER TO RUN MUSICMAGICSERVER.
USER=pi
# PATH TO THE MUSICMAGICMIXERSERVER
export MUSICHOME=/home/pi/MusicIP/MusicMagicMixer/
case $1 in
start)
# next line was original
# su - $USER -c $MUSICHOME"MusicMagicServer start & > /dev/null"
sudo -u pi /home/pi/MusicIP/MusicMagicMixer/MusicMagicServer start & > /dev/null 2>&1
echo "Running MusicMagicServer"
exit
;;
stop)
# next line was original
# su - $USER -c $MUSICHOME"MusicMagicServer stop & > /dev/null"
sudo -u pi /home/pi/MusicIP/MusicMagicMixer/MusicMagicServer stop & > /dev/null 2>&1
echo "Stopped MusicMagicServer"
exit
;;
*)
echo "Usage: /etc/rc.d/init.d/mmserver { start | stop }"
exit
;;
esac
--------
sudo cp /home/pi/MusicIP/MusicMagicMixer/mmserver /etc/init.d
cd /etc/init.d
Then register the start script and reboot:
sudo update-rc.d mmserver defaults
sudo reboot
There is a Memory Leak in the Quemu emulation of Music IP and will lead to high memory consumption over few weeks.
Best way is to restart MusicMagic Server due to memory leak ever night, in my case I chose at 4:00.
quick instructions using crontab:
At shell:
crontab -e
Add following lines:
0 4 * * * /home/pi/MusicIP/MusicMagicMixer/mmserver stop
1 4 * * * /home/pi/MusicIP/MusicMagicMixer/mmserver start
save and exit and check if in crontab saved:
crontab -l
Reboot and musicIP should be restarted every night. this way it should consume only single digit percentage of your raspberry pi memory.
Set Timeouts for the LMS MusicIP Plugin to higher values to account for the slow speed of the Raspberry - I386 Emulation:
- shut down LMS
- open plugin/musicip.prefs from your Prefs folder
- add "timeout: 120" to the end
- restart LMS
to use recipes, copy recipes.xml to your/home/.MusicMagic directory
The next steps might be outdated and thus not required unless you run into memory issues:
Also ensure that while scanning new music you set in the LMS GUI settings - preferences - Database Memory Config to "normal", not high or max. Otherwise you might run out of memory or you need to create large swap files to cope with 1-2 GB memory consumption while importing MusicIP info during the scan process.
If you have very large libraries, please update the swap partition and reboot (this is primarily for a Pi with 1 or 2GB, a 4GB pi should be fine without modifications):
sudo nano /etc/dphys-swapfile (change conf_swapsize to desired value-- 4096)
sudo nano /sbin/dphys-swapfile ((change conf_maxswap to desired value -- 4096)
Comment