[Logo] Jaikoz and SongKong Forums
  [Search] Search   [Recent Topics] Recent Topics   [Members]  Member Listing   [Groups] Back to home page 
[Register] Register / 
[Login] Login 
Messages posted by: arick  XML
Profile for arick -> Messages posted by arick [20]
Author Message
I am regularly getting a "fpcalc.exe" failure while running "Retrieve Acoustic Ids". (log message below) It seems to happen relatively randomly, but in approximately 3% - 5% of the cases. I have just been closing the window, but with 20,000+ files, this gets tedious and it makes me nervous about the correctness of the generated Acoustic ID.

Generating the ID's on my library of 20k+ songs is on track to take more then an hour, which seems awefull slow for a local operation, on a 4 Core, 8 MByte machine that isn't doing anything very CPU intensive.

I am running the 64-bit Jaikoz on WinDoze 7 Pro 64-bit.

Problem signature:
Problem Event Name: APPCRASH
Application Name: fpcalc.exe
Application Version:
Application Timestamp: 4ef32640
Fault Module Name: fpcalc.exe
Fault Module Version:
Fault Module Timestamp: 4ef32640
Exception Code: c0000005
Exception Offset: 0005f5cc
OS Version: 6.1.7601.
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

Read our privacy statement online:

If the online privacy statement is not available, please read our privacy statement offline:

paultaylor wrote:
So I guess the safest thing to do is run Create AcoustIds  

By "Create AcousticIds", do you mean the menu option "Retrieve Acoustic Ids"? I checked the help text, but wasn't able to find this menu option to "Create AcousticId's", and your usage seems to imply the same menu option as "Retrieve Acoustic Ids".
Modifying the Jaikoz64.ini file settings is absolutely the best way to go!!! I used this setting

and even hitting the online MusicBrainz database I was clean up my local 25 GByte music repository very quickly.

Another very important setting is turning OFF the setting for "check for original release". That also has a major performance impact!

I am probabaly both naive and OCD, but I always update my meta-data as part of cleanup and renaming my collection. That is why I included the recommendation to create a local instance of MusicBrainz. According to the MusicBrainz site, the rcommended solution to set up a local copy of MusicBrainz is to set up a virtual machine using Virtual Box and the provided virtual image, which includes the ability to keep your local copy updated. For folks with large music repositories, this would seem to be much more performant, and makes you a better network citizen <sfsf>

Seth has 8 GBytes of RAM, as do I, so I am assuming that both of us have the hardware bandwidth to at least explore this option.
Awesome. I didn't know that JThink was using JIRA.

Is http://jthink.net:8081/browse/JAIKOZ and http://jthink.net:8081/browse/SONGKONG where users should submit bug reports?
If you are going to be using Jaikoz, I suspect that most performant solution will be to setup a local instance of MusicBrainz. This is what I am in the process of doing. Unfortunately, at 5 GBytes for the VM image, with my bandwidth, that will take a day or so to download.
But there was a couple of points I wanted to get back with you on.

There may be some issues with the Jaikoz help text
Modifying the Executable Icon Properties
Using the latest version of the Jaikoz 64-bit, I tried modifying the icon that calls the executable, exactly as described in the help text. I added Jmaxheap=1536000000 to the end of the command line in the properties of the icon on the desktop, and restarted Jaikoz.

Then I checked the memory usage by clicking on the "console" tab on the very bottom window pane in Jaikoz. Typically, this is the window pane that you use to get detailed information about the individual song files. In the "View" menu, this window pane is called "Show Detail Pane ". Click it on and off a couple of times, and you will see which window pane I am referring to.

TBL: According to Jaikoz console window, changing the Jmaxheap value in the properties of the bug-shaped icon on the desktop doesn't seem to have any affect. So, I am digging into this issue a bit myself, since I have two or three music repositories that are between 25 and 50 GBytes each.

Modifying the Jaikoz.bat File Properties
The last time I was doing massive changes to my music repositories, I used the Jaikoz.bat file. I believe that this was version 4.5.1. This is the contents of my Jaikoz.bat file from then ...
 @echo off
 java -Xms150m -Xmx4500m -XX:MaxPermSize=200m -splash:splash.png -jar lib\jaikoz.jar -l2 -m2 -f

Obviously, the JVM that I must have had installed in the OS must have been a 64-bt version of the JVM. Otherwise the maximum heap size that I was using would have been too large for a 32-bit version of WinDoze.

Your physical memory size and the version of Jaikoz executable that you are using don't seem to line up
From the filename of the executable that you are using, it appears that you are running the 32-bit version of Jaikoz, and that you are running on a WinDoze 32-bit version of the OS. I am guessing this because the filename for the 64-bit version of Jaikoz is Jaikoz64.exe, and the 64-bit version of WinDoze OS would have installed a 32-bit application in C:\Program Files (x86)\Jthink\Jaikoz

Physical memory size of WinDoze 32-bit
No matter how much physical RAM you install in your machine, 32-bit WinDoze is only capable of addressing about 3 1/2 GBytes of physical RAM. The rest of that RAM is just going to waste.

Maximum Heap Size of a 32-bit JVM
On a standard WinDoze machine, the maximum heap size is 2GBytes.
On WinDoze server, you can 3GBytes.
On a Linux machine, you can get 4GBytes.

