Messages

Remove card, remove battery. Insert battery. Startup cam without card. Result?
If camera starts up: Format card inside cardreader and start with this one. Works now without ML?

You didn't answer my question.
The money you intend to gather should be spent on
- buying a cam?
- "buying" developer's time?

In medival times it was common belief soiled cloth with some wheat left alone for 21 days will generate mice spontaneously. I hope you don't believe a ML port for 100D will erupt from a pile of money just by itself.
You need a developer and time and effort.

If you want raw video now: Get a cam able to do so.

Crowdfunding what? A cam? We had crowdfunding (sort of) before for specific items without pushing money to Kickstarter/IndieGoGo or other crowdfunding sites.
Or crowdfunding a developer's sabbatical? Do you have a dev in mind willing doing so?

Daniel, IMO you truly don't have to be afraid bothering folks around here. I'm speaking for myself - of course - but you're helping a lot driving this project forward. Thorough testing, bug reports with detailed descriptions, reasonable suggestions (and not that much mixing up facts and conclusions) -> valuable input. Keep 'em coming ...

Back on topic: You nailed it!
Fun thing is:
- If bin\lib is present it will be used by Exiftool.exe. And Exiftool's version doesn't matter at all. It now depends on Exiftool.pm's version.
- If lib directory is absent: Exiftool will work without error and Exif will be transferred just fine to output file.
So just delete/rename "lib" and your good to go with exiftool v9.9.5.

Tested with Windows 8.1. No Perl library installed but using plug-in files and directories only. I'm wondering what will happen if library is installed in search path (roughly equal to placing files into bin in OS X/Unices).

Linked guide covers outdated "stable" v2.3. No stable version for 6D available.

Format card in cardreader, format card in cam. Run EOS Utility to downgrade Canon firmware 1.3.3. to 1.2.3.

Without error message or detailed description what you have done, which EOS Utility version you used and where a problem occured you will have to wait for ML for 1.3.3 ...
"Doesn't work" doesn't work for problem solving.

Running plug-in in Windows will use cr2hdr.lrplugin\bin as "working directory". No need to change that.

As discussed above:
- OS X: Install Exiftool 9.9.8
- Windows: Replace bin\Exiftool.exe and bin\lib directory in with contents in Exiftool 9.9.8

Compare plug-in files. There must be differences

And something we have to settle: Go on with Beta3 linked in first post or updated (latest) files?

User Guide covers old "stable" v2.3. User guide for nightly build is in the making ... sort of.
Help for updated user guide is needed. Check http://www.magiclantern.fm/forum/index.php?topic=11269.0

Histobar is RAW only. See Overlay tab -> Histogram

Kind of new ... http://magiclantern.fm/forum/index.php?topic=8539.msg79115#msg79115

Use cardreader ...

The DNG files I was using were using lossless compression and when I was doing these tests I didn't have Adobe DNG Converter installed.

Sorry? cr2hdr without DNG converter will produce uncompressed DNG only

You are using "Nightly Build". The video you linked covers "stable" v2.3 and that version is outdated = not supported anymore.
Try http://magiclantern.fm/forum/index.php?topic=5705.0
or http://magiclantern.fm/forum/index.php?topic=8431.0

Iwill there ever be one?

"Prediction is very difficult, especially about the future."
But there is a new sound system in development. But - as always in ML development - there is no time scale ...

Fine!
Consider updating to latest plug-in version (which includes updated cr2hdr).

Not that good. Warning doesn't tell that much. On Windows I used Process Monitor to trace all actions and found the string containing call to cr2hdr.exe (+ arguments and stuff) transferred to command line interface (= terminal in OS X slang). Copied string and ran it in commandline and there was an error message about exiftool.pm.
Don't know OS X and how to trace there.

Now replace bin\lib with the one included in exiftool 9.9.8. and retry.

Do you want to add some infos about your workflow, cam used, ML version? Are we talking about FRSP at all? And does mb mean megabytes or megabits?

https://bitbucket.org/kichetof/lr_cr2hdr/downloads/cr2hdr.3.0-BETA3.zip

Outdated. Kichetof has to perform some householding duties ...

I'm guessing that the plug-in ignores the system wide cr2hdr, exiftool, etc. files and instead uses the ones that are packaged inside of cr2hdr.lrplugin.

Works as designed. Plug-ins messing up with system files doesn't sound like the best approach.

In order to get to them on the Mac through the Finder a user needs to either use the Terminal or Control click and Show Package Contents. (This may be obvious to developers but not to users that might be trying to follow this conversation.)

"Beta" rings a bell? But you're right. Unneeded hickups here.

Description of steps taken

As long you are using an old cr2hdr you will have troubles with Exif, I suppose. Use kitchetof's latest downloads, check exiftool.pm and if it is 9.9.3 I suppose it won't work. My exiftool.exe (Windows) is 9.9.5 and I replaced plug-in's bin\lib files with version 9.9.8. Now it works.

Again: Forget kichetof's bitbucket "Download" (bitbucket.org/kichetof/lr_cr2hdr/downloads/) because he doesn't use this repository for development but a local one and he hasn't synced it in ages.

I might be able to lay my hands on OS X but can't promise.

I hope Marsu42 comes back to clear things up about rack focus and focus stack. Stumbling over those options, too.

For starters try this (you have to find your numbers depending on lens/distance/magnification):
- Set near focus point as focus end point 0 (here)
- Focus stacking -> Number of pics behind > 0
- Number of pics in front = 0
- Focus steps / picture = 2


For peace of mind while tuning:
Shoot tab -> Shoot preferences -> Snap simulation Blink & Beep

Yes, that's outdated. Update with http://www.magiclantern.fm/forum/index.php?topic=11056.msg147298#msg147298
Old cr2hdr is gone and new cr2hdr was formerly known as cr2hdr-20bit.
If you see a cr2hdr-20bit arguments tab after update you might use tip provided by david az to get rid of old version.
Report back, please.

BTW: CR2 out-of-the-cam is always compressed (lossless).

About file sizes: cr2hdr generates uncompressed DNG. Lightroom will convert it to lossless compressed DNG when manipulating metadata.

And you did much more than suggested making it very difficult to find out where the problem might be.
david az jumped in - I suppose - following former discussions about context menu troubles with plug-in but this is not our problem here.

Please take a look into your plug-in folder cr2hdr.lrplugin/bin/lib/image/exiftool.pm. Find line $version and tell which version is found.

File *-dualiso.dng is not a virtual copy but a real one. LR plug-in will copy original *.DNG to *-dualiso.DNG before cr2hdr jumps in and processes *-dualiso.dng from "RAW" dual ISO to "merged HDR" (= without interlaced lines). This is because cr2hdr has no argument to change output file name and will replace source file with output file (aka overwriting it).
In LR both files (unchanged source and processed file) will be treated as image stack virtually hiding their physical representation. Unstack them and select directory where both files are located.
Create a new dual ISO file, import it as DNG and convert it with plug-in. I suppose you will find a file named *-dualiso.txt inside the directory where LR copied your DNG. Look for last lines. I suppose you will find some error message there. File will be absent if conversion worked without error.

EDIT: Use export option "Export ..." not "Dual ISO converter (cr2hdr)". First option will let you access plug-in's GUI and you can change options/arguments. One of those items is "Mark original as rejected" ...

http://www.amazon.de/InLine-Audio-Adapter-Klinke-Buchse/dp/B00183NLHW