![[Home]](/images/oinklogo.png)
SSODS F.A.Q.
Under construction, never finished and probably always outdated.
Coming sooner or later.
Go here for the old SSODS 3.x FAQ.
On TurboStations:
dbsource: dbi:mysql:database=slimserver:host=localhost:port=3306:mysql_socket=/tmp/mysql.sock
On DiskStations: don’t know, but probably something similar to the above
In SBS: go to Server Settings → Advanced → Performance and set «Artwork Resampling» to «Resize Artwork».
SSODS comes with all binary Perl modules required by SBS. This is because the ones shipped with SBS may or may not work on your system. SSODS deactivates all the binary Perl modules in SBS ($SSDIR/CPAN/...). If you want to use a module that is shipped with SBS you need to tell SSODS. E.g. for Audio::Scan you would do (untested..):
mv /opt/ssods4/var/home/SqueezeboxServer/CPAN/Audio/Scan.pm-SSODS-off /opt/ssods4/var/home/SqueezeboxServer/CPAN/Audio/Scan.pm touch /opt/ssods4/var/home/SqueezeboxServer/CPAN/Audio/Scan.pm-SSODS-ignore mv /opt/ssods4/var/home/SqueezeboxServer/CPAN/arch/5.10/arm-linux-gnueabi-thread-multi/auto/Audio/Scan/Scan.so-SSODS-off /opt/ssods4/var/home/SqueezeboxServer/CPAN/arch/5.10/arm-linux-gnueabi-thread-multi/auto/Audio/Scan/Scan.so touch /opt/ssods4/var/home/SqueezeboxServer/CPAN/arch/5.10/arm-linux-gnueabi-thread-multi/auto/Audio/Scan/Scan.so-SSODS-ignore
SSODS renames all relevant files to *-SSODS-off. If you create an empty *-SSODS-ignore file SSODS will ignore this particular file. You also need to rename the xy-SSODS-off to xy. You need to do this with all files that are included in the module in question. See /opt/ssods4/share/sbs/shipped-binaries for hints (you can also delete the relevant lines in there and re-install the SBS tar ball) . Note that you have to replace arm-linux-gnueabi-thread-multi with the directory that corresponds to your system (arm-linux-gnueabi-thread-multi for the arm version of SSODS, powerpc-linux-thread-multi for the ppc version of SSODS and i386-linux-thread-multi for the i686 version of SSODS).
Recent (development?) SBS versions use the Linux::Inotify2 Perl module to monitor the music library directories for changes. This allows SBS to detect newly added files and to initiate a scan of these files automatically.
SSODS does not include this module. This is because SSODS is built to run on different systems, which may or may not have the inotify functionality in the Linux kernel.
The «My Music → Browse Music Folder» is a work-around to add a new album to the database without triggering a rescan of the whole library. Browse to the newly added album and add it to the playlist, which will run the scanner program on this directory, which will add the files to the library.
SSODS does not include mplayer (anymore). SSODS is built with a minimal approach. It’s meant to be used with «normal» music files (i.e. mp3, flac, ogg) and hardware players (SB3, Radio, Boom, Transporter). This may break the ability to play certain exotic music formats for some users. My recommendation in this case: convert the files to mp3.
It is, however, possible to use mplayer obtained from another source (Optware, compiled yourself, ..) with SBS in SSODS. To do so SBS must be able to find the mplayer binary. It looks in /opt/ssods4/bin for external programs. Hence, you need to copy or link the binary to that path. E.g.:
ln -s /path/to/mplayer /opt/ssods4/bin
Plenty. Among them:
If you set a SSODS web interface password only the first 8 characters of the password are actually used. E.g. if you enter «1234567890» as the password only «12345678» is actually used. You wouldn’t usually notice this because this happens when setting the password and also when entering the password to access the page. Never mind. 8 characters should be enough to protect SSODS. :)