Is there a possibility that someone from BMD could check their in house units and see if this is also occurring for them on the 4.7 firmware?

Also if another firmware update is pushed through to correct the issue, some valuable additions would be to correct the crosshatching in davinci resolve. You can see the effect happening in my sample pictures when shooting RAW. It's tedious to have to shift the pan and tilt by 0.5 for every clip.

Another addition would be to have the recording codec shown over the hdmi display. Unlike the pocket camera this is not a feature. It'd really help to reassure the user of their codec. Especially since you can now change codec via sbus, with no visual feedback as to what the camera is recording in this could get dangerous with accidental button presses.

Ryan, the recording frame rate and resolution setting is on the top left corner of the monitor on both the Video Assist and SmallHD monitors, which show the receiving resolution frame rate of the signal, so it is. It necessary to have the camera place this in the bottom camera settings line. The Pocket Camera shows this on its monitor, as it has a built in monitor, the Micro camera lacking a monitor, uses the attached monitor status line to get this frame rate / resolution setting info displayed.

Camera firmware is not going to correct a Resolve display issue, I think you need to do that in Resolve’s firmware.

Toggling Focus peaking and Zebras would be nice, especially the Zebra. Since the Micro uses an external monitor, I use the monitor’s peaking settings and turn this off in the camera, so I can get a clean screen very quickly. However, I do use camera Zebras to accurately get overexposure/clipping info, so toggling this with SBus would be handy. Cheers

Thank you for the response Denny. I know that the frame rate is already displayed and have no issue with that nor did I mention it as an issue. Further on the small hd dp4 the frame rate is actually in the bottom left corner and I don't believe the resolution is displayed as the BMMCC only records in HD.

You are misinformed for the codec as firmware 4.7 added the ability to change codec via sbus. For my unit using the smallhd dp4 the codec is not displayed on screen. I think this is a basic feature that is avaliable on every other BM camera. The micro should have it and make it a toggle, if you don't want clutter simply turn it off. I do find this an issue or inconvenience. This is further a problem now that you can create a remote that changes the codec and potentially change it accidentally.

Ryan, you are completely correct, my apologies, I missed the bit where codec can be changed via SBus, which would require a display to know what it is. I haven’t applied it to my camera yet, as I am waiting to get some before footage before doing so, after some reports of pixel issues. Thanks for the correction. My SmallHD 501displays frame rate and resolution (yes the Micro Cinema is 1080 only, but the display shows 29.97 1080p in the upper right hand corner, as does the Video Assist. Other monitors like the DP4 may display it elsewhere of course.Cheers

Probably it may help to remove Fixed Pattern Noise and this allow to recover more information from shadows and extend dynamic range. Currently Fixed Pattern Noise can be removed only in pots by substracting Fixed Pattern Mask layer as described in this thread viewtopic.php?f=2&t=19422 Due different cooling systems Fixed Pattern Noise in Micro Cinema Camera is more visible than in Pocket Cinema Camera.

CaptainHook wrote:Black shading does not target FPN in the URSA Mini 4.6K (Pro). It's purpose is to minimize black balance/offset drift for the 4.6K sensor.

Ah interesting, how would FPN be targeted?

My assumption is that the difficulty lay in not also reducing the cameras dynamic range but I'd have no idea how it'd be done.

A question a lot of us have is why the pocket seems to have none and the micro seems to be so affected? I've heard some people say it's the cooling system, some say that it's the left over circuitry from trying to make it global shutter. Really interesting stuff.

Is it something that can realistically be fixed in firmware while keeping acceptable IQ?

CaptainHook wrote:Black shading does not target FPN in the URSA Mini 4.6K (Pro). It's purpose is to minimize black balance/offset drift for the 4.6K sensor.

I think black shading = 'magically fix sensor issues" for many people - probably cos they don't really have any significant comprehension about what it actually does (me included)

I'm guessing here but I'm thinking the stuck pixels thing is maybe because some sort of fix for bad pixels on the sensor which has been active in previous firmware maybe went missing this time? (ie its not making bad pixels it's more a case of not hiding them like it used to)

I wonder if it would be possible to let the camera's "fix" stuck pixels on it's own. Like JVC, Sony and others do!!

Offcoarse you can fix the Stuck pixels now with Resolve. But for live video you are still in trouble if you have a stuck or hot pixel in your camera.

This is a major issue why i don't spend money on a few ursa pro's for live video as i'm afraid i will run into trouble within a few months with several stuck pixels in a set of 6 cameras. (Yes 6 cameras. We run a 4K OBV and want to have 6 cameras with that OBV! )

Seems pretty solid. I intentionally went handheld to see if anything was moving with the micro shake. all the splotchy looking stuck pixels seem to be gone from what I can tell.

The only thing of note was that I did find one or two pink pixels but it only for a second or so. it seems to be caused by the drastic change in colours going from brown/gold to black. So I assume there is a stuck pixel there and the fix for it is working to cover it up but me constantly moving it in and out of the black letter is giving it a hard time.

Otherwise it would seem it's fixed, nothing I or anyone would notice shown at normal viewing but I would be interested to test out a macro lens and see what happens, too bad I don't have one

Other things are.-Please put the codec on the display in the top left corner with the ability to toggle it off for those using the video assist.-cross hatching is still present.

Look forward to see other people do better tests than mine to see if it's fixed or not.