Zero duration for large WAV files (>7 hours (2,2 GB)) after save recording

[panchenkodv]

Package version 6.0.0

Environment

• OS: Android
• Browser [e.g. chrome, safari] if issue is on web platform.

Describe the bug

Broken headers on big wav files.

Add your record configuration RecordConfig(...)

const RecordConfig(
encoder: AudioEncoder.wav,
sampleRate: 44100,
numChannels: 1,
bitRate: 192000,
),

To Reproduce

Steps to reproduce the behavior:

1. Start recording with config given above in a file
2. Wait more than 7 hours
3. Stop the recording and save it.
4. File would have proper size, but in headers it would have 0 length. When you try to play it, you'll get 00:00:00 duration.

Expected behavior

File have proper duration.

Additional context

For files less than 2GB (<6,5 hours) everything is fine.
Also after using comand-line tool as sox like this
sox --ignore-length super_long_record_1760312595150.wav fixed_super_long_record_1760312595150.wav
fixed_super_long_record_1760312595150.wav is playable and contain all data which I record before.

[llfbandit]

Thanks for the report.

That's indeed big files!
Are you able to upload truncated files for both files (44 bytes or a bit more)? I only need the header to check what's wrong.

[panchenkodv]

Thanks for the report.

That's indeed big files! Are you able to upload truncated files for both files (44 bytes or a bit more)? I only need the header to check what's wrong.

Yes, sure. Here truncated file. (I've to zip it as broken wav file always fails to upload here)

truncated_.zip

[llfbandit]

I made an attempt to fix this issue.
I haven't tested it under your conditions though.

The following commit also contains potential improvement for RAM pressure (to be confirmed).

Commit caaaf6b in branch https://github.com/llfbandit/record/tree/wave

Feedback very welcome before releasing this.

[panchenkodv]

Hi! I've tested this fix on my Android app and looks like it doesn't help. I've the same issue on saving files bigger than 2 147 483 648 bytes. As I see this fix is for WEB recording, not for IOS and Android.

Also I want to know how do you deal with files over 4GB length? As I know this length does not fit into standard RIFF/WAVE header and those files should use RF64 header. I presume that now if I try to record file more than 4GB this file will be corrupted. Is it right?

[llfbandit]

Oh, I assumed that was on web platform... Anyway, web changes are good ones.
Whatever the platform, WAVE is limited to 4GB due to uint32, so 2^32. RF64 is not supported.
I'm on it to fix this on Android and truncate if necessary.

From your previous message, iOS is also targeted by this issue?

[panchenkodv]

I'm using Flutter for Android and IOS development, but have no chance to test it on IOS device, only on Android. I think that chance of same behavior on IOS is very high, but can't test it nearest future.

[llfbandit]

Fix on same branch. Feedback welcome.
Checked on iOS side, this should be OK. Processed directly with AVAudioRecorder.

[panchenkodv]

Hi! I've tested the fix on 2,5GB file and everything is working as expected! Thank you!

[llfbandit]

Thanks for the feedback.
I'll create a release soon.

[llfbandit]

Released in record_android 1.4.5

[panchenkodv]

Hi again! Have you created release record_android 1.4.5?

[llfbandit]

Yes https://pub.dev/packages/record_android/changelog

[panchenkodv]

Oh, sorry. I've tried to find tag 1.4.5 on github here. My bad, wrong place. Thank you!