Recent content by chunky

If we would get 4K „resolution“ instead of only imagesize this would be fair - of course! You know the difference between resolution and imagesize-/dimension?! In „true“ 4K (3840x2160) every single pixel can adopt to an individual state not influenced by surrounding pixels. An ideal 4K camera...

Here we see DJI still cheats us with wrong specs on their website. We are still told we get 4K resolution from the camera - they still mix up with „image size“ or „video mode“ and they are to arrogant even to change this here!

das That proves this guy has „no clue“, maybe even not a 4K screen to judge since you won‘t see a difference on a FHD screen. In real life sceenes IT IS a relevant difference between P4pro 4K30p and M2P FFOV!

HQ mode is „ok“, men, it really is. FFOV is described differently and quality is really low. This has to be improved by DJI to fulfill the specs and quality demands. We didn‘t buy a sub 2.7K drone but got one! FFOV resolution is clear behind an at least „native sampling“ 4K camera (like HQ...

They write 4K resolution - CHECK!! The M2P also doesn‘t cannibalize the P4pro since it has no „professional“ 4K60p, adding the ascent and descent numbers are higher with the P4pro, the controller is more ergonomic with better sticks and a better gimbal wheel.

Maybe compare this, no question, a bit weak to prove my statement about „resolution“ that I felt certain sure about. Other definitions I found are about differentiation of (mostly repeating) conditions. Maybe I find better proves to „image-/video resolution“ vs. image-/picturesize. Image...

The ‚soft optics‘ seem to work better in HQ and photo mode - curious magic...!!??

Cliff‘s and my resolution chart tests are good enough to show the M2P resolution is less than P4pro‘s resolution. We „expect“ both to do 4K resolution, M2p is even specified as being 4K resolution (not the P4p, there we read „videomodes“ or so...). We have „fire“ now everywhere, different...

It‘s always my aim to help the weaker and prevent wrong information being spread, so that‘s the reason why „we“ are still talking. I well know the function of CCDs even if it‘s nearly „past perfect“ these days. A denotation is not stuck to one technology only because it was used with it before...

I didn‘t test this yet. Video pixelcount (image size) is not the same as video resolution (differenciate image information). nK video-/imageresolution means any pixel in the image can assume an individual state not affected by surrounding pixels (like in synthetic graphics without anti aliasing...

I already explained you how this is done - with simple CMOS switches between pixels but you are still one way. Any idea how Sony does the Exmor RS, guy?? Reading the whole sensor with 960fps to the SoC... Really ;-) ;-) ;-)??? I‘m engineer, going with the time and knowing actual technique - but...

You are wrong in one point - DJI specified the video to 4K RESOLUTION - not imagesize and that‘s the point!! They don‘t reach 4K resolution by far since the image is won by binning means getting 2x2 pixels for one! See the specs, the faqs about FullFOV and the manual regarding FullFOV - all...

The only problem is there is NO down scale as described, they are just „interleaving“ - no, we had this, they‘re binning and that always gives up resolution instead of gaining it since debayering effects would become less visible through real downscale!

So it is, binning and skipping is really not the same (better SNR with binning) but resolutionwise it‘s the same and I also don‘t see „RAW subsampling“ is delivering anything close to the specified 4K resolution, it‘s hardly close to real 2.7K resolution! DJI listen - I wait a bit until you...

+1 for part 1, but I wouldn‘t say sharpening helps here really. I only found noise kicking in quite early and getting rid of noise with Neat Video is still lot‘s of computing power, even with stromg GPUs. Resolve Studio is not the same league.