ok, I’ll resend the report later today Paul. Thx
1 song folders instead of albums or compilations grouping
support resent
something must be wrong…getting some whole albums kept in the “singles” folder instead of album ones…
just sent another support for this last test.
I don’t know what to do anymore for this to get to an acceptable result…
I can see errors like this in the Errors and Warnings section of report
Duplicate Path:/Volumes/Multimedia/Audio/Various/07 - Various Lounge/00 - Singles/Groove Armada - A Private Interlude (Kinobe remix)(Breakbeat).mp3 for /Volumes/Multimedia/Audio/Various/07 - Various Lounge/Various Singles/Groove Armada -A Private Interlude (Kinobe remix) (1).mp3 unable to rename
Do you have duplicate copies of these files ?
Sorry, just remembered I fixed this issue last week
https://jthink.atlassian.net/browse/SONGKONG-1899
should have a bug fix version (6.6.1) available for you later this week.
Thx Paul. Is this the cause of the albums not being considered as album though?
Not sure, but is a step towards solving the problem.
SongKong 6.6.1 now available, so please rerun and resend support files
New version installed and ran with no much improvement in the result…
Still got whole albums in “singles” folder.
Still got 1 file album/compilation folders
Also got duplicated folders (album name+(1)) that could be merged in one
new support file sent.
-
It has run better, the checked against MusicBrainz and Discogs before task cancelled by SongKong because of unreported error should be ignored, this should have been fixed by [SONGKONG-1894] - Unexpected Error because songs loaded greater than song sent to StartMatcher, but I made a mistake in the fix.
-
The remaining Duplicate Path errors can be ignored but confusingly for me they are occurring because trying to rename files to a new filename that is the same except for case i.e using ‘of’ instead of ‘Of’. Windows is case-insensitive so prevents this but you are running on MacOS which treats as different so problem should not occur. Can you help me with this, is it a Windows formatted disk or something ?
-
Okay I think I have found the problem with albums not being moved to albums folder, in your mask you have
if((mbreleasetype=='Album'))
but mbreleasetype can contain multiple values, primary types like Album and secondary types like Soundtrack so you need to use
if(mbreleasetype.indexOf('Album')>-1)
more info at http://www.jthink.net/jaikozforum/posts/list/20976.page
So please fix the rename masks and rerun and we can take it from there.
Actually I have realized that because this fails SongKong then trys to rename the subfolder part by adding a (1) to folder name and this is causing the unnecessary (1) folders. So I need to fix this but first I need to understand MacOS complaining about writing new filename that only differs in case, so waiting for info from yourself.
Although I am running SongKong from an OSX plateforme, the files are located on to a QNAP nas, would that be the cause?
ok, will try that when back home later on today.
Although I am running SongKong from an OSX plateform, the files are located on to a QNAP nas, would that be the cause?
[/quote]
I would have thought that being a linux based system Qnap would treat the name in different case as different, but maybe they have modified something. Maybe it is related to Samba or similar if that is what is used to access the Nas files, https://forum1.qnap.com/viewtopic.php?p=145275&sid=a198308827f22825491f44bf847263ce
What Qnap nas do you have, and are you aware you can install SongKong on many of their nas drives - http://www.jthink.net/songkong/en/install_docker_qnap.jsp
yes I’m aware I can install songkong on the qnap http://www.jthink.net/jaikozforum/posts/list/20105.page 
It’s a TVS471
Okay, well I would like to continue with solving your issues on macOS regardless but I think the issue you originally had on Qnap is now solved because now songkong runs on Qnap as if root.
ok, but I guess I’ll find similar issues on QNAP than desktop version in terms of renaming and matching, correct?
Please don’t use Qnap yet because I want to resolve on MacOS with another bug fix release using your data to test.
With Qnap you wouldn’t have the filenaming sensitive issue and also fixing files should be quicker because working locally, but yes you may still have some matching issues.
ok, rewriting my scripts in order to separate Albums from Comilations from Single files according to the forum question your mention above but would like your confirmation that they’ll work as expected:
COMPILATIONS:
if(mbreleasetype.indexOf('Compilation')>-1)
{
"00 - Compilations"
+"/"
+ '' + (year.length>4 ? year.substring(0,4):year)
+"/"
+ ifnotempty(album,' ')
+"/"
+ ifmultidisc('Disc ' + ifnotempty(pad(discno,2),'/'))
+ ifnotempty(pad(trackno,2),' - ')
+ ifnotempty(artist,' - ')
+ title
}
else
{
'00 - Singles'
+ '/'
+ ifnotempty(artist,' - ')
+ ifnotempty(title,'')
+ '('
+ genre
+ ')'
}
ALBUMS:
{
'00 - Albums' + "/" +
ifnotempty2(albumartist,artist,'/')
+ '' + (year.length>4 ? year.substring(0,4):year) +" - "
+ ifnotempty(album,'')
+ ifnotempty(discsubtitle,'')
+ '/'
+ ifmultidisc('Disc ' + ifnotempty(pad(discno,2),'/'))
+ ifnotempty(pad(trackno,2),' - ')
+ ifnotempty(artist,' - ')
+ ifnotempty(title,'')
}
else
{
'00 - Singles'
+ '/'
+ ifnotempty(artist,' - ')
+ ifnotempty(title,'')
+ '('
+ genre
+ ')'
}
Will that work?
re-ran with above scripts.
Support file resent
It seems to have worked, but not made major difference. I should have a new version within a couple of days that you can try.