![]() ![]() Right now it doesn't work in the grid, but otherwise it is consistent in the whole application. This should be consistent within whole application - in the Tag Panel. the one used now? I can't see an overwhelming need for it, but I agree that it may be easy enough to implement. How important is the user specified separator vs. It looks like you may not be aware of the double backslash that Mp3tag currently uses as the multiple field separator. There's a recent thread on this very subject. I didn't spend much time thinking about the _n%tagname% feature, and it also seems most complex to implement. _1%artist% could always adress only the first tag value, while _2%artist%, _3%artist% following.introduce additional schema of accessing second, third etc.add an option how the default tag value representation (for instance %artist%) should be rendered. ![]() In case there are many values of a particular tag, there should be a possibility to retrieve those values. This would be useful for using files in the players that don't support advanced tags (APE, ID3v2.x etc) and read info only from ID3v1. concatenate using separator (with editbox allowing to specify the separator).In the Options window, in the Tags pane, there should be an option allowing how the multiple tag values are handled inside the ID3v1 tags. Support for mulitple tag values in old ID3v1 tags ![]() This way more clear way of showing the values can be used in the Grid. When user enters a field to edit its value, the separator specified above is used instead to show the point of split. The grid should be able to display the multiple values using the specified separator. Support for mulitple tag values in the grid I realize that this does not solve all cases (how to analyse Artist1 Artist2 - is it Artist1 + Artist2 or Artist1 + Artist2) - but should be fine in 99.99999% cases. When application reads the tag value and should display it, and if the specified separator is encountered in the tag value (for instance user uses to separate values, but there is the character in the title, C-like schema should be used (the separator is doubled). The Extended tags screen should not incorporate this schema (or maybe add an option in the Options dialog - Use this separator also when entering values in Extended Tags dialog), as it allows to precisely specify the tags values. The desired separator could be specified in the Options screen. My experience shows that they are quite easy to implement, but should improve the ease of maintaining a huge audio collection.Įasy way of entering the multiple values of one tag with use of a user specific separator. I would like to propose a few additional features. ![]()
0 Comments
Leave a Reply. |