Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: Suggestion: different parsing of track-/discnumber (Read 6123 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Suggestion: different parsing of track-/discnumber

Heya, I've seen that when I play my FLAC files in foobar, the track column shows up some strange results, for example with the song "Someone's in the Wolf" by Queens of the Stone Age, the track column shows "1/1.9/16" . This is track 9 of 16 of the only disc (i.e. a 1 disc album as most are). When I tag my files in mp3tag I tag the track numbers X/Y and similarly with the discnumber. When I do this with my mp3 and aac files the track column in foobar shows like it should as "1.09" .

However in mp3tag when I tag my aac files it automatically changes the values after the / sign to a different metadata value e.g. totaltracks or totaldiscs. Should this happen for FLAC files as well so being an mp3tag bug or is it a foobar bug in its reading of the metadata being incorrect?


I hope at least 1 person followed my ranting bug report, so anyone who did and can provide some help would help ease my frustration with the situation.

Suggestion: different parsing of track-/discnumber

Reply #1 –
AFAIK, X/Y format for a TRACK and DISC tag is defined for ID3 tags. FLAC uses Vorbis comment tag and use separate tags for total tracks and total discs.
Please, someone correct me if I'm wrong.
Also if you for example tag a FLAC file with PUBLISHER tag, it will be written as ORGANISATION. Look here
If age or weaknes doe prohibyte bloudletting you must use boxing

Suggestion: different parsing of track-/discnumber

Reply #2 –
not a bug, but how foobar reads the tags. For example, I rip CDs to FLAC in dbpoweramp and have it set to identify disc #. So the tags indicate the disc # and total number of discs. If only one disc, then 1/1 is the outcome.  When I bring these files into Foobar2000, they show up as you indicated "1/1.9.16" which is showing disc 1 of 1 and track 9 of 16. If you prefer it to not show the disc info you can modify either the initial tags or the display in foobar2000.  I typically set the track #'s to display 2 digits when I rip so that track 5 comes before track 10 (i.e., 05 before 10).

Quote from: AliL on
Heya, I've seen that when I play my FLAC files in foobar, the track column shows up some strange results, for example with the song "Someone's in the Wolf" by Queens of the Stone Age, the track column shows "1/1.9/16" . This is track 9 of 16 of the only disc (i.e. a 1 disc album as most are). When I tag my files in mp3tag I tag the track numbers X/Y and similarly with the discnumber. When I do this with my mp3 and aac files the track column in foobar shows like it should as "1.09" .

However in mp3tag when I tag my aac files it automatically changes the values after the / sign to a different metadata value e.g. totaltracks or totaldiscs. Should this happen for FLAC files as well so being an mp3tag bug or is it a foobar bug in its reading of the metadata being incorrect?


I hope at least 1 person followed my ranting bug report, so anyone who did and can provide some help would help ease my frustration with the situation.

Suggestion: different parsing of track-/discnumber

Reply #3 –
Quote from: garym on
not a bug, but how foobar reads the tags. For example, I rip CDs to FLAC in dbpoweramp and have it set to identify disc #. So the tags indicate the disc # and total number of discs. If only one disc, then 1/1 is the outcome.  When I bring these files into Foobar2000, they show up as you indicated "1/1.9.16" which is showing disc 1 of 1 and track 9 of 16. If you prefer it to not show the disc info you can modify either the initial tags or the display in foobar2000.  I typically set the track #'s to display 2 digits when I rip so that track 5 comes before track 10 (i.e., 05 before 10).



OK, so we've establishes that mp3tag is not at fault as dbpoweramp does the same thing (unless they are both at fault) so it MUST be a bug in fb2k if it is reading the files incorrectly as it can handle the / in the file for id3 tags in mp3 files but not vorbis comments in FLAC files.

Therefore I'm changing the topic title to "Bug Report: Incorrect Reading of Vorbis Comments in FLAC's".

Edit: OK, as I can't edit the title of the topic, could a mod do it?

Suggestion: different parsing of track-/discnumber

Reply #4 –
foobar2000 is not really acting incorrectly, because there is nothing in the vorbis comment standard which says the tracknumber and discnumber tags should be parsed in the same manner as id3v2.

but it might be a reasonable feature request 

Suggestion: different parsing of track-/discnumber

Reply #5 –
Quote from: Cosmo on
foobar2000 is not really acting incorrectly, because there is nothing in the vorbis comment standard which says the tracknumber and discnumber tags should be parsed in the same manner as id3v2.

but it might be a reasonable feature request 


OK then, could a mod therefore change the topic title to something reflecting a feature request of how it parses the vorbis comments and move it to the appropriate forum? Many thanks.

AliL

Suggestion: different parsing of track-/discnumber

Reply #6 –
Many thanks to whichever mod changed the topic title, but in case the feature should not be implemented, does anyone know of a way of automatically editing the tags so that the numbers after the / in the track metadata field get moved to the totaltracks metadata field and then removed from the former field so the tags are displayed as they should? Or am I going to have to do this manually?

Thanks in advance for the help,

AliL

Suggestion: different parsing of track-/discnumber

Reply #7 –
Open Properties, right-click, choose Auto Track Number.

This works folder-wise (one folder = one album), which means that you can process all your FLAC files at once.
 

Suggestion: different parsing of track-/discnumber

Reply #8 –
Now if I was to do this and the track numbers ended up being messed up because the playlist went:

1/11
10/11
11/11
2/11
3/11
4/11
5/11
6/11
7/11
8/11
9/11

Because of fb2k not parsing the tracknumbers correctly, is there any way of undoing this because I have done this before on a test sample and undo doesn't undo tagging changes? Maybe this is a bug?

Suggestion: different parsing of track-/discnumber

Reply #9 –
Did you actually try what I suggested, or for how long do you plan to continue your "not (...) correctly (...) blah blah (...) bug" agenda?

Suggestion: different parsing of track-/discnumber

Reply #10 –
Sorry, I didn't explain properly. Due to fb2k parsing the tags differently to how I expected, when I tested your solution on an 11 track album, this was the result:

1/11    -->  1
10/11  -->  2
11/11  -->  3
2/11    -->  4
3/11    -->  5
4/11    -->  6
5/11    -->  7
6/11    -->  8
7/11    -->  9
8/11    -->  10
9/11    -->  11

Obviously, this isn't how I want my files to be tagged, so am I doing something wrong or is there another possible solution?

And I'm sorry for asking whether the undo command not undoing tagging was a bug, but usually undo means undo! But I suppose this only affects in-program events and not other external files (e.g. the music files themselves).

Thanks for the help,

AliL

Suggestion: different parsing of track-/discnumber

Reply #11 –
The solution is to properly sort your playlist before you open the properties dialog.

You probably tried to sort it using the Track column. That won't work, because it sorts items as strings. Note that this is not a bug, because it would work if your files were properly tagged, which they aren't, and which isn't foobar2000's fault.

Thus, you have to find an alternate approach to sort your files. If your filenames have proper leading tracknumbers, you can use "Edit, Sort, Sort by File Path". If that doesn't work, "Sort by" in combination with a pattern like "%album artist%|%album%|$num(%tracknumber%,2)" should do it.

Suggestion: different parsing of track-/discnumber

Reply #12 –
Quote from: Frank Bicking on
You probably tried to sort it using the Track column. That won't work, because it sorts items as strings. Note that this is not a bug, because it would work if your files were properly tagged, which they aren't, and which isn't foobar2000's fault.



I wasn't trying to say that it was fb2k's fault that my files weren't tagged properly, but it's not mine either. It's just the way that the vorbis comment standard works and how fbk2 handles the metadata.


Many thanks for the "Edit, Sort, Sort by File Path" idea, I've now tried that and as far as I can see, it has worked a treat. Thank you!