Latest posts for the topic "Unable to retrieve acoustic ids"

Unable to retrieve acoustic ids

Anonymous — GMT

Hi, I'm running jaikoz on linux and have the following issue: When I try to retrieve accoustic IDs, I get the following kind of messages: Feb 8, 2007 4:55:18 PM: WARNING: Unable to retrieve an acoustic id for /home/me/music/Jethro Tull/This Was/02- Jethro Tull - Some Day The Sun Won't Shine For You.mp3 because this track cannot be analysed Feb 8, 2007 4:55:34 PM: INFO: Retrieved 0 acoustic ids successfully

Re:Unable to retrieve acoustic ids

paultaylor — GMT

Is this happening for every track ,or just the occasional one. Could you send your log files to support at jthink dot net so that I can investigate.

Re:Unable to retrieve acoustic ids

Anonymous — GMT

I am on the trial version, and I am having the same problem. I am running Mac OS X. I will send the log files.

Re:Unable to retrieve acoustic ids

paultaylor — GMT

The linux 1.5 version uses a new version of the Get AcousticId program which is much more accurate, I think this would fix the original posters problem. For OSX this new version of the Get Acoustic Id program is not availble yet, but should be very soon.

Still getting this error

jayekub — GMT

I am using a licensed copy of 1.5.0 on Linux and I'm still getting message with almost every mp3 file I've tried it on. Is there any way to get more verbose output so I can find out what it is that's wrong with my files? All these files load and play fine in every other program I've tried them with...

Re:Unable to retrieve acoustic ids

paultaylor — GMT

I'm suprised you our still not having much luck. Jaikoz v1.5 performs much better for Linux than v1.4.1, however I don't think it is still quite as accurate as the Windows version, but unfortunately the code for generating acoustic ids is not written by me, but provided by MusicIP so i dont know the full details of the differences, I have asked MusicIP if they can give me any more information on the differences. Could you try running Jaikoz on Windows against these files as a test/workaround ? Paul

Re:Unable to retrieve acoustic ids

Anonymous — GMT

I'm getting the same error with jaikoz 1.6.1 (full license) on Suse 10.1. When retrieving acoustic IDs for just about any song, the console displays Code:

WARNING: Unable to retreive an acoustic id for 
INFO: Retrieved 0 acoustic ids successfully
INFO: Completed retrieval of Acoustic Ids for 1 files

The terminal screen says: Code:

[Fatal Error] :-1:-1: Premature end of file.
08/04/2007 00.48.19:WARNING: Unable to create Puid for:0:null

Interestingly, if I manually run genpuid on these files (with an anonymous key from musicip), many of them do in fact return a puid. Which leads me to believe the problem is with jaikoz. Any ideas?

Re:Unable to retrieve acoustic ids

paultaylor — GMT

Anonymous wrote:

I'm getting the same error with jaikoz 1.6.1 [Fatal Error] :-1:-1: Premature end of file.

This specific error is new , Ive never seen it could you please send your your full jaikozuser0-0.log and jaikozdebug0-0.log so I can analyse this properly.

Re:Unable to retrieve acoustic ids

Anonymous — GMT

Same error with 1.7.0 on Suse 10.1 and 1.6.1 on Suse 10.2 (different system). Any progress?

Re:Unable to retrieve acoustic ids

paultaylor — GMT

I have not yet managed to get hold of a Suse system to try and reproduce this, it is not happening on my Fedora Linux system

Re:Unable to retrieve acoustic ids

cpicton — GMT

For testing like this, I find vmware extremely useful. You can install any OS/Distro you need to, to test compatibility. The server version is free to download and use (www.vmware.com)

Re:Unable to retrieve acoustic ids

paultaylor — GMT

cpicton wrote:

For testing like this, I find vmware extremely useful. You can install any OS/Distro you need to, to test compatibility. The server version is free to download and use (www.vmware.com)

thanks for the tip

Re:Unable to retrieve acoustic ids

