SongKong Jaikoz

SongKong and Jaikoz Music Tagger Community Forum

Curious Requirement to be Online to Rename SubFolders & Filenames From Metadata

Retrieving AcoustIDs, MusicBrainz and Discogs data are the remote functions. Renaming from tags is a local function and shouldn’t touch the network. Jaikoz puts a remote lookup inside it anyway, and with no network that one step retries for hours instead of failing over to the tags

What happens: Correct Sub Folders / Filenames from Metadata sends a release lookup to search.jthinkws.com for every song that has a MusicBrainz or Discogs release ID in its tags. It’s one request per release, not per song. Songs without a release ID cause no lookups.

It happens whatever the mask is. I tested two masks:

  • My own custom mask, after removing every mb_… field from it.
  • A plain tags-only mask: AlbumArtist - Album (Year)/Track - Artist - Title .

Both still made the lookups: 106 in one run and 60 in the other. So the mask doesn’t need the data. It looks like Jaikoz loads the MusicBrainz script fields for every song before evaluating any mask.

The call chain, from an offline run:

java.net.UnknownHostException: search.jthinkws.com at ...JthinkSearchServer.doQuery at ...MusicBrainzSearchRelease.queryByReleaseId at ...matchinghelper.ReleaseCache.getOrAdd at ...settings.scripter.MusicBrainzScriptFields.addFields at ...autoformat.PathFormatter.evaluateMask at ...autoformat.PathFormatter.formatValue at ...SubFolderAnalyser.updateData

What’s sent: the log shows only the query, in this form:

?type=release&query=reid:(<release id>) AND src:1&limit=1&offset=0

src:1 is MusicBrainz and src:2 is Discogs. Neither the mask nor the resulting names appear in it.
Even so, every rename tells the server which releases are in the library and when.

When offline: the task doesn’t fall back to the tags. It retries the same release over and over with growing waits; I saw one release still being retried after about 2 hours 40 minutes, at about 4½ minutes between tries. So the task looks frozen.

Possibly not HTTPS: the stack runs through Java’s plain-HTTP handler ( sun.net.www.protocol.http.HttpURLConnection ), not its HTTPS one. I’m going by the class names; I haven’t captured the traffic to confirm it.

Requests & Considerations:

  1. Make renaming from metadata fully local. The remote functions (AcoustID, MusicBrainz, Discogs) are separate actions already.
  2. Failing that, fetch release data only when the mask actually uses an mb_… field.
  3. When offline, fail fast and use the tags instead of retrying for hours.
  4. Give us an option to turn off online lookups outside the Remote menu.
  5. Use HTTPS for these requests, if they don’t already.
  6. Many functions we paid for do not require internet; yet opening the application requires internet.

Ok, thank you for this I will look into this it does seem there is no need to get releases for renaming if they are not used, I assume it is only doing this because they are not already in release cache which would be the usual case.

But Jaikoz does expect Internet access, at the very least it needs this to fully verify your license when you start it

1 Like

Out of curiosity, if an update to the program for any of these items, does that mean a new license must be purchased to see that update? I am not exactly 100% on how the updates expiration works for things reported like this. Thanks for your attention regardless.

Any fixes I make are only made to the latest version of Jaikoz, we don’t retro fix earlier versions, that would be impractical. You don’t need to buy a new license, but if your version expiry date has expired you would need to purchase 1 year of updates to update Jaikoz to the latest version with fix.

Raised issue https://jthink.atlassian.net/browse/JAIKOZ-1570