title
Products            Buy            Support Forum            Professional            About            Codec Central
 
Results 1 to 15 of 17

Thread: Tagging - How CD Ripper handles Vorbis/Flac Comment Fields

Hybrid View

Previous Post Previous Post   Next Post Next Post
  1. #1

    Join Date
    Feb 2018
    Posts
    16

    Tagging - How CD Ripper handles Vorbis/Flac Comment Fields

    Hi there,

    since March I am using dbpoweramp R16.2 Reference for OS X and this forum had been really of help to me to configure DBPA, setting up my preferred configuration and also have inspired me further how to tag music collections. I am quite happy so far with the functions of DBPA.
    Many thanks to DBPA team, Spoon, PeterP and to the forum members.

    So my post is about this ‘quite’ because the following issues give me headaches when processing each and every single CD (so far non-classical CDs to .flac). I wish these could be fixed or at least worked-around. Please have a look:

    I.‘Multiple value separator ; does not work for some fields’

    Description:
    Found this in GROUPING, LOCATION, LANGUAGE or MOOD.
    (Example) Entering in the tag editing window frame (lower middle of DBPA GUI) ‘Hubba; Bubba’ to either of the fields above causes CD Ripper to create only a single field with the value ‘Hubba; Bubba’ in the ripped files but should create two entries, like:

    If
    GROUPING=Hubba; Bubba
    then
    GROUPING=Hubba
    GROUPING=Bubba

    I was surprised because it works for GENRE and others, ARTIST, of course. Expected a consistent handling of the ‘; ‘ separator across the Vorbis Comment Fields.

    User Impact:
    - Prevents from ripping CDs using DBPA only (And CD Ripper clearly got the functions/potential to deliver this!), because it's always needed to add an additional processing step; which is re-loading the ripped tracks into a tag editor afterwards to edit and store multiple values appropriately.
    - Significant time increase spent for ripping, at least

    II.Field Mapping
    II.1 ‘ENSEMBLE field disappears after ripping’

    Description:
    Happens when
    ENSEMBLE=band name
    and also
    ALBUMARTIST=band name
    are set. In short: To both fields the same value assigned.
    And it just happens? in the background, or have I overlooked sth perhaps?

    User Impact:
    - Cannot browse a separate index of bands (in non-classical) and also in future will not be able to index/filter for classical music ensembles from duetts over chamber to orchestras (when tagging classical music).
    - Prevents from ripping CDs using DBPA only, because it's always needed to afterwards load the ripped tracks into a tag editor to recover ENSEMBLE.
    - Time consuming and additional error source

    II.2 ‘COMMENT mapped to DESCRIPTION’
    Description:
    Solved. could successfully change this to leave it unmapped as COMMENT.
    Found a setting under DBPA configure>Codecs>ID Tagging.

    User Benefit:
    Transparent and user controllable as wanted. Nice. (Unfortunately I could not find a similar setting for ENSEMBLE, is it hidden elsewhere?)

    III.‘No Predictive Typing when filling Tag Comment fields’
    Believe I read about it in some Release notes but I got to admit I am not sure. Either way, I'd appreciate to have such support.

    User Benefit:
    - Reduces likelihood of creating unwanted ‘ghost’ indexes during tagging. E.g. when GENRE intent is typing ‘Classical’ but it happens to end up in ‘Classicall’ as a typo.
    - Saves time because no (less often) retagging step needed.

    thanks for reading

    Any thoughts / suggestions?

    Pantin

  2. #2
    dBpoweramp Guru
    Join Date
    Nov 2007
    Location
    Florida, USA
    Posts
    4,247

    Re: Tagging - How CD Ripper handles Vorbis/Flac Comment Fields

    Quick answer to one of your issues. Only a few tag fields accept multi values. This is not a dbpa limitation. It is the tag standard.
    Last edited by garym; 04-06-2018 at 08:07 PM.

  3. #3

    Join Date
    Feb 2018
    Posts
    16

    Re: Tagging - How CD Ripper handles Vorbis/Flac Comment Fields

    Quote Originally Posted by garym View Post
    Quick answer to one of your issues. Only a few tag fields accept multi values. This is not a dbpa limitation. It is the tag standard.

    which ones are defined by standard to support multi values? would you have a link you could share please. or could you quote from the standard document, if you cannot do otherwise - thx

    so far I couldn't find such a de jure information from searching the web.

  4. #4
    dBpoweramp Guru
    Join Date
    Nov 2007
    Location
    Florida, USA
    Posts
    4,247

    Re: Tagging - How CD Ripper handles Vorbis/Flac Comment Fields

    Quote Originally Posted by Pantin View Post
    which ones are defined by standard to support multi values? would you have a link you could share please. or could you quote from the standard document, if you cannot do otherwise - thx

    so far I couldn't find such a de jure information from searching the web.
    Can't recall where I saw the information. I know I saw this somewhere. I vaguely recall @mville posting some info on this on a thread on this forum. rather than grouping field you might try STYLE for subgenre info. Not sure whether STYLE accepts multivalue, but you could try that too.

  5. #5
    dBpoweramp Enthusiast
    Join Date
    Jan 2014
    Posts
    63

    Re: Tagging - How CD Ripper handles Vorbis/Flac Comment Fields

    Pantin,
    In the past I used multiple values for the STYLE tag for some of my FLAC music. I used Mp3tag to add the multiple values. It was done some time after ripping, when I considered adding STYLE to all of my music.

  6. #6
    dBpoweramp Guru
    Join Date
    Dec 2008
    Location
    London, UK
    Posts
    3,535

    Re: Tagging - How CD Ripper handles Vorbis/Flac Comment Fields

    It is my understanding that in theory, where applicable, any vorbis tag can be multi-value, but over the years many server/player software(s) have not not followed this standard (for reasons unknown). So, some tags are treated as multi-value and some are not.

    I guess dBpoweramp has identified this and has adapted to this situation i.e. it is pointless for dBpoweramp to write a multi-value MOOD tag to file, if no other software is able to parse the tag correctly.

    Currently dBpoweramp supports the following vorbis/flac multi-value tags:
    ALBUM ARTIST, ALBUM ARTIST SORT
    ARTIST, ARTIST SORT
    COMPOSER, COMPOSERSORT
    GENRE
    SOLOISTS, SOLOISTSSORT
    STYLE

    and (but I have not used, so cannot confirm)

    LYRICIST (Original lyricist(s)/text writer(s))
    ORIGINAL ARTIST (Original artist(s)/performer(s))
    WRITER (Lyricist/Text writer)

    I am happy to be corrected here, if my understanding is not correct or I have not included important information.

  7. #7

    Join Date
    Feb 2018
    Posts
    16

    Re: Tagging - How CD Ripper handles Vorbis/Flac Comment Fields

    +missing information in regards to:
    "
    I.'Multiple value separator ; does not work for some fields'

    Found this in GROUPING, LOCATION, LANGUAGE or MOOD.
    "

    and also same for STYLE.

    also GROUPING may be known to some as CONTENTGROUP. I am using this to add sub-genre information.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •