Hello,
I believe this is a bug. When viewing the metadata fields for at least two types (i.e., FLAC and m4a) of encoded music, the "Encoded by:" field appears blank on Dopus. However, it does appear within Mp3tag v3.27a. Below is an image of a FLAC file.
Opus reads/writes ENCODED BY rather than ENCODED-BY for that field.
What Opus uses seems to be what at least some other tools use, but it may not be universal, as it isn't one of FLAC's standard tags.
We might be able to support both, if usage with the alternate name is widespread. Which tool(s) produce that result? Or is it being manually specified as a name/value pair?
(As an aside, the Properties dialog that comes from Windows seems to incorrectly map ENCODER to the field it calls "Encoded by" for FLAC files, which is definitely completely wrong!)
Already stated in my post. Mp3tag.
No worries. I just wanted to bring this to your attention.
Mp3tag doesn’t show Encoded By for FLAC files outside of the Extended Tags dialog, which shows arbitrary name/value pairs determined by the tool that initially added the tags in question.
What’s actually creating the tag with that name? (If it’s Mp3tag, what are the actions to create it?)
ENCODEDBY is the standard field Mp3tag uses, which dopus cannot read. I have added ENCODED BY so that dopus can read it. Mp3tag maps it differently for different containers.
But not with VorbisComments:
Please note that fields of VorbisComments (used with FLAC, OGG, SPX) and of APEv2 tags are not mapped internally by Mp3tag but are displayed with their actual name unless they use a user-defined field mapping.
That's Mp3tag's internal name but I can't see anything anywhere saying it should be used within FLAC tags.
If I convert an MP3 with an Encoded By tag to FLAC using dbPowerAmp, the tag it writes is "ENCODED BY" with a space in, the same as Opus uses.
Same with foobar2000 doing the conversion, it outputs "ENCODED BY".
So I think "ENCODEDBY" is probably wrong here, and "ENCODED BY" is the defacto standard within FLAC tags, even if it is in a generic drop-down list within Mp3tag (which is not specific to FLAC tags).
If that's the case and you add ENCODED-BY (even though I think ENCODEDBY is more common next to ENCODED BY), you have to be consistent and add ENCODEDBY as well. And I'm sorry to say it, but I trust Mp3tag more than dopus when it comes to editing metadata.
I am okay with the status quo. I was reviewing some old music files and noticed that it didn't readily come up on the Dopus metadata window. I just need to make sure to stick with "ENCODED BY" as the standard for music files.
Thanks for looking into this, Leo.
Neither dbPowerAmp nor foobar2000 do that, and I consider those tools pretty much standard when it comes to FLAC tag support.
If someone can find a tool that converts from MP3 (or whatever) to FLAC and converts a standard Encoded By field in the MP3 into a tag name with no space, then I might be more convinced this is needed. Mp3tag having the tag name in a generic drop-down list doesn’t cut it for me; as it presumably offers the same list of extra tag names for all formats without doing anything specific for FLAC etc.
Yes, but it doesn't have to be, because the ENCODED BY field is a custom metadata field, and I wish Dopus would recognize these custom fields in the (far) future (without having to write a jscript*) to provide more flexibility.
I believe that ENCODED BY is not an official metadata field within a vorbiscomment tag at all and that someone simply added ENCODED BY because it matches other metadata like id3 by default and doesn't need to be mapped otherwise.
foobar2000 also shows the ENCODED BY field (which I have set in Dopus) as a user-defined field.
*All I need is a tutorial on how to extract a custom metadata field from a file using an Evalutor column.
There is no official vorbiscomment field for this tag, so whatever is used is going to be an "extra" tag.
But the defacto standard seems to be "ENCODED BY" not "ENCODEDBY", since that (and only that) is what both dbPowerAmp and Foobar2000 write when converting the "official" ID3v2 tag into a FLAC tag. So far no one has come up with any counterexamples. (Choosing "ENCODEDBY" by hand in Mp3tag doesn't count. You could choose literally anything there. The software itself isn't ever saying that ID3v2's encoded-by tag maps to ENCODEDBY in FLAC.)
Anything that has a problem with "ENCODED BY" is going to have problems with FLAC tags converted by at least three programs, and probably more. Although no examples have been given so far, any such software is what needs changing IMO, rather than changing Opus to use a non-standard tag name and (and get into the horrible business of writing the same tag to multiple values, which can then go out of sync if something else edits one but not the other, and then not knowing which one to give priority to when they're different... what you're asking for would make things worse, not better).
The possibility to add your own fields, which the specifications of vorbiscomment and ID3v2x allow, makes it worse?
Isn't that exactly why there is mapping for syncing the fields?
But let's leave it at that. There's no point in discussing further if you dismiss a suggestion for improvement as “worse, not better”. I can live with it and continue to use Mp3tag.
And I'm aware that your list is still very long, I don't mind if it takes a long time.
