Blackout-Powell Native 24p Patch - GH1 FTW!!!

CColton said:
I've also heard that even stretched to full 1080p, the MJPEG hack doesn't resolve as much detail as a 1080p frame "should" or normally would.
Click to expand...
Indeed, MJPEG resolution will remain limited to 720p after being upsampled to 1080p in post. But since this 1920x720 MJPEG mode records in 4:2:2 color, its 720p->1080p chroma resolution will be significantly more detailed than the 540p chroma resolution of an AVCHD 1920x1080 frame. That's why it's useful for green-screen rotoscoping.
 
Andor said:
I don't mind the pull down method with JES, so do you think this is better than your 75Mps patch? I'm just looking for the highest quality image in the end...
Click to expand...

I'd like an answer to this too! Thanks for another great patch lpowell!
 
DrDave said:
I don't think it is the card speed either--if you look at the remaining time counter, you can see the numbers really speed before the crash, so something in the software has triggered an overrun.
I haven't tested why it kicks in outdoors as opposed to indoors, maybe the shutter speed is an issue, in addition to the higher resolution of bright sunlight.
Click to expand...

lpowell has pretty much nailed the reason i think with his theory/testing on the hi contrast edges, this is obviously triggering something in the camera and killing the recording.

Maybe my problem is i live in sunlight nearly all year round, good problem to have though :-)
 
rambooc1 said:
...I shoot mostly deep DOF which appears to trigger the errors. That is in my opinion the reason for most of my fails.
Click to expand...
Deep DOF can definitely max out the AVCHD encoder's bitrate. Check out this clip again:


If you examine the trees in the background, you'll see they're not quite in focus. I did this both to reduce the bitrate and to minimize edge farkle while panning. Likewise the foreground grass is soft, just short of looking muddy. As Rambo pointed out in an earlier post, the bitrate of this video never exceeds 30Mbps. When panning at 24p, crisp edges are a nightmare. I want it smooth!

Is it possible to apply the 25pN magic tweaks of this new patch to the 40Mbps High reliability patch so it is still 100% reliable but in 25/24pN????
Click to expand...
Hmm... Maybe there's something we can do about that.
 
I tried the hack today but unfortunately I had write errors on 2 Full HD shots. I was using my new .95 Voigtlander and since I was only doing a quick test I didn't have the ND filter on so aperture was set at 11! I was also shooting at 100 shutter instead of 50. I live in PAL land so 25 native was being recorded. So this combination which admittedly is a little extreme failed. I was using a Class 10 card so I am sure that wasn't the problem. I have returned to the 40 Mps reliable patch along with the 60 Mbps MJPG which produces fantastic ( although large) piccies. At least I gave it a go anyway. Thanks guys for the fantastic work you put into this conundrum.
 
I was getting half the bitrate with the exact same shot with this patch. I'm sticking with the 75mb patch.
 
cant wait to try this new Blackout-Powell Native 24p/25p Patch

great addition to the family of great patches now established.

well done guys! :smile:

i guess no patch is 100% perfect, yet between all the established patches we have ones to covers the whole spectrum! :smile:

again top work lpowell & Blackout!

will this work on the GF13?
 
Last edited:
so....the only reason to use this patch is if you are editing AVCHD natively or for some reason cannot transcode and do the inverse pulldown. ok, one more reason, anamorphic greenscreen.

otherwise, there is no increase in quality compared to other patches.
 
Personally I have found the quality improvements on the higher end negligible, and not as important (to me) as avoiding transcoding the footage twice and the hassle of doing a proper pulldown (not hard but just another step). So I welcome the patch, and I may be experimenting with filter combinations as well as tweaking the settings a little more to my liking to get the most out of it.

either way we got some more options!
 
seems that AVCHD is more of a pain for Mac users.
On a PC, I just use TMPGEnc Xpress to transcode and do pulldown in one easy step.
I also use it to render for online distro from my master, adding a little unsharp mask and noise/grain removal or contrast/saturation pop as needed. Super easy workflow.

I was curious as to why all the hoopla about this patch and wondered if there was any extra IQ from recording 24p versus 24 in 60i.
 
