That means the transmit data rate to ground from the craft would also half the data rate, naturally increasing range. So what would normally take 10MB to store to SD card with H.264 takes only about 5MB for H.265 to store the same video. The general compression efficiency of H.265 is about 2X. This could be the result of transmitting less data from the MA2, naturally increasing range. On another note, the stated range for MA2 is more than M2, however they both use OcuSync2.
And vice versa, the Go4 app won't work with MA2 because it doesn't support H.265 decoding. Since the Fly app is required for MA2, and incompatible with M2, this could be because Fly app doesn't support H.264 decoding which M2 craft requires. The other evidence of this difference in OcuSync2 is the app. Has anyone else confirmed this the problem why SC doesn't work with MA2? I presume this is why the SC ( Smart Controller) doesn't work with MA2, because it doesn't support decoding M.265, yet. Although MA2, M2P, and M2Z all claim to be Ocu-Sync 2, it appears this is a clear difference between MA2 and the M2 craft. This evolution to M.265 transmit from the craft is likely the result of newer chips, lightweight enough, and cheap enough to use in the craft that can encode with H.265. I don't think that's the case with M2P/ M2Z, I presume they use M.264 as before with earlier craft, and it's not mentioned in the M2 spec. However with the MA2 it says in the specs the craft TRANSMITS the video from the craft to the controller using H.265. This newer codec is more efficient, needing about half the space to store the same video.
The MA2, M2P and M2Z all support recording to the SD in H.265.
0 kommentar(er)
