You can now shoot 1952x1112 on the BMPCC OG!

Well...actually it's only ever shot at 1952x1112 but it's been cropped by NLEs through metadata to 1920x1080.

Some people on the Magic Lantern forums have created a script to batch change the metadata of cDNG clips to get that data back and usable.

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

It's only a 4.6% resolution increase but the extra resolution can be used to increase field of view or for re-framing/stabilization.

Here's the Reddit thread where I found out about it:
https://www.reddit.com/r/bmpcc/comments ... ution_for/

I know this is a long shot since the camera has been discontinued but since it's the exact same amount of data that the camera already records, it would be great if BMD enabled this in an actual firmware update so people can frame with it in-mind. I know it's only an extra 32px in each dimension but at that resolution, it's still noticeable and would save time people a lot of time. Of course, I'm aware there was a lawsuit filed against BMD for including cDNG in it's cameras so if that technically prevents BMD from being able to provide a firmware update to the camera in anyway, then I get that.

Glad I didn't sell ours.

Now I'm kicking myself for recording all my footage in Prores for the last ten years. After getting the BMCC6K I did free my pocket from its cage and bought a cheap Panny lens so I can take it on the run, free and wild like it was meant to be. Semi-pocketable as the lens is sorta big. Bagable, though. Since I did that I have been shooting RAW, so this is a timely update for future endeavors since I'm not taking that hog 6K on the run like that. It's going to get the Smallrig yoke of oppression now (someday when they release it). Thanks for sharing this!

[Kristian Lam]

The extra pixels were needed for debayering purposes so you'll find that all our CDNG captures should have a border of pixels that makes it slightly wider than the advertised resolution.

This work with the BMMCC OG too

The extra pixels were needed for debayering purposes so you'll find that all our CDNG captures should have a border of pixels that makes it slightly wider than the advertised resolution.

That's what I was originally assuming because demosaicking obviously requires some adjacent values for interpolation, even for edge pixels. However I was confused because 32 extra pixels felt excessive and Resolve seemed to be demosaicing the image just fine without them. Like I'm not aware of any demosaicking algorithm that uses 35x35 pixel ketnels.

I don't know if this is actually all that helpful. It might be nice for some micro reframing but scaling 1952 to 1920 is going to invoke unwanted scaling artifacts. Any resolution gains from a marginally larger sensor will be eradicated when scaled to a standard deliverable resolution.

Good Luck

scaled.tiff (159.59 KiB) Viewed 1285 times

As far as I remember, even the original BMCC had 32 additional sensor photosites beyond the advertised media resolution and these extra photosites were used in the debayer processing.

The ML Raw viewer from almost a decade ago revealed and likely processed the outer pixels, don't have the footage anymore to compare. Reminds me of how primitive the Pocket firmware used to be. Change a battery, clip resets, change a card, clip resets. Clip suffixes were basically useless as you'd have hundreds of clips that ended with C0000, C0001, etc.,

Good Luck

mlraw.JPG (182.38 KiB) Viewed 1228 times

I wonder if this works with the Production 4k as well?

I don't know if this is actually all that helpful. It might be nice for some micro reframing but scaling 1952 to 1920 is going to invoke unwanted scaling artifacts. Any resolution gains from a marginally larger sensor will be eradicated when scaled to a standard deliverable resolution.

Good Luck

scaled.tiff

Howard is correct.

The extra pixels are there so you get “nice” 1920 x 1080 out of the algorithm.

JB