When the filter processor runs, it writes information into a file , which you can find in the InguzEQ folder.
- On Windows, this is in .
- On Windows Vista, this is in .
- On linux, this is in .
You can read this log file with a text editor. On linux and Mac systems, you can use in a terminal window, to see updates as they happen.
No updates in the log?
If you play music but there are no updates in the log file, first check that the SlimServer “file types” are selected properly (see the installation instructions for details).
On linux and Mac systems, check the log file permissions: it should be writeable by “everyone”. In a terminal, you can set this by .
On linux and Mac systems, check for a file “error” in /usr/share/InguzEQ. This may contain useful information if InguzDSP cannot run (for example, because of an incompatible Mono install).
A typical log
For each track played, you should see a series of lines in the log, like this:
20070104235906: InguzDSP (version 0.9.12) -wav -d 24 -id 00:04:20:10:01:ae -r 44100
20070104235906: 00:04:20:10:01:ae This evaluation version will expire 6/1/2007 12:00:00 AM
20070104235906: 00:04:20:10:01:ae Gain -16 dB
20070104235906: 00:04:20:10:01:ae Impulse Impulses\Normal.wav, matrix MatrixImpulses\Space.wav
20070104235906: 00:04:20:10:01:ae EQ00323806D3
20070104235907: 00:04:20:10:01:ae 16/44100 PCM => 24/44100 PCM TRIANGULAR, gain -16 dB
20070104235921: 00:04:20:10:01:ae 232:The pipe is being closed
20070104235921: 00:04:20:10:01:ae 1802240 samples, 14609.375 ms, 2.7379679144385 * realtime, peak -6.6932641448126 dBfs
The number at the start of each line is a timestamp: in this case, 2007-01-04 (January 4th), 23:59:06. The “00:04:20:10:01:ae” which follows the timestamp is the ID of your Squeezebox (its MAC address).
In normal use, you’ll also occasionally see series of log lines such as this:
20070105000200: 00:04:20:10:01:ae Configuration changed
20070105000200: 00:04:20:10:01:ae Configuration changed
20070105000200: 00:04:20:10:01:ae Impulse Impulses\Normal.wav, matrix MatrixImpulses\Space.wav
20070105000200: 00:04:20:10:01:ae EQ005215B387
A sequence like this is logged each time you change the equalizer settings using the remote control.
Clipping!
Clipping is when the digital signal gets too large: the signal’s too loud, and the only way for the filter processor to handle these is to clip off the peaks (and then reduce the volume a little). If clipping happens, you will see messages in the log such as this:
20070108225053: 00:04:20:10:01:ae CLIPPING+
20070108225058: 00:04:20:10:01:ae CLIPPING-
It may be OK to see one or two clipping messages, but if you see lots — more than a couple in an hour’s listening, for example — then you’ll need to decrease the filter processor’s gain control.
Too quiet?
Depending on your setup, you might find you have the opposite problem: the signal is way too quiet. This doesn’t produce log messages like clipping does. Instead: take a look at the last line from the log above:
20070104235921: 00:04:20:10:01:ae 1802240 samples, 14609.375 ms, 2.7379679144385 * realtime, peak -6.6932641448126 dBfs
The “peak” value here means: during this track, the loudest signal was about 6.7 decibels below full-scale. (These numbers should always be negative. Zero decibels is as loud as the signal could possibly get; anything more is clipping).
Watch this peak value as you play a mixture of different types of music. If the peak value never goes above, say, -9dBfs, then you have lots of room to increase the processor’s gain control.
Other error messages
Other error messages are usually just that: errors. Please send us email!
