I wanted to ask, is this version more stable than the last 2018Jul22 croprec build? Particularly regarding bad frames and such.
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: masc on April 17, 2023, 01:58:33 PM
@togg: you could plan to do the color correction and grading in MLVApp - it is made for this.
Quote from: masc on April 15, 2023, 11:19:31 AM
Processing in MLVApp and importing this into Resolve? I don't understand the need of replicating, when you can use the original for free.
Quote from: masc on April 12, 2023, 01:27:29 PM
I think you are wrong. All the detail comes out very different and shadows look just dead with this setting. It is way more than just a curve... If you look for the MLVApp look in another application, the closest should be ACR. Using Resolve for MLVApp look this is a really hard task.
Quote from: ilia3101 on October 05, 2022, 03:04:08 PM
Oh ok. I wouldn't even claim MLV App matches the exposure correctly. The 1.2 stops is just an absolute guess. Adobe camera raw probably knows better about this stuff (at least on CR2s)... although in the case of DNGs generated from MLV, the exposure offset metadata may be missing, so it's possible camera raw doesn't do the 'hidden exposure' with those. Just guessing.
If you have any interest in doing it, I'd love to see a comparison between:
1. CR2 photo through camera raw
2. MLV video through MLV App
3. A DNG created from that MLV, through camera raw
Where the MLV and the CR2 use the same aperture, ISO and shutter settings. ISO 100/200/400/800, not the inbetween steps. I'd do it myself if I had Adobe software.
My (likely wrong) prediction: 1 and 2 exposure will match, but 3 will be darker.
Quote from: masc on October 05, 2022, 11:34:14 AM
Adobe Camera RAW brings a very similar amount of noise and similar looking results, when I compared both. At least if you setup the chroma denoiser sliders to comparable values.
Quote from: wib on July 10, 2021, 03:00:51 AM
super reportage ! les gars sont passionnés !
so what was your set up ?
Quote from: masc on June 05, 2021, 10:53:41 AM
Even on a 10 years old quadcore CPU you can have "close-to-realtime" playback in MLVApp when using default settings. For 1080p I get 22fps on my iMac2011. The more fancy features you use, the slower the processing will be.
Quote from: masc on January 31, 2021, 10:32:21 PM
@togg: the .bpm is auto generated as soon as you start telling MLVApp where the pixels are.
https://www.youtube.com/watch?v=Xwd2DFGjMx0
Quote from: masc on January 27, 2021, 08:16:57 PM
@togg:
1) how did you get this picture? What exactly does it show?
2) no need for this
--> you define the bad pixel map for any clip. This map is saved as .bpm in the MLVApp folder. As soon as you activate bad pixel map fix for any other clip using the same camera raw stream settings, the same .bpm will be used again. So ideally, you create this map once for your setting and use it forever for all future clips (in the same setting).
Quote from: Kharak on December 10, 2020, 11:23:55 PM
It depends on your shooting style, I personally don't like to hold the camera out in front of me, it creates too many shakes and with all the added gear it quickly becomes a heavy brick that shakes when I get tired.
If not shoulder mounted ofcourse, I usually keep the right hand on Top handle and left hand on focus wheel/lens barrel and shoot from the hip or chest. But the caveat is after a long day of staring down in to the monitor, the neck is gonna hurt.
You already have a side handle, I don't know about this wooden one, maybe it is better, but it looks like your rig will pull down on the left because of the center of gravity being placed where the camera sits, this will most likely cause more shakes for you as you battle the gravity pulling down to your left.
Page created in 0.095 seconds with 14 queries.