Size limitations of WAV container

[YourMJK]

Just something else that came to mind regarding long/large input files:

As I understand it, the MXV format uses 64bit offsets for audio.
But the WAV container uses a 32bit field for encoding the file size in the header which limits its maximum size to 4GiB (2^32-1 B).
I've also seen some programs breaking at 2GiB, probably because they are interpreting it as a signed integer (2^31-1 B).

For 48kHz, stereo, 16bit audio this means a maximum of ~6.2h (or ~3.1h for signed integers).
For 48kHz, stereo, 24bit it's ~4.1h (~2.1h).

I don't have an issue with this personally, my MXV files are unlikely to ever be that long.
So no need in fixing this ;)

But I thought this might be something that should be documented somewhere, maybe also with a warning during execution.

[YourMJK]

Of course, I one would want to fix this, the simplest solution would be to just split the audio and create multiple WAV output files if necessary.

Alternatively, a different container format supporting PCM audio larger than 4GiB could be used, like

• RF64 (extension of WAVE)
• CAF
• MOV (MP4 does not support PCM)
• MKV (with .mka extension)

But I doubt someone will ever run into this issue, so these solutions are probably unnecessary/overkill.

[Dadido3]

Yes, this is a valid point.

The best solution would be to offer different containers, and using some sane default that's well supported and doesn't have such limits.

Alternatively i thought about remuxing the video and audio data directly into a MKV or similar video container. This would eliminate the need for the intermediate JPEG and audio files alltogether.