Some of the utilities available in Puppy have for a number of years relied on the "freedb.org" database for cddb information.
eg such programs as Asunder, pCD, pMusic etc use cddb online information for identifying CD contents such as artist, album name, album art, track name etc.
Earlier this year the freedb.org host for this database went offline.
fredx181 recently suggested that there is a replacement database available at gnudb.org
So if your ripping or music cataloging utility seems to be unable to collect online information, or hangs for a period of time waiting to access a database that is no longer there - you may simply need to let that utility know that the cddb server has changed it's name from
freedb.freedb.org
to:
gnudb.gnudb.org
(port remains at 8880)
For Asunder this can be entered manually using the preferences/advanced tab. (And/or can be stored in the Asunder config file if you run persistence like a savefile)
But for pCD - and probably some other puppy utilities that use the cdda2wav utility a different approach is needed.
It is necessary to pass a runtime parameter string to cdda2wav
If you call cdda2wav directly then the method is to add the runtime parameter -cddbp-server=gnudb.gnudb.org to enable cdda2wav to contact the correct cddb server database.
Here is an example that tells cdda2wav to contact gnudb and rip first track from drive /dev/sr0
Code: Select all
root# cdda2wav dev=/dev/sr0 cddb=0 -cddbp-server=gnudb.gnudb.orgAny utility relying on cdda2wav may need this edited into it's code.
(For pCD it is currently necessary to modify one line in the code as shown here)
However it could be beneficial to force a permanent change to cdda2wav so that any utilities calling the cdda2wav functions will automatically be redirected to the new database. (Maybe newer puppies already have this change but not sure...)
I checked with Heiko Eißfeldt (who along with Jörg Schilling developed cdda2wav) and he has said that there are two ways to best deal with this.
Here is his reply (option 2 may be easiest):
The good news: In the current version 3.02a10 gnudb is already hard coded.
1. (assuming you have the compilation tool chain and know how to build
cdda2wav)You can get the latest sources here as part of the schilytools package:
https://sourceforge.net/projects/schilytools/files/.
Download, extract, and type "make" in the main directory. You should
find cdda2wav
in the cdda2wav/OBJ/.../ subdirectory afterwards.This method should be a non brainer.
Or if you have already source files and want to change the hard coded
setting in your version yourself,
you should edit file local.cnf.in in the cdda2wav directory and search
for a line with
CDDB_SERVERHOST=...Edit and recompile (call make). This method replaces the outdated hard
coded settings.
The binary should then be found in the sub directory OBJ/.../.==
2. If you don't can or want to recompile cdda2wav, there are two methods
(one you have already used with command line parameters).
But there is also support for two environment variables to override the
hard coded settings.
If you (permanently) set
CDDBP_SERVER="gnudb.gnudb.org"
CDDBP_PORT=8880
cdda2wav uses values from these env vars instead of the hard coded ones.
So here there is no need
to recompile and to supply any extra command line parameters.This could be done in your ~/.bashrc file, for example. Add something
like this:
CDDBP_SERVER="gnudb.gnudb.org"
CDDBP_PORT=8880
export CDDBP_SERVER
export CDDBP_PORTGood luck and Happy Christmas to you,
Heiko
So this gives some options for users who are experiencing startup delays with audio and ripping utilities in Puppy