• 50i GOP 1 (like SMBU V1, EOSHD 88 UNIFIED, PICTORIS)
• HBR GOP1
• 50p low GOP
• bitrate max FSH 40 mbps intraframe,
• good for doc.,
• Death Charts

thanks

highest possible careful tweaked settings for very high image quality with enough stability for short takes up to 5 - 8 minutes.

Improved for best low light noise and textures in all modes, perfect for high iso, and excelent image texture in good light.

Arri Alexa image quality inside the GH2, (just missing the Alexa dynamic range of course)

default version:

*SH and H slots are better for good light in low iso and for more detailed scenes in good light

*SH slot is higher quality and more stable with manual focus legacy lenses

*H slot more stable with native lenses with electronic contacts

*H slot also better for use with image stabilization

*hbr is better in good light than in low light

*default version is more stable in SH and H 720p and in HBR than the boson version

*24p 24H and 24L are the same of boson

*great quality in all modes

boson version:

*SH slot improved for low light textures and noise

*H slot better for good light in low iso, better for more complex details scenes in good light

*H slot is more stable for native lenses

*HBR does the low light / good light balance automaticaly for better noise in low light or better detail in good light

*24p has same noise quality in both good light or low light for constant image texture this keeps same random noise in all light conditions, good for intercut with SH

*a little less stable in 720p and HBR than the default version

*best quality in all modes

seta = workhorse default

setb = workhorse boson

setc = workhorse default lower datarate in SH and H for more stability in 720p and hbr

setd = workhorse boson lower datarate in SH and H for more stability in 720p and hbr

sete = same as seta, but the 24H and 24L are optimized to deliver sharpest image for steady complex detail scenes, it does the automatic adaptation in 24p for low light noise or good light steady complex detail scenes

setf = same as setc, but the 24H and 24L are optimized to deliver sharpest image for steady complex detail scenes, it does the automatic adaptation in 24p for low light noise or good light steady complex detail scenes

all tests performed in NTSC with the Sandisk 32GB SDHC Class 10 U1 45Mbps card.

transcode the original mts files to Apple ProRes 422 full range using the 5DtoRGB free software before editing to avoid the diagonal pattern rain problem. Try the ProRes HQ, normal and LT versions to perceive the best balance between quality/file size.

as of september 05 2014 all versions are modified flowmotion 2.02 with extensive careful tweaking

please donate to www.personal-view.com

Whats it all about? Achieving the best looking overall pictures around - throughtout the popular GOPs. The great thing about Cluster X developments is you can mix and match some of the settings to combine into your favourite setting (e.g. GOP1 for 24p and 25p/FSH, GOP 6 For 1080i60/30p and 12/15 for 720p etc...). Slipstream settings do this for you (mixed and matched and with spanning capabilities where we can plus 80% modes on H & iA mode support).

This has been a tough (and still ongoing) challenge, each setting (and ptools patch change) takes an age to check & measure. Its exhausting work - even with 4 cameras on the go. The measuring to check Quantisation, frame sizes and stability adapting one change at a time is pretty debilitating on mental energy. I hope people appreciate waiting for each setting to appear.

All the new Cluster X series settings for each GOP attached below have been tested on the notorious 14-140 Pany sharp lens. Give me feedback.

Its as simple as A, B, C, D, E, F ! Each .ini setting in ptools for Cluster X Series will equate to setA ('DREWnet' 12/15 GOP), setB ('Nebula' 6 GOP), setC ('Spizz' 3 GOP), setD ('Moon' 1 GOP/3 GOP), setE (Slipstream 1) & setF (Slipstream 2). Any updates will stay on these sets.

"Bitrate is King. Who needs hi powered scaling matrices when enough Bitrate (if you have it) can drive the quantisation..." Quote from my conversation with Dark Shikari - X264 dev 2012

If you enjoy these settings please don't forget to donate to personal-view by clicking on the link above. Gratitude and thanks to Vitaliy Kiselev.

.

Cluster X 'Slipstream'

A series of GOP combination settings drawn from the Cluster X series but set at nominal bitrate settings (40 to 72Mbps) to achieve a better spanning percentage for longer recordings plus the ability to be used on slower sd cards. Slipstream attempts to correlate the actual clip duration to the TS (transport stream) duration whilst providing error free population of the cpb buffers. And it seems to work very well at these settings. :-)

