I have replaced the comparison video with an updated version. The same camera files but not cut the off so early. Dunno why I was trying to save file weight by cutting the shots off short. It's not my server space.
I would like to redo the comparison anyway, keeping lens lens lengths similar to avoid unconscious bias, but have to wait for weather and a more photogenic subject. Ideally it should include the video cameras as well, but that starts to get complicated.
As for the HDMI converter, first of all it just one big pain in the bum that it has to be there at all, with all of its associated clutter (a pox on ... I mean, thanks once more to those cheery fellows at Sony for omitting the composite output) but I accept the aggravation for the huge benefit of through-the-lens monitoring. A separate camera is all well and good but the lack of accurate framing with a different length lens and no idea if the main camera is badly exposed/ out of focus or even still on etc. etc. is a stiff price to pay for avoiding less than 100g weight penalty (if you remove the board from the metal box).
I power the converter from an Extension PCB 5v supply. There is a second Extension PCB giving out 12v for the navigation LED's. Both take power from the main PDB.
The subject of payloads has been discussed before and one thing that this camera resolution comparison has demonstrated is the relative smoothness of the flight with the significant mass of the Canon 5D on board. The Sony 5N is light enough (even with the unmodified HDMI box) that the MR still had plenty of agility and therefore can still do the 'Drone Bounce'. With the 5D on board it loses that agility and the resulting flight is noticeably smoother. BUT, the Sony permits 150% more flight time and its not THAT bouncy or bad. Horses for Courses.