SongKong Jaikoz

SongKong and Jaikoz Music Tagger Community Forum

Performance improvements

#1 
Caused by: ERROR 23505: The statement was aborted because it would have caused a duplicate key value in a unique or primary key constraint or unique index identified by 'SQL080715233835090' defined on 'RELEASE'.
Caused by: ERROR 23505: The statement was aborted because it would have caused a duplicate key value in a unique or primary key constraint or unique index identified by 'SQL080715233835140' defined on 'ARTIST'.

[list]Check for existence of key before selecting it, exceptions are more expensive than a select before insert.[/list]
[list]Provide an interface to increase the memory limit, 300M is paltry.[/list]
[list]Provide a method, platform supporting, to enable the -d64 switch (x86-64 support), on at least OSX. many speedups![/list]
[list]remember manual corrections made after correcting from musicbrainz[/list]

#2

I already do, I mot sure why this is occuring but think must be a threading issue, please send me your logs.

On Todo list.

On Todo list, wil come on OSX when move to Quaqua 5 interface (currently using Quaqua 4)

[quote=mjc]
Remember manual corrections made after correcting from musicbrainz[/quote]
Various (buit not all) Musicbrainz lookups are cached, what exactly do you mean here ?

#3

[quote=paultaylor][quote=mjc]
Check for existence of key before selecting it, exceptions are more expensive than a select before insert.
[/quote]
I already do, I mot sure why this is occuring but think must be a threading issue, please send me your logs.
[/quote]

will do shortly, reproducing it.

seems to work ok when I just use -d64 on the command line. am I missing something?

[quote=paultaylor][quote=mjc]
Remember manual corrections made after correcting from musicbrainz[/quote]
Various (buit not all) Musicbrainz lookups are cached, what exactly do you mean here ?[/quote]

OK, say the data I get back from MusicBrainz isn’t quite what I wanted - eg, they give me a lot of (disc 1), (disc 2), etc. if I make that change after having done a MB lookup, and then later redo the lookup, it pulls down MB’s data again. It would be nice if it recognized that as ‘user corrected’.

I don’t want the (disc 1),(disc 2), etc because they have the ID3 tags correct and I don’t like to have a cluttered album list.

#4

Quaqua uses some C libraries, and I understod that only a 32bit version of these was provided in Quaqua 4.

[quote=mjc]
Remember manual corrections made after correcting from musicbrainz. Say the data I get back from MusicBrainz isn’t quite what I wanted - eg,
they give me a lot of (disc 1), (disc 2), etc. if I make that change after having done a MB lookup, and then later redo the lookup, it pulls down MB’s data again. It would be nice if it recognized that as ‘user corrected’.

I don’t want the (disc 1),(disc 2), etc because they have the ID3 tags correct and I don’t like to have a cluttered album list. [/quote]

That would be nice, but how do we differentiate between user corrected and user has messed it up. I am going to add an option to Preferences/Music/AutoFormat to strip the (disc 1), (disc 2)
syntax because alot of people (inclusding me) don’t like it but I’m not sure I can provide a magic bullet for all circumstances.

Of Course you can change the settings in Preferences/Musicbrainz/AutoFomat so that fields are not overwritten.

#5

[quote=paultaylor]
That would be nice, but how do we differentiate between user corrected and user has messed it up. I am going to add an option to Preferences/Music/AutoFormat to strip the (disc 1), (disc 2) syntax because alot of people (inclusding me) don’t like it but I’m not sure I can provide a magic bullet for all circumstances.

Of Course you can change the settings in Preferences/Musicbrainz/AutoFomat so that fields are not overwritten.[/quote]

Hmm; maybe provide a ‘force fresh lookup from musicbrainz’ option?

#6

Thats what ‘Update tags from Musicbrainz’ already does , am I missing the point here ?