Hi there. I'm aware that Custom Scan is no longer supported, but for now it mostly seems to work on my server (running 8.1.1), so in the hope of any feedback from other users...
LMS natively imports OGG ratings (RATING). Custom Scan imports MP3 ratings (POPM) by default. All good. However, if I want to import AAC ratings saved by Mediamonkey into the tag RATE, I have to use the custom rating tag option in Custom Scan. I had hoped it would work like this:
FILE has POPM/RATING tag (no RATE tag) -> value untouched in database
FILE has RATE tag (no POPM/RATING tag) -> value from tag added to database
However, as it functions for me, it is treating a custom rating tag as a forced replacement for the default, so all ratings for OGG/MP3 files (the custom tag RATE isn't present) are nonetheless given a new default value of 100, rather than being left with the original POPM/RATING value. Thus:
FILE has POPM/RATING/RATE tag -> 100 value added to database
All files receive a new and wrong value even though the tag is correct.
If this is unusual and the result of changes in LMS since Custom Scan stopped being developed then of course that's just life, but if this is not normal then suggestions for fixes would be welcome.
LMS natively imports OGG ratings (RATING). Custom Scan imports MP3 ratings (POPM) by default. All good. However, if I want to import AAC ratings saved by Mediamonkey into the tag RATE, I have to use the custom rating tag option in Custom Scan. I had hoped it would work like this:
FILE has POPM/RATING tag (no RATE tag) -> value untouched in database
FILE has RATE tag (no POPM/RATING tag) -> value from tag added to database
However, as it functions for me, it is treating a custom rating tag as a forced replacement for the default, so all ratings for OGG/MP3 files (the custom tag RATE isn't present) are nonetheless given a new default value of 100, rather than being left with the original POPM/RATING value. Thus:
FILE has POPM/RATING/RATE tag -> 100 value added to database
All files receive a new and wrong value even though the tag is correct.
If this is unusual and the result of changes in LMS since Custom Scan stopped being developed then of course that's just life, but if this is not normal then suggestions for fixes would be welcome.