Slipstream #1 (Rev B): Release Date: 10/03/2013

A mix of Nebula and DREWnet settings all tightly packed into 72Mbps max 24p and around 40-52Mbps for everything else which in my PAL tests SPAN! You also get 80% mode at 24H and iA modes working. NTSC 720p60 and FSH/HBR30p should now span.

1080p24/1080i50/HBR25p/720p50 at GOP 6 1080i60/HBR30p & 720p60 at 12 GOP

Slipstream #2: Release Date: 10/03/2013

Including;-

1080p24H 88Mbps GOP3

FSH1080i50/HBR25p 60Mbps GOP3

720p50 62Mbps GOP6

FSH1080i60/HBR30p 44Mbps GOP12

720p60 52Mbps GOP12

Slipstream #3: Release Date: 15/03/2013

Including THE GH3 MATRIX ON ALL REC MODES;-

1080p24H 150Mbps GOP1 (moon style)

FSH1080i50/HBR25p 70Mbps GOP1

720p50 62Mbps GOP6

FSH1080i60/HBR30p 64Mbps GOP3

720p60 52Mbps GOP12

NB: Ive had one occasion where the camera just freezes with no apparent error. If this happens simply leave the camera alone for a minute or two until it fully writes out to sdcard (emptying all buffers) THEN turn off/battery pull. Hopefully you will notice that all your spanned files are there on next powerup.

==MY TEST==

I went on a shoot this weekend, and was using Sandisk Extreme 16gb 30mb/s cards. I wanted to ensure both spanning and playback in camera for the shoot, so I went with driftwoods "spanmybitchup" patch. I did just a few short preliminary tests: the test I did was to shoot the papasarts star chart (which I've attached--I also attached the more extreme codec test chart v2 2010), and let it run. I waved my hand around in the frame from time to time and also had some talking to get audio. Everything seemed good: I was getting spanning and smooth playback in camera with audio. (EDIT: also attaching Stray's death charts with color information!)

==MY SHOOT==

So during the shoot, after a few shots, I was getting the message "motion image cannot be played" for all my clips (or something like that I don't remember exactly)--my heart sunk! An actor asked me to check to see if we recorded something on a previous take, I had to say that "yes it was" without checking. I was worried about requests for playback--and this was only with one actor: imagine this on shoot with clients! For certain shots, I wanted to be sure that something was recorded since I wasn't at the camera, and I couldn't do this. The scene I was shooting was an actor in a car at night--he was lit and most everything else was dark. That's when I got the messages. I put in a new Sandisk card, and formatted it. Reshot the same scene and I was getting the same error.

==LESSONS==

1) In camera playback is important at least for some of us, and for some, like me, it is even more important than low gop. For me, I am willing to forego a very very high quality low GOP setting (awesome work driftwood!!) that doesn't have playback in camera on good SD cards for an improved long GOP with ultra reliable in camera playback. I'm NOT saying that everyone wants this or should want it (especially if you have the cash for more super high end SD cards or for extra harddrive space). But I'm guessing some people are in my situation as well.

2) It seems there's a relatively standard procedure for patch development (using streamparser, tweaking settings incrementally, etc etc). BUT there seems to be no standard procedure for testing spanning and in-camera playback. You might not think that makes a difference, but it seems that it does: it seems to matter what you shoot when you are testing things like spanning and in-camera playback. Or, at least the number of clips you shoot or the ISO you shoot at makes a difference: otherwise, I don't know how to explain the divergence between my pre-shoot tests and what happened on the shoot. I welcome some constructive thinking about standardizing spanning and camera playback tests.

==DESIRES==

The ideal for me would be to get a hack that improves quality over the stock settings, that has very very reliable spanning and in-camera playback with audio, and works on good quality cards like the Sandisck 30 mb/s (16gb). I know some people are getting the SandDisk extreme pro 64gb cards... but a lot of people (like me) already have a stash of good quality cards and don't want to fork over even more money to get these super high end cards.

I did test w/ @cbrandin 's (Chris's) 66M patch. We know that this doesn't span (but getting around 10 or 11 minutes is okay for me, although I'd love spanning). But what I did notice is that I couldn't get in camera playback with this either. I'm going to try the 44M patch.

