Stathman reacted to Attila Bakos in Colorizer Film Simulation LUTs for Fujifilm X-T3 F-Log
Finally finished this project:
More info: http://colorizer.net/index.php?op=xt3
Stathman reacted to androidlad in I WILL be getting a Fuji X-T3!
Shot a water sports festival with X-T3, hugely empowered by the enhanced face detection in the latest firmware, face select also came in handy when switching subject.
F-log, HEVC 400Mbps LongGOP, sharpness and NR -4, custom WB.
Graded with GHalex LUT, simple contrast/saturation adjustments
A couple observations:
1. Face detection does not work at all with sunglasses, would be great if it could.
2. To get the purest colours from X-T3, custom WB is the way to go! Use a proper white/neutral grey card to set a custom WB to the key light.
Stathman reacted to Anaconda_ in I WILL be getting a Fuji X-T3!
Here's a screen grab of the images in Resolve, the left screen is the XT3 file and the right is from the Ninja. I set them both to 300 and lined them up to form basically one image with a line in the middle. I thought that would be the easiest way to see if there's any difference in the colour. - both are set to Full in Clip Attributes. To my eyes, they're exactly the same, but if there is a difference, I wouldn't even think about it while shooting.
One thing I did notice though, is the capture from the Atomos is 2 or 3 frames behind the file straight from the camera, nothing major, and I'm sure it's not camera / recorder specific, but worth noting.
If people want, I could also post screen grabs from the colour page, showing the histogram, vector scope, curves etc. But they don't change at all between the clips. Safe to say they're exactly the same image from that perspective too...
Stathman reacted to Attila Bakos in Interpretation issues of Fujifilm video files in Davinci Resolve, Premiere Pro and Final Cut Pro
The issue this video covers was already mentioned in several topics, but I promised a video explanation and fixes, so here it is.
Beware: long, boring, bad English.
Stathman reacted to Andrew Reid in DPReview BANS links to EOSHD!!
Barney Britton has responded to say he is now consigning all my emails to his spam folder and breaking off communications.
If he won't remove the ban on EOSHD at DPReview, then Amazon will.
And I sent him this:
It isn’t a closed matter or a case for the spam folder for me. I will be taking things to Amazon, putting in a complaint with them about the negative impression your forum ban is creating for EOSHD, the censorship of your own users and the damage it has caused to the reputation of my site. No doubt I will be pointing out the history of copyright infringement and slander on your forum to them as well, because I have screenshots of posts that were left up for months before being deleted.
As well as the inconvenience the forum URL ban places on your users (and Amazon’s customers), it means that Google is picking up EOSHD related topics and discussions on your forum, placing these above the original topics on EOSHD and they are all orphaned without a link to the source, damaging the SEO ranking of my site and causing material harm to my income.
The forum ban has been in place for how many years now - 3? 4?
You have over several years wound me up to such an extent that you’ve created a negative impression with other staff at DPReview such as with Scott, Chris and Jordan, as well as your forum users. It’s an absolute disgrace. I didn’t have a problem with anyone else at DPReview apart from you and Shawn. Gannon makes a string of idiotic mistakes, but you’re persistently insidious.
Think about that next time you have the cheek to ask me to seek to edit my opinions on my own forum.
At least I managed to refrain from calling him a cock-womble this time.
Time to turn my focus to Amazon, after all they are the real boss. It is time for Amazon to put an end to the personal vendettas.
Stathman got a reaction from MacMurphy in Fuji X-T3 reborn with HLG
Following @androidlad's findings i did some tests trying to decide which to choose, Flog or HLG.
FLOG: ISO 640 - SHUTTER 2000 - WB 5300K - F8
HLG: ISO 1000 - SHUTTER 3200 - WB 5300K - F8
Both shots exposed with Multi Metering aiming at 0 on the display meter.
Here are the results:
FLOG + FUJIFILM FLOG to WDR BT.709 LUT
HLG + LUTCalc HLG to ALEXA X2 LUT
HLG + LUTCalc HLG Rec709 LUT
FLOG + FUJIFILM FLOG to WDR BT.709 LUT + MINOR EXPOSURE ADJUSTMENTS
HLG + LUTCalc HLG Rec709 LUT + MINOR EXPOSURE ADJUSTMENTS
You can download the original files if you want.
Stathman reacted to Snowbro in "Boom Be Gone!" (Adobe's new Content Aware Fill Tool)
Knowing Adobe, it will fry your CPU using this, but leave your GPU unused
Stathman reacted to IronFilm in "Boom Be Gone!" (Adobe's new Content Aware Fill Tool)
I hope in the future as the VFX tools we have at hand get better and as crew awareness increases then we'll be able to happily have booms in shot much more often for the sake of improved sound. This is already common place on many shoots such as "House of Cards", and advancing VFX technology will lead to an expansion of situations booms can be put into shot.
Stathman reacted to Andrew Reid in Canon M50 - Magic Lantern
Magic Lantern have hacked the Canon M50 today, in a surprise move, since it was previously thought Canon had blocked the M50 from loading any scripts.
Features of the first version of Magic Lantern for the M50 dubbed "Hello World" include 6K RAW video (using pixel binning) and animated wallpapers.
Read the full article
Stathman reacted to OliKMIA in Back on the ball - a word about the lack of updates at EOSHD recently
Nice, +1 for the written articles versus videos. Looking forward to see all this content. Thanks.
Stathman reacted to Andrew Reid in Back on the ball - a word about the lack of updates at EOSHD recently
I'm going to be back up to full throttle on EOSHD starting today. For those of you who are wondering where I've been and what I've been doing, here's a glance at what I've been working on...
Read the full article
Stathman reacted to Attila Bakos in Atomos Ninja V and Fuji X-H1
I finally figured out why I experienced problems with the LUT. An incorrect YCbCr->RGB conversion will result in values outside the 0-1 range. The LUT sees these values as 0 and 1 in Resolve, that's the reason for the inaccuracy. Premiere handles the LUT differently, there is no clamping there, and the results will be perfect, identical to using the DCTL version in Resolve. However it's possible the build a perfect LUT for Resolve as well, which will come in handy for non-Studio users. I actually built one, I plan to publish it alongside a video describing the problem in detail.