Anonymous — GMT

Has there been any progress on this issue? It's been about a month since I first posted.

Re:Unable to retrieve acoustic ids

paultaylor — GMT

Anonymous wrote:

Has there been any progress on this issue? It's been about a month since I first posted.

i havent forgotten but OpenSuse is not officially supported so i must admit it has not been top priority. I have been trying to use Innotek VirtualBox to get a working Suse installation, but without success.

Re:Unable to retrieve acoustic ids

Anonymous — GMT

paultaylor wrote:

Anonymous wrote:

Has there been any progress on this issue? It's been about a month since I first posted.
i havent forgotten but OpenSuse is not officially supported so i must admit it has not been top priority. I have been trying to use Innotek VirtualBox to get a working Suse installation, but without success.

have the same problem with "this track cannot be analysed" on Suse 10.2 any help to fix it? Using full licence 1.9.4, it's a issue of priviliges? I can let you test it on mine server if you can't install virtual machine and get OpenSuse if you are interested. let me know at thedop@gmail.com

Re:Unable to retrieve acoustic ids

issic — GMT

Anonymous wrote:

paultaylor wrote:

Anonymous wrote:

Has there been any progress on this issue? It's been about a month since I first posted.
i havent forgotten but OpenSuse is not officially supported so i must admit it has not been top priority. I have been trying to use Innotek VirtualBox to get a working Suse installation, but without success.
have the same problem with "this track cannot be analysed" on Suse 10.2 any help to fix it? Using full licence 1.9.4, it's a issue of priviliges? I can let you test it on mine server if you can't install virtual machine and get OpenSuse if you are interested. let me know at thedop@gmail.com

I wrote it :-)

Re:Unable to retrieve acoustic ids

Nocturnal — GMT

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.

Re:Unable to retrieve acoustic ids

paultaylor — GMT

Ok, so this problem has happened on three occasions nows, and always with Linux, I haven't managed to replicate it myself. Can you clarify for me is this happening consistently for the same files. For example in the debug log where it says Unable to create Puid for:132, the 132 refers to the 133nd file (because records are labelled from zero) in the list when sorted by record number. So if this problem occurs again after identifying the record you could right click on it s record header and just select 'Remote Correct/Correct Acoustic Ids' to retry this one file. If it does reoccur could you send me the file and/or try against Windows or OSX to see if the problem persists. Another thing that might be useful would be if you increased the logging output but this will slow down jaikoz so you only really want to do it for when running a test , not all the time. You can increase the logging by using the jaikoz.sh shell script and editing the value -l2 in jaikoz.sh to -l7.

Re:Unable to retrieve acoustic ids

Nocturnal — GMT

paultaylor wrote:

[...] Can you clarify for me is this happening consistently for the same files. For example in the debug log where it says Unable to create Puid for:132, the 132 refers to the 133nd file (because records are labelled from zero) in the list when sorted by record number. So if this problem occurs again after identifying the record you could right click on it s record header and just select 'Remote Correct/Correct Acoustic Ids' to retry this one file. [...]

(The list in the GUI of Jaikoz also starts from 0.) What I did was first analyse a directory of 517 files with genpuid (all files at once). I saved the output in a file. Then I opened the same directory in Jaikoz, started the acoustic analysis, and waited until 2 songs had shown the error. Then I cancelled the operation, and retried acoustic analysis on them separately. This did work. The PUID for these songs was also present in the saved output of genpuid itself. Then I closed Jaikoz (without saving anything), reopened it, and did everything exactly the same. There were errors again, but this time on different files! The files that gave errors the first time, had no problem this time. Again right-clicking and analyzing only that file gave no problems. The files that had errors this time also didn't give any error with genpuid. It is possible that these files are corrupt, but even that can't explain why it doesn't always hang on the same files. What I am wondering about is the error format: Code:

[Fatal Error] :-1:-1: Premature end of file.
23/06/2007 01.06.15:WARNING: Unable to create Puid for:11:null

