Whoops, thats the wrong version of Cluster v2e/f. Apologies about leaving in a test version of 720p60 when I was comparing my matrices with Lee's. I'll upload the correct cluster matrix (a derivative of my Sedna matrix and used in v2a) version under newly titled v2g. You'll notice the matrices should be as v2a though I have edited i frames.

I was wondering why I was getting problems today. The other side of the coin is that Cluster is not aimed at comparing itself with lower GOPs, it is an experiment in saving memory for long recordings whilst retaining decent quality over stock. I want to make that clear first. However, it performs rather well in 24p beating Flowmo - and HBR is only just behind running at less memory. And Ive still to see an all conquering 720p setting from anyone including my v2 versions - I must say, Flowmo performs excellent at 720p - well done to Lee. Cluster v3 has a bit of work to go.

@driftwood

I am sorry to be unable to perform help of your 6GOP setting. BTW, your setting which is not Intra becomes reference material especially for me. Thank you always! :-)

@LPowell

"I believe this is crucial for achieving P and B-frame image quality comparable to I-frames."

I take care similarly. How much do you think the tolerance level in the range of DC value is?

@driftwood @LPowell

I feed back the result of my usual test to you.

Each left is shot illuminating fine textiles with a halogen lamp. Each right is shot the moving Stray's chart. http://www.personal-view.com/talks/discussion/comment/51720#Comment_51720

Both FM2.01 and Cluster will have too high the bit rate, and will stop during recording. I think that it will probably stop also at the wood which I am always testing with my DIY steadicam.

I think that 60p not stopping is not realized unless it is adjusted so that 55M may not be exceeded at least.

In addition, I think that the GOP table of HBR30p of FM2.01 also has the necessity for adjustment to a slight degree.

*All the film modes are "cinema[-2.-2.+1.-2]".

@driftwood

"However, it [Cluster] performs rather well in 24p beating Flowmo....."

In what respect? Thanks.

...and DC values will change according to changes in picture detail.

@jrd detail.

@lebowski1998 - "It would be great to have something ~100mb/s size, spanning of course, and will work with in camera playback, mostly 24p, but occasional slow motion use of 60fps..."

http://www.personal-view.com./talks/discussion/3337/gh2-flow-motion-v2.01-update-failsafe-hbr-720p-modes/p1

yep, which is decent enough... we've had it higher but unstable.

Hey Guys, So I am really confused. There are soooo many hacks out there and I just dont know witch one of all those I should use. I tryed some of them but I never knew if this was a old one and if there would be better ones. I am making Music Video Clips and short films. So I really wanna have this sharp cinematic look (for example RED Scarlet style). Can you tell me witch is the best hack for my work? Also visit my youtube page (http://www.youtube.com/nitramdre) to see what work i do and what hack would suit me.

PROBLEM, HELP! When I made my latest short film "No Mercy" (

) I found some really wierd pixel stuff on my footage. Here is the sort film I've done. Now, if you pause at 2:48 and look at his hair you will see what i mean. It got worse because of Youtube but still on my stock footage it look kinda the same. So weird. Can't figure out what it is and the weird thing is you dont see it always. Some shots are fine and some of those have this "pixel" problem. You can also look at the image down below. I think you can see it better there. On the second one you can see all the Pixel Squares better.

I use the SanDisk 30mb/s 16GB. Is that maby the problem? I'm thinking of buying a SanDisk 95mb/s 64GB. I heard that was the best SD card out there on the market. I would really appriciate your help guys. Thanx alot!

Greets Martin

This may interest some of you PTool tinkerers.

My goal was to produce an intra 24p/VMM patch free of redundant and/or ineffectual settings given the constraints of a 45MB/s card. This is just an exercise, not an attempt to achieve absolute image quality; it's possible that for these moderate bit rates, higher GOP settings can beat intra. Caveats out of the way, here's what I have:

A Little Light Intraspection (ALLI) v1.1

24p and VMM ONLY

138 Mbps 24H, 95 Mbps 24L spanning, VMM H unstable, VMM L spanning.

24H 24L

ALLI changes only six parameters:

• Video bitrate 24H & 24L: 150000000 and 88000000.
• 1080p24 Frame Limit: 5750000. Version 1.0 didn't use a frame limit, which caused the video buffer to run down.
• 1080p24 GOP Size: 1 & Encoder setting 1 1080i/p: 1. The former is apparent. Without the latter, the video is useless -- choppy frames skipping all over the place. I don't understand its function, but it is necessary.
• 1080p24 Scaling Fallback. Without altering this scaling table, 24L mode will oscillate in and out of fallback mode to hit the target 24L bit rate, making the bit rate graph look like a series of plateaus. The default fallback table is extremely coarse, so DC jumps to around 20. Simply replacing the fallback table with the default Scaling I table allows the encoder to hit the target bit rate while maintaining the same DC.

Version 1.0 had a set quantizer value, but the encoder does a better job of choosing QP depending on scene complexity.

ALLI is not without problems. Attached is a frame grab of my death chart (actually a death CRT) shot with the 14-42 kit lens at 42mm, f/7.1, 1/80, ISO 640. The jump in QP presents itself as mosquito noise, which is highly annoying. At closer examination, this mosquito noise looks like discontinuities between adjacent blocks. I've tried correcting this with the deblocking tables, but I'm out of my element here, so my efforts were fruitless. If you have insight into deblocking, please share.

So if you enjoy tinkering, this may be of some use. I'd love to hear if this is stable for others with a different variety of SD cards, or especially if you can improve it.

@Ashun Good testing. A few points. Your Intra 138M setting will fail on the buffer/run down because its not enough bitrate.

"Encoder setting 1 =" controls the frame type usage in the GOP.

Encoder 1080* (*or 720) = 1 (equals stable Intra only) when GOP is set to = 1. Set to 2 or 3 and you will notice erratic Intra if the GOP setting is set to 1. Its a bloody nice effect though ;-)

Subsequently,

Encoder 1080* (*or 720) = 2 will only use i and p frames in your GOP settings (So long as GOP >= 2).

Encoder 1080* (*or 720) = 3 will make use of i, p and/or i and b frames in your GOP setting (So long as GOP >= 3).

Hope that helps.

If you look way back at the patches thread, youll notice I made 3GOP variations utilising P or B frames in the the original Driftwood GOP3ILLAs which pushed B and P frames to the level of i frames.

@Ashun The lower 24L Stream Parser chart you uploaded above shows the encoder being forced into a type of Fallback Mode, starting at frame 44. When this occurs, the encoder's bitrate allocation mechanism fails to estimate I-frame bitrate requirements correctly, and produces clamped I-frames with degraded image quality. This type of dysfunctional behavior is likely the result of your attempt to alter the 1080p24 Scaling Fallback Table to suppress the undulating fallback pattern you observed in 24L mode.

@kovtun66 In its B-frame mode, the AVCHD encoder has a built-in preference for using three-frame patterns, in the form of IBB and PBB sequences. In practice, it's been difficult to produce consistent encoding behavior when the GOP-length is not evenly divisible by 3.