High ISO needs more HW resource

Started by miyake, September 05, 2012, 08:54:46 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

miyake

Is this a well known things?
I just understand it.

CBR 3.0 + ISO3200 = recording stop immediately
CBR 2.6 + ISO3200 = recording stop immediately
CBR 2.4 + ISO3200 = sometime recording stop
CBR 1.0 + ISO 3200 = no problem

CBR 3.0 + ISO200 = no problem
Then push ISO button and ISO change dynamically, will recording stop when we changed to over ISO 1600

a1ex

The noise is considered detail and requires higher bitrate.

nanomad

Right
A simple test is to compare the bitrate of ml vs Canon iso 500. On dark scenes I found Canon to be more noisy and with a higher bitrate
EOS 1100D | EOS 650 (No, I didn't forget the D) | Ye Olde Canon EF Lenses ('87): 50 f/1.8 - 28 f/2.8 - 70-210 f/4 | EF-S 18-55 f/3.5-5.6 | Metz 36 AF-5

miyake

Thank you for your explaining.
Anyway, CBR is not Constant bitrate. We can't set maximum bitrate for CBR. right?

a1ex

CBR is maximum bitrate (not per frame, but with some kind of averaging). I think the process goes like this:

- record frame 1 with some fixed QScale
- see what frame size it got
- compute QScale for frame 2, according to CBR factor and other settings
- record frame 2 with this QScale
- repeat

miyake