Started off slowly and developed a routine to achieve what I wanted (as suggested ohrenkino.many thanks ) Since I raised this I put in a lot of time and effort and changed all my separators to " " especially for composer info (and artist especially when a compilation album was involved) as well as genre. So, in short, which is the best separator to use in my case? Anybody know? Anyhow, using this would eliminate the problems enumerated above but I would not have the benefit of having this read as split fields by a program with that functionality. I though there was a program that uses "/" as a separator but I can't find which. ![]() I could just use "/" with no spaces before or after to save space. Quick question: it is " " not " " or " ", correct? I think this would remove any split fields creating during the conversion to alac and still give me the benefit of getting split fields if I move to a player that uses " " as a separator. I believe I could work around this unwanted consequence by just copying the tags from the. I do first tag in FLAC and then convert to ALAC with dBpoweramp. I was considering using " " as I don't believe I need the space in " ", because it has the advantage of being recognized as multiple fields in programs like Foobar2000, but after reading about dBPoweramp splitting fields with this separator, I don't think this will be wise for the same reasons as using "". Since I use iTunes primarily, and it does not support this, I assume this would not be a good idea. So using this will result in several fields for the same tag. I don't think it would be wise to use "", because, as aforementioned, it is used by Mp3Tag to split the field. I believe the max characters is 255 and that extra space or two between " / " and " /" or "/" could make the difference in fitting a long tag, an extra value or string of values. One reason why I am considering changing the separator is due to space. I must be getting old.Īnyhow, I am trying to put the issue to bed. That is why I am now annotating, as much as possible, the reasoning for my decisions. I know I researched it pretty heavily, and there was a reason, but I cannot remember why. I have been using " / ", but I cannot remember why. I too am beginning to wonder if I am using the best separator. The conversion to each format takes about 24hrs so I do not want to do it too often :). Given I have > 60000 tracks I want to get it right as I have my master copy as FLAC and then convert a copy as ALAC, LAME and AAC using dbPoweramp once I am happy with the FLAC version. What works best for most players or is it a case of creating something if the player you decide to use does not like a particular separator character? Ie should ALAC be different to FLAC or LAME etc. ![]() ![]() I assume a simple "-" as a separator would simply be just an extension to the actual statment in the field and would just look like a longer single word.?Īlso I probably should ask whether the multi value separator should be different between codecs ![]() Would you have to do a merge duplicate field when using a "\" ? This displays well with the music players that I use currently but whether if or I may want to use another player in the future I am wondering if there is a better solution that is more universal?.īeen thinking about whether it would of been best to use the "\" as a separator or even a simple "-" between names of multiple artists, composers and genres in those fields? I would then do an action of merge duplicate fields for these fields after ripping a CD (or after a bunch of CD's). To date I have been using a " " as a separator for the Artist, Composer and Genre fields.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |