Jaikoz- Discussion Forum

Hello

When i try to start Jaikoz i get this error:

Code:

Jaikoz java.sqlBatchUpdateException: A lock could not be obtained within the time requested

What is wrong?

because I would like to organize my huge music collection like this:

A/Artist/Album/Track

ex: The Troggs - Wild Thing - Flower Power: Groovin' (disc 2) (album)
%artist%-%title%-%album%

What I want: VA - The Troggs - Wild Thing - FP (title)

So basically, how do i embed the artist name in all tracks?

Grabbed logins from bugmenot.com just to stop by and thanks the author of this program and his replies on these forums (which were quite useful as I wondered few things not in the manual).

Big up.

There appears to be a bug with filters under certain scenarios.

I have loaded 781 tracks, but only 25 (all from same album) are visible.

EDIT: It fixed itself moments later... not sure why... maybe it was loading?

Jaikoz is a powerful mp3 tag editor. Automation is provided by the MusicBrainz database. The license fee appears reasonably priced at £15, £1.50 of which goes to MusicBrainz.

Usability: Jaikoz performs the basic manual editing properties well. Support for more complex editing (e.g. genre, album art) is pretty poor. Getting to grip with the advanced features is quite a challenge (although on occasions worth the effort) and some of the functionality is rather counter-intuitive. For example understanding what actions are performed by "auto correct" is quite important, but difficult to grasp. A quick start guide and a shorter manual would be of benefit, but most certainly not a substitute for better design.

Performance: Jaikoz is resource hungry and requirements increase linearly based on the number of files loaded. Jaikoz recommends a minimum of 512mb of RAM, although this seems insufficient in my experience for even a modest music collection. Lots of memory is more important than processing power.

Reliability: Poor. In my opinion Jaikoz should be classed as beta. I base this decision having tagged my music collection using Jaikoz and encountered two major bugs and several annoyances, see for example:

http://www.jaikoz.net/jaikozforum/posts/list/812.page
(cause of the above http://www.jaikoz.net/jaikozforum/posts/list/795.page)
http://www.jaikoz.net/jaikozforum/posts/list/819.page
http://www.jaikoz.net/jaikozforum/posts/list/808.page

Although MusicBrainz is independent, I will mention it here as I am funding its running. In my experience the MusicBrainz server is terrible.

Support: Paul seems to be doing an excellent job!

Closing remarks. I consider Jaikoz to be a good example of beta release software. On these ground I do not feel the license fee is presently justifiable. Having said that Jaikoz has the potential to be a wonderful piece of software. However, I wonder if the current licensing model will thwart development. I would love to see Jaikoz becoming open source. Developers world-wide will no doubt collaborate to deliver a truly brilliant package. A income stream can still be obtained from open source software by licensing server side access -- e.g. MusicBrainz and/or other server side services.

bugmenot wrote:

paultaylor wrote:

Possibly, i can see why you would want to do that but it is very specific and probably wouldnt be used by many people.

Reason -- because Jaikoz autocorrect has tagged the year incorrectly, so I would like to go through and fix.

Possibly define a plugin environment to allow third parties write plugins (similar to Firefox).

paultaylor wrote:

Only info pertinent to what you are doing in Jaikoz are logged, unfortunately if I removed logging info about what files caused problems (if thats what you mean) the logs would be less useful in diagnosing problems. I suppose its a trust issue to some extent, firstly buy software from companies you trust, secondly consider do you think I would have any interest in mining any information you provided.

Hi Paul,

Yes, I was referring to file information. I agree with everything you say, however, you are missing the bigger picture. How many log files do you currently have? How many files do these log files list? How many of these files are in violation of copyright law? If these numbers are large then there is every possibility that the record industry have an interest in your logs and may seek a warrant to obtain that information. This may not affect the majority of your law abiding customers, but I do not wish to be caught up in any such investigation.

Moreover, who knows of what value these logs will be to someone in the future...

Regards,

Call me paranoid,
but I like to minimize my digital footprint in today's digital world.

Moreover, even if you are trustworthy, various sources (beyond your control) could be interested in the contents of the log files you are storing...

paultaylor wrote:

Hmm, I wonder if you dont have a spare 60 seconds to 'run Action/Create Support Files' and email me your logs or just you are concerned about spam from be as a result of sending me an email (hence the use of bugmenot).

Spam doesn't bother me. Privacy does! Having looked at the logs they reveal a LOT about individual users.

paultaylor wrote:

Sorry but without more information there is little I can do about this issue.

In the interests of my privacy it will have to remain a bug.

Maybe putting less in log files would tempt me! ;-)

paultaylor wrote:

I dont think it would be terribly useful, the best you are likely to get is album name and artist name, which are probably in the filename anyway.

Because Jaikoz doesn't give a nice way to handle albums. I can handle tracks, but not albums.

My approach:

* Rename subfolders from tags
* Manually go through subfolders using file browser and change names to fix inconsistencies.

Maybe better functionality would be to handle albums in a better way

paultaylor wrote:

Possibly, i can see why you would want to do that but it is very specific and probably wouldnt be used by many people.

Reason -- because Jaikoz autocorrect has tagged the year incorrectly, so I would like to go through and fix.

What does the following error mean:

Code:

01/03/2009 15.27.18:com.jthink.jaikoz.manipulate.musicbrainzhelper.MusicBrainzServerQuery:doQuery:WARNING: URL key:X-Rate-Limited:[700.3 700.0 10]

I would like to be able to filter using arbitrary conditions. For example:

Records where album matches another album, but the year differs.

There's a correct tags from filename, why not correct tags from folder?