averan said:
I was curious as to why all the hoopla about this patch...
Click to expand...
Well, what's the most compelling new feature of the GH2? The 23Mbps Full-HD 24p codec, is it not?

Native 24p has been an elusive, highly sought after GH1 quest since the first days of the hack. Many of us had given up on it for quite some time, myself included. There was no hidden secret to unlock, it instead required a steady accumulation of field experience and test evaluation. In short, it was not something that could be cracked in one marathon all night session.

To be sure, the GH2 offers a variety of attractive new features, but Native 24p was the one that clearly set it apart from the GH1. Now the lines have blurred once again, making the options that much more interesting.
 
but why??
is it really just the convenience factor? or is there a technical reason why 40+mbps 24p in 60i on a GH1 is inferior to 24mbps 24p on a GH2? i mean, what's the big deal?
 
For us PAL users, it's less of an issue I feel. My DVX100 used to record 25p in a wrapped 50i package, and it wasn't an issue at all really, whereas in USA and NTSC land, the pull-down makes 60i wrapping a pest.

I am wondering if I should revert back to non native 25p in 50i to avoid the empty frames. What do you think LPowell? What might I experience with the 50i wrapping that I won't like?
 
Andor said:
I don't mind the pull down method with JES, so do you think this is better than your 75Mps patch? I'm just looking for the highest quality image in the end...
Click to expand...
Both the Blackout-Powell Native 24p Patch and the 75Mbps Peak Performance Patch produce average bitrates of around 45-50Mbps with highly detailed subject matter. The maximum bitrates are different: 55Mbps for the Native 24p Patch and 75Mbps for the Peak Performance Patch. That gives the Peak Patch an edge in encoding extremely complex Intra-frames, at the cost of reducing its safety margin and making it very sensitive to SD card write-speed. The Native 24p patch works reliably with inexpensive Class 6 SD cards, while the Peak Performance Patch requires top-quality Class 10 SD cards.
 
Lucas Adamson said:
I am wondering if I should revert back to non native 25p in 50i to avoid the empty frames.
Click to expand...
The Blackout-Powell Native 24p Patch should not produce any empty frames at all, in either 24p or 25p. All tests I've conducted produced flawless video streams, even in cases where I was trying to break the codec. However, Blackout's original settings were developed for 24p, and I haven't had time to put in as much testing on the PAL side as in NTSC mode.

I'm hoping PAL users can provide some help in evaluating the performance and reliability of the several 25p patches we now have available. I think this is even more important than a 24p solution, as the GH1 remains the only Lumix G-series camera that supports true 25p recordings.
 
Hack settings variations questions to lpowell

Hack settings variations questions to lpowell

lpowell said:
A Full HD 1080p frame produces too much data for the MJPEG codec to handle reliably. The 1920x720 MJPEG mode in the Blackout-Powell Native 24p Patch is the widest that will support 4:2:2 color depth at moderately high bitrates of around 50Mbps. It also works natively with 1.5X anamorphic adapters, which will produce widescreen videos that require no stretching in post-production.
Click to expand...

Do you know what the highest frame rate is, then, that will handle full 1920x1080 MJPEG frames?

(How) do the frame rate halving settings, 60->30 and 50->25, affect any of the AVCHD and MJPEG hacks?

Is the amazingly fast down counting RTC possibly an indication as to why the camera does generate these write speed errors, if, supposedly, unnecessary so far as it concerns the card?

This may be a buffer thing, but perhaps there are variations in the hack settings and/or the frame rate halving options, that will result in yet another dimension in hack variations. How about a 200 Mbps 12 fps hack, if that is possible at all...

I believe there have been reports about the write speeds error showing up with the GH2 as well, so also Panasonic is not all that "reliable". Perhaps they should have applied an even more strict marketing strategy, although I think no-one really experiences this as a problem. I'm not sure. Anyone who reports this error may have been using the GH2 for a paid job as well.
 
Well, after a day or two of recording, all I can say is this totally rocks! Definitely better than my version, which has slightly higher bitrate but was much less stable. This is the perfect blend. Hats off! And speaking of rocks, for the perfect filter--anyone tried a rock crystal anti alias filter yet?
 
You must log in or register to reply here.
Back
Top