Dragonframe 4 onion skin how to#
Dragonframe 4 onion skin update#
Dragonframe 4 onion skin manual#

You also have to be able to build a codebase that can be reconciled across multiple variant firmware images (every camera model has a different one), and once the firmware gets updated, you have to accommodate the changes.

You have to be able to run your own code on it, and you have to know what values in what registers you can manipulate, and what those values represent (this is where the majority of the initial hacking time goes: trying to figure out by trial and error what a value in memory is for).

Dragonframe 4 onion skin how to#

You have to know the OS of the camera, so you can figure out how to run your own new code on it (Canon's DryOS is well-documented). (The DIGIC processors Canon uses are ARM-architecture).

You have to know the architecture of the system you're developing for, because you have to know what your compilation target is. They're looking at a blinking LED to read out the entire firmware image. There's also the fact that Magic Lantern was able to shortcut some of their development by utilizing folklore about getting firmware images out of a camera that were figured out by the CHDK team that worked on the Powershot compact cameras. But it does seem that Canon shooters disproportionately include a bunch of embedded systems/firmware pros who mess about with firmware/hardware in their day jobs. I was once told that Canons are designed by engineers while Nikons are designed by photographers. I'd posit the 'not enough Р“Сber-geeks in the Fuji' fold theory is probably the correct one. Manufacturers make those to make their own lives easier.Р”В«ut you know why there's no Nikon version of Magic Lantern? To me, it's the fact that Nikon encrypts part of their firmware image that would be a likely cause. Well, a diagnostic/developer mode is a completely different deal. My point is, why have I not stumbled on any of this for Fuji cameras? Am i just missing it? Do no secret menus even exist? Not enough uber-geeks own Fuji? Another reason?

Dragonframe 4 onion skin update#

The chances are, even if there was still the will to put together a user-led update programme, Fuji would end up leapfrogging it with their next update before the other project had decided on a name for itself. ThatРІР‚в„ўs never been an issue in Fuji land, where Fuji themselves generally make a habit of stretching the hardware as far as they can in successive firmware updates. If you look at Magic Lantern, that whole project was born out of frustration that Canon had provided great hardware but werenРІР‚в„ўt allowing it to be used to the full in firmware, hence users doing it for themselves. I guess the answer does lie in the fact that Fuji have always provided these improvements for us.

Dragonframe 4 onion skin manual#

IРІР‚в„ўm pretty sure there are no hidden menus or tricks a while back I got hold of a service manual for the X-Pro1 (IРІР‚в„ўm not going to post links or samples but itРІР‚в„ўs out there if you spend enough time googling) and disappointingly there was nothing like that in there - all the service centre configuration is done via hooking the camera up to a PC running some internal Fuji software, nothing is done on the camera itself.Р”Р„t the time IРІР‚в„ўd been hoping for some button combination to remap the sensor (which is now a user menu option on current cameras) but the X-Pro1 procedure involves not only special software but a special light box to put the camera in - definitely no nifty hack there!Р”Р„s for why others havenРІР‚в„ўt tried to reverse engineer firmware etc.