[AF] Popularimeter Tag Fails in 2.48c


#21

Not obvious to me. Could you clarify, Dano? Is there some forum policy prohibiting complete audio files? And if so, what's meant by "complete"?


#22

I would add that recent soon to be released changes in both winamp and MM will make mp3tags handling (described in post 16) break pretty badly.

I don't understand why mp3tag is ignoring the issues in this thread?


#23

Surely the reason it is a problem is it is a failure to operate as required. See http://help.mp3tag.de/main_tags.html#POPM for how it is supposed to operate.

Can anyone tell me the latest version of Mp3tag that does not suffer from this failure? Thanks.


#24

2.48b

EDIT:

(for winamp anyway. I don't know when the "app specific" fields got added for MM and WMP, might be in the version history though)


#25

Thanks.

I take that to mean: when POPM has email rating@winamp.com, anyway.


#26

just to be clear, it means that if u have rated your files using winamps default value (which u state above), then the last mp3tag to show the raw data for that is 2.48b

just fyi, the new winamp thankfully allows the user to denote any email or txt string they like.

however, it will be earlier versions of mp3tag than 2.48b to get POPM to show the raw data if u rated files with MM or WMP. I don't know which earlier versions, but u might be able to deduce it from the version history.


#27

[quote name='MrSinatra' post='70650'] it means that if u have rated your files using winamps default value (which u state above), then the last mp3tag to show the raw data for that is 2.48b

Meaning the last Mp3tag not to suffer from "all of my %popularimeter% and POPULARIMETER references have stopped working" on files rated using Winamp's default settings is 2.48b.

In the matter of this confused implementation, I think we need every bit of clarity we can get. :slight_smile:


#28

Can someone please summarize the issue that is reported in this thread?


#29

thanks for the interest!

the most basic issue, is that %popularimeter% does not work as a column, meaning it does not show any data at all, if the text string ID in a POPM frame is one that mp3tag recognizes, namely:

windows media 9 series (RATING WMP)
rating@winamp.com (RATING WINAMP)
no@email (RATING MM)

the proposed solution is to allow both columns to work simultaneously. so if a file had:

rating@winamp.com|196|0

...in its POPM frame, then it would continue to show "4" in a RATING WINAMP column, but it would simultaneously show "rating@winamp.com|196|0" in a %popularimeter% column, instead of nothing, which it currently shows.

the main point is that I want to see the raw data in the one column, and currently I can't if it has one of those "recognized" txt ID strings.

"popularimeter" is missing from your listing to create columns btw. it used to be there, altho I can't recall if it was in the "information fields" or "extended fields" list.

--

you should also be aware of the following things:

just because the text id might seem to suggest a given program wrote the rating, does not mean a DIFFERENT program didn't write a different rating later. currently, MM will write 252 for 5 stars, but winamp will write 255. if a winamp user re-rates the file, OR gives it a different rating, the MM txt string REMAINS in place, but the value changes. this then completely breaks what you are trying to do in the "app" rating columns. see post 16.

Also, I have gotten the devs at MM to agree to use "255" instead of 252 and "1" instead of 23 going forward, but that change has yet to be released. in addition, winamp will in its next release, allow the user to specify their own email addy, as opposed to the default above, (also my request).

thx for your attention to this issue!


#30

Surely the more basic issue is that %popularimeter% (and POPULARIMETER) does not work anywhere under those conditions - not just in a column definition. Correct?

It was missing as long ago as V2.44:

I too would like %popularimeter% to be restored to full function. And I suggest that until that time, the Help at http://help.mp3tag.de/main_tags.html be amended to show the current reduced function.


#31

afaik, that is correct, and what I was implying, although I agree it is better stated directly.


#32

Thanks.


#33

I posted this a while back:

/t/14581/1


#34

Florian,

Do you still need more feedback than what was given? I see that this wasn't addressed in the recent release.

Let me know if I can clarify anything for you?


#35

my first post in this thread was from July 7 2011.

I will continue to be patient, however I would at least like to know from Florian what his assessment of this bug is? do I have any chance of finding that out?

thanks, -mdw


#36

two years since the last post.

any chance this will be addressed?

the easiest fix is to just allow the popularimeter column to always work and show the raw data no matter what. no reason it can't work simultaneously with the other 'string specific' columns like RATING MM and so on.


#37

I too would like some news on a fix to this.


#38

hi Florian,

this bug has been around for about 7 years now, and is marked awaiting feedback.

here is the best summary:

the most basic issue, is that %popularimeter% does not work as a column, meaning it does not show any data at all, if the text string ID in a POPM frame is one that mp3tag recognizes, namely:

windows media 9 series (RATING WMP)
rating@winamp.com (RATING WINAMP)
no@email (RATING MM)

the proposed solution is to allow both columns to work simultaneously. so if a file had:

rating@winamp.com|196|0

...in its POPM frame, then it would continue to show "4" in a RATING WINAMP column, but it would simultaneously show "rating@winamp.com|196|0" in a %popularimeter% column, instead of nothing, which it currently shows.

the main point is that I want to see the raw data in the one column, and currently I can't if it has one of those "recognized" txt ID strings.

"popularimeter" is missing from your listing to create columns btw. it used to be there, altho I can't recall if it was in the "information fields" or "extended fields" list.


#39

I think that if you have 2 columns, one with the value and field POPULARIMETER and (an empty) one with RATING WINAMP and you have already filled POPULARIMETER and then enter data in the column RATING WINAMP then you get 2 POPM fields as these 2 columns do not know anything about each other. There is (yet) no synchronization mechanism.


#40

The main issue why this has not been addressed in the proposed way, i.e., having both POPULARIMETER with the raw data in Email|Rating|Playcounter and the different app-specific RATING MM, RATING WMP, ...) fields is the following:

Displaying both fields, where in fact one of them is a derived field, i.e., would really break Mp3tag's way of showing what's in the file. You'd end up with a POPULARIMETER field (showing what's inside the tag) and a RATING MM field, which is then only a view on the very same data. Mp3tag is designed to only show one field per real tag data (that's either raw POPULARIMETER or a app-specific rating). Changing that would require per-field level sync mechanisms, where changing one field would also automagically change another — this is a direction I don't want to go into.

In fact, @MrSinatra I was thinking of the way Mp3tag handles rating lately and read some of your posts here and on the Winamp and MediaMonkey forums. My initial goal with adding the app-specific rating fields was to ease the manipulation of them and to provide means to display something star-alike without having to use endless scripting that splits up the POPULARIMETER values. Those fields were added when MediaMonkey used completely different values than the other apps (you've analyzed this thoroughly).

I now think that adding those app-specific was a mistake — which is unfortunately not so easy to revert. My dream-solution is to remove the different app-specific RATING MM, RATING WMP, ... fields and to have Mp3tag show the raw data (POPULARIMETER, RATING, RATE, ...). To ease displaying this data, instead of having dedicated fields I can imagine having a scripting function, e.g., $rating(%field%) that converts the raw value in a star-like representation.