Hi @Rammstein

The video was shot in 24H using Standard film setting, -2, 0, 0, -2. I used a fixed shutter speed of 1/25-sec and a selection of apertures and ISOs (between 160 and 1250 ISO). We were there about 30 minutes, but even so the light was fading a bit at the end of the shoot hence the high ISO.

I was pretty careful with exposure so I didn't need to adjust too much in post. However, all the shots were given a bit of "curves" tweaking (but not that much).

The only shots which had more than that were the strange colour ones (in the bushes) which were done with MB looks, and the shot of Kiera against the sky betwen 1.12 and 1.15. In the original of this shot, the sky was bleached out and a strong white colour, so I keyed out the sky and put in a subtle pale blue gradient in its place.

Where the eggs animate in, I built up a sequence in reverse. I did this because it's very difficult to add objects and not disturb the ones already there. So we made an arrangement of eggs and ran the camera, then took them away one by one and then reversed the sequence of individual shots to animate them appearing.

One bit of learning for me: I did the text in a graphics editor, complete with drop shadows, and then imported them as pngs. I realise now I should have blurred them a bit, as the white text alises quite badly.

I'm very pleased with it, though, considering we had our bag of eggs but planned the rest of it on the walk to the location!

Hey everyone, I just loaded Cake 2.2 today to test it and had a weird recording error. I shot 1st for about 3mins, then 12 secs and finally for around 2mins. I wasn't able to record another time. The camera just wouldn't record anymore. I used a SDXC 95MB/sec, shot in HBR 25p @ f2, shutter 50 and iso 1000. Standard -2-1-2-2. Anyone had the same problem?

EDIT: found the thread about the card. Sorry!

@balazer

I was playing with StreamParser and some footage from Cake 2.2 when I ran into the following stream "behavior": http://cl.ly/0b2X1y113z2S323l1y1B

I've got a sandisk extreme [NON-pro] 45mb/s card (the one that replaced the extreme video HD 30mb/s card) and the footage was about some foliage moved by the wind (a quite gentle wind, not strong...).

24H, ex-tele on, 160iso, camera on tripod, panny 20/1.7 pancake.

Is it ok?

This prompted me to examine some of my footage with stream parser and I get the cadence problem too in 24H, sometimes, with cake 2.1, this was shot with legacy glass so no AF. I haven't tried v2.2 yet.

It is normal to see ups and downs of the frame sizes. That is the encoder's rate control adjusting the quantizer setting to keep the bit rate in range. Whether or not an uneven pattern of frame sizes is really a problem depends on what quantizer settings the encoder is using for the frames. As long as the small frames aren't too low in quality, it is fine. Have you looked at the video? The video can appear perfectly normal even with this kind of unevenness in the frame sizes. Occasionally on a very high detail, low motion scene the frames get too big, and the encoder is forced to lower the size of subsequent frames more than you'd like. It is a consequence of having short GOPs, a high maximum bit rate setting, and a low minimum quantizer setting. But am not going to change those things just to get a little more even bit rate in those kinds of scenes, because that would reduce the quality of more common scenes. If you want to tune the settings to better handle that particular kind of scene, raise the quantizer setting in PTool to 20 or 22.

Attached is an example of uneven frame sizes in 24H. That unevenness looks bad in Stream Parser, but there's not a thing wrong with the video. The quantization parameters are not too high, and the video looks great. What matters here is that the small frames are good quality, and they are. Don't let the relatively large size of the large frames throw you off. Those frames are huge. If anything, the problem is that the big frames are too big, and hitting the frame limit. This would be fixed by raising the minimum quantizer setting, but again, at the expense of quality in more common scenes.

Thanks for the feedback, gameb. Glad it's working well for you.

I can't say anything more about what you've shot without a more detailed analysis. You are welcome to raise the quantizer setting, to tune the settings more to that kind of scene.

@balazer cake 2.2 spans also on GF2 FSH Sandisk 32GB Extreme - great patch for that little camera!

Thanks for the info, Chris. It seems I have some work to do to fix this.

Shot with Cake 2.1 using the 300% VMM and 720p60 (SH).

An embarrassing mistake is 2+2=3, the one you made is just a human mistake...

No, I wasn't going to change the reliability or memory card requirements. The way the settings are working, a high detail, low motion scene will generate sustained bit rates of around 67 Mbps. But if you pick the camera up and move it around, the bit rate drops to around 40 Mbps, even though the encoder could still be using less quantization (to make higher quality and higher bit rates). I wanted to find a way to boost the average bit rate while keeping the max bit rate the same. But I couldn't find a way to do it, without resorting to frame limits or fallback mode. So instead I will keep things much the same as they've been, with the same max bit rate and the same card compatibility, except correcting the problem of 24H sometimes going into fallback mode for some high detail, low motion scenes. I will post settings tomorrow after one more round of tests.

In general the minimum class 10 should be used, so why go below class 10 anyway ?