What programs generate these? The first one doesn't seem like your log format. [edit]I found out it's an error from your XML parser. So probably the output received from genpuid isn't up to par all the time...[/edit] The second one states the list number (so probably from your program) and then 'null'. Where do you print this message? What should follow the list number? Seems like that parameter isn't initialized... I'll retry this with more debug output later... I'm also going to try redoing the entire directory with genpuid, seeing if it also sometimes fails on different files.

Re:Unable to retrieve acoustic ids

paultaylor — GMT

Nocturnal wrote:

What I am wondering about is the error format: Code:
[Fatal Error] :-1:-1: Premature end of file.
23/06/2007 01.06.15:WARNING: Unable to create Puid for:11:null
What programs generate these? The first one doesn't seem like your log format. [edit]I found out it's an error from your XML parser. So probably the output received from genpuid isn't up to par all the time...[/edit] The second one states the list number (so probably from your program) and then 'null'. Where do you print this message? What should follow the list number? Seems like that parameter isn't initialized... I'll retry this with more debug output later... I'm also going to try redoing the entire directory with genpuid, seeing if it also sometimes fails on different files.

Thankyou for taking the time to look at this, it appears that the problem is not file related but related to the interaction between Jaikoz and Genpuid. This lines comes from jaikoz: 23/06/2007 01.06.15:WARNING: Unable to create Puid for:11:null The null is because there is an exception but it has no error message, it is not because something is not inilitized. I dont know where [Fatal Error] :-1:-1: Premature end of file. is coming from but I guess it is coming from genpuid in some way. Ive just reread your message how do you its from the xmlparser, thats interesting. Yes please try with more debugging, this may give the extra information I need to fix this.

Re:Unable to retrieve acoustic ids

Nocturnal — GMT

paultaylor wrote:

I dont know where [Fatal Error] :-1:-1: Premature end of file. is coming from but I guess it is coming from genpuid in some way. Ive just reread your message how do you its from the xmlparser, thats interesting.

When you look it up on Google, the first result shows the exact same error message, coming from the Java SAX XML parser. No doubt you also use some kind of Java XML parser on the output of genpuid... "Premature end of file" would probably refer to the XML data you feed (from genpuid) into the parser, so the problem is probably either the XML returned by genpuid, or the variable you use to store it in (maybe it doesn't get reset properly after every run?)...

Re:Unable to retrieve acoustic ids

Nocturnal — GMT

BTW, I see this issue on Windows, as well, just not as frequently.

Re:Unable to retrieve acoustic ids

paultaylor — GMT

That is important to know, Im reviewing the code BTW are your machines multiple cpus.

Re:Unable to retrieve acoustic ids

paultaylor — GMT

Nocturnal wrote:

maybe it doesn't get reset properly after every run...

That isnt the issue, but I have found something else that maybe causing the problem, a debug log showing the problem occurring would be useful if you have a chance.

Re:Unable to retrieve acoustic ids

Nocturnal — GMT

paultaylor wrote:

Nocturnal wrote:

maybe it doesn't get reset properly after every run...
That isnt the issue, but I have found something else that maybe causing the problem, a debug log showing the problem occurring would be useful if you have a chance.

That's good news! I don't have a debug log yet. I'm running a session of 22 000+ files now, already going 20+ hours, I really didn't want to slow that down or risk a hang with that many files :). The error only occured 25 times in 10 000 files so it really is a rare bug. I don't actually have multiple CPU's, but I do have Hyperthreading activated, which the OS (both Windows and Linux) will treat as if they were 2 CPU's. I do have some more output (different error messages but I'm pretty sure they're caused by the same problem): Code:

