Skip to content

Increase maximum AVI frame limit#3

Open
rubiefawn wants to merge 2 commits into
hfiggs:mainfrom
rubiefawn:fix/avi-max-frames
Open

Increase maximum AVI frame limit#3
rubiefawn wants to merge 2 commits into
hfiggs:mainfrom
rubiefawn:fix/avi-max-frames

Conversation

@rubiefawn
Copy link
Copy Markdown

There was previously an arbitrary limit of 100,000 frames on the length of captured video. The actual data type of this configurable limit is a 32-bit unsigned integer, so the maximum value has been raised to the maximum 32-bit unsigned integer value instead.

Some other things that were supposed to be 32-bit unsigned integers were for some reason signed integers instead, so their types have been fixed as well.

Resolves #2.

There was previously an arbitrary limit of 100,000 frames. The actual
data type should be a 32-bit unsigned integer, so the limit has been
raised to the maximum 32-bit unsigned integer value instead.

Some other things that were supposed to be 32-bit unsigned integers were
for some reason 32-bit signed integers instead, so their types have been
fixed as well.
Comment thread CaptureCfg.cpp Outdated
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

AVI file size limitation and unintended video segmentation

1 participant