Mavic Pro-2 vs Zoom and P4P - Line Skipping + Sensor Heat?
- Thread starter Cliff_622
- Start date
They should have done a 1 inch sensor with 1080p resolution. Very big pixels with good light intake. And a 1:1 read-out.
What should „RAW subsampling“ be ;-)?!
This answear is a joke!
If the complete 5.5K sensor is read we would have nothing else than with the P4Pro that downsamples the 5.5K image to 4K output.
As many tests state the 4K FFOV mode only gives resolution of close to 2.7K real image information, horizontal as vertical.
With simple maths this is half the 5.5K resolution of the sensor, so the sensor resolution is divided by two - maybe by lineskipping or pixelbinning (I expect the later since SNR seems to improve a bit in FFOV).
We have some people here that are somewhat deeper in the techs, don‘t expect everyone to be plain stupid.
This answear is a joke!
If the complete 5.5K sensor is read we would have nothing else than with the P4Pro that downsamples the 5.5K image to 4K output.
As many tests state the 4K FFOV mode only gives resolution of close to 2.7K real image information, horizontal as vertical.
With simple maths this is half the 5.5K resolution of the sensor, so the sensor resolution is divided by two - maybe by lineskipping or pixelbinning (I expect the later since SNR seems to improve a bit in FFOV).
We have some people here that are somewhat deeper in the techs, don‘t expect everyone to be plain stupid.
It is given in the response.
In short: "Raw subsampling" is not simple average pixel binning, it's a optimized and more advanced pixel binning!
Last edited:
Specsheet to the possibly used sensor:
https://www.sony-semicon.co.jp/products_en/IS/sensor0/img/product/cmos/IMX183CLK-J_CQJ-J_Flyer.pdf
What we learn is that the sensor can be windowed/cropped and so gives us in 16:9 the following framerates (according Table 3):
16:9 height: 5472 / 16 x 9 [px] = 3078px,
so 16:9 image is 5472 x 3078 [px],
what is 3648 / 3078 [px] = 1.185 times faster for readout than the full 3:2 sensor area.
So we would get 24.98 x 1.185 = 29.6 [fps] in 10bit and 21.98 x 1.185 = 26 [fps] in 12bit - at least enough for creating „real 10bit from 12bit“ in 24p or 25p!
We don‘t know what‘s going on in the P4pro that it‘s possible to get full scan 30p that would only be a tiny bit higher than the „specified“ 29.6p. Maybe the Input/LVDS frequency is a bit higher from the (SoC’s) PLL, „maybe the older sensor“ in the P4p is a bit different.
BTW: nearly everyone found the FFOV resolution to be lower than that from the P4p, why should this only been seen in testcharts (which not only represent a single color at least in one case), not in real recordings?!
At least „Cliff...“ and also me compared „real recordings“ and we both come to the same conclusion, the M2P lacks behind!
You see this in grass and trees/branches and also in diagonal lines which show soft since interpolated humps!!
DJI, don‘t think us stupid!
Deliver what you promised us in the manual and the FAQs - (close) „4K resolution“, not only imagesize!
https://www.sony-semicon.co.jp/products_en/IS/sensor0/img/product/cmos/IMX183CLK-J_CQJ-J_Flyer.pdf
What we learn is that the sensor can be windowed/cropped and so gives us in 16:9 the following framerates (according Table 3):
16:9 height: 5472 / 16 x 9 [px] = 3078px,
so 16:9 image is 5472 x 3078 [px],
what is 3648 / 3078 [px] = 1.185 times faster for readout than the full 3:2 sensor area.
So we would get 24.98 x 1.185 = 29.6 [fps] in 10bit and 21.98 x 1.185 = 26 [fps] in 12bit - at least enough for creating „real 10bit from 12bit“ in 24p or 25p!
We don‘t know what‘s going on in the P4pro that it‘s possible to get full scan 30p that would only be a tiny bit higher than the „specified“ 29.6p. Maybe the Input/LVDS frequency is a bit higher from the (SoC’s) PLL, „maybe the older sensor“ in the P4p is a bit different.
BTW: nearly everyone found the FFOV resolution to be lower than that from the P4p, why should this only been seen in testcharts (which not only represent a single color at least in one case), not in real recordings?!
At least „Cliff...“ and also me compared „real recordings“ and we both come to the same conclusion, the M2P lacks behind!
You see this in grass and trees/branches and also in diagonal lines which show soft since interpolated humps!!
DJI, don‘t think us stupid!
Deliver what you promised us in the manual and the FAQs - (close) „4K resolution“, not only imagesize!
So why should „this“ be used when it was not necessary with the P4pro and - binning and „advanced“ BINNING - what‘s behind this? Who cares?
We loose resolution that is promised in the manual and the FAQ‘s - we have NO (not closely) 4K resolution, we only get nearly 2.7K so this „advanced binning“ shows no benefit (in resolution)!
When DJO talks about „binning“ we only get interpolated 2.7K to 4K image what is no 4K resolved image and also has no groundwork for 4K! I didn‘t buy a 2.7K camera!!
I was offered a 4K camera and when DJI talks about „binning“ it‘s clear that there is no 4K resolution any more present!
There is no „magic“ „advanced binning“ known for bayer sensors that retains the native (5.5K) resolution, DJI also wins no nobel price here but trouble since nobody sees a benefit, not in testcharts nor in real life captures!
I have to agree, Chunky. No one is asking for anything unreasonable, here, just video and stills that are comparable to the P4P, which uses the same size sensor.
This reeks of intentional crippling for product differentiation, to me. I bet you'll see a new drone from DJI in a year or 18 months which somehow, amazingly, manages to provide P4P level quality from that 1" sensor. At a slightly upgraded price, of course.
This reeks of intentional crippling for product differentiation, to me. I bet you'll see a new drone from DJI in a year or 18 months which somehow, amazingly, manages to provide P4P level quality from that 1" sensor. At a slightly upgraded price, of course.
The simple pixel binning of the Mavic 1 Pro by more than 30 fps had a very bad quality, which caused strong color flickering on all contrast edges. The new advanced pixel binning is much better but also softer.
I want what they promoted - (close to) 4K „resolution“, no hyper magic advanced binning blablabla that‘s nothing but interpolated 2.7K.
Especially in wideangle resolution is necessary, I can live with the cropped „only native“ HQ mode for the longer 42mm.
Especially in wideangle resolution is necessary, I can live with the cropped „only native“ HQ mode for the longer 42mm.
The sensor can read 12,10,9,8, etc. Below MediaInfo in one of my M2P clips in 4K, when you export in H264 the video is 8 bit.
Complete name : E:\m2p\DJI_0008.MP4
Format : MPEG-4
Format profile : Base Media
Codec ID : isom (isom/iso2/avc1/mp41)
File size : 649 MiB
Duration : 52 s 686 ms
Overall bit rate : 103 Mb/s
Encoded date : UTC 2018-09-02 13:01:48
Tagged date : UTC 2018-09-02 13:01:48
Writing application : Lavf56.15.102
Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : [email protected]
Format settings : CABAC / 1 Ref Frames
Format settings, CABAC : Yes
Format settings, RefFrames : 1 frame
Format settings, GOP : M=1, N=29
Codec ID : avc1
Codec ID/Info : Advanced Video Coding
Duration : 52 s 686 ms
Bit rate : 103 Mb/s
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 29.970 (30000/1001) FPS
Original frame rate : 29.000 FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.416
Stream size : 649 MiB (100%)
Encoded date : UTC 2018-09-02 13:01:48
Tagged date : UTC 2018-09-02 13:01:48
I call the highlighted in red from DJI's reponse BS, go to 5:50 in the video below, the M2P has much higher aliasing and less definition than the Autel Evo. And these are not charts.
The M2P in 4K FOV has the clarity of the Mavic Air at double the cost. Well yes, DR and noise is better, I guess this is the consolation prize.
Uhh, the encoders (SoC) output stream has nothing to do with the sensor readout bitdepth.
You can also make an 8bit MPEG2 from a 16bit REDRAW clip.
But, even for 8bit output the sensor should (must) be read in at least 10bit to perform „lossless“ gamma adaption (D Log M/HLG), so for real 10bit output we should expect 12bit sensor readout. Otherwise we would get less than real 10bit graduation.
The 5 min limit is SONY's own design issue, Panasonic LX10 (similar in size to RX100) also uses SONY 1" BSI 20MP sensor and such limitation does not exist in 4K.
Also GH5 using SONY sensor does not overheat and many of the competitor SONY cameras do.
Ah, that‘s not the same: LX10 has lower 4K resolution than RX100V since it‘s also only „native“ cropping the sensor in 4K so you get 36mm instead of 24mm for photo.
RX100V uses the full width with oversampling like the P4pro.
Image comparison: Digital Photography Review
GH5 is a complete different animal with a M43 sensor and a big body that can dissipate temperature better.
Question is what happens with heat in the P4pro in 4K oversampling video when not cooled by the props when filming on the ground.
I have mine not here (I’m on vacation) to test.
Similar threads
DJI Drone Deals
New Threads
-
EXO Drones: Autonomous Drones will Revolutionize Facade Cleaning.- Started by The Droning Company
- Replies: 0
-
Transforming Landscapes with 3D LIDAR Mapping.
- Started by The Droning Company
- Replies: 0
-
-
-
Forum statistics
