This is niggling me now. I still don't need lame to write v2 tags,
because the id3v2 utility does what I need, but I'm puzzled that I can't
get a fairly long-standing feature of lame to work. I wonder if anyone
else can reproduce what I'm seeing.
My test cases are in the post above. In short, lame seems to create a
v2 tag, but the id3v2 utility reports it as a blank tag.
I've dug a little deeper since that post, and have used a hex editor to
look at the content of the TPE1 field, and it is indeed empty. So that
rules out the possibility that the id3v2 utility is unable to read the
lame tag properly - the text I've specified on the lame command line
just isn't in the file.
I've tried various things, such as enclosing the tag in quotes, changing
the character encoding (latin, UTF16), padding the tag field, both v2
options ('--id3v2-only' and '--add-id3v2'), and nothing seems to work.
The same command line that successful writes a v1 tag into the file
(with --add-id3v2) doesn't put anything in the TPE1 field when either of
the v2 options is specified.
I did notice in some online documentation that the '--id3v2-only' flag
has to come before any other tagging options, but that makes no
difference to the outcome.
I find this odd, since the v2 tagging option has been around for a
while, and Ralphy has said he's used it successfully. So is there
something about the 64-bit piCore environment on a Pi4 that is causing
this problem? I guess I could try it on one of my other Pis to test
that possibility.
------------------------------------------------------------------------
chill's Profile: http://forums.slimdevices.com/member.php?userid=10839
View this thread: http://forums.slimdevices.com/showthread.php?t=111997
_______________________________________________
ripping mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/ripping
