[Abcde-users] FW: Abcde and aiff
Jason Miller
aidenn0 at geocities.com
Thu Apr 24 00:31:01 BST 2025
Dry Martini Holding Company 😎 <qrp at kg4kgl.net> writes:
> Sent from my iPhone
>
>> On Apr 22, 2025, at 20:05, Jason Miller <aidenn0 at geocities.com> wrote:
>>
>> Dry Martini Holding Company 😎 <qrp at kg4kgl.net> writes:
>>> Both the files that “work” and those that do not display properly, are both utf-32BE.
>> Did you mean UTF-16BE? ID3v2 doesn't specify a UTF-32 encoding; possible
>> values for the encoding are:
>>
>> $00 ISO-8859-1 [ISO-8859-1]. Terminated with $00.
>> $01 UTF-16 [UTF-16] encoded Unicode [UNICODE] with BOM. All
>> strings in the same frame SHALL have the same byteorder.
>> Terminated with $00 00.
>> $02 UTF-16BE [UTF-16] encoded Unicode [UNICODE] without BOM.
>> Terminated with $00 00.
>> $03 UTF-8 [UTF-8] encoded Unicode [UNICODE]. Terminated with $00.
>>
>> (source https://id3.org/id3v2.4.0-structure)
>>
>> -Jason
>
>
> I got those results from running the Perl script, encguess. I did not spend much time with this. So it may have guessed wrong.
It did guess wrong; encguess is for guessing the encoding of text-files,
so is not likely to work on binary files such as AIFF.
More information about the Abcde-users
mailing list