Post Reply 
 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
not all custom mp3 tags are shown?
09-12-2012, 22:51
Post: #11
RE: not all custom mp3 tags are shown?
(09-12-2012 22:42)alexinc Wrote:  nope. Shy its listed under the first entry before the ';'. Cool no big deal to me, as i prefer the genre tag. just a thing i noticed when starting to play around with your software.

I appreciate the feedback, and I'd like to understand what's happening. As you're just seeing the first style entry, this suggests to me that foobar may be doing something unexpected, rather than putting the whole string into a TXXX field. Can you look at the file with Perry's ID3 viewer and let me know what's in there?

Quote:now if remixed by may become a part of minimserver it may become the tool of my choice. last but not least i'm quite sure the samsung story may get solved sooner or later too. the next days i'm trying to get into the tree architecture to get my collection viewed as close as possible i'm used to setup my db with foobar... Big Grin

It shouldn't be difficult to add support for Remixed By. The Samsung TV issue might be harder to solve.
Find all posts by this user
Quote this message in a reply
09-12-2012, 23:06
Post: #12
RE: not all custom mp3 tags are shown?
glad to help where i can. Cool

37 TXXX 3723 109 STYLEProgressive HouseTranceProgressive Trance

as you can see there is no seperator shown when using id3 tag viewer. foobar seperates it with ';' when opening file properties. but minimserver serves the files as progressive house only. not the other 2 styles and not the complete string of all 3 styles.
Find all posts by this user
Quote this message in a reply
10-12-2012, 11:17
Post: #13
RE: not all custom mp3 tags are shown?
(09-12-2012 23:06)alexinc Wrote:  glad to help where i can. Cool

37 TXXX 3723 109 STYLEProgressive HouseTranceProgressive Trance

as you can see there is no seperator shown when using id3 tag viewer. foobar seperates it with ';' when opening file properties. but minimserver serves the files as progressive house only. not the other 2 styles and not the complete string of all 3 styles.

Thanks very much for this. It appears that the styles are separated with NUL (0x00) characters in the TXXX frame. According to the ID3v2 spec, a TXXX frame can contain only a single string value, so multiple values separated by NUL characters aren't allowed. In ID3v2.4 (but not ID3v2.3), using NUL as a separator for multiple values is valid for other text frames, but not for TXXX. So this looks like a bug in foobar, which should be writing multiple TXXX frames instead of writing multiple NUL-separated values in a single TXXX frame.
Find all posts by this user
Quote this message in a reply
10-12-2012, 12:10
Post: #14
RE: not all custom mp3 tags are shown?
I have this problem too. I edit all my tags in mp3tag. Some of my custom tags applied to mp3's don't appear when browsing certain indextags. Those files have only one tag though, so no issues with separators.
For example, all files in my library appear when browsing by artist, but when browsing by artistsort, the mp3 albums get excluded. The same goes for my custom tag label.
Find all posts by this user
Quote this message in a reply
10-12-2012, 13:37
Post: #15
RE: not all custom mp3 tags are shown?
(10-12-2012 12:10)Cableguy Wrote:  I have this problem too. I edit all my tags in mp3tag. Some of my custom tags applied to mp3's don't appear when browsing certain indextags. Those files have only one tag though, so no issues with separators.
For example, all files in my library appear when browsing by artist, but when browsing by artistsort, the mp3 albums get excluded. The same goes for my custom tag label.

There's a known issue with the LABEL tag. The ID3v2 specification uses the TPUB 'Publisher' frame to hold Publisher or Label information. Some tagging programs (but not Mp3tag, according to this page) put LABEL tags into TPUB frames, and MinimServer currently doesn't read TPUB frames. I could change MinimServer to read TPUB frames, but the result would be that your Label tags are displayed as Publisher tags. Sad

ARTISTSORT is problematical as well. From a bit of web searching, Mp3tag writes this to the TSOP 'Performer Sort Order' frame. This is only valid in ID3v2.4, but Mp3tag writes it to ID3v2.3 as well. MinimServer currently doesn't read the TSOP tag. I could change this, but the result might be that your ArtistSort tags are displayed as PerformerSortOrder tags, and this might only work if your files are written with ID3v2.4 tags. Sad