Thoughts?

@rajamalik @thepalalias @Benibube thank you for the comments guys. @cjdincer

rajamalik, @coors thanks for testing the setting(s) guys; rajamalik Congratulations for your little b...

Releasing the setting, after very long time working on it, the name and some info see 1st alinea:

I know it was/is a challenge (AQ4 and Q8 in the same setting) for most detailed and lower compression setting and want everything constant bitrate-style and rajamalik asking for the most detailed one every time but here is the release of the "OBS AQ4-Q8 161M-setting exTReme-KAYSERI A-GraDetail" setting, the setting shows (due to using lower compression in the setting, but I believe so you see more), maybe say high ISO, a little bit more noise/maybe artifacts, I did not used 3rd party matrix, but the goal is to get every bit (in this situation pixel) what GH2 is seeing/recording, out of it and see everything yourself when playing back and in post too, and cbr-style bitrates too; (do the rest/editing in post).

Okay it's logical to say when you have an very detailed and low compression setting, on high ISO you see some more noise/artifact etc. but you get everyhing out of the gh2 I believe. But I believe, if an "matrix master" can make a matrix especially for this or similar setting then we get an setting with some reduced noise/artifacts directly on the sd-card itself. But matrix by the way is a subjective matter therefor it is up to you to judge or not judge things by matrix way but settings way. And I did not used third party matrix for the setting.

But, on the other hand: maybe there will be enthousiat users to get/shot/capture, you name it, this way and do rest in post, I think and believe it is maybe some personal taste and this setting is on paper very good for low detailed scenes or for someone always looking for it or exactly want details and seeing that little bit more.

The setting gives you constant bitrate-style bitrates and for example 720p50 give you around 100Mbit-range bitrates, this is high in comparison with some other gop-1 720p50 settings/ and some of the other gop-1 720p setting are not working reported earlier by others I though. Don't forget 1080iFSH(50) is available too and also to try for slow motion with deinterlacing in post for 1080p50, maybe this setting is better then other 1080i also, who knows. (This is for some of you as a fan of deinterlacing 1080i to 1080p50 in post, instead of 720p50 give a try too.)

Suggestion: Maybe, from scratch, a matrix master or a matrix maker can make a matrix to also temper some noise/artifacts, high ISO etc. especially for this setting, but also this setting is for people who get the most details out of gh2 and loves to do things in post...

Setting itself, "OBS AQ4-Q8 161M-setting exTReme-KAYSERI A-GraDetail":

(for me unbelievable to let the setting work with AQ4 and Q8 in the same setting at the same time, "All to detail and low compression" at a such high setting, especially when you know that settings for some mode influences the other mode, but I've got them work together for:)

• working (/or say, I tested) for the modes => 1080p24H, 720p50SH, HBR, 1080iFSH(50), 80%24L but, with such high bitrate setting it was not easy to get, all the modes above, working
• for all the modes I've written above, constant i-frames-style (+ b-frames for 720p50), cibf-style, except for 80%24L though it has high i-frames between around 360KB to max around 780KB, average around 600KB, and constant bitrate-style, cbr-style, for all the modes I've written above too, (including for 80%24L mode)
• tested with manual lens, (auto-lens check for yourself)
• there is a time-limit 3:45min but every mode is working for me with my setup (sd card and manual lens), so recording and also in cam playback available for, maybe including but not limited to (does mean other modes such as 720p60 needs testing, test for your country, I tested the PAL), the modes from above
• sandisk 8GB SDHC 95Mbits/s card

some bitrates I've got during testing, setting for 1080p24 is high to the 150M range, but see others very good ones: - 720p50 100M (for slo-mo see 1080i fsh(50) mode too, for using deinterlacing in post) - 1080i FSH (50i) 100M (especially for people who want 1080p slow motion with deinterlacing) - HBR 100M (I think very good one for hbr) - 80% 24L 100M

here is the setting as .zip file attached

I understand that most patch settings tamper with the number and type of frames in each (open) GOP, but I have not yet found any mentioning on how many frames are written into one closed GOP.

Or does anybody know what the maximum amount of reference frames is that the GH2 output uses? (H.264 would allow up to 16, but since many decoders are not willing to store that many decoded frames for later use as a reference, the lower H.264 profiles are limited to much less.)