View Single Post
Old 8th May 2013, 16:36   #20
Forum King
Aminifu's Avatar
Join Date: Aug 2011
Location: Phoenix, AZ
Posts: 4,658
Originally Posted by MrSinatra View Post
that's not the point I was trying to make, the other thread was not related b/c of 3rd party codecs. it was about yet another genre issue, (3 so far) which is why I posted it.
Ok, but that thread is about different apps and codecs using slightly different look-up tables for the numerical codes associated with ID3 genre values. Maybe the look-up tables should be the same, but it does not surprise me that different apps and codecs would use different implementations when they can. Look at how ratings are handled for example.

This thread and the one about flac are not about that and are basically talking about the same issue. Namely, instead of displaying the genre value read from the file, the value displayed is the last one used in the Alt + 3 dialog. Maybe the latest internal build fixes this, we will see in time.

Bringing that other thread into the discussion needlessly confuses things and frankly I have a hard time reconciling that with your methodical approach to troubleshooting.

Originally Posted by MrSinatra View Post
I don't care at all about v1 tags personally, but if any time by devs or anyone is to be spent looking at anything buggy, I believe in doing it as methodically as the best information one has allows. I guess that's a radical pov.
Is it a radical pov to believe that a formal standard procedure is not needed in all cases?

To fix this issue, access to the Winamp code and a working knowledge of what that code is trying to do is required. When someone with the access and knowledge says the issue is understood, then it is a waste of time to re-present the issue in an alternate way, imo.

To find a work-a-round for this issue (or any issue), code access and a working knowledge of the code is not needed, imo. Any Winamp user is able to come up with suggestions. People are very ingenious. A user's suggestions can sometimes trigger an idea with a dev as to where to look in the code. A formal standard troubleshooting procedure is not needed in order to provide suggestions and work-a-rounds could be equally workable or off-base, if a formal procedure is used or not.

It is not easy to know when the Winamp standard troubleshooting procedure is needed. But from reading threads (new and old) over the past 2 years, it is not used very often and it becomes clear pretty quickly (and asked for) when it is needed. Many times there is no real issue, the user just needed to have read the documentation. Imagine the time wasted (reading or skimming through stuff) for those trying to help, if the user in those cases presented all the formal info.

Winamp Pro v5.666.3516 fully-patched - Komodo X Touchscreen v1.0 by Victhor skin
Windows 10 Home 64-bit v1809 desktop - Logitech Z906 5.1 speaker system
Aminifu is offline