I ran the same test on an Ubuntu 18.04.1 LTS 64-bit Macbook, and the
same commands now work as expected, i.e. the --id3v3-only flag results
in a v2 tag that contains my text and is correctly read by the id3v2
utility.
Code:
--------------------
chris@chris-MacBook:~/Documents$ lame *--id3v2-only --ta lameartist*
test.MP3 testout.MP3
LAME 3.100 64bits (http://lame.sf.net)
Using polyphase lowpass filter, transition band: 16538 Hz - 17071 Hz
Encoding test.MP3 to testout.MP3
Encoding as 44.1 kHz j-stereo MPEG-1 Layer III (11x) 128 kbps qval=3
Frame | CPU time/estim | REAL time/estim | play/CPU | ETA
8768/8768 (100%)| 0:10/ 0:10| 0:10/ 0:10| 21.038x| 0:00
-------------------------------------------------------------------------------
kbps LR MS % long switch short %
128.0 13.9 86.1 96.9 1.8 1.3
Writing LAME Tag...done
ReplayGain: -8.6dB
chris@chris-MacBook:~/Documents$ id3v2 -l testout.MP3
id3v2 tag info for testout.MP3:
TSSE (Software/Hardware and settings used for encoding): LAME 64bits version
3.100 (http://lame.sf.net)
TPE1 (LEAD PERFORMER(S)/SOLOIST(S)): LAMEARTIST
TLEN (Length): 229000
testout.MP3: No ID3v1 tag
--------------------
So it looks like a quirk of the pCP lame utility that's causing these
blank tags to be written. Could it be something to do with the build
configuration?
I also noticed that the transcoding task was much faster on the Macbook
than on my Pi4 (10 seconds versus 51 seconds). That was a bit of a
surprise - I thought the 1.5GHz quad core Pi4 was closer to the 2.4GHz
Core 2 Duo 2008 Macbook than that factor of 5 suggests. Could it be due
to the fact that the lame build on the Macbook is 64-bit, and on pCP it
is 32-bit?
------------------------------------------------------------------------
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
