Skip to main content

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: 'Bug' report / feature request for the 'File Integrity Verifier' extension (Read 1116 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

'Bug' report / feature request for the 'File Integrity Verifier' extension

While playing around with ffmpeg and looking for a format to store large uncompressed audio files over 4 GiB, I happened to find a small problem with the RF64 format (a subset of BWF).

It looks like the 'ds64' extension in the header for files over 4 GiB of the RF64 format has not been taken into account yet.?

Currently in use under Windows 10:
Quote
Core (2023-01-13 20:48:54 UTC)
    foobar2000 core 1.6.16
foo_verifier.dll (2022-02-06 21:40:24 UTC)
    File Integrity Verifier 1.4.2

To reproduce:
Code: [Select]
>ffmpeg -f lavfi -i sine -t 50ms -c:a pcm_s16le -rf64 1 -y 50ms.wav

>hexyl -c 0x80 50ms.wav // (original header from ffmpeg output)
Code: [Select]
┌────────┬─────────────────────────┬─────────────────────────┬────────┬────────┐
│00000000│ 52 46 36 34 ff ff ff ff ┊ 57 41 56 45 64 73 36 34 │RF64××××┊WAVEds64│
│00000010│ 1c 00 00 00 a4 11 00 00 ┊ 00 00 00 00 3a 11 00 00 │•⋄⋄⋄ו⋄⋄┊⋄⋄⋄⋄:•⋄⋄│
│00000020│ 00 00 00 00 9d 08 00 00 ┊ 00 00 00 00 00 00 00 00 │⋄⋄⋄⋄ו⋄⋄┊⋄⋄⋄⋄⋄⋄⋄⋄│
│00000030│ 66 6d 74 20 10 00 00 00 ┊ 01 00 01 00 44 ac 00 00 │fmt •⋄⋄⋄┊•⋄•⋄D×⋄⋄│
│00000040│ 88 58 01 00 02 00 10 00 ┊ 4c 49 53 54 1a 00 00 00 │×X•⋄•⋄•⋄┊LIST•⋄⋄⋄│
│00000050│ 49 4e 46 4f 49 53 46 54 ┊ 0d 00 00 00 4c 61 76 66 │INFOISFT┊_⋄⋄⋄Lavf│
│00000060│ 36 30 2e 33 2e 31 30 30 ┊ 00 00 64 61 74 61 ff ff │60.3.100┊⋄⋄data××│
│00000070│ ff ff 00 00 00 01 ff 01 ┊ fd 02 f8 03 ee 04 e0 05 │××⋄⋄⋄•×•┊וווו│
└────────┴─────────────────────────┴─────────────────────────┴────────┴────────┘

>hexyl -c 0x80 50ms-edited.wav // ('RF64'$filesize ... 'data'$datasize)
Code: [Select]
┌────────┬─────────────────────────┬─────────────────────────┬────────┬────────┐
│00000000│ 52 46 36 34 a4 11 00 00 ┊ 57 41 56 45 64 73 36 34 │RF64ו⋄⋄┊WAVEds64│
│00000010│ 1c 00 00 00 a4 11 00 00 ┊ 00 00 00 00 3a 11 00 00 │•⋄⋄⋄ו⋄⋄┊⋄⋄⋄⋄:•⋄⋄│
│00000020│ 00 00 00 00 9d 08 00 00 ┊ 00 00 00 00 00 00 00 00 │⋄⋄⋄⋄ו⋄⋄┊⋄⋄⋄⋄⋄⋄⋄⋄│
│00000030│ 66 6d 74 20 10 00 00 00 ┊ 01 00 01 00 44 ac 00 00 │fmt •⋄⋄⋄┊•⋄•⋄D×⋄⋄│
│00000040│ 88 58 01 00 02 00 10 00 ┊ 4c 49 53 54 1a 00 00 00 │×X•⋄•⋄•⋄┊LIST•⋄⋄⋄│
│00000050│ 49 4e 46 4f 49 53 46 54 ┊ 0d 00 00 00 4c 61 76 66 │INFOISFT┊_⋄⋄⋄Lavf│
│00000060│ 36 30 2e 33 2e 31 30 30 ┊ 00 00 64 61 74 61 3a 11 │60.3.100┊⋄⋄data:•│
│00000070│ 00 00 00 00 00 01 ff 01 ┊ fd 02 f8 03 ee 04 e0 05 │⋄⋄⋄⋄⋄•×•┊וווו│
└────────┴─────────────────────────┴─────────────────────────┴────────┴────────┘

The report of the 'File Integrity Verifier' extension:
(file paths were edited)
Quote
Item: "...\50ms.wav"
MD5: 42F0F8D38589A2DA783DA2D743F40E67
CRC32: A3048DE1
Warning: Indicated RIFF size exceeds actual file size, file appears to be truncated
Warning: Malformed or truncated chunk found at 106 bytes, claimed length 4294967295 bytes, truncated to 4410 bytes

Item: "...\50ms-edited.wav"
MD5: 42F0F8D38589A2DA783DA2D743F40E67
CRC32: A3048DE1
No problems found.


All items decoded successfully.
1 item decoded with minor problems.

List of decodable but suspicious items:
"...\50ms.wav"

I have looked around a bit and found this about the RF64 format:
https://en.wikipedia.org/wiki/RF64

The last and updated recommendation for RF64 (subgroup of BWF), nicely titled:
'Long-form file format for the international exchange of audio programme materials with metadata'
Page #7 (self numbered as 5)
https://www.itu.int/dms_pubrec/itu-r/rec/bs/R-REC-BS.2088-1-201910-I!!PDF-E.pdf
(Thanks to the good output I could then get from the 4294967295 bytes (0xffff ffff) to the -1 as Int.)

and here also in other languages:
https://www.itu.int/rec/R-REC-BS.2088-1-201910-I/en

Sorry, it almost became a short novel. (;

Thank you and best regards.

PS: And of course thanks for the time and the wonderful player foobar2000 with its solid features and all its extensions.

Re: 'Bug' report / feature request for the 'File Integrity Verifier' extension

Reply #1
Here again a small update:

Uhm, not beautiful. It seems that ffmpeg then writes over 4 GiB only a very reduced header.

Unfortunately I had not tested this before, sorry for that.

But the good news is that the test is terminated without warning by the extension.

Quote
Item: "...\elbe.wav"
MD5: 6DC380B07E4662984DB5C2978AC0A32E
CRC32: 0AEA206A
No problems found.

Quote
File name : elbe.wav
File size : 12.1 GB (13 022 402 706 bytes)
Duration : 18:50:25.014 (3 255 600 648 samples)
Sample rate : 48000 Hz
Channels : 2
Bits per sample : 16
Bitrate : 1536 kbps
Codec : PCM
Encoding : lossless

>hexyl -c 0x200 elbe.wav
Code: [Select]
┌────────┬─────────────────────────┬─────────────────────────┬────────┬────────┐
│00000000│ 52 46 36 34 ff ff ff ff ┊ 57 41 56 45 64 73 36 34 │RF64××××┊WAVEds64│
│00000010│ 1c 00 00 00 8a 18 32 08 ┊ 03 00 00 00 20 18 32 08 │•⋄⋄⋄ו2•┊•⋄⋄⋄ •2•│
│00000020│ 03 00 00 00 08 86 0c c2 ┊ 00 00 00 00 00 00 00 00 │•⋄⋄⋄•×_×┊⋄⋄⋄⋄⋄⋄⋄⋄│
│00000030│ 66 6d 74 20 10 00 00 00 ┊ 01 00 02 00 80 bb 00 00 │fmt •⋄⋄⋄┊•⋄•⋄××⋄⋄│
│00000040│ 00 ee 02 00 04 00 10 00 ┊ 4c 49 53 54 1a 00 00 00 │⋄ו⋄•⋄•⋄┊LIST•⋄⋄⋄│
│00000050│ 49 4e 46 4f 49 53 46 54 ┊ 0d 00 00 00 4c 61 76 66 │INFOISFT┊_⋄⋄⋄Lavf│
│00000060│ 36 30 2e 33 2e 31 30 30 ┊ 00 00 64 61 74 61 ff ff │60.3.100┊⋄⋄data××│
│00000070│ ff ff 00 00 00 00 00 00 ┊ 00 00 00 00 00 00 00 00 │××⋄⋄⋄⋄⋄⋄┊⋄⋄⋄⋄⋄⋄⋄⋄│
│00000080│ 00 00 00 00 00 00 00 00 ┊ 00 00 00 00 00 00 00 00 │⋄⋄⋄⋄⋄⋄⋄⋄┊⋄⋄⋄⋄⋄⋄⋄⋄│
│*       │                         ┊                         │        ┊        │
│00000200│                         ┊                         │        ┊        │
└────────┴─────────────────────────┴─────────────────────────┴────────┴────────┘

Attached are the first 256 bytes of the header as rf64-wav-header-of-a-lage-file.bin

I hope I didn't waste too much of your time. ):

With best regards.

Re: 'Bug' report / feature request for the 'File Integrity Verifier' extension

Reply #2
I don't know if the attached files are actually valid BWF/RF64, but WavPack handles them just fine, and WavPack has a habit of doing things right.

fb2k's integrity verifier is not that happy.

Files are 32-channel sine, 10 seconds, got them from
https://www.lynxstudio.com/downloads/aurora-n/sample-wav-file-zip-encoded-1khz-sine-wave-32-channels-44-1khz-bwf/
https://www.lynxstudio.com/downloads/aurora-n/sample-wav-file-zip-encoded-96khz-pcm-24-32-channels-rf64/
and xz'ed them down to virtually nothing.

Re: 'Bug' report / feature request for the 'File Integrity Verifier' extension

Reply #3
Acknowledged, thanks for reporting.
Microsoft Windows: We can't script here, this is bat country.

Re: 'Bug' report / feature request for the 'File Integrity Verifier' extension

Reply #4
Acknowledged, thanks for reporting.

Thank you for your work and time. All my RF64s have passed the integrity test of the files with the current beta of Foobar2000. (foobar2000 2.1 preview 2023-11-27 - 32bit)

The following refers to the above mentioned version with a fresh installation of the 32bit edition (foobar2000 2.1 preview 2023-11-27 - 32bit):
While playing around, I discovered a few problems with the Wav decoder, Foobar's internal type recognition, the integrity test and the tag transfer.
This mainly concerns the problem with the 4-GiB limit of wave files. The decoder seems to recognise the limit quite late (sometimes only when it wants to transfer the tags) or the files are converted correctly at the edge of the 4 GiB limit, but Foobar does not recognise the file as valid.

Code: [Select]
Core (2023-11-27 14:59:50 UTC)
    foobar2000 core 2.1 preview 2023-11-27
foo_converter (2023-11-27 15:00:20 UTC)
    Converter 2.1 preview 2023-11-27
foo_devconsole (2014-02-09 23:19:28 UTC)
    DevConsole 1.0.4async
foo_ui_std (2023-11-27 15:00:02 UTC)
    Album List 2.1 preview 2023-11-27
    Decoding Speed Test 2.1 preview 2023-11-27
    Default User Interface 2.1 preview 2023-11-27
    File Integrity Verifier 2.1 preview 2023-11-27


Only for quick comparison between dec and hex:
4.294.967.295 bytes = 0xffff_ffff = 4GiB

:: Will be fine on recognition and format validation.
Code: [Select]
>ffmpeg -y -hide_banner -report -f lavfi -i anullsrc=r=48000:cl=stereo:d=22369 -metadata artist="artist" f22369.wav
>sfk list -size f22369.wav & hexyl f22369.wav
  4294848094 f22369.wav
┌────────┬─────────────────────────┬─────────────────────────┬────────┬────────┐
│00000000│ 52 49 46 46 56 2e fe ff ┊ 57 41 56 45 66 6d 74 20 │RIFFV.××┊WAVEfmt │
│00000010│ 10 00 00 00 01 00 02 00 ┊ 80 bb 00 00 00 ee 02 00 │•⋄⋄⋄•⋄•⋄┊××⋄⋄⋄ו⋄│
│00000020│ 04 00 10 00 4c 49 53 54 ┊ 2a 00 00 00 49 4e 46 4f │•⋄•⋄LIST┊*⋄⋄⋄INFO│
│00000030│ 49 41 52 54 07 00 00 00 ┊ 61 72 74 69 73 74 00 00 │IART•⋄⋄⋄┊artist⋄⋄│
│00000040│ 49 53 46 54 0e 00 00 00 ┊ 4c 61 76 66 36 30 2e 31 │ISFT•⋄⋄⋄┊Lavf60.1│
│00000050│ 36 2e 31 30 30 00 64 61 ┊ 74 61 00 2e fe ff 00 00 │6.100⋄da┊ta⋄.××⋄⋄│
│00000060│ 00 00 00 00 00 00 00 00 ┊ 00 00 00 00 00 00 00 00 │⋄⋄⋄⋄⋄⋄⋄⋄┊⋄⋄⋄⋄⋄⋄⋄⋄│
│*       │                         ┊                         │        ┊        │
│fffe2e50│ 00 00 00 00 00 00 00 00 ┊ 00 00 00 00 00 00       │⋄⋄⋄⋄⋄⋄⋄⋄┊⋄⋄⋄⋄⋄⋄  │
└────────┴─────────────────────────┴─────────────────────────┴────────┴────────┘

:: Wav Converter w/o Tag transfer
:: "Track converted successfully.", but the technically intact Wav file is not recognised by Foobar.
Code: [Select]
>ffmpeg -y -hide_banner -report -f lavfi -i anullsrc=r=48000:cl=stereo:d=22369.620729 ffffffb8.flac
>sfk list -size ffffffb8.flac ffffffb8.wav & hexyl ffffffb8.wav
     3901867 ffffffb8.flac
  4294967224 ffffffb8.wav
┌────────┬─────────────────────────┬─────────────────────────┬────────┬────────┐
│00000000│ 52 49 46 46 b0 ff ff ff ┊ 57 41 56 45 66 6d 74 20 │RIFF××××┊WAVEfmt │
│00000010│ 10 00 00 00 01 00 02 00 ┊ 80 bb 00 00 00 ee 02 00 │•⋄⋄⋄•⋄•⋄┊××⋄⋄⋄ו⋄│
│00000020│ 04 00 10 00 64 61 74 61 ┊ 8c ff ff ff 00 00 00 00 │•⋄•⋄data┊××××⋄⋄⋄⋄│
│00000030│ 00 00 00 00 00 00 00 00 ┊ 00 00 00 00 00 00 00 00 │⋄⋄⋄⋄⋄⋄⋄⋄┊⋄⋄⋄⋄⋄⋄⋄⋄│
│*       │                         ┊                         │        ┊        │
│ffffffb0│ 00 00 00 00 00 00 00 00 ┊                         │⋄⋄⋄⋄⋄⋄⋄⋄┊        │
└────────┴─────────────────────────┴─────────────────────────┴────────┴────────┘

:: filesize of decoded wav on the 4GiB edge
:: internal wav decoder (without tags) say sucessful, but detetion of wav messed up
Quote
No problems occurred.

Source: "\/replaced\/\4g-edge.flac"
  Destination: "\/replaced\/\4g-edge.wav"
  Track converted successfully.
Code: [Select]
>ffmpeg -y -hide_banner -report -f lavfi -i anullsrc=r=48000:cl=stereo:d=22369.621094 -metadata artist="on the edge" 4g-edge.flac
>sfk list -size 4g-edge.flac 4g-edge.wav & hexyl 4g-edge.wav
     3901887 4g-edge.flac
  4294967296 4g-edge.wav
┌────────┬─────────────────────────┬─────────────────────────┬────────┬────────┐
│00000000│ 52 49 46 46 f8 ff ff ff ┊ 57 41 56 45 66 6d 74 20 │RIFF××××┊WAVEfmt │
│00000010│ 10 00 00 00 01 00 02 00 ┊ 80 bb 00 00 00 ee 02 00 │•⋄⋄⋄•⋄•⋄┊××⋄⋄⋄ו⋄│
│00000020│ 04 00 10 00 64 61 74 61 ┊ d4 ff ff ff 00 00 00 00 │•⋄•⋄data┊××××⋄⋄⋄⋄│
│00000030│ 00 00 00 00 00 00 00 00 ┊ 00 00 00 00 00 00 00 00 │⋄⋄⋄⋄⋄⋄⋄⋄┊⋄⋄⋄⋄⋄⋄⋄⋄│
│*       │                         ┊                         │        ┊        │
│0100000000│                         ┊                         │        ┊        │
└────────┴─────────────────────────┴─────────────────────────┴────────┴────────┘


>ffmpeg -y -hide_banner -report -f lavfi -i anullsrc=r=48000:cl=stereo:d=22369.621093 -metadata artist="maybe on the edge" 4g-lower-edge.flac

:: converting flac to wav with internal converter w/o tag transfer
Quote
Converting: "\/replaced\/\4g-lower-edge.flac"
Destination: "\/replaced\/\4g-lower-edge.wav"
Track converted successfully.
Code: [Select]
>sfk list -size 4g-lower-edge.flac 4g-lower-edge.wav & hexyl 4g-lower-edge.wav
     3901893 4g-lower-edge.flac
  4294967292 4g-lower-edge.wav
┌────────┬─────────────────────────┬─────────────────────────┬────────┬────────┐
│00000000│ 52 49 46 46 f4 ff ff ff ┊ 57 41 56 45 66 6d 74 20 │RIFF××××┊WAVEfmt │
│00000010│ 10 00 00 00 01 00 02 00 ┊ 80 bb 00 00 00 ee 02 00 │•⋄⋄⋄•⋄•⋄┊××⋄⋄⋄ו⋄│
│00000020│ 04 00 10 00 64 61 74 61 ┊ d0 ff ff ff 00 00 00 00 │•⋄•⋄data┊××××⋄⋄⋄⋄│
│00000030│ 00 00 00 00 00 00 00 00 ┊ 00 00 00 00 00 00 00 00 │⋄⋄⋄⋄⋄⋄⋄⋄┊⋄⋄⋄⋄⋄⋄⋄⋄│
│*       │                         ┊                         │        ┊        │
│fffffff0│ 00 00 00 00 00 00 00 00 ┊ 00 00 00 00             │⋄⋄⋄⋄⋄⋄⋄⋄┊⋄⋄⋄⋄    │
└────────┴─────────────────────────┴─────────────────────────┴────────┴────────┘

:: converting flac to wav with internal converter with tag transfer
:: (tags are not transferred)
Quote
Converting: "\/replaced\/\4g-lower-edge.flac"
Destination: "\/replaced\/\4g-lower-edge-with-tags.wav"
An error occurred while finalizing the encoding process (Unsupported format or corrupted file) : "\/replaced\/\4g-lower-edge-with-tags.wav"
Conversion failed: Unsupported format or corrupted file
Code: [Select]
>sfk list -size 4g-lower-edge.flac 4g-lower-edge-with-tags.wav & hexyl 4g-lower-edge-with-tags.wav
     3901893 4g-lower-edge.flac
  4294967292 4g-lower-edge-with-tags.wav
┌────────┬─────────────────────────┬─────────────────────────┬────────┬────────┐
│00000000│ 52 49 46 46 f4 ff ff ff ┊ 57 41 56 45 66 6d 74 20 │RIFF××××┊WAVEfmt │
│00000010│ 10 00 00 00 01 00 02 00 ┊ 80 bb 00 00 00 ee 02 00 │•⋄⋄⋄•⋄•⋄┊××⋄⋄⋄ו⋄│
│00000020│ 04 00 10 00 64 61 74 61 ┊ d0 ff ff ff 00 00 00 00 │•⋄•⋄data┊××××⋄⋄⋄⋄│
│00000030│ 00 00 00 00 00 00 00 00 ┊ 00 00 00 00 00 00 00 00 │⋄⋄⋄⋄⋄⋄⋄⋄┊⋄⋄⋄⋄⋄⋄⋄⋄│
│*       │                         ┊                         │        ┊        │
│fffffff0│ 00 00 00 00 00 00 00 00 ┊ 00 00 00 00             │⋄⋄⋄⋄⋄⋄⋄⋄┊⋄⋄⋄⋄    │
└────────┴─────────────────────────┴─────────────────────────┴────────┴────────┘

Thank you and best regards.

##################
Informative part, in case anyone is interested in how the flac decoder reacts.
And two hexdump's of RF64 files (flac vs. ffmpeg), which are also recognised correctly by Foobar2000.

Code: [Select]
>flac -s -d --force-legacy-wave-format 4g-lower-edge.flac & flac -s -d --force-extensible-wave-format 4g-lower-edge.flac
4g-lower-edge.flac: ERROR: stream is too big to fit in a single WAVE file
4g-lower-edge.flac: ERROR: stream is too big to fit in a single WAVE file
Code: [Select]
>flac -s -d --force-rf64-format 4g-lower-edge.flac
>sfk list -size 4g-lower-edge.flac 4g-lower-edge.rf64 & hexyl 4g-lower-edge.rf64
     3901893 4g-lower-edge.flac
  4294967328 4g-lower-edge.rf64
┌────────┬─────────────────────────┬─────────────────────────┬────────┬────────┐
│00000000│ 52 46 36 34 ff ff ff ff ┊ 57 41 56 45 64 73 36 34 │RF64××××┊WAVEds64│
│00000010│ 1c 00 00 00 18 00 00 00 ┊ 01 00 00 00 d0 ff ff ff │•⋄⋄⋄•⋄⋄⋄┊•⋄⋄⋄××××│
│00000020│ 00 00 00 00 f4 ff ff 3f ┊ 00 00 00 00 00 00 00 00 │⋄⋄⋄⋄×××?┊⋄⋄⋄⋄⋄⋄⋄⋄│
│00000030│ 66 6d 74 20 10 00 00 00 ┊ 01 00 02 00 80 bb 00 00 │fmt •⋄⋄⋄┊•⋄•⋄××⋄⋄│
│00000040│ 00 ee 02 00 04 00 10 00 ┊ 64 61 74 61 ff ff ff ff │⋄ו⋄•⋄•⋄┊data××××│
│00000050│ 00 00 00 00 00 00 00 00 ┊ 00 00 00 00 00 00 00 00 │⋄⋄⋄⋄⋄⋄⋄⋄┊⋄⋄⋄⋄⋄⋄⋄⋄│
│*       │                         ┊                         │        ┊        │
│0100000020│                         ┊                         │        ┊        │
└────────┴─────────────────────────┴─────────────────────────┴────────┴────────┘
Code: [Select]
>ffmpeg -y -hide_banner -report:level32 -i 4g-lower-edge.flac -rf64 always doit.wav
>sfk list -size doit.wav & hexyl doit.wav
  4294967388 doit.wav
┌────────┬─────────────────────────┬─────────────────────────┬────────┬────────┐
│00000000│ 52 46 36 34 ff ff ff ff ┊ 57 41 56 45 64 73 36 34 │RF64××××┊WAVEds64│
│00000010│ 1c 00 00 00 54 00 00 00 ┊ 01 00 00 00 d0 ff ff ff │•⋄⋄⋄T⋄⋄⋄┊•⋄⋄⋄××××│
│00000020│ 00 00 00 00 f4 ff ff 3f ┊ 00 00 00 00 00 00 00 00 │⋄⋄⋄⋄×××?┊⋄⋄⋄⋄⋄⋄⋄⋄│
│00000030│ 66 6d 74 20 10 00 00 00 ┊ 01 00 02 00 80 bb 00 00 │fmt •⋄⋄⋄┊•⋄•⋄××⋄⋄│
│00000040│ 00 ee 02 00 04 00 10 00 ┊ 4c 49 53 54 34 00 00 00 │⋄ו⋄•⋄•⋄┊LIST4⋄⋄⋄│
│00000050│ 49 4e 46 4f 49 41 52 54 ┊ 12 00 00 00 6d 61 79 62 │INFOIART┊•⋄⋄⋄mayb│
│00000060│ 65 20 6f 6e 20 74 68 65 ┊ 20 65 64 67 65 00 49 53 │e on the┊ edge⋄IS│
│00000070│ 46 54 0e 00 00 00 4c 61 ┊ 76 66 36 30 2e 31 36 2e │FT•⋄⋄⋄La┊vf60.16.│
│00000080│ 31 30 30 00 64 61 74 61 ┊ ff ff ff ff 00 00 00 00 │100⋄data┊××××⋄⋄⋄⋄│
│00000090│ 00 00 00 00 00 00 00 00 ┊ 00 00 00 00 00 00 00 00 │⋄⋄⋄⋄⋄⋄⋄⋄┊⋄⋄⋄⋄⋄⋄⋄⋄│
│*       │                         ┊                         │        ┊        │
│0100000050│ 00 00 00 00 00 00 00 00 ┊ 00 00 00 00             │⋄⋄⋄⋄⋄⋄⋄⋄┊⋄⋄⋄⋄    │
└────────┴─────────────────────────┴─────────────────────────┴────────┴────────┘

Re: 'Bug' report / feature request for the 'File Integrity Verifier' extension

Reply #5
RF64 issue that might be ffmpeg:
fb2k doesn't seem to be happy with ffmpeg-generated RF64 that contain floating-point PCM. An example uploaded at https://hydrogenaud.io/index.php/topic,123862.msg1036400.html#msg1036400

@Decaf5192 that might be relevant to you as well?

 

Re: 'Bug' report / feature request for the 'File Integrity Verifier' extension

Reply #6
RF64 issue that might be ffmpeg:
fb2k doesn't seem to be happy with ffmpeg-generated RF64 that contain floating-point PCM. An example uploaded at https://hydrogenaud.io/index.php/topic,123862.msg1036400.html#msg1036400

@Decaf5192 that might be relevant to you as well?


Not RF64, BW64. Which isn't RF64 even if the Wikipedia page says so. Corrections over in that thread. My bad.