Author Topic: What more can/should we do with ML?  (Read 11132 times)


  • New to the forum
  • *
  • Posts: 14
Re: What more can/should we do with ML?
« Reply #25 on: December 31, 2018, 12:42:53 AM »
OK, I'll bite. Do you happen to also run firmware 1.0.4 on the 5D4? Otherwise it may take a little longer.

For M50 I've already got a very good tester; feel free to check out the progress.

Yep! I'm running 1.0.4! I didn't even realise there were newer versions till I just looked them up! All good on the M50, but I am running firmware version 1.0.0 if that helps at all! Let me know!


  • Senior
  • ****
  • Posts: 393
  • pesky kid
Re: What more can/should we do with ML?
« Reply #26 on: February 03, 2019, 07:52:57 AM »
For me the most important feature I wish I have with 4K builds is card spanning.
It's so distracting that we had this feature before.
Because the mind blowing 45/48 FHD mode is only 6-7 sec on my camera!!!
Ironically, this is just a "coding task" no need to investigate something new.
I even tried several times to do this myself, but, despite of vast amount of code analysis background,
this task is overkill for me: not enough of C knowledge and details about underlying hardware and OS functionality.
Mlv_rec and mlv_lite modules are significantly different regarded how data record is implemented
and no possible to just copy code from one to another.
I understand, that for main developers this is just boring job, they spend time discovering something new.
Anyone with decent C skills and MKIII camera???