[Fatal Error] :1:1: Content is not allowed in prolog.
24/06/2007 19.46.35:WARNING: Unable to create Puid for:2556:null
[Fatal Error] :1:20: XML document structures must start and end within the same entity.
24/06/2007 19.55.24:WARNING: Unable to create Puid for:2997:null
[Fatal Error] :-1:-1: Premature end of file.
24/06/2007 19.57.38:WARNING: Unable to create Puid for:3132:null
[Fatal Error] :-1:-1: Premature end of file.
24/06/2007 19.57.49:WARNING: Unable to create Puid for:3135:null
[Fatal Error] :1:20: XML document structures must start and end within the same entity.
24/06/2007 19.57.56:WARNING: Unable to create Puid for:3136:null
[Fatal Error] :-1:-1: Premature end of file.
24/06/2007 20.04.30:WARNING: Unable to create Puid for:3505:null
[Fatal Error] :1:20: XML document structures must start and end within the same entity.
24/06/2007 20.08.34:WARNING: Unable to create Puid for:3741:null
[Fatal Error] :-1:-1: Premature end of file.

This shows that it's really a problem with recording of the output of genpuid. Since I doubt the problem is in the output itself, it might be caused by processing the output before it's entirely finished (i.e. it still has to write "npuid>" or something)? If you need me to beta-test a possible bugfix, let me know. :)

Re:Unable to retrieve acoustic ids

paultaylor — GMT

Nocturnal wrote:

Since I doubt the problem is in the output itself, it might be caused by processing the output before it's entirely finished (i.e. it still has to write "npuid>" or something)? If you need me to beta-test a possible bugfix, let me know. :)

Yes I think there is a possibility of reading before output has completed, which would be more likely on a multi-threaded system, I may ask you to beat test sometime this week, thanks.

Re:Unable to retrieve acoustic ids

paultaylor — GMT

I believe this is now fixed in Jaikoz 1.10 please let me know

Re:Unable to retrieve acoustic ids

tvanbeck — GMT

I'm running Suse 10.1 and Jaikoz 1.10 and I'm having this error for every file. 1.10 did not resolve this issue.

Re:Unable to retrieve acoustic ids

paultaylor — GMT

Every file, this was not the behaviour that existed before, can you send me a log file please ?

Re:Unable to retrieve acoustic ids

juanqui — GMT

I experience the smae problem with Jaikoz 2.1.0 build 1039 under windows XP. I have 101 mp3 files that Jaikoz doesn't assign a musicIP ID to. It does search for one, (although occaisionally VERY slowly), but they are not actually assigned. It seems to happen to certain artists/albums, but I haven't found in wich these are different from the rest of my collection. If you tell me hoe to create a log, I'll send you one...

Re:Unable to retrieve acoustic ids

paultaylor — GMT

