@Vitaliy_Kiselev The thread says too many static tests + first i saw the title which seemed to be for motion testing, if i misunderstood or not relevant enough to post here no problem but I was going purely by thread title at the time of posting it.

@cbrandin

About low bitrates.
Rule here must be simple.
Low modes (24L for ex) bitrate setting must be always in between top and boottom settings for high mode (24H).
If it is not so, you'll get this problem.

>Your second response is a lot more productive.

If you stop talking to me in mentor tone it'll be even better.

>Are those actually controlling multiple settings in the firmware now or is it one discreet field value. Those settings appear to act differently than they originally did.

They are changing many things. I wrote this in main hack topic before release.
Including corresponding top and bottom settings that you can find in testers section.

@mpgxsvcd
I understand that you want to help. And are doing testing. I value that.
But read your message without emotions and after this read my response.
If you do not understand me still, just do not go to testers topics.

I wouldn't bother with testing the Top and Bottom Bit rate settings right now. I just tested those with a 94% of 32000000 value and it actually decreased the average bit rate. I did a completely controlled test on a tripod with identical settings which I saved in the C1, C2, and C3 slots for 720p, 1080i, and 1080p.

I will post the sample files and the Stream Parser data in a moment. For now I haven't found a reason why just setting the bit rates to 32000000 isn't are best option for the time being? It is completely stable and offers extremely good picture quality. If stability isn't your main concern then the 42000000 setting works very well also.

>Vitaliy, what is the "bottom bitrate", a minimum? If so, experimenting with that might make a difference.

It might, but it might not. :-)
Try to play with top and bottom numbers for 24H keeping the same bitrate setting.
Keep bottom always smaller, and top < your bitrate setting /1024.

@cbrandin
I also think so, as bitrate is too low.

Altitude doesn't have a measurable effect (at least not for these tests). Let's not get too fancy here, it isn't necessary.

By the way, I didn't find much difference between frame types (as I expected), the big difference was in overall quality. I didn't do any image adjusting except for normalizing contrast.

Chris

@B3Guy

Doesn't altitude affect the period of the pendulum as well?

String length = 1 meter. Use video from when the target goes from edge to edge (inside) - you just have to be somewhat wider when you start. Weight doesn't matter (except the swing will last longer). Pick frames close to the center. Make sure the target isn't swinging in and out of focus (takes a little practice). I have some test results. I wasn't all that precise and the results are very revealing - stay tuned.

Chris

I'm not sure aperture, lens length, etc... makes any difference. Pretty much any lens configuration will max out 1080 resolution. It is important, however, to have the target the right size in the viewfinder. I plan to do most of my testing with the 20mm lens. What we're looking for is relative resolution between frame types; absolute metrics concerning lenses etc... is another issue. As for how fast the image is moving - well, we are shooting video after all, so speed should be easy to measure. Also, you could calculate image speed vs. angle from center as long as you know what the extremes are.

Why would an image that corrects angular velocity be necessary? All we want to see is how well detail holds up in P and B frames vs. I frames, and whether higher bitrates improve the temporal behavior of the codec. I wonder, for example, whether even if a higher bitrate doesn't improve static images, if it does improve dynamic ones. For example, if you look at an I frame and the immediately preceding frames have much lower detail then we know detail is being lost, at a higher bitrate they might look better even if the I frame doesn't. After several seconds it should be possible to have captured samples of images in all positions and with every frame type.

I'll play with this a bit more and see if I can come up with a simple protocol.

The idea of a standardized testing setup is great. Just some ideas, Same lighting steps, same distance, as close as the same lens as possible, same fstops, etc.... Then we can post/graph/grid the results based on some type of quality indicator.