Jaikoz- Discussion Forum

I see this issue, too.
This is under Gentoo Linux with all latest updates and Sun's VM 1.5.0_11.

Examples: Code:

 [Fatal Error] :-1:-1: Premature end of file.
 21/06/2007 19.41.12:WARNING: Unable to create Puid for:29:null
 [Fatal Error] :-1:-1: Premature end of file.
 21/06/2007 19.45.07:WARNING: Unable to create Puid for:95:null
 [Fatal Error] :-1:-1: Premature end of file.
 21/06/2007 19.45.56:WARNING: Unable to create Puid for:112:null
 [Fatal Error] :-1:-1: Premature end of file.
 21/06/2007 19.46.32:WARNING: Unable to create Puid for:127:null
 [Fatal Error] :-1:-1: Premature end of file.
 21/06/2007 19.46.45:WARNING: Unable to create Puid for:132:null
 [Fatal Error] :-1:-1: Premature end of file.

I have uploaded all log files (userlog, debuglog and part of the console output) here.

I was wondering why so many characters are removed during the local auto correct? It says somewhere this improves the matching, but I don't understand that.

Take for instance the Radiohead album "OK Computer". It has a song titled "Exit Music (For a Film)". If you remove the parenthesis from the title, but the parenthesis ARE present in the Musicbrainz DB, wouldn't the matching be made more difficult?

Same goes for characters like single quotes, double quotes, slashes, ...

I know this can be completely customized or turned off, but I was wondering why this was done in the first place?

I thought you would want to preserve as much as possible of the ID3 tag present, only removing illegal/undisplayable characters, sending that off to match with Musicbrainz, save the found data in the ID3 tag, and form a filename from it, only replacing illegal filesystem characters like '?' with a space, underscore, or nothing...

I think I have found the (or at least part of the) problem.

Using Wireshark I found out that genpuid always tries to connect to the MusicIP server through port 10001 first. When that fails, it uses port 80 as a fallback. Port 10001 is blocked here, port 80 isn't. So it has to wait for a timeout on the connect to port 10001 before it falls back to port 80.

And since Jaikoz starts genpuid over for each song, it needs to wait for the timeout for each song. When using genpuid in recursive mode (-r), the timeout only occurs once.

I don't have the router password to unblock this, however, and the guy who does is on holiday :s

At least now we know what causes this

When I've loaded a couple thousand songs in Jaikoz, and I start the acoustic analysis on them, I expect it to use most of my CPU cycles. After all, the decoding of an MP3, the mathematical analysis of it, etc. are all very CPU intensive tasks. However, when I monitor the CPU usage, it is only around 20% most of the time, with 1 spike of 80+% per song analysed.

This is odd, isn't it? Shouldn't it just use the maximum CPU power available and make analysis faster? I know that it also sends and receives data, but that should not prevent it from using, on average, more CPU time, right?

Acoustic analysis takes about 25 seconds per song on my PC.

Could this be a problem with settings, and/or the genpuid program, and/or is there anything I can do to speed things up? Is the time (~25s/song) normal?

Like the topic title says, I'd like it if the bit rate, length (of the audio, like mm:ss) and file size are available as columns in Jaikoz's table. This would make it a lot easier to decide which one of duplicate files you'd like to keep.

It could be even more easy if there was another action that handles duplicates automatically. Its settings could look like this:
"If the musicIP ID/musicbrainz ID is the same, keep the one with the largest/smallest bitrate/filesize/duration.
If the criterium above is equal, keep the one with the largest/smallest bitrate/filesize/duration.
If the criterium above is equal, keep the one with the largest/smallest bitrate/filesize/duration.
If the criterium above is equal, ask me which one to keep/ignore this duplicate/call the Java police."