Jaikoz creates a fingerprint on the file then looks to see if the fingerprint exists in the MusicIP database, if it does then the puid is retrieved and stored in the file, it can then be used to try and look up musicbrainz data for that puid (although Musicbrainz may not have the puid in the database. There are three main reasons why a puid is not assigned to a file. 1. The puid does not exist in the MusicIP Database, Jaikoz doesn't currently submit new tracks that dont exist ion the MusicIP database, but this should be an option in the next version. 2. The track is too short or the audio is too poor quality to correctly identify the Puid. 3. Operatng system differences, puid identification is currently slightly better on Windows and OSX than it is on Linux, so some files may not match on Linux but would match on a Windows system. This situation is being improved by MusicIP.

Re:Unable to retrieve acoustic ids

wynlyndd — GMT

paultaylor wrote:

There are three main reasons why a puid is not assigned to a file. 1. The puid does not exist in the MusicIP Database, Jaikoz doesn't currently submit new tracks that dont exist ion the MusicIP database, but this should be an option in the next version.

Thanks for explaining that (or re-explaining as the case may be). I was wondering why certain songs I couldn't get a fingerprint generated. I thought it was all local where generation was concerned.

Re:Unable to retrieve acoustic ids

jochenk — GMT

I still get this error for every file with 2.4.1 under Linux (Gentoo), but not under Mac OSX. Here are the log files. Regards, Jochen

Re:Unable to retrieve acoustic ids

paultaylor — GMT

You only tested against 12 files, not a very exhaustive test. Does your linux installtion support 32bit and 64 bit because the 32 bit libraries are required for the fingerprinting to work.

Unable to retrieve acoustic ids

jochenk — GMT

May 25, 2008 2:58:07 PM: INFO: Retrieved 0 acoustic ids successfully May 25, 2008 2:58:07 PM: INFO: Unable to find a match for 4,011 tags May 25, 2008 2:58:07 PM: INFO: Completed retrieval of Acoustic Ids for 4,118 files Most of these files are processed correctly under MacOSX. Also, my Linux is 32bit only. Regards, Jochen

Re:Unable to retrieve acoustic ids

paultaylor — GMT

Can you email me a file that works on Mac but not on Linux so I can investigate further.

Re:Unable to retrieve acoustic ids

gaikokujinkyofusho — GMT

Hi, I am also having problems with In the concole i get the following error for a variety of tracks: Nov 8, 2008 8:15:00 PM: WARNING: Unable to retrieve an acoustic id for song 36 fileG:\My Music\Chumbawamba-Amnesia.mp3, because this track cannot be analysed Nov 8, 2008 8:15:00 PM: INFO: Retrieved 0 acoustic ids successfully Nov 8, 2008 8:15:00 PM: INFO: Unable to find a match for 1 tags Nov 8, 2008 8:15:00 PM: INFO: Completed retrieval of Acoustic Ids for 1 files Its a pretty good quality file, fairly popular, a few minutes long, and i am using a a bought copy of Jaikoz for windows. Any thoughts on how i could fix this? (it is also happening for other similar files). Thanks in advance, -Gaiko

Re:Unable to retrieve acoustic ids

paultaylor — GMT

Some tracks cannot be analysed because of bugs in Genpuid provided by MusicIP . I do not develop this software but you can either send me the file and I will pass it on or send it direct to support at musicip dot com and they should be able to find what the problem is.

Unable to retrieve acoustic ids

dartman — GMT

Hi, I'm refreshing this ... I use Jaikoz 3.5 installed on Windows XP, my flac files are located on D-link NAS DNS-323 controlled by Linux. For every file i receive a message "unable to retrieve an acoustic id for song, because this track cannot be analyzed" Could you guys help me ? Many thanks

Unable to retrieve acoustic ids

wynlyndd — GMT

dartman wrote:

Hi, I'm refreshing this ... I use Jaikoz 3.5 installed on Windows XP, my flac files are located on D-link NAS DNS-323 controlled by Linux. For every file i receive a message "unable to retrieve an acoustic id for song, because this track cannot be analyzed" Could you guys help me ? Many thanks

My first guess : permissions problem. Have you moved one of the files in question to you machine and attempted the same process? If so, did it fail or work?

Re:Unable to retrieve acoustic ids

dartman — GMT

I thought about it. I set permission scheme to 777 on NAS, I have mapped this resource in my Windows environment. I can change file names, etc... I tested MusicBrainz and it worked properly, tagged artwork to flac files ie. So why Jaikoz doesn't work?

Re:Unable to retrieve acoustic ids

paultaylor — GMT

Please try as suggested and copy to local drive to see if that makes any difference.

Re:Unable to retrieve acoustic ids

dartman — GMT

Everything works well when I copied file to my local drive.

Re:Unable to retrieve acoustic ids

paultaylor — GMT

So its a permissions problem then, perhaps you need to connect as a specific user on your nas. One reason why it might work with Picard but Not Jaikoz is that Jaikoz generally writes changes to a new file, then only when that has been checked is the old file deleted and the new file renamed to the old file. Whereas I think Picard might just modify the existing file which is more dangerous. So Jaikoz requires permissions to create files in the parent folder whereas Picard doesn't, please check that.

Re:Unable to retrieve acoustic ids

sandeepkhanna — GMT

Currently evaluating Jaikoz ... What is the best sequence of actions to cleanup/scrub a large music collection? After years of efforts doing manual, mass tagging from file/folder names and more recently learning about AmpliFIND/MusicBrainz signatures ... I decided to proceed as follows: 1) Use MusicIP Mixer to deep analyse every track and possibly fetch and update tracks with AmpliFIND PUID. I am assuming the the PUIDs fetched will be saved in the tracks after lookup. 2) Identify & Eliminate duplicates using MusicIP Mixer 3) Use Jaikoz to do a mass lookup & update tracks with MusicBrainz IDs based on AmpliFIND PUIDs. Also, perform other tag/file/folder adjustments as needed since Jaikoz seems to have a lot of flexibility with this. 4) Use a TuneUP iTunes companion (on Mac/Windows) OR Banshee/SongBird (Linux) to lookup and associate CoverArt with Albums. TuneUP actually gives multiple choices of artwork per track which are retrieved from various sources on the internet (Amazon, Google images, etc). Is the above a sensible approach ? Also, can Jaikoz on Linux (Mandriva 2010.0 AMD x86_64 with Java HotSpot(TM) 64-Bit Server VM build 1.6.0_16-b01) perform STEP (1) instead of me having to do the deep track analysis using MusicIP Mixer on Windows?

