34
34
under Linux. Find libusb here:
36
36
Debian: apt-get install libusb0
37
apt-get install libusb-dev
39
libnjb is not included in the Debian
40
distribution, you have to build it from
41
source! For the moment you'll have to
42
download the CVS version and install it
43
(only the CVS version is reliable as
46
apt-get install libnjb0
47
apt-get install libnjb-dev
49
will soon be available.
51
RedHat: An RPM package of libusb is included in the
52
RedHat distribution. New versions are available
53
at RawHide (RedHat beta). It is installed by
37
apt-get install libusb0-dev
39
libnjb is now included in the Debian
40
distribution. You might need a newer
41
library revision (subsitute the "0"
42
for something higher).
44
apt-get install libnjb4
45
apt-get install libnjb4-dev
47
should be available, and you may need later
48
interface revision numbers (substitute the
49
"4" for something higher).
51
Notice that Debian also carries gnomad2 so
52
why bother installing libnjb separately...
54
Red Hat / Fedora Core: An RPM package of libusb is
55
included in the Red Hat / Fedora Core
56
distribution. (New versions are available
57
at RawHide (beta)). It is installed by
54
58
default, you don't have to do anything about it.
56
60
The Gnomad2 RPM package includes statically
57
linked libnjb and id3lib. You need not install
61
linked libnjb and libid3tag. You need not install
58
62
either, just smack in the Gnomad2 RPM.
61
4. Gnomad2 also requires the library id3tag to build.
64
SuSE: Use YaST to satisfy the dependencies. You need
65
atleast the following packages unless you already
71
Most users will prefer to install libnjb and gnomad2
75
4. Gnomad2 also requires the library libid3tag to build.
63
77
NOTE: Gnomad has switched from using id3lib to using
64
78
libid3tag produced by the libmad project. This
65
library is used by e.g. gtkpod and the gstreamer
66
project use id3tag instead of id3lib. These two
67
libraries are confused all the time, so please
79
latter library is used by e.g. gtkpod and the
80
gstreamer project use id3tag instead of id3lib.
81
These two libraries are confused all the time, so
70
84
Get it here: http://sourceforge.net/projects/mad/
71
85
http://sourceforge.net/project/showfiles.php?group_id=12349
73
FIXME: update info below.
75
Debian: apt-get install libid3
76
apt-get install libid3-dev
77
NOTE: do NOT install libid3tag0!!
79
RedHat: The RPM of Gnomad2 already includes a
80
statically linked version of id3tag library.
81
You do not need to install it to install
87
Debian: apt-get install libid3tag0
88
apt-get install libid3tag0-dev
89
The versions from testing (upcoming Debian 4.0)
90
are needed for gnomad2 to work.
92
Red Hat/Fedora Core: The RPM of Gnomad2 now requires that
93
you have the libnjb RPM installed too.
84
95
If you want to compile from sources:
85
You may as well build the id3lib from source
86
as most RPMs seem unreliable on RedHat 8.0 and
87
upwards. Communicate with the id3lib project
88
and download their tarballs/use their
96
You may as well build the libid3tag from source,
97
but nice RPMs exist at livna and freshrpms.
98
See the Fedora FAQ (http://www.fedorafaq.org/)
92
101
5. Install gnomad using this sequence:
204
213
Gnomad will always try everything it can to retrieve
207
* first it reads the ID3 info (on MP3 files)
216
* first it reads the ID3 info (on MP3 files) or WMA
217
ASF metadata (on WMA files)
208
218
* next it looks at the filename path to determine
209
219
probable metadata
210
220
* if this fails it will use the string <unknown>
212
There is yet no logic to read WMA metadata. Don't
213
use WMA. Mail Creative and tell them to include
222
Don't use WMA. Mail Creative and tell them to include
214
223
support for Ogg Vorbis instead.
216
225
When transferring files from harddisk to jukebox,
218
227
the view on the right. If some part of it is missing
219
228
after a rescan, that's a bug.
221
7. Q: But how do I...
230
7. Q: If I set Gnomad2 to open a 2900 song music dir, it takes
231
12 minutes to open. If I open it up in another directory,
232
it starts in seconds. If I then change to my 2900 songs,
233
I have to wait 12 minutes again. Is this normal?
235
A: Sadly yes. This is because the MP3 and the associated
236
ID3 tag format gives no good way of [quickly] determining
237
the length of the songs, so this info has to be retrieved
238
from the file anew on every scan. I have evangelized the
239
use of ID3v2:s "TLEN" tag, which makes it possible to tag
240
a file with its playlength, so that gnomad and others don't
241
need to go to such extreme measures to find out how long
242
(in time) they are. Look into the file "mp3file.c" for
245
I might add a "progress" dialog and cancel function though,
246
so one know what is happening...
248
8. Q: But how do I...
223
250
A: Hey! did you try selecting something and clicking the
224
251
right mousebutton? Different popups may appear
225
252
depending on what is selected. Notably in the playlist.
227
8. Q: Sometimes the graphics freeze for example when I delete
254
9. Q: Sometimes the graphics freeze for example when I delete
228
255
some files on the jukebox.
230
257
A: OK so Gnomad2 is not 100% multi-threaded. Might fix it
231
258
someday when everything that is more important has been
232
259
fixed. Sit back and enjoy the show.
234
9. Q: Gnomad2 seqfaulted/crashed on me!
261
10.Q: Gnomad2 seqfaulted/crashed on me!
236
263
A: OK so neither Gnomad2 nor the libnjb, libusb or id3lib
237
264
are entirely stable. Please start up you GDB and help
259
286
errors (and this happens from time to time) may be either
260
287
in libnjb (unlikely) libusb (more likely) or the kernel
261
288
of your operating system (also very likely).
290
11.Q: The beginning of some songs are clipped off!
292
A: I've seen people using MP3 files with bad tags. For example
295
49 44 33 03 00 00 00 02 1d 65 ...
297
The first three bytes represent the letters are "ID3" which
298
says this is a ID3v2 tagged file. Next some flags, then the
299
value 00021d65, which is supposed to be the length of the tag.
301
However 21d65 is *not* the length of the tag so the tag is
302
corrupt. If I try to remove the tag by stripping these bytes,
303
I remove parts of the song. The problem is with the tag software
304
used for this file which has produced a bad tag.
306
There are two ways to solve this:
310
2. Switch off the option "remove all ID3 tags from files
311
transfered to the jukebox" in the Gnomad2 preferences tab.