Messages

Sounds like you weren't in the right folder to build cr2hdr. You have to be in the directory containing the dual ISO code. It is in magic-lantern/modules/dual_iso

Error: Port hg not found

My mistake.

port install mercurial

Hi all.

Really new to this and I have a "dumb" question. I'm on Mac (Mountain Lion) I have the source code and pre-built toolchain. Could someone point me where to go from there. Not quite sure what to do with it to use my 5D2 .cr2 files and get cr2hdr working.

I just wrote up something http://www.magiclantern.fm/forum/index.php?topic=7645

[I'm assuming you are fairly comfortable using a command line interface and navigating the filesystem with commands like cd]

It seems like lots of people are using wine to run the command line tools provided with Magic Lantern. Here is how to compile and create symbolic links to the binary to make the workflow a little bit simpler .

I'm assuming you are fairly comfortable using a command line interface and navigating the filesystem with commands like cd. If you aren't then this is not the resource for you, you have plenty of other reading to do before you will be ready for this. Edit: for emphasis.

You're going to need a few tools for this: MacPorts, hg, dcraw, and a pre-compiled arm toolchain.

First step is download and install MacPorts, a command line-based package system similar to APT for linux. After installation is complete you are going to want to install a few packages.

In terminal type 'sudo port install mercurial' to download install hg', which we will use to download the source. You'll be prompted for your administrator acct. password. Follow any warnings or suggestions on updating the package list.

Next we're going to download dcraw, which is needed by cr2hdr and raw2dng for conversion purposes. Again in terminal type 'sudo port install dcraw'.

We're done with MacPorts for now and can use hg to download the source tree. Navigate in Terminal to whereever you wish to download the ML source files and type 'hg clone -r unified https://bitbucket.org/hudson/magic-lantern';. This will create a folder ./magic-lantern/ which contains all the source files.

Now that we have the source we need to get a pre-compiled toolchain to compile the code. Save and extract.

Now we have to tell the ML build files where they can fine the compiler. open ./magic-lantern/makefile.user.default in a text editor and and change the following line to indicate where you extracted the toolchain.

Change

Code Select Expand

ARM_PATH=~/gcc-arm-none-eabi-4_7-2012q4

to

Code Select Expand

ARM_PATH=~/path/to/compiler

For me its

Code Select Expand

ARM_PATH=~/Downloads/Magic_Lantern/gcc

Be sure to not end your path with '/'

Save this new file as makefile.user (dropping the .default extension). Now we are ready to build.

First, you must compile the autoexec.bin and associated .sym file for your camera.

Now, in terminal, go to your source ./magic-lantern/modules/raw_rec

Type make. You will get some warnings about not having compiled the source for any model but these instructions are purely for getting the utilities to compile. You'll end up with our first utility, raw2dng, amongst other things like the module files.

Now we are going to make a link to raw2dng so that it can be run as a command in terminal no matter what directory you are in.

Type 'sudo ln -s raw2dng /usr/bin/raw2dng' This creates a symbolic link to the original file.

Now we are going to do the same for cr2hdr. Enter ./magic-lantern/modules/dual_iso

Type 'make' then 'sudo ln -s cr2hdr /usr/bin/cr2hdr'.

Voila now these 2 utilities are compiled and ready to be run from any directory through the terminal. For example with dual ISO images, enter the folder with the images and type 'cr2hdr IMG_0000.cr2'

To be totally honest there are probably some bumps you are going to run into and files you may have to edit to get everything compiling. I'll do my best to help but I have very limited programming experience and mostly have gotten through this with the help of Coutts 'developing on Mac' wiki article and a lot of trial and error.

Dual ISO raw video did not work for me. Only did 1 test though.

The bitrate option applies only to regular h.264 video recording.

Thanks a lot, but I get error:

studios-mac-pro:canon studio$ ./cr2hdr IMG_0155.CR2

Input file     : IMG_0155.CR2
sh: dcraw: command not found

got Xcode and gcc tools, I will try to compile on local

You need dcraw. As I said, I used MacPorts to install it. Macports is a command line based package installation system for OSX that is similar to Linux package systems like APT.

Building the cr2hdr tool in a mac environment is super easy. Just follow the instructions for downloading the source repository and a prebuilt tool-chain in the 'getting started with development' thread. Then make in the dual_iso modules folder. It builds both the module and cr2hdr.

Here is the binary built as of Aug 11th. cr2hdr for Mac

This is a command line version. I would suggest making a symbolic link to where ever you save it in /usr/bin so you can run it in whatever folder you save your images. You also are going to need to install dcraw. I installed it using MacPorts.

Working on the 5D2 fine for me. I'm trying to figure out how to put it to the test. I'll post some samples in the coming days.

Just like the difference between a crop sensor and a FF sensor, it has the equivalent field of view but lacks the other qualities of that longer focal length like compression and DoF.

I think the key phrase here is 'doesn't seem to.' I would be surprised if images are not transferred to the card ASAP. It wouldn't make sense if you are trying to market high burst rates. The buffer is only so big and the faster you can unload data from the buffer, the faster you can capture more data.

Bitrate increased? FPS override being used without disabling audio record? You're going to have to give more information.

< 6volts is safe I believe.

PTP interfaces, like DSLR Remote Pro and other software, can write improper settings to your camera. I doubt that the link between this behavior and your use of that software is coincidence. One of the devs might have some suggestions but you might need to send it in for service.

You could probably use LRTimelapse to adjust them globally but maintain the differences. Or maybe someone could write a script to adjust the sidecar.

I don't think this project needs your business consulting services. Coincidentally you don't offer any according to your website.

Try CHDK or maybe that zibri guys iphone hacking project.

No, Magic Lantern does not currently accept donations. Also, soliciting for a campaign and offering to create tutorials if you are well compensated sounds self-serving and not in the spirit of the project. Maybe you should find some other site to offer your services to.

This is only possible in movie mode, not in photo mode. Under the ISO submenu of the ML Expo menu, change the ML ISO setting to something like -.3 or -.5. Anything lower than that and you are going to get super pink highlights.

Also you should consider using the nightly builds. v2.3 is almost 1yr old at this point. A lot has been added or improved since then. Simply replace the 'autoexec.bin' files on your card with one downloaded from the Nightly Builds board. New updates are added every day.

Get a new card reader. Don't trust your data with a giant piece of crap. Try a different card if you have one.

It's a trick to let you use the scroll wheel in the ML menus.

The nightly builds are not compiled with module support. The 'M' is the module menu. Users are either compiling ML for themselves, or downloading builds provided by other users.

As always, there is no support or guarantee with Magic Lantern. Especially random builds linked from the forums. This is not included in the nightly builds for a reason. It is very experimental and not user-friendly.

www.dpreview.com

Depends on what you want from the camera. Are you new just to ML or also photography and DSLRs?

Exposure override only works in M. If you want to set the aperture and let the camera decide the shutter, what do you need expo override for?

There are enough places to buy and sell used gear on the web already. It's one thing if this was a board for a niche market but we're all using popular cameras that have tons of lenses and accessories available for them. This isn't the Large Format Photography Forum.

Plus the first time someone gets burned, the mods and admin would never hear the end of it and would have to police it constantly.

Best not to use the same card in 2 different models. The configuration files are model specific.

http://www.magiclantern.fm/bestpractices