Post some before and after stills. This may be what THomas was referring to, that if you're using CS5 then it's not as much of a difference versus using ProRes/Quicktime formats. For me, in FCP, it's a huge different. If you're in FCP, then yes, you should be using ProRes 422HQ (or something around that).
GH2 AF100 with a hacked GH2
- Thread starter PaPa
- Start date
Post some before and after stills. This may be what THomas was referring to, that if you're using CS5 then it's not as much of a difference versus using ProRes/Quicktime formats. For me, in FCP, it's a huge different. If you're in FCP, then yes, you should be using ProRes 422HQ (or something around that).
PaPa
Major Contributor
I use DNxHD at 220 with the same settings you posted and i got these results. I'm on pc however.
Thomas Worth
Active member
Tell me what you guys want. I have the code open in front of me right now on the PC, so if it's something easy I can throw in I'll do it.
Free Version:
1. Keep 1.8 Flagging Option but default it to 1.8 so people don't mess with it.
2. Default the Decoding MAtrix to 709
3. Add a "don't show this message again" box for the warning when dragging and dropping .MTS files.
Paid Version
1. Add a preference pane that allows you to setup what you want as soon as you open the program, that way you don't ever have to change it. (if this already isn't there. I'm broke so I can't get the batch version yet, been one by oneing it lol)
Also, Thomas, what do you think about adding a denoise step in a future version that's a bit more expensive? Something that can do what Denoiser MB Does when you drop the Luma Offset and raise the Chroma offset. It literally just removes the ugly chroma mess and leaves the noise, which in my eyes looks sick and can be denoised further. That would reduce the headache of having to denoise chroma before going to grading, then doing it one final time to balance the overall dB.
Sorry, had to throw that in!
Thomas Worth
Active member
Let me explain why I removed this.
The flagging puts the burden of gamma correction on the NLE. If it sees that there's a gamma flag, it will use this to apply additional gamma correction. I don't like the idea of the NLE monkeying around with the gamma after it's already been transcoded perfectly, so this has been removed. Plus, there's no way I can guarantee that the gamma will look right in one program vs another.
However, if you want to mimic the 1.8 setting, you can use a GLSL shader. It is literally one line of code, and can be loaded automatically by 5DtoRGB. You can apply any gamma setting you want during transcoding, and this is done prior to the encoding step so the quality will be better than trying to do it in the NLE. Instructions on how to do this can be found in the manual.
Already looking into this!
I need to dig deeper into this, plan on doin a workflow post for my blog and this will help.
Thanks.
Fan-freakin'-tastic. Understandable that it will add more time to the transcode, I'm willing to bet that it'll be a lot less stressful than constantly spitting out generations of files. Key for me, personally, would just be the ability to convert the chroma to something that looks like luma, but of course incremental sliders and fine adjustments for those that want more out of it. I do NOT expect (or need) Neat Video depth of noise reduction.
I imagine it would require creating a panel for a video viewer so that you know exactly what you're getting... but definitely worth paying for.
One last question: DPX is fantastic, it's exactly what I'd be going to for a DaVinci grade. I'm curious as to why there isn't a 10-bit Uncompressed option? Does it make sense with formats like DPX and DNX, ProRes4444 already loaded to have an Uncompressed option at all? I don't need it, but was curious.
Hey Thomas,
I read the 5DtoRGB Batch manual entry on the GLSL Fragment Shader, but I'm still lost as to what concrete steps I would take to actually execute it on a transcode. Is there somewhere I'm supposed to be plugging this into the 5DtoRGB app? Or is it more like a command I'm running at the system level, from Terminal, and it's acting more like a LUT on my footage? I've poked around a bit in the .app folder and opened up the .plist file but I don't see anywhere to add a GLSL command.
I think a lot of us were happy with what we were getting from the 1.8 gamma setting on older versions of 5DtoRGB so if there's a way to replicate that behavior in the new version it would be nice.
Edit: Okay, I see now the instructions were a bit above where I was looking, in the program options section. I think I've got the gist of it now.
I read the 5DtoRGB Batch manual entry on the GLSL Fragment Shader, but I'm still lost as to what concrete steps I would take to actually execute it on a transcode. Is there somewhere I'm supposed to be plugging this into the 5DtoRGB app? Or is it more like a command I'm running at the system level, from Terminal, and it's acting more like a LUT on my footage? I've poked around a bit in the .app folder and opened up the .plist file but I don't see anywhere to add a GLSL command.
I think a lot of us were happy with what we were getting from the 1.8 gamma setting on older versions of 5DtoRGB so if there's a way to replicate that behavior in the new version it would be nice.
Edit: Okay, I see now the instructions were a bit above where I was looking, in the program options section. I think I've got the gist of it now.
Last edited:
Thomas Worth
Active member
You add the line of GLSL to a text file. Save it as "default.glsl" into the same directory that contains the files you want to transcode. It will automatically be loaded once you start the transcode.
You can also load other shaders using the "Import" option.
All of this will be obsolete soon...
I need to get the DNxHD codec. I tested it using QT Animation and it worked, but that transcodes really slowly.
But now of course I will be going to look at the manual and how to apply 1,8 gamma via scriptfile.
hi thomas. could you explain further the 1.8 gamma? atleast i want to be able to replicate the 1.8 gamma on my NLE on the newer version of 5dtorgb. since if i import plain mts and the new version it looks basically the same.
oh when can we have a windows paid version?
EDIT: ok after some coffee i get what youre saying now... so is there a way for the 5DtoRGB to convert the file with the 1.8gamma baked in and without the flagging? the new version converted files looks too contrasty and i dont know how to bring the gamma back
Last edited:
details wise, i do think its a compromise of moire vs. details and af100 took the less moire road. and for me its ok. the difference is not even discernible to the audience.
heres my test on the 5dtorgb on my af100 footage
BEFORE
http://www.dvxuser.com/V6/attachment.php?attachmentid=38358
AFTER
http://www.dvxuser.com/V6/attachment.php?attachmentid=38359
@PaPa
Nice tests! im surprised how unsaturated the GH2 footages are. I cant remember getting that low saturation on my GH2 :\
nostalgic looks like a warm version of cinema. smooth is a bit more contrastier but i bet it will save in highlight roll offs.
http://www.dvxuser.com/V6/attachment.php?attachmentid=38359
Here are three grabs, original MTS, QT Animation and DNxHD. Only Animation shows the jump in gamma.
(Iso 800, F2,0 on a 50mm Minolta MD Rokkor)
Here a dl-link to the full size PNGs I rendered out: Link
DNxHD
MTS
QT Animation
I´m on a PC and this old version of 5D has no Prores anyways. As transcoding everything to animation is silly (slow and 10x bigger than original) I will look into the code line option tomorrow and that then with the new version of 5D.
EDIT: Maybe this thread should be moved or divided or tidied up`, as the headline won´t tell anyone that we´re talking 5DtoRGb in here?
Last edited:
Thomas Worth
Active member
Copy the following line into a text file and save it as "default.glsl" in the same folder as the clips you want to transcode:
Code:
gl_FragColor.rgb = pow(gl_FragColor.rgb,vec3(1.0/0.818));Now, see that 0.818? That's the value you want to adjust to change the output gamma. This works like the Gamma Correction effect in Final Cut Pro, except it works in 10 bit right on the GPU before compression occurs.
It's being worked on. I haven't forgotten about Windows users!
@thomas
hmm 1.5.6b seems to be buggy for me... and i cant seem to get the default.glsl to work..
1.5.4 works well here though!
(its weird premiere sees the converted clip is 1 sec smaller than my mts file... AE doesnt)
after some coffee i get what youre saying now...
so is there a way for the 5DtoRGB to convert the file with the 1.8gamma baked in and without the flagging? the new version converted files looks too contrasty and i dont know how to bring the gamma back
or to put it shortly, we love the 1.5.4's gamma 1.8 look. we would love to have it to look consistent when imported throughout different NLEs.
hmm 1.5.6b seems to be buggy for me... and i cant seem to get the default.glsl to work..
1.5.4 works well here though!
(its weird premiere sees the converted clip is 1 sec smaller than my mts file... AE doesnt)
after some coffee i get what youre saying now...
so is there a way for the 5DtoRGB to convert the file with the 1.8gamma baked in and without the flagging? the new version converted files looks too contrasty and i dont know how to bring the gamma back
or to put it shortly, we love the 1.5.4's gamma 1.8 look. we would love to have it to look consistent when imported throughout different NLEs.
Last edited:
PaPa
Major Contributor
As i said in my post, i desaturated the clean's very very slightly to better match what the AF100 produced. But that's it. So i consider it fair game.
Oh i see. I guess the af100 would be easier to match to the GH2 that way. thanks for that info
Thomas Worth
Active member
Sorry, I should have mentioned this earlier. The shaders only work with the Mac version. I'll add this feature to the Windows version soon.
Jaime Valles
Veteran
Thanks, Kholi! I'm back. Planning a top-secret feature film to be shot on my GH2, so I'm learning all I can about the hack and such. I can't really make heads or tails out of the Personal View site, so I'm very glad that all this info is here on DVXUser.
Anyhoo, back on topic. How 'bout that 5DtoRGB, huh?
That explaines why I can´t get any results.