@zilk: Which patch exactly is used for this capture video screen?

Which GH2 profile and parameters did you use to get such a ultra flat image? Which lens?

@towi

Then again, as you know, I never use auto-anything... so when a codec survives my torture movie it will (most likely) survive any real world scene ...

Yes, this is the difference of a position between you and me. :-)

For example, if WB is changed, a result will change considerably. However, it is physically impossible to check all the WBs. Therefore, I always use AWB for the test.

There are many such other elements. This is not for using auto but is a method for making it stabilized in every setup.

On the other hand, I also think that free arrangements are attained in the settings used only by limited setup personally.

I attach greater importance to Buffer Analyzer than to Stream Parser, when testing in these DeathScreens.

@bkmcwd

the setting which cleared this Death Movie is also often frozen by static Death Screen

in my experience when the codec survives the first 34 seconds (including the black frames / black wipes which push the frame size to the max) it will also survive any static torture tests. Too, when I am testing new settings I always start with recording 2 minutes of the first frame of my codec torture movie (so the wired B/W chart) and check the Streamparser data. First when everything went fine I am checking the setting with motion.

Then again, as you know, I never use auto-anything... so when a codec survives my torture movie it will (most likely) survive any real world scene ...

@Azo

Have you performed this extensive suite of tests on your latest Valkyrie 444 TZ4 patch?

Of course! :-)

However, it still may not be perfect. It is because I did not try all the lenses in the world. Although I think that it is probably OK ...

@Azo @towi

I am assuming that the @towi death screen movie puts more stress on the camera then the old death screen movie is this correct?

It is also yes and also no. It is because the setting which cleared this Death Movie is also often frozen by static Death Screen etc.

I have been doing at least four kinds of tests recently.

1. static Death Screen

2. moving Death Screen on static Death Screen combination

3. towi's Death Movie

4. continuation zooming on static Death Screen

All these are tried on max brightest monitor with ISO1000/SS800 etc.

Since these tests will try the element with which each is different, I cannot say at a word which brings about the highest stress. :-)

@bkmcwd

Katsu San thank you for updating the Valkyrie 444 TZ4 patch :) So I am assuming that the @towi death screen movie puts more stress on the camera then the old death screen movie is this correct? If so I will run the tests on all of the patches that I plan on using. Thanks @towi for the new death screen....

Valkyrie 444 TYPE-ZERO4 & Lite BETA4.3

bkmcwd "Valkyrie 444 TYPE-ZERO4 BETA4.3" (Standard) - seta.ini - Released 12/08/2013

bkmcwd "Valkyrie 444 TYPE-ZERO4 Lite BETA4.3" - setb.ini - Released 13/08/2013

*All the rec modes were changed from BETA4.2. :-)

This TYPE-ZERO4 is also the version as which "balance of gradation and resolving" was considered in all the modes. (Scaling Matrices are the same as TZ3 or previous Lite.)

I think that the freezing issue at the moment of the focusing and zooming was solved nearly perfectly also in Panny lens use.

Although towi's Death Movie is cleared in all the modes, there is no telling whether span is possible in other than 24p.

Cautions are required to use iDRC or iA only in 60p.

Please try it! And I am very glad if I can get feedbacks from you.

*If this is also still unstable, I will further adjust.

Special thanks to @Azo, @towi and all silent users of my settings! :-)

Of course, many thanks to @cbrandin and KING @driftwood!

• Superb-looking Pure Original 444 matrix from cbrandin is adopted in 24p mode

• Modified 444 matrix from my BETA Team in Japan is adopted in HBR/1080i and 720p modes

• Upto 140M for Top Quality 1080p24 at Q18 / 'Standard'

• Upto 140M for Top Quality 1080p30 at Q18 in 24L mode with 80% Slow-Motion Mode (No Sound) / 'Standard'

• Upto 110M for Top Quality 1080p24 at Q18 / 'Lite'

• Upto 140M(110x1.25=137.5M) for Top Quality 1080p30 at Q18 in 24H mode with 80% Slow-Motion Mode (No Sound) / 'Lite'

• Upto 75M for Top Quality HBR/FSH modes

• Upto 75M for Top Quality 720/50p modes

• Upto 75M for Top Quality 720/60p modes

• Extremely reliable top performance in AVCHD 24H and 24L

• 80% Slow-Motion is available in 24L only with 'Standard'

• 80% Slow-Motion is available in 24H and 24L both with 'Lite'

• Fully working iA and iDynamic range modes if you require them (Take care only in 720/60p)

• Beautiful 3 GOP bringing short GOP style detail & movement-rendition in all the modes

• Bush of Death / Death chart tested.

• Wonderful Pasadena Pulse Audio Patch V2 B2, by Per Lichtman

• Top quality 2K mjpeg Mode in HD by Nick Driftwood

• In camera playback is sometimes not available in 24p. (Standard) In other mode, Sometimes available after reboot the camera.

*Supposing you use "SH" mode safely in 60p, please turn OFF iA and i dynamic range control. On the other hand, in other rec modes, it is satisfactory at all.

*I especially recommend you use with SanDisk 95MB/s 64GB SDXC card.

@rahorto

Many thanks for your feedback! :-)

SanDisk Extreme Pro 95MB/s 32gig

Also at the same speed, the difference between SDHC and SDXC is more than imagination. Even so, now, I have to stabilize it further.

I seem to be able to release the new version soon.

Thanks again.

@spreeni

Hi mate! :-)

do you think the new Spizz will do a better quality than Duke or Valkyrie?

This is a matter of taste. Personally, I prefer Duke or Valkyrie. However, I interesting challenges in Spizz.

Duke (Beta1) produces a very good quality in PAL,

Supposing you can use it satisfactorily, to be sure, BETA1 will be very good. However, there is a risk of freezing in it strictly. I feel appropriate bit rate of 25p in PAL as being around 60M.

Now, I am repeating the experiment in order to further stabilize. The result is due to be harnessed in Spizz or other settings.

@driftwood Thank YOU Nick! :-)

I am going to improve Spizz in addition to 24p more.

@towi

Thanks for feedback, mate! :-)

You could use BETA1 satisfactorily, since you are an expert.

@towi

Thanks for your explain, mate! :-)

Well, actually I do not agree ... or maybe I don't understand what you mean by "GOP table that prioritizes static".

About this, my words were lacking. I feel the tendency for the GOP table in which greater importance is attached than to the B-frame to the I-frame. to be adopted was among the sets which you liked in the past. Does not make a lot of sense in itself. I understood your opinion, of course.

BTW, I will explain, even in the PAL side, why I think BETA4 is better than BETA1.

If there is no freezing problem in too high the bit rate at the moment of span, I also like BETA1. However, too high the bit rate drops a video buffer, and a risk of as a result freezing at the moment of span becomes large.

These are the result of altered the GOP table of BETA4 respectively. In "3.0.0.3.15.15" and "3.0.0.3.18.18", video buffer will fall in death chart. There is no problem, if all the people using Duke are not made to span. However, I myself aim at the "stable" setting in the first place.

And the result of BETA4("6.0.0.6.15.15") is very good to compare the NTSC side. Since there are many common parameters at NTSC and PAL, these balance is also important.

Probably, it will be satisfactory that the expert uses BETA1, after understanding the above situation. However, I dared to have explained these for the general user.

Many thanks again.