Well, I've got a full set of smallrig using bf promotions. I'll see how it goes!
Etiquette, expectations, entitlement...
@autoexec_bin | #magiclantern | Discord | Reddit | Server issues
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Show posts MenuQuote from: Kharak on November 25, 2020, 10:38:06 AM
I use 8sinn cage with the (i think its called) scorpion top handle, got 4 hot shoe mounts in the handle plus screw mounts all over. With rails under the cage, i still have not managed to get a perfect balance. But with monitor placed on the back hotshoe on the handle, hip shooting is a breeze and very stable, but going one handed low is a tad too shaky for me.
I am currently looking for the classic Juicedlink RM333 (anyone know someone?), to be placed on the back end of the rails for a uniform front/back balance. Because adding a shotgun at the moment throws of the balance and having a zoom recorder under or on the side is just not working. (Plus they have the worst battery life and syncing is crap).
I am trying to increase the cameras "momentum" not sure if that is the right word, but the bigger the rig, the smaller the shakes, but too big and it becomes cumbersome, so its really about finding a balance between how heavy and balanced I want it.
I would just becareful about making your rig too wide, rather I would lenghten the rig for better movement.
Quote from: wib on September 27, 2020, 03:26:52 PM
here for example, mostly visible at 30s, the guy walking with a grey backpack, his bag curve is like a staircase. It's more noticeable if you watch it on a 4K monitor
(shot in 1080p but anamorphic preset)
Quote from: cmh on April 28, 2020, 05:59:00 PM
To my understanding:
- There is no information clipped if we use rec709 (or linear whatever) in the raw tab and it's totally okay to, before any grade, use the first node as a color space tranform to log (like rec709 to alexa or cineon).
- Using bmdfilm in the raw tab is a no-no and needs further color processing (a lut to match this particular canon camera for exemple like Digital Bolex do) but to verify my statement we should both shoot a color chart (which I don't have) in the same lighting conditions and compare the results of our cameras with your 1.50 dpx for exemple.
- There's probably missing metadata in our dng compared to blackmagic cameras cdng, like ISO apparently that would explain the fact that we have to change exposure (as we said before the whole histogram is on the left which is not what a blackmagic camera would get).
edit: It might be the value named BaselineExposure. Compared with exiftool it is set to 3.09 on an ursa mini, 0.76 on a Digital Bolex D16 and 0 on an eos m cdng from MLVApp.
Tf you want to overwrite the original files with a value of 1.25 so you don't have to correct for exposure:
exiftool -BaselineExposure=1.25 -overwrite_original *.dng
It is a quick operation.
Quote from: cmh on March 14, 2020, 12:57:08 AM
Just a basic color correction on random scenes using the power grade you shared to see how it holds up with skin tones in different conditions (an olive complexion shot at 5000K at multiple times of the day).
I'm using the 1.50 dpx and the Rec709 Fujifilm 3513DI D65 lut at 30% as a last node instead of Juan Melara's lut.
Fujifilm 3513DI is way too green in the shadows. I'll stick to Kodak 2383 next time and correct the red cast I get from it.
I tried to get rid of the Alexa CST multiple times but I've always ended up correcting highlights here and there using curves and tone mapping so I'll just keep it as it is.
Quote from: ilia3101 on February 12, 2020, 10:53:25 PM
Because to be honest BMDFilm is a bullshit concept. For each Blackmagic camera it seems to have a different gamut and a different curve. I found a matrix on some blackmagic forum, and the log curve may have been added by masc. Both are definitely wrong.
What gamut and curve does BMDFilm have for non Blackmagic cameras in Resolve? Who knows...
TLDR: I do not recommend it, use a better defined log profile like Arri Log C
Quote from: cmh on January 29, 2020, 09:05:58 PM
The grade 1.50.1 (third still I presume) is pretty simple but it has really great skin tones on an EOS M (the reds are leaning towards the orange tho).
My previous workflow for a quick first pass grade:
I used to enable Pre Tone Curve in the raw project settings, leave the color space to rec.709/sRGB and up the gain to +20 in the raw tab with few other settings: Saturation -5, Color boost +10 to temper the red channel a bit, Highlight -30, Shadows +10. Finally a gamut mapping node: Gamma sRGB, Tone Mapping Luminance, Max Input 1000.
It doesn't look bad but the problem is that if I do a daylight white balance of a mixed lights environnement, skin tones might have to be fixed separately.
Your grade is pretty spot on right off the bat. Thanks for sharing. It's a nice improvement compared to what I used to do, I'll try to fiddle a bit with it.
Quote from: Dmytro_ua on January 09, 2020, 01:50:36 PM
Could you share a preview image of the RAW file and your edit result?
Quote from: ozcancelik on December 05, 2019, 09:18:16 AM
It can be logo but for icon I think only extension ".MLV" can be text. Also my idea was "RGB with Sliders". Thats what MLV Apps mostly doing.
Quote from: codemonkey on July 12, 2019, 10:50:59 AM
thanks for pointing that out. i wanted to stay in raw in resolve, but there's no way around that when i shot in hdr.
is there an easier way to automatically adjust white balance in mlvapp with with a colorpicker thing with a white
is there something better than prores4444 for editing in resolve?
Quote from: Ilia3101 on July 24, 2019, 07:17:30 PM
an explanation:
Don't use camera matrix: camera's native RGB channels are interpreted as rec709 primaries, and white balance is done in those colour channels - I do not recommend this mode for accuracy, also different cameras will not match.
Use camera matrix: camera colours are converted to MLV App's processing gamut accurately using camera specific matrix, and white balance is done in LMS colour space (where the R, G and B channels imitate eye colour cells), which should preserve colour constancy better.
Uncolourscience fix: Same as use camera matrix, except the white balance is not done in LMS gamut, instead it is one that @Danne came up with by tweaking matrix values, it helps reduce blue clipping at lower colour temperatures (2000-3000K), but should not be used if there aren't any clipping problems, as it can and will affect colour quality or accuracy. This mode will be removed when BetterProcessing branch is complete (it should fix the clipping issues).
Quote from: DavidP on July 23, 2019, 08:15:53 PM
Hi guys, Ive been away a long time and have an Ursa Mini Pro as my main cam now but just ordered a trusty old 5d mk iii in the hope it will make a nice B cam! So this app looks very promising but I notice it has no inbuilt preset looks? LUTS. What are you guys using to take into resolve and match with other cameras?
Quote from: yourboylloyd on June 11, 2019, 07:30:30 AM
Lexar is trash man.
Consider going with a smaller card. The 64GB's that I've had have worked flawlessly for years now. CF cards weren't meant to go past 64GB anyway. 128GB and most other NAND based cards will have close to 3000 write cycles before failing.
Quote from: timbytheriver on June 11, 2019, 10:07:26 AM
My experience with Lexar 1066x was that it was sloooow on my 5D3. There's a thread on it here somewhere...
Quote from: katrikura on June 12, 2019, 01:47:24 AM
Hello, I have 3 KomputerBay cards, 128 and 64GB, I've never had problems recording in a 5D3 at 1920 x 1080 14 bit, I bought several lexar and they have lower performance. That is my experience.
Quote from: yourboylloyd on June 10, 2019, 09:31:30 PM
Yeah I had a 128GB that died out recently on me too after about a year. Amazon's really really good with refunding.
Page created in 0.125 seconds with 13 queries.