Welcome Guest

Pages: 1 2
Replacing Custom Delimiter Bug?
2MR2PostJuly 4, 2023, 12:05
Avatar photo
Administrator
Posts: 2085
Registered:
August 23, 2012, 19:27
Normal topicReplacing Custom Delimiter Bug?

Okay ... it is entirely possible that the files you download use a semi-colon to separate multiple artists and do not encode them properly for ID3v2.4. ie. they incorrectly place a semi-colon in the encoded data.

Send a dump of the downloaded files before you save to them. I do not need the saved files as they are encoded correctly.

CarlinSmithPostJuly 4, 2023, 12:37
Newbie
Posts: 19
Registered:
January 1, 2020, 15:15
Normal topicReplacing Custom Delimiter Bug?

While I take a look to find a file that might be formed that way from a music store like Qobuz/Blue Coast Records let me ask for a recommendation.

If a file comes with metadata in the Artist field as "Artist A & Artist B" and I wish to have that as two artists separated by a ; as that is what the downstream player uses I should edit in Yate how? I have always edited the field manually replacing with the semicolon<space> and then wrote the file.

Is this correct or you do recommend something else?

2MR2PostJuly 4, 2023, 12:53
Avatar photo
Administrator
Posts: 2085
Registered:
August 23, 2012, 19:27
Normal topicReplacing Custom Delimiter Bug?

If your player always uses a textual ; then you cannot encode the files correctly to represent multiple items in a field. This includes FLAC and all ID3 based formats (mp3, dsf, dff, wav, aiff, etc.). MPEG-4 files can be configured in a variety of ways. The most typical is that multi-item encodings are ignored in which case the delimiters are written to the files.

If you always want to write the semi-colon text to the files then manually enter the semi-colons ... but DO NOT set the multi-item delimiter to a semi-colon.

If you change the multi-value delimiter back to ;;; and you manually use a single semi-colon, the files will be written as you wish. Of course any player such as Audirvana, Roon, MinimServer, etc. will treat the fields as a single item. ie. not recognizable separate entities.

The issue is that purchased/downloaded tracks might properly encode the multiple artists in which case you'll have to manually change the ;;; sequence to ;. It's been my experience that purchased tracks typically use a textual representation as they don't care if you can identify the separate names individually.

After changing the multi-item delimiter back to ;;; simply saving the files will restore them as you wish. You can do a File>Save Selected Files>Always to force save them.

CarlinSmithPostJuly 4, 2023, 17:59
Newbie
Posts: 19
Registered:
January 1, 2020, 15:15
Normal topicReplacing Custom Delimiter Bug?

Thanks for the counsel. I must have changed the multi-delimiter in Yate but didn't notice the down stream affect until recently as changed it back to default and everything seems correct.

Pages: 1 2
Mingle Forum by Cartpauj | Version: 1.1.0beta | Page loaded in: 0.02 seconds.