Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Topics - alMalsamo

Pages: [1]
We do quite a lot of event videography, and one of the nicer features of the 5D Mark III is that the default camera firmware allows for recording 30 minutes straight without needing ML's movie restart feature.  We are very greatful to the movie restart feature for 30+ minute recordings, but this feature request is not about that.

As you know, the 5D Mark III still splits up video files into 4 GiB chunks, even when the CF or SD card uses the exFAT filesystem.  This limitation is the basis for the mlv_rec RAW video recording option labeled

Files > 4 GiB (exFAT)

This request is for the same feature in H.264 mode.  During post-production, we have noticed that even with the camera supposedly being able to "continuously" record to 29:59, there are dropped frames during the 4GiB file changes!  The first 4GiB file generally records for 16-17 minutes, after which the next file is created: in between, there are about 4 video frames that are lost in this transition, meaning the 5D Mark III is not able to truely record to 29:59 straight through!

It is frustrating because when using exFAT, there is no need to make 4GiB splits.  Ideal ML behaviour would be to auto-detect the filesystem on the recording media and simply keep recording until the 29:59 limit is reached in a single file if exFAT is used.  If this ideal behaviour is too difficult, then simply giving a menu option as with the mlv_rec's "Files > 4 GiB" option would be a huge improvement for all of us who need continuous recording with no dropped frames.

It would, at least in our case, be a killer feature of the ML software!  We are otherwise being unfairly held back by FAT-era limitations in a post-FAT world.

Hallo, first time ML user here, and I am very excited to get going!

I got ML 2.3 working great on a 32GB SDHC card using the firmware update method on my 60D, so I have a small taste of how things should be running!  I normally only use 128GB Lexar SDXC cards in this body, however.  I want to set up every SDXC card I have to make ML run as soon as I load the card, but I can't get my first one working!

I am running Debian GNU/Linux at the moment, and I am trying to use the script found in the Google Groups page linked in the instructions PDF.  It is annoying that something seemingly as simple as turning on a bootable flag in the SDXC card's exFAT filesystem is tripping me up, but here is the output I have from.  I had to use the third version, as the other two were not working. Also, I compiled 'exfat_sum.c' and set both the resulting exfat_sum executable and script file +x permissions.

# ./ /dev/mmcblk0p1

MagicLantern card pacher Only

Applying EXFAT parameters on /dev/mmcblk0p1 device:
 writing EOS_DEVELOP at offset 130
 writing BOOTDISK at offset 122
 recompute checksum. old=0x0, new=0xf801fffff801ffff

After this finishes, I can no longer mount the card on the computer, nor the camera, and I must reformat again in the camera for it to be functional again.   :'(

Getting ML working on my 128GB cards is a must, so anyone with some tips on how to properly set exFAT filesystems to be bootable under GNU+Linux (or even Mac OS X CLI), please impart your wisdom!


Pages: [1]