capture fails after 4 GB

Status: Abandoned

Brought to you by: dimmman, meag

#520 capture fails after 4 GB

Milestone: 3.0

Status: closed-fixed

Owner: nobody

Labels: Capturing (3)

Priority: 5

Updated: 2018-08-01

Created: 2011-12-11

Creator: Floris

Private: No

after about 12000 frames it corrupts the rest of the cature process while the filesize of the video still increases but the video will restart...

I really need this... capturing as image sequence will take nearly 24 hours and a 70GB of space so also not a workaround for me.

I used 900fps (so i can add smooth motionblur afterwards)

Discussion

Floris - 2011-12-13

Also

loading in virtualdub it said:
AVI: Index not found or damaged - recontructing via file scan.
AVI: Keyframe flag reconstruction was not specified in open options and the video stream is not a kneon keyframe-only type. Seeking the video stream may be extremely slow.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Floris - 2011-12-13

I used ffdshow ascodec
(and btw... its totally unclear which codecs ezquake supports)

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Floris - 2011-12-13

okay, there is no frame number where things go wrong.

It's after the video file exceeds 4 GB

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Floris - 2011-12-13

(repairing in virtualdub only can correct the keyframs but while it does make it allow the video file to be opepened by my video editor, the part after 4GB still remains corrupt/black)

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Floris - 2011-12-13

sidenote: I do have 4 GB ram installed but a quick look at windows taskmanager it shows ezquake doesnt eat ram while capturing.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Floris - 2011-12-14

so....to sum it all up: after filesize exceeds 2 GB the video gets the keyframe problems, and after 4 GB the rest of the video will be lost.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

JohnNy_cz - 2011-12-14

Thanks a lot for the extensive info. This sounds like a 32-bit signed integer overflow problem.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Floris - 2011-12-14

summary: capture fails after 12000 frames --> capture fails after 4 GB - (and gets bugged after 2 GB)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

JohnNy_cz - 2011-12-14

summary: capture fails after 4 GB - (and gets bugged after 2 GB) --> capture fails after 12000 frames
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

JohnNy_cz - 2011-12-14

"If you decide to capture in AVI format before encoding, you need to be aware of the 2 GB file limitation. The original AVI format specification required that hardware and software tools built to that specification support AVI files that are smaller than 2 GB. The specification was changed to allow files that are larger than 2 GB, but some of the hardware and software tools that support the AVI format do not yet support this updated specification. This AVI format is often called AVI Type II or extended AVI."

It should be investigated whether we can use the updated functionality of Windows Media API.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Floris - 2011-12-15

summary: capture fails after 12000 frames --> capture fails after 4 GB
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

dimman - 2013-12-03

Group: --> 3.0
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

meag - 2018-08-01

status: open --> closed-fixed
If you would like to refer to this comment somewhere else in this project, copy and paste the following link: