SongKong Jaikoz

SongKong and Jaikoz Music Tagger Community Forum

Application Suggestions

I really like the app, just throwing these out there.


Is it possible for Jaikoz to work on a directory by directory basis? For example, I have a directory tree that looks something like:

main (150k songs) ->
Artist One (10 songs)
Arist Two (20 songs)
etc…
Artist Last (10 songs)

I’d like to cover all of the directories under main, without having to manually load each artist directory. For example, if I currently point “open folder” to main, it will try to load 150k songs…not the best for memory…but if I do each folder manually (or in groups of 10 or 100), it’s a lot of manual work to get through the whole set.

It would be nice if I could just point it at main, have it to autocorrect on each direct subdirectory it finds, one at a time. This might improve automation and reduce memory footprint.

Small heap (memory) display

Sometimes, incoming albums already have a home in the “move to” locations (i.e. I already have this recording). But the difference between the two recordings could possibly be a higher or lower bitrate. For example, the incoming bitrate might be a higher quality and I would want to replace what is already there. I was thinking of something like "if the ID is the same (i.e. same track) allow for some logic to pick a winner and do a replacement or rejection if needed. Perhaps all tracks for a group would have to meet that criteria.

More buttons at the top (i.e. it would be nice to have all / most menu functions available in button form…perhaps have the button bar be editable.

Recording roll up? Picard has a neat feature that allows groups of songs to “rolled up” to an album so they can addressed together (i.e. for artwork, etc…). Jaikoz seems to only work at the song / track level

If I have a large incoming set of recordings, it’s not entirely clear which sets are sub standard (i.e. low quality bitrate, missing tracks, unmatched by the metadata engines. It would be nice to simply dump all tracks into a “quality check” filter and have it clearly mark sets that meet some minimum requirement (i.e. must be matched, bitrate above 128k, complete set and then can be moved. mark others with red or move to reject.)

Having different sets or groupings of autocorrect functions (i.e. set “a” might include a move and metadata update, set “b” might not…depending on the types of mp3s being worked on)

Something to check my email with? Just kidding.

Hi, the trouble with your idea (that has been suggested before) is that goes against Jaikozes ethics of check before you save, you have no chance to review the changes before the filles get closed and the new folders opened.
I have thought about creating a full autoamted tagging with a minimal ui, but its not got past an idea yet.

In the meantime when you use the Open Folder dialog you dont just have to select just one folder, you can select multiple folders in the same directory. So I would recommeding working in batches of artists, perhaps 10,000 songs at a time.

Jaikoz can also open songs listed in a playlist.

Okay, though bit techical for most users I wouldnt want to display by default.

Try loading files from both locations and using the Action/Delete Duplicates this matchesd based on Musicbrainz/AmpliFind Ids and always picks the hiher bitrate.

These are much requested feature that will be added at some point, but make sure you have View/Advanced option enabled. The biggest problem for me is creating icons to represent the different tasks.

Jaikoz originally only worked at song level , but in later releases the matching is done at release level first. but the interface doesnt really show that. A revised Manual Tag from Musicbrainz tasks that does wnat you want is on the cards but not done yet.

Have you tried View/Show View Pane and switched to the Audio tab, that might go some way to address this issue.

Yes, this has been requested before but still way down on the ‘TODO’ list