THANK YOU! Someone finally gets it!
I'm pretty sure everybody else participating in this thread also 'got it'. Your request is not rocket science.
(even though your intentions why it would be useful were not very well explained in the beginning)
You just don't like the opinions about it.
And you forgot to quote the last remark of the person who you believe is the only one 'who gets it', which was:
"As a concept it probably doesn't make much sense to implement."
So, at this moment there is still nobody who thinks it would be a good idea to get your wish implemented.
Perhaps still nobody is getting it?
I think if there was anyone not getting it, it was you, since after all was said and done, you still didn't understand what I was asking in my previous thread lol.
Look, I get it. You don't agree with my wishlist request. You voted. You've voiced and explained your opinion. You've done your part. Be on your way please. Don't keep bringing things up trying to provoke me. I didn't come here to argue. This serves no purpose other than to circle jerk, which isn't the intent of the forum nor my thread.
While we're still on the topic of having forgotten to "quote the last remark of the person who i believe is the only one 'who gets it'", let me do that:
But I still trust Steven would had been able to implement it in a way that would be understandable if he were to do it ;-)
I agree with this completely. I respect their opinion that it may not make the most sense. However they still believe that, should Steven implement it, he would do so in a manner that would not cause confusion. I believe this as well, because as I suggested, he can make the local database take precedence when the "store ratings in the music file" setting is unchecked. To recap one last time, since I don't allow musicbee to SAVE ratings to tags, I would naturally also expect musicbee to not GET ratings from tags.
Let's put this debate to rest now since I don't see us reaching a conclusion at the current rate.
To clarify, after finding out about the behaviour where either one or the other of the tags is kept I thought it would be too much work to implement, for something so niche.
But if it was already able to keep track of both tags then this would be much simpler to implement obviously. As I mentioned before, exposing the "library rating" tag as a seperate field which can then be used by whomever for whatever purpose without polluting existing functionality.
But it's interesting that this is the way it used to work for you before SonicRings, I'm not sure what is going on there. Steven should be able to chime in on that one.
Yeah, MusicBee clearly keeps track of internally rated tracks separately from the tracks that simply have their ratings stored in the tags. Therefore I think it's completely possible for Steven to allow us to ignore the tags without impacting the internal ratings.
@SonicRings Just to be sure that we are on the same page. When I tested that I first had the option "store rating in the music file" enabled. That allowed me to change the rating tag embeded in the file. After that, I disabled the option and changed the rating again. That resulted in the embeded rating tag to be removed. I could see the change using the tag inspector.
Are you saying that for you it works or used to work differently at some point?
I've never enabled that setting so it seems that our methods of testing are the reason we've experienced different results. I can imagine that once you enable the setting to store all ratings to the tags, later disabling it would then remove all tags' ratings.