First a visual proof of concept, effect color stabilizer + ft-auto white balance only applied to lower right. Video by Amedeo Gallo, hope it’s OK with U bro ,-)
Mind you, it’s not the best video example as:
A – the clouds interfere with WB and luminosity in the overall image and
B – source it’s a highly compressed vimeo downloaded from vimeo =)
IF working within a raw sequence results would improve vastly, either syncing Auto WB in camera raw or inside LR and with TLtools (free). This AE approach would still be valid and probably would carry enhanced results.
Then the BTS or behind the scenes ,-)
Where on my last entry I said:
Ok, I really don’t think is such a good idea to
I gave up, probably the only one who could find a solution is Panasonic itself.
Mostly ’cause panachonik it’s too busy selling cakes ,-) to care about “old fart” GH3. So I downloaded @yellowapple video from vimeo and tried many things, mostly focusing on the ones that didn’t involve payed software… but only within AE I managed a couple fixes:
In both I created a mask around problematic areas (over exposed in yellowapple’s video to enhance the issue), which I used as a track matte and I had a copy of the layer for background.
First, the money burner; RE:Deflicker at a whooping 250$, oh yeah!!!
Despite the steep price, I got the best results from the plug and it works in 32bpc.
I triplicated the effect and used it averaging each channel and despite I set time range to the whole comp (146 fr) the analysis was pretty quick.
Second, the “free” one; Color Stabilizer + ft-auto white balance (name your own price plug). Maybe AE inbuilt plugs, auto levels or autocolor could also work, dunno didn’t try it out.
This one only works in 16 bpc, but IMHO results seemed good enough to use it and move on. If interested U can READ and download over the thread
You don’t need to TL using jpeg @yellowapple @Odur !!! Try this =)
Then the x265 and Hybrid bit.
For those of you cats who doesn’t know what a codec is, here’s wiki to rescue:
A codec is a device or computer program capable of encoding or decoding a digital data stream or signal.[…] a codec is a program (an implementation) which can read or write such files. In practice, however, “codec” is sometimes used loosely to refer to formats.
Regarding video I personally consider a healthier wider (also spread) practice to “use” the wrappers as if formats; mp4, mov, mts, avi, etc. So now specifically about the x265 codec, wiki again:
x265 is an open source free software and library for encoding video using the High Efficiency Video Coding (HEVC/H.265) standard.x265 is currently licensed under a dual GNU General Public License (GPL) 2 license and commercial license, similar to the x264 project.
Basically x264 was the best free implementation ever of the h264 codec (AVC – advanced video coding) found at the core of most mp4, movs, mts (avchd), etc. dominating the scene for a decade. The people behind the mask behind the wall behind… are claiming x265 is the same to revolutionary codec h265. The revolutionary part is because, as image files are getting bigger in resolution and size, this codec allows for faster and bigger compression; meaning more quality in less size done quicker; EFFICIENCY is gonna get us kill.
See Bilu and JardaIn
So I wanted to play with the codec and I downloaded very nice Hybrid app (free for win and mac) and I compressed a file; it took a very very very long time but I check the ultraslow box, so have to make more tests comparing with other codecs. At the time of writing this youtube doesn’t seem to accept x265 (wrapped in mp4) files, but vimeo does… and I went there and uploaded a video; of course vimeo recompressed it as a h264 mp4 =)
And that’s it, here & now; fixing the past and prepared 4 the future 😛