Messages

@Shimbarovsky: if your reply was addressed to my post, sorry I don't get it. I wrote that the recording is working ok until I press the Set button, and I was wondering what purpose the Set button has in recording mode.
Sure I must try to record at lower resolution to double check this and report here. Will do ASAP.
Cheers!

It works in 1080 and records correctly for as long as I wish.
But if, for error or distraction, I press the set button while recording, everything hangs.
I know, just don't press it but I'm wondering what the set button is supposed to do while recording? Should it zoom the display like when not in record mode? Is it possible to disable it?
I didn't check with older versions, if it's worth it I'll give it a go.
Thanks!

I installed the July 2018.3 build and having an issue when recording 1080p RAW footage.
If while recording i press the SET button, the camera freezes and i need to pull out the battery.
Is there something i can check to avoid this?

The loaded modules are mlv_rec, mlv_play and mlv_snd.

Thank you!
Umberto

@AWPStar: It is more a digital ISO ramping between steps induced by letting the camera handle the ISO adjustments than a deflicker. I will be able to upload something next Monday. Thanks!

Hi all! Just crossing this thread and just tried MLVProducer.
It really clicks on me, very cool tool!
I'm wondering if it can be used or extended to digitally smooth ISO jumps, like i was asking in the following thread:

https://www.magiclantern.fm/forum/index.php?topic=19665.0

Thanks!

Gave a spin to Bridge. Guess that CS5 is a bit too "vintage" for the script as apparently there is no result (watching with Bridge).
Anyway i fear that this would not be the right solution for Resolve, if Resolve is not capable to understand ACR metadata. The alternative algorithm that dmilligan suggested for MLVFS looks more appealing for my case.

I will try to dip my foot into dmilligan code, hope being able to remember how to code in C (usually a Java developer, with some spare time C++).
My offer for a contribution is still valid, anyway

@Danne: This may be what i'm after. I stopped using Bridge several years ago but now i'll give it one more  spin! Thanks.

@mothaibaphoto: I didn't mean to mislead anyone. Sorry if what i wrote made me looking a bad-guy. I simply performed some tests and drawn some conclusions. Too bad information is so fragmented that is very difficult to find an easy answer. Or maybe i didn't search enough, it's possible.

I simply performed the following tests:
1) Extracted the frames with MLRAWViewer: noticed that there are huge steps in exposure on my footage.

2) Extracted the frames with MLVFS with no parameters: same huge steps.

3) Extracted the frames with MLVFS and --deflicker parameter: noticed a better smoothing in exposure steps, not what i'm after but better than nothing. Given that dmilligan wrote that the deflicker algorithm writes into DNG metadata and that not all NLEs can interpret such metadata, by noticing a difference in DR my conclusion was that DR supports the metadata. Maybe this is a wrong conclusion so if you can correct me i'm more than happy. But i'm not a bad guy, just trying to learn something new.

P.S. The thread you linked stopped at 2013. Maybe more recent DR version addressed the metadata issue? Don't know.

Now the current algorithm is more clear to me, thanks dmilligan!

What i expected is to keep the current exposure as it is, and just ramping between ISO steps, which is different from the deflicker algorithm that is based only on the current frame analisys. This way the image would be kept as near to the original shot as possible, with a slight adaption only when ramping.
Something like a new iso-smooting-frames parameter, that let the user specify how many frames (at maximum) take for a ramp. Obviously if a ramp needs less frames to be accomplished, less frames would be used. Sure this algorithm needs to know what's before and what's after the current frame. I don't know MLVFS internals, i can imagine you already keep some kind of cache with frame parameters so you don't need to rebuild everything from scratch, but i'm just guessing.

I am a programmer but i fear i would take forever to wrap my mind around MLVFS code... i have not big money for my project (otherwise i had purchased a set of Rokinon Cinema lenses LOL) but if a contribution can help the development please let me know!

P.S. regardless i activate or not RAW video logging in movie tweaks, i cannot manage the 5DMKIII to produce the video *.log file with parameters changes. And MLFVS shows an empty *.log file. Where i'm wrong? I supposed that ML would write a sidecar log file, but this doesn't look so. It's all kept into the MLV file?

Thanks!

Thanks dmilligan for the hint!

Finally managed to understand how to achieve my result:
1) enable raw logging into Magic Lantern. Without raw logging no smoothing is possible
2) install MLVFS... not butter smooth but i guess it's not meant to be super easy. anyway, installed
3) resolve recognizes the metadata as it reacts correctly.

Now i'm asking myself if the deflicker algorithm speed can be biased. Is the result computed over all the clip length as some kind of interpolation? I noticed that the deflicker parameter drives some kind of exposure level, not smoothing time. I guess that modules such as exposure ramping are not effective in biasing the speed, as they are developed for timelapse...

I beg your patience... I suppose that the best way to get what i want is to plug a cinema lens with declicked aperture ring and work with aperture while shifting from light to dark zones... and deflicker is some kind of "placebo" feature? without offence to the feature itself, just to understand the feature.

Thanks again!

Thank a1ex for the reply.
I'm fine with digital ISO adjustments, definitely better than changing the shutter speed.

What i'm finding really difficult is to use MLFS + PFM (i'm on Win7x64) to get my files (i managed to create the MLV virtual folder but didn't understand how to pass the deflicker parameter so at the end i get the same result as MlRAWViewer).
Anyway, if i activate the video logging (which produces a frame by frame log file along the MLV file, with all parameters changes) is there some application that can leverage on this information to render a correct video sequence?
I'm just asking because i don't really know how to handle this log file by myself, and if it can be of any help.

Thanks!

Maybe i did something dumb...
I'm using MLRawViewer to convert MLV to CDNG sequences. Do i need to set something to enable smooth exposure transitions?
Would enabling video logging on the 5DMKIII add some support infos to help in the conversion?
Or simply it's not possible and the only way is to shot in manual mode?

Thank you again!

Hello all!
I'm trying to shoot clips in Aperture priority mode while moving from dark to light areas. While in the live view i see a very nice exposure ramping, if i review the MLV sequence in post i notice jumps in exposure.
I tried to use the deflickr module and to follow some post processing workflows, for example by correcting the black and white levels on the DNG sequence with EXIFTool, but they are the same over the whole clip.
What should i check to reproduce those smooth exposure transitions in my editing environment? (Resolve in my case)
Thank you!

Ah beh, l'ho notato adesso il thread sticky.

Io sono zona Vicenza, videoamatore a tempo perso con passione di video speleologici e di montagna. Sto muovendo i primi passi (un po' ansiosi) in ML con la mia 5DMKIII.
Ciao a tutti!

Umberto

Hi all! New to the forum.

I'm from Italy, a spare-time-filmmaker aiming to work mainly on caving videos. I used a BMPCC from a friend but found it to be very difficult to manage, both battery wise and in low light.
Purchased a second hand 5DMKIII last year mainly for photography, and never had the "bravery" to install ML firstly because my camera came with the latest firmware, then because i feared to fry something.

Well this week i decided to go on and downgrade to 1.2.3 FW then install ML on my machine.
It was smoother that i thought, and no fried my 5D yet! 
And I was speechless from the first tests.

So... to keep it simple: Thank you!