When I have a spare day or two, I'll gather information on all the tag mappings used by all the tagging programs, try to guess which of the many alternative mapping choices represent the prevailing industry standard, and implement those mappings in MinimServer.
Find all posts by this user
Quote this message in a reply
10-12-2012, 15:15
Post: #16
RE: not all custom mp3 tags are shown?
Thanks for the feedback. Would a solution be to name the container to something else, like LABLE and LASTNAME?
Find all posts by this user
Quote this message in a reply
10-12-2012, 15:44 (This post was last modified: 10-12-2012 15:49 by simoncn.)
Post: #17
RE: not all custom mp3 tags are shown?
(10-12-2012 15:15)Cableguy Wrote:  Thanks for the feedback. Would a solution be to name the container to something else, like LABLE and LASTNAME?

That should work. You can then set the indexTags property to display LABLE as Label, etc. Smile

Edit: To clarify, the tag in the file would be stored as LABLE and you would set the indexTags property to LABLE:Label to have this displayed correctly in the control point index.
Find all posts by this user
Quote this message in a reply
11-12-2012, 21:02
Post: #18
RE: not all custom mp3 tags are shown?
Hi everyone. I'm also trying to get the Style tagging working.

To my understanding, there is a ID3 tag TIT1 (I think) that is used for "content grouping". Is this the field / tag that is used for Style? I guess there must be some sort of common understanding between tagging programs about which filed to use.
I have noticed that iTunes has a "Grouping" field - is this the same TIT1 field?

And if want to be able to browse on this tag/field, what indexTag should I enter in the Minimserver properties?

Greetz, Willem, Netherlands
Find all posts by this user
Quote this message in a reply
11-12-2012, 21:34
Post: #19
RE: not all custom mp3 tags are shown?
(11-12-2012 21:02)whgmkeller Wrote:  Hi everyone. I'm also trying to get the Style tagging working.

To my understanding, there is a ID3 tag TIT1 (I think) that is used for "content grouping". Is this the field / tag that is used for Style? I guess there must be some sort of common understanding between tagging programs about which filed to use.
I have noticed that iTunes has a "Grouping" field - is this the same TIT1 field?

And if want to be able to browse on this tag/field, what indexTag should I enter in the Minimserver properties?

Greetz, Willem, Netherlands

Please don't post the same question to multiple threads. I've responded to it in the original thread that you started.
Find all posts by this user
Quote this message in a reply
12-12-2012, 12:21
Post: #20
RE: not all custom mp3 tags are shown?
(10-12-2012 13:37)simoncn Wrote:  There's a known issue with the LABEL tag. The ID3v2 specification uses the TPUB 'Publisher' frame to hold Publisher or Label information. Some tagging programs (but not Mp3tag, according to this page) put LABEL tags into TPUB frames, and MinimServer currently doesn't read TPUB frames. I could change MinimServer to read TPUB frames, but the result would be that your Label tags are displayed as Publisher tags. Sad

ARTISTSORT is problematical as well. From a bit of web searching, Mp3tag writes this to the TSOP 'Performer Sort Order' frame. This is only valid in ID3v2.4, but Mp3tag writes it to ID3v2.3 as well. MinimServer currently doesn't read the TSOP tag. I could change this, but the result might be that your ArtistSort tags are displayed as PerformerSortOrder tags, and this might only work if your files are written with ID3v2.4 tags. Sad

When I have a spare day or two, I'll gather information on all the tag mappings used by all the tagging programs, try to guess which of the many alternative mapping choices represent the prevailing industry standard, and implement those mappings in MinimServer.

To solve the above two issues (and other similar problems caused by alternative mappings for the same tag), I'm planning to add a new feature to MinimServer to alow user-defined tag remapping. For example, if you had a mixture of LABEL tags (in FLAC files) and PUBLISHER tags (mapped from TPUB fields in MP3 files), and you wanted all these tags to be treated as LABEL tags for indexing purposes, you'd be able to add something to indexTags to make MinimServer do that.

This isn't quite the same as the current facility to display a different index name for a tag. The new feature would allow different tags to be merged together for indexing purposes, which isn't possible with index entry renaming.
Find all posts by this user
Quote this message in a reply
Post Reply 


Forum Jump:


User(s) browsing this thread: 1 Guest(s)