GH2 AF100 with a hacked GH2

going to try some of the other hacks and compare. Need to get a lower bitrate cause these cards are filling up fast.
 
Just bought the mac version on the itunes store. Best $50 bucks spent in a while!

My dream would be some improvements in workflow-
Automatic TC rewrite A way to automatically re-write the TC to something like free run for all the clips in the batch. -just give the Start TC.
Proxy encoding - one clip in 444 the other in LT with the option to save in two places.
TC window burn
Project based work flow.

Something totally out there: The ability to use a audio track as the TC. That way we could feed TC into the audio mic in (you would have to attenuate the TC signal quite a bit so some hardware is required) That would solve a lot of 2 system audio headaches.

I would pay extra for those futures. Not having any time code in the DSLR world is a big headache for me.
 
Last edited:
Nice. More suggestions. I'd add I'd also be willing to pay more for the program (obviously) for the updates. Pro Version? With Noise reduction? Yes.

bitcrusher said:
Just bought the mac version on the itunes store. Best $50 bucks spent in a while!
Something totally out there: The ability to use a audio track as the TC. That way we could feed TC into the audio mic in (you would have to attenuate the TC signal quite a bit so some hardware is required) That would solve a lot of 2 system audio headaches.

I would pay extra for those futures. Not having any time code in the DSLR world is a big headache for me.
Click to expand...

Especially like this. I hate syncing sound and trying everything I can to avoid it. The more automated the better...
 
Just downloaded 5DtoRGB for testing.
5DtoRGB can't seem to open GH2 m2ts file. I only got it to work by renaming all the m2ts to mts. Is this the workflow?
 
Beats me... It has always been m2ts. Perhaps the avccam software that I use to copy the sd card to my Mac changes the file extension from mts to m2ts.
 
Last edited:
I also tried 5DtoRGB and the converted files look far superior to the mts-files (though about 10x bigger). But I have a serious problem which makes it impossible for me to use 5DtoRGB properly: I'm a GH1 owner and since the GH1 doesn't record 24p natively but wraps it into 29.97 interlaced, I get these weird "interlaced lines" (don't know what they are called, but you get what I mean). Is there something I can do about it? I'm using CS5.5, PP to edit, AE to remove 3:2 pulldown (which of course doesn't work after conversion).
 
Another test i posted in the AF100 section to clear up some misconceptions:

AF100 - 24mm lens F2.8 ( focused on the white fluffy thing on the desk )
CineD
Norm 1
detail at -5
chroma at -5

AF100

fullpl.jpg


Link: http://img717.imageshack.us/img717/1665/fullpl.jpg


400% Zooms

af100close01.jpg


Link: http://img694.imageshack.us/img694/1204/af100close01.jpg


af100close02.jpg


Link: http://img10.imageshack.us/img10/1276/af100close02.jpg

GH2 in Cinema Mode with Quantam V2 and 5DtoRGB ( -2 -2 -1 -2 )

cinemal.jpg


Link: http://img843.imageshack.us/img843/6276/cinemal.jpg


400% Zooms

cinemaclose1.jpg


Link: http://img804.imageshack.us/img804/2421/cinemaclose1.jpg


cinemaclose2.jpg


Link: http://img834.imageshack.us/img834/4065/cinemaclose2.jpg


Smooth mode ( -2 -2 -1 -2 )

smoothl.jpg


Link: http://img836.imageshack.us/img836/5775/smoothl.jpg


400% zooms

smoothclose1.jpg


Link: http://img600.imageshack.us/img600/3812/smoothclose1.jpg


smoothclose2.jpg


Link: http://img804.imageshack.us/img804/1419/smoothclose2.jpg
 
metavox said:
I'm a GH1 owner and since the GH1 doesn't record 24p natively but wraps it into 29.97 interlaced, I get these weird "interlaced lines" (don't know what they are called, but you get what I mean). Is there something I can do about it?
Click to expand...
If you'd like to try a GH1 Native 24p patch, I'd recommend either Blackout-Powell or Max Latitude patches, linked in my signature below:
 
Finally got my 5DtoRGB Batch program... just wish the 1.8 settings were still there. Messing with shaders is giving me trouble and I don't understand that enough to actually do it properly... blerg..
 
I emailed them to find out, waiting on a response. The shader works now but it's turning my footage black and white... which would be cool if I needed black and white footage... lol.
 
Hi Thomas, thanks for your work. Are you still taking suggestions?

I like the way you manage the timecode (in fact you added a specific request I made earlier that made my life easier and my workflow possible, THANKS AGAIN!), there's only one step that I have to manually fix after the transcode, and that's the Reel info. If I could somehow provide that info with a command line argument or maybe just the program took it from the file's parent folder name... I would be golden.

I'll try to pitch my boss to buy the new version but the 5d2-shot feature we're working on will be reaching final cut in about one or two months, so I'm not sure I should touch anything now. Will the newer version give me more quality to generate my online files or are the changes centered on avchd? Has the CLI syntax changed since 1.5.3b?

Thanks!
 
Last edited:
Tim Joy said:
I got the batch ver too and I was like, where is the 'bake in gamma' settings ? Any insight there.
Click to expand...
There was (or at least I thought there was) a good reason to get rid of the gamma options. However, after getting lots of feedback on this I didn't realize how popular the gamma correction feature was. So, it will be coming back with the ability to specify any gamma value you want. It works like the gamma correction filter in Final Cut Pro. You can specify a gamma value (i.e. 0.818, 1.22) and it will be applied during transcoding. This will be baked in, so any application you use to open the file shouldn't meddle with it. This will be coming in the next update and will be available free from the App Store as usual.

Daniel G said:
I like the way you manage the timecode (in fact you added a specific request I made earlier that made my life easier and my workflow possible, THANKS AGAIN!), there's only one step that I have to manually fix after the transcode, and that's the Reel info. If I could somehow provide that info with a command line argument or maybe just the program took it from the file's parent folder name... I would be golden.
Click to expand...
File names will be written to the reel name field in the next update. Was that what you needed? Or was there something specific you needed to put into that field?

Has the CLI syntax changed since 1.5.3b?
Click to expand...
Only to reflect the new options (luma range, post-processing). Other than that, it should be similar.
 
Thomas Worth said:
File names will be written to the reel name field in the next update. Was that what you needed? Or was there something specific you needed to put into that field?
Click to expand...
File names will be fine for future red-style workflows but for this feature I need parent folder names and/or user input via CLI argument.

Thanks.
 
The ability to resize the footage on output would also be huge. We could conform different sized footage to one project-wide common format, not only on framerate, like we already do, but also on size.

That could also enable a reduced output for proxy use, although I'm not a fan of this.
 
You must log in or register to reply here.
Back
Top