Re:Unable to retrieve acoustic ids

paultaylor — GMT

Yes, Jaikoz can do the analysis for you, and the Puids are saved automatically. Furthermore Jaikoz can also eliminate duplicates based on Music IP id, Musicbrainz Id or both. But MusicIP Mixer does not save PUIDs to the file it uses an older system which canot be detected by Jaikoz so using MusicIP Mixer beforehand is a waste of time from the point of view of Jaikoz,.

Re:Unable to retrieve acoustic ids

sandeepkhanna — GMT

When performing the Action->Retrieve Acoustic IDs in Jaikoz ... it rather goes very very fast (as seen in the console) compared to MusicIP Mixer which takes a few seconds (3-4) before populating the PUID fields. Do I need to purchase and install the Full license before my copy of Jaikoz can truly generate & use the PUIDs? Also, once the deep analysis (PUID lookup) was complete, I can select all tracks, right click and "Archive Analysis (modifies file)", which saves the PUID data. There is also a "Fix tags" option in MusicIP Mixer which seems to use the MusicIP database or is it using MusicBrainz behind the scenes. What bothers me is, that once archived the analysis (saved PUIDs) in the mp3s and reopened those in Jaikoz, Jaikoz doesn't show some as having the PUIDs! This happens only for a subset (1000s though). I also confirmed in MusicIP Mixer by re-reading the songs from disk, that they retained their PUIDs.

Re:Unable to retrieve acoustic ids

Alfg — GMT

MusicIP Mixer doesn't collect the PUID !! nor saves it It only collects and saves the "MusicMagic Data" and "MusicMagic Fingerprint" with the main purpose generating playlists in MusicIP Mixer. The only advantage - except generating playlists in MusicIP Mixer - is, the songs are analyzed and as a result known in the MusicIP (AmpiFIND) database. The programs at AmpliFind around the database now generates a PUID for the song and when you use Jaikoz the next day, you don't have to wait for 24hours getting the PUID. If you only use Jaikoz, you have to run Jaikoz two times for songs that are new to the AmpliFIND database. Getting the PUID without Jaikoz, you have to use the program genpuid.exe (genpuid_win32_1.4.zip) and write some scripts around that DOS program (maybe the is (was) a Linux version too).

Re:Unable to retrieve acoustic ids

dartman — GMT

paultaylor, it was a permission issue. I've used D-link DNS-323 as a NAS for my music. Unfortunately this is not stable platform and there are a lot of complains about files access rights. So, I change it for QNAP 410, looks much better. BTW, Could you provide me best practice for autocorrector tasks? I have a base for over 7.000 cd, all ripped to flac files and I don't want to experiment so much :-) Many thanks,