Messages

Hey Folks,

I'm in the process of gathering hardware to build a stack rail, based loosely on this project (https://pulsar124.fandom.com/wiki/Pulsar124_Wikia)

My target cameras are Canon 550D and 600D

I am interested in finding out what (sensible) approaches I might consider to triggering the camera (and flash)  -  is this something Magic Lantern can help with - via an API or python/arduino library?

IIUC the current favoured response is to fake the cable trigger/electronic trigger (very hardware, much hack), but it'd be extra nice to be able to adjust camera settings and get feedback from the camera.

Hey folks,

This floated past me elsewhere and I figured it would be relevant here...

https://www.digitalcameraworld.com/news/30-canon-cameras-at-risk-of-ransomware-canon-issues-firmware-advisory

I have concerns it may impact access to the firmware depending on how Canon tackle this...

Hey Folks,

I am preping a bunch of cards for my 550D.  I noticed the make_bootable.sh script fails to recognise some cards where the volume name is not EOS_DIGITAL, but is instead EOS_DEVELOP.

sure, it's a trivial matter to adjust the script to catch the appropriate card names but i'm wondering if there is something I'm missing - why are some cards DIGITAL and some DEVELOP? does it matter? is it a consequence of the "upgrade" method to prep the cards via the camera? should the script be upgraded to reflect this? Why do people still think digital watches are a pretty neat idea?


lazy change...

line 22:
  dev=$(mount | grep EOS_DIGITAL | awk '{print $1}' )
change to:
  dev=$(mount | grep EOS_D | awk '{print $1}' )

"safer" version - match either...

  dev=$(mount | grep 'EOS_DIGITAL\|EOS_DEVELOP' | awk '{print $1}' )