New M2 Firmware 11-22-18

[Inspirephil]

Here are two file information screens: The one on the left is for a file recorded PRIOR to the update and the one on the right is AFTER the update. There are a few interesting differences aside from the bitrate (old is 104Mb/s and the new is 99.9Mb/s). Note the reference to frame rate. The old one has a value for "original frame rate" (which happens to be lower than selected frame rate - no idea why) and the new one does not have that. This 23 vs 23.976 may relate to the "Bits-(Pixel*Frame)" value of 0.524 (old) versus 0.502 (new).

Maybe some mpg specialist here can shed some light on this. I would be guessing as to what it means.

Doesn’t seem like that would be the case after updating but that’s DJI for ya!

 

[Roamer105]

Doesn’t seem like that would be the case after updating but that’s DJI for ya!

There was a more subtle change to video recording between the 000 and the 100 firmware: original bitrate was 103 and after the 100 update turned to 104. Now it is 99.9... go figure.

 

[pbj_dk]

Here are two file information screens: The one on the left is for a file recorded PRIOR to the update and the one on the right is AFTER the update. There are a few interesting differences aside from the bitrate (old is 104Mb/s and the new is 99.9Mb/s). Note the reference to frame rate. The old one has a value for "original frame rate" (which happens to be lower than selected frame rate - no idea why) and the new one does not have that. This 23 vs 23.976 may relate to the "Bits-(Pixel*Frame)" value of 0.524 (old) versus 0.502 (new).

Maybe some mpg specialist here can shed some light on this. I would be guessing as to what it means.

DJI did do something to the SD card reader or it's firmware! My SAMSUNG EVO U3 XC1 128GB, that had worked flawlessly on my M2P suddenly didn't record anything any more? I went thew all settings in the app and of cause also formatted the card within the drone. I do that on every update. Everything looked fine on the the app (no of pictures left, when taking one, no of mb left when taking video etc), but nothing was written to the card while recording. Went throw all the settings again, formatted the card within the drone again and flew again with the same result: no data and when reading on a PC: Card not formatted.
Thought - Ohhh well - bad card - threw a brand new one in (same brand/type), formatted within the drone. Everything fine, but still smashed disk format, when reading the card afterwords.
Out of frustration formatted the first card on my PC ( in exFAT 32), threw it in the drone at took pictures and video in my living room: No problem. The drone could write the data and I could read it on my PC. Took that card out flying i 3 dregrees C for 40 minutes, still everything fine. I could take the card out and read it with my SD adapter to my phone. Got curious and formatted the card throw the app within the drone again: BOOM - same problem. No data and neither my phone or PC could read the card any more.
Maybe my M2P has a bad card slot? But this is a new problem since the update 22/11-2018 . they worked fine before that. If I format it on my PC exFAT 32 - it works fine, if within the drone, the drone can read it (no errors) but my PC or phone (external reader) can't. Can't as in "Disk not formatted".

 

[Kilrah]

Formatting wth the drone is known to be occasionally problematic, avoid it if it gives issues. Not even new to the M2, been so since the Mavic Air.
The data is actually recorded fine, and you can read it if you use the drone as reader, just not if you take the card out.

 

[pbj_dk]

Formatting wth the drone is known to be occasionally problematic, avoid it if it gives issues. Not even new to the M2, been so since the Mavic Air.
The data is actually recorded fine, and you can read it if you use the drone as reader, just not if you take the card out.

Ohh - I didn't know as a new DJI product owner. Flew Youneec before and here the mantra was: format the card within the drone to make sure. I did cabel coulpe the drone direct to the PC using i'ts reader to my PC unfortunately with the same result.
As long as I know not to format cards in the drone, I'm fine. However they should look into this problem? I's annoying to delete manually.

I'm happy with the new improvements in this update! ;-)

 

[Prmath]

After the new FW update......
I did a compass calibration. Should I do the IMU as well?
TIA

 

[Lon Denard]

There was a more subtle change to video recording between the 000 and the 100 firmware: original bitrate was 103 and after the 100 update turned to 104. Now it is 99.9... go figure.

This is something I've been talking about for awhile when people complain about "missing features". I'm concerned that the processor may get overloaded with too many processes running at the same time. It can only juggle so many balls at one time. Perhaps that decrease was to help compensate for precision landing? There's only so much water in the pail.

 

[Kilrah]

No, that's BS, things are not even handled by the same processing units.
They probably went to 99.9 because some devices refuse to play files >100.

 

[Lon Denard]

No, that's BS, things are not even handled by the same processing units.
They probably went to 99.9 because some devices refuse to play files >100.

Okay, let's say you're right, it doesn't change the fact that there is a finite "bandwidth", for lack of a better term, This drone has a lot of balls in the air. Every new feature potentially adds another ball...