That's not a camera issue, because In software like Davinci Resolve or video players these files looks identically. But in Premiere Pro, After Effects and Photoshop .MP4 files has wrong, shifted colors (looks like they're in Rec.601 space).
Did you see the shimmer there?
I have no time yet, I'll see later.
In a Rec.601 file, the visible values start at 16, it is OK for dark noise to be recorded in values 12, 13, 14, 15 because they will all be displayed as pure black unless edited. So someone seeing this file displayed as Rec.601 would not see most of the flicker and lines. However the file is marked as full range, the visible values should start at 0, so when displayed correctly as a full range file, noise at level 12 will be easily seen.
My concern is that whoever calibrated the exposure set it up using a Rec.601 display and not the full range display they should have been using, that would explain people seeing the noise when they play it properly. If it was calibrated correctly using a full range display, why are there no values less than 12?
Yes, some software will display or edit it incorrectly, and some operating systems/graphic cards will be configured incorrectly, and some monitors are incorrectly calibrated. There are many reasons why different people will see different amounts of flicker/lines noise. My question is only, why is none of the image darker than level 12 when it is a full range file that should go down to 0?
Still this can be from the 264 codec, it is for 1080P, and for 4K you need 265, I installed it myself by default.
I have never tried the A119 V3 configured for 4K and H265, what colour space does that use? Maybe that has no flicker?
But the raw files we are looking at and which have some visible flicker are all H264 and marked as full range BT.709. If they started at 0 instead of 12 then I don't think anyone would be complaining about flicker since it would be nearly invisible even on the noisiest camera!