Bug 320 - COMMENT keyword in "Title Format"
: COMMENT keyword in "Title Format"
Status: RESOLVED WORKSFORME
Product: Logitech Media Server
Classification: Unclassified
Component: Tagging
: 5.x or older
: PC Windows XP
: P2 normal (vote)
: Future
Assigned To: Vidur Apparao
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2004-05-21 01:51 UTC by Dave Parboo
Modified: 2008-12-18 11:53 UTC (History)
0 users

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dave Parboo 2004-05-21 01:51:22 UTC
If the COMMENT keyword is included in "Title Format", for example, "TITLE
(ARTIST) - COMMENT", a group of "hex words" follows instead of the
appropriate comments. This also happens if there are no comments to display.
Regardless of whether there are comments or not, the number of hex words
varies from three to ten.
Comment 1 KDF 2004-05-21 10:40:40 UTC
using COMMENT works for me.  Many of mine have allmusic.com reviews in the
comments and they come out just fine (although huge).  

What program are you suing for tagging?
Comment 2 KDF 2004-05-21 10:41:16 UTC
sorry...using for tagging
Comment 3 Dave Parboo 2004-05-21 13:48:41 UTC
iTunes 4.5 is used for tagging
Comment 4 Dave Parboo 2004-05-21 14:05:35 UTC
Changing the skin does not make a difference. However, Tag&Rename works fine.
Comment 5 Blackketter Dean 2004-05-22 14:02:28 UTC
Dave: can you attach a smallish example MP3 file that exhibits this behavior?
Comment 6 Dave Parboo 2004-05-22 14:38:53 UTC
The smallest file that I have that exhibits this feature is 1.2Mb - is this 
too large?
Comment 7 Blackketter Dean 2004-05-22 14:42:37 UTC
that would be fine.  
Comment 8 Dave Parboo 2004-05-22 15:06:30 UTC
I'm having problems sending the mp3 file to you as an attachment to this bug 
report (hangs Internet Explorer and dumps several pages worth of garbage) - 
may I send it via e-mail? If so, please let me know which address to send it 
to.
Comment 9 Vidur Apparao 2004-06-05 14:28:23 UTC
Dave, go ahead and send the file to vidur@slimdevices.com and I'll try to
recreate the problem.
Comment 10 narya 2004-09-14 22:23:47 UTC
I noticed this behaviour on some of my iTunes 4.6 managed files as well (using 
Slimserver 5.2.1 now). Going back into iTunes and changing anything within the 
comments field and saving would fix it all the time. (In addition to that I 
selected all songs with an empty comment field in iTunes and entered a single 
character, like a dash, to avoid the hex numbers for these files.)

Alexander.
Comment 11 Blackketter Dean 2005-03-11 13:56:27 UTC
Need an example to test.
Comment 12 narya 2005-04-08 01:23:09 UTC
This problem seems due to iTunes (mis-)using a comment field to store 
its "Sound Check" information.

When Sound Check is turned on, iTunes adds a second comment with the 
descriptor "iTunNORM" and stores volume information with the gelp of those HEX 
words.

Slimserver seems to only read the first available comment, instead of reading 
the comment with a blank descriptor, which usually contains the text one 
enters as "real" comment.

Hope this helps.

Alexander.
Comment 13 KDF 2005-04-08 09:32:51 UTC
please attach a sample song with comments such as these.
Comment 14 KDF 2005-08-08 15:11:06 UTC
iTunes 4.9, turned on SoundCheck and waited.  Loaded up mp3's into hex editor to
verify that iTunesNORM exists.  Rescanned with cleared library.  I see no hexits
as part of the COMMENT, neither in player display or in the songinfo page.
Either this was not the cause, the new infoformat has fixed this issue, or
iTunes has reworked the placement of this tag info in such a way as to remove
the issue.  Marking as fixed.  Can be re-opened if sample files can be provided
that still exhibit this problem
Comment 15 Chris Owens 2008-12-18 11:53:30 UTC
Routine bug db maintenance; removing old versions which cause confusion.  I apologize for the inconvenience.