[Bug]: File size too large

[anukulKun]

Search existing issues

• I have searched the existing issues

Describe the bug

Expected behavior

It should have render.

To Reproduce

No response

Screenshots

OS

None

OS Version

No response

Other OS

No response

Additional context

No response

[Arianw14]

Yes experiencing same bug again and again , hate it.

[ExtraBinoss]

What version of Recordly are you using, I think it was fixed in 1.3.0 beta ?

[Arianw14]

I just downloaded one week ago from here.

[ExtraBinoss]

I just downloaded one week ago from here.

Yes this was most likely 1.2.0/1.2.1, you can see it after the recording button in HUD ("...") and go down to see the actual version.

A new version will be coming soon to fix this issue, 1.3.0 beta is already in testing and we will have some great news soon !

[TafadzwaD]

I just downloaded one week ago from here.

Yes this was most likely 1.2.0/1.2.1, you can see it after the recording button in HUD ("...") and go down to see the actual version.

A new version will be coming soon to fix this issue, 1.3.0 beta is already in testing and we will have some great news soon !

I am still experiencing the same issue, on the 1.3.0 beta (MacOs)

[bebuilder]

现在正在遇到这个问题，要怎么办才能导出

[meiiie]

Update after checking current main: #404 is already merged and covers the output-side >2 GiB mux/save path. #520 is the remaining candidate for a different path: reading a >2 GiB source recording through read-local-file during export metadata/fallback handling.

For now, the practical workaround is still to keep the source recording under 2 GiB: use a shorter take, lower resolution/frame rate if available, or split the recording before export. I left a review-aid note on #520 because the fix should avoid buffering the entire source file in memory.