Bug Report:
Priority: Minor
Issue Description:
Both the online help text, and the offline help text, continue to contain references to the "Update Lyrics" feature. This feature has not been a part of the product for almost two years. These references create the impression that Jaikoz currently provides such a capability. Therefore, these references are confusing, and misleading. To some, they may be perceived as false-advertising.

Recommended Solution:
Remove, from the help text, any and all references to this capability, both offline, and online, until such a time as this feature is once again available in the product.

Discussion Points:
This issue, the reasons, some potential solutions etc. have been discussed in a number of forum posts over the last two years or so. Old-timers are familiar with the situation. While they are not always happy with it, they understand that there has been no deliberate attempt to be deceptive.

New-comers tend to be less understanding.
If I understand your question correctly, I believe section 3.5 Memory Management addresses this issue exactly. For the online details of this, see Memory Management.

The bottom line is that you need to specify the memory arguments to the JVM on the command line that is used to start Jaikoz.
Jaikoz is in save mode right now. Before I close out, I will save off the support files and send them in.
I am running on the latest (4.5.3) and I currently doing 23,000 songs.
Jaikoz has been running for two days. The first day it got through MusicBrainz, and now it is chugging through Discogs.

BTW: I think there is a minor bug in the progress box. The first line currently says:
AutoCorrector: Task 1 of 14: Correct Metadata from Discogs. 

In my case, this is actually task 2, not task 1.
Paul's comments above help me understand why I have been struggling with the Base Folder and Sub-Folder.

When I see the term "Base Folder", my perception is that the property "Base Folder" refers to a static, semi-permanent property that defines the root of my music repository, regardless of which sub-folder it is that I happen to be working with at any one point in time. This is consistent to the way that the other preferences on the General tab of Preferences are treated.

What makes sense to me, is that Base Folder is the absolute location where Jaikoz will apply the pattern that I have defined in sub-folder preferences, just as Database Folder remains an absolute.

However, I believe that the current implementation of Jaikoz assumes that Base Folder is a dynamic property that is primarily useful for selectively applying Meta-Data changes, and that the user changes this every time that they switch to a new set of music tracks.

IMHO, this capability is better handled in the definition of the pattern for the sub-folder in Preferences. The preferences allow for conditionally including or excluding the nodes of the renamed path, so there doesn't seem to be a critical need to update the sub-folders by redefining the base folder.

In my case, I have only defined two levels of sub-folders:
The links given at http://www.jthink.net/jaudiotagger/maven/source-repository.html[/url] do not work.

You get to this site from the link at http://www.jthink.net/jaudiotagger/maven/index.html[/url]

It appears that Oracle has changed the forwarding since they took over Sun's sites.
I have had similar performance issues with Jaikoz the first time that it looks up a lot of AccousticalID's from either of the two databases.

I am running in 64 Bit mode with -Jmaxheap=5536000000.

My experience has been that it eventually chugs through everything, but with 20,000 files, it has taken a couple of days to do each stage.
If the user sets the option to copy deleted files to a designated folder:

1) Jaikoz doesn't create this folder,
2) If the user doesn't manually create this folder, Jaikoz returns an ambiguous error message.

Suggestion, in the code that duplicates the "To be deleted" files, either explicitly add a check for the folder, or throw a less generic exception so that higher level of code can ask the user if they want Jaikoz to create this folder, or if the user wants to manually create the folder.

I've tried creating brand new folders and put some test files in them. I could get Jaikoz to create new folders to match the Metadata in the songs, move the files into the new sub-folders, update the filenames, and save these changes to the filesystem.

Jaikoz is able to mark a duplicate file for deletion, but despite the fact that Jaikoz actually created the folders, moved the files, renamed the files and updated their mp3 tags, it could NOT physically remove the duplicated files. I am very puzzled!
Delete Duplicates is still failing, even on an internal drive (C.

I copied the same two folders that I was using previously (just because they each have one, identical file) to my C:\Temp directory. It still fails to delete, and it does so in exactly the same way. I was able to then go in manually and delete the files.

Any chance that this is some WinDoze 7 permissions thing?
I narrowed it down to two directories, with one file each. Both files matched on their ID and Fingerprint. Once I got the error message, I captured and sent off the support files.

I will try out using an internal drive instead of the USB when I get home this afternoon.
Whenever my "actions" include a song marked for deletion, Jaikoz responds with a dialog box saying that the file cannot be deleted and cancels all actions.
I have full admin privileges and I am able to manually delete the files.

This happens with either "Delete Duplicate" and "Delete Files".
My music files are located on an attached USB3 drive.
I am running on WinDoze 7 professional.
I have the latest Jaikoz.
I have a professional Jaikoz license.
You are correct. Mia Culpa.

I was looking at the wrong date field. Going back and looking more carefully, while it is true that Paul Taylor
Joined: 21/08/2006 
the date when he posted the announcement was in September.
Umm, that was five years ago. Jaikoz still doesn't have any way to reliably fetch lyrics?
Jaikoz keeps rejecting my license file, and resetting me to the temporary license.

I received the typical email with the file attached as "license.zip". I have tried to unzip it with both WinDoze 7 and with 7-zip. This produces a file named "license.jai".

Then I:
o - open Jaikoz,
o - File -> Update License,
o - Navigate to the license.jai file,
o - select the license.jai file,
o - click on the "Open" button.

Jaikoz rejects the license file, renames it to license.old, and resets me to a trail license.

What am I missing here? Do you have to manually activate the license or something?
Profile for arick -> Messages posted by arick [20]
Go to:   
Powered by JForum 2.1.6 © JForum Team