2015-12-11, 16:40
Thanks for your thoughts Zag & Razze on my (simple) steps to help users with their tagging.
a) I'm putting together a technical over view of tags and how we process them, for myself as much as anyone. If someone (like you Zag) would like to convert this into something for users that would be great.
b) Kodi has an event log?! Who knew
What else goes in it? When scanning a big collection it could end up with a lot of lines, any interaction issues with other processes? Not sure all tag scanning needs to be logged every time, I would just like the ability to analyse the quality of tagging in the files a user is trying to add to the library.
c) One concern about rejecting poorly tagged files is how do we notify the user. Listing rejected files in a log (own, debug or event) possibly mixed in with other things, the average user is not going to notice or know why their music is missing from the library. But I'm not sure about on screen message either....
Both beginners and advanced users could benefit from clearer reporting of tagging issues.
a) I'm putting together a technical over view of tags and how we process them, for myself as much as anyone. If someone (like you Zag) would like to convert this into something for users that would be great.
b) Kodi has an event log?! Who knew
What else goes in it? When scanning a big collection it could end up with a lot of lines, any interaction issues with other processes? Not sure all tag scanning needs to be logged every time, I would just like the ability to analyse the quality of tagging in the files a user is trying to add to the library.
c) One concern about rejecting poorly tagged files is how do we notify the user. Listing rejected files in a log (own, debug or event) possibly mixed in with other things, the average user is not going to notice or know why their music is missing from the library. But I'm not sure about on screen message either....
Both beginners and advanced users could benefit from clearer reporting of tagging issues.
