SongKong Jaikoz

SongKong and Jaikoz Music Tagger Community Forum

SongKong Recent.path not always updating

#1

Hi Paul, et al,
I have noticed for a bit (before today… maybe months ago? My use of SongKong is in fits and spurts) that the default path to work with is not updating (or not in all cases).

A bit more detail:
I’m using the docker/server version of SongKong, on a NAS. When I pull up the web UI, it shows the filesystem tree, but the currently selected folder is one I haven’t used in ages. I ran a search here (for “recent.path” as I spotted in general.properties) and only found this: Clear File>Open Recent dropdown list. I wonder if what that user was trying to express wasn’t just that he wanted to clear it, but that it wasn’t updating…
In my case, that’s the issue - I don’t care about clearing it, but it never updates to whatever folder I’ve used recently. I’ll do a little test and describe the steps:

Test 1:
I click on a folder ("/music/SongKong/Drop Music Here"), and click the “Monitor Watch Folder” link, and start the job. I click cancel after a minute, then close the report, and it’s back to “/music/Music/Artists/Metallica/new”. Oh, also, the dialog when I click cancel says “Meta Grater has been cancelled, report will be displayed when cancellation has completed” (emphasis mine) - so that’s a minor little UI glitch.

Test 2:
I pick the same folder (/music/SongKong/Drop Music Here) which happens to be empty at the moment, and choose the Fix Songs job. SongKong immediately detects I’m wasting time, and kicks me back out to the start screen with a red dialog indicating there were no files to work on. It’s also sent me back to /music/Music/Artists/Metallica/new. Dang.

Test 3:
Same as test 2, but I’ve put a few files in there. It runs the job, I close the report, and now it’s got me in the correct (same - /music/SongKong/Drop Music Here) folder.

So I guess it does work from a certain perspective (probably the most common use case), but it’d sure be nice if it worked in case #1, too (that’s MY most common use case). I guess I don’t care too much about case 2, but that does seem like it would be more intuitive - I just don’t see that as being a case that people will encounter very often.

On the other hand, I just found a good work around (but I’ll forget it next time I fire up SongKong, 3-6 months from now! :smiley: )

Thanks

#2

hi what have you mapped the /music and /songkong virtual folders to?

#3

Heh, I’m realizing the folder names I have may be confusing… Anyway…

Here’s the snipping from my docker export:

“volume_bindings” : [
{
“host_volume_file” : “/Audio”,
“is_directory” : true,
“mount_point” : “/music”,
“type” : “rw”
},
{
“host_volume_file” : “/docker/songkong”,
“is_directory” : true,
“mount_point” : “/songkong”,
“type” : “rw”
}

The docker container is running in the Docker instance on my Synology NAS.

So, /music (in the docker container) maps to /Audio on my NAS,
and /songkong maps to /docker/songkong. This is where the songkong config files are.

Now, don’t be confused by the fact that my /Audio folder contains a folder called “Music”, and another folder called “SongKong” - those are what you see me referring to in the post above:

/music/SongKong/… --> /Audio/SongKong/…
/music/Music/… --> /Audio/Music/…
/songkong --> /docker/songkong

If I had to play a hunch, Paul, it would be that since a user exits the “Monitor Watch Folder” by “Cancelling” it, and the failed Auto Fix (test case 2 - where no files were found) … failed to do anything, hence didn’t complete successfully, but test case 3 completes normally, and DOES update the recent.path… I’ll be that the path update only happens at the end of a non-cancelled, non-failed, job… Which makes sense except that case 1 never really gets to do that.

#4

Hi replicated and raised https://jthink.atlassian.net/browse/SONGKONG-2773

And this one

#5

Okay solved issue, the problem was when start task in Remote UI we check

  1. If folder exists
  2. If folder contains songs
  3. Only if both true do we add to recent list

So because Watch Folder empty to start with it fails 2

Removed requirement 2 for 3 so also fixes the issue when run Fix songs on empty folder

#6

Awesome! Thanks, I look forward to that update - that behavior was bugging me for a while, and it wasn’t till I started snooping around, and saw recent.path that I realized there was a definite problem.

#7

Now fixed as part of 11.6.1

1 Like