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.

Show posts Menu

Messages - engardeknave

You have to convert to .tif first with Enfuse. I've used everything for this, but Irfanview is an easy option that works well out of the box. After you convert to .tif, you can then process the .tifs with Enfuse. I'm not sure if Enfuse GUI can do multiple brackets at once, but I don't think so. Photomatix can convert multiple brackets in one operation directly from .cr2 files.

Personally, I coded a massive VB script to do everything including a first stage of color adjustments and keystoning, so I just have some final tweaks to do manually. This took months.
I don't know how that works. I never use video, and I've actually since switched to Nikon. But you probably just need to make the script look for .dng files. Ie., see the line: ' if valfname(file.Name,".CR2") then ' and disable all the file organizing (organize=false).
At the top:


And maybe comment out inputfolder=getfolder(...
Feature Requests / Re: [WONTFIX] Bracketing
June 30, 2014, 08:00:24 AM
To avoid scrolling around so much use expo presets.
I rarely get excited about traveling anywhere, but this looks very worth the trouble. Also not everyone in the world with a camera has been down there, so it's still possible to capture something at least somewhat novel. And indeed these photos are incredibly interesting.
I turned off LV when shooting brackets and it goes much faster that way (5D2).
Just stumbled upon this. Results look very compelling. Math looks hilariously impenetrable.

Automated colour grading using colour distribution transfer [pdf]
General Help Q&A / Re: ML for landscape photography.
April 30, 2014, 07:49:06 AM
RAW histogram

I was blind

but now I see
Garry, my existing scripts consist of several thousand lines of vbscript that automatically process and sort hundreds of bracket sets from several shoots at once. I'm asking A1ex to make Ceronoice work with paths so I don't have to employ weird hacks or copy gigabytes of temp files during this process.
A1ex, will you make this work with full paths & file names for the input and output files yet? I'd like to script this to run along side my current workflow so I can compare the results. Would be tested on a ton of files.
Quote from: rudison on December 18, 2013, 11:27:22 PM

CeroNoice.exe 1.dng 2.dng 3.dng 4.dng
dng_validate.exe -3 out out.dng
exiftool.exe -tagsfromfile 1.dng out.tif

I'm extremely interested in this module.
General Help Q&A / Re: magic zoom vs focus peaking
April 03, 2014, 03:40:15 AM
This question doesn't really make sense. Magic zoom is as accurate as your eyes are.
The script works by running cr2hdr with the current directory set to the folder containing the images. This is because I couldn't cr2hdr to work correctly with paths and file names. The current directory is set at the line wshshell.currentdirectory=inputfolder. You can check if the current directory is properly set (to c:\test) with msgbox wshshell.currentdirectory. You also might try replacing the line wshshell.currentdirectory=inputfolder with wshshell.currentdirectory="c:\test".
Started: 4/2/2014 2:35:34 AM

Input folder is C:\pictures

Searching for .CR2 files
Queued "C:\cr2hdr\cr2hdr.exe" --compress "IMG_7361.CR2"

Converting Dual ISO .CR2 files
Executing: "C:\cr2hdr\cr2hdr.exe" --compress "IMG_7361.CR2"

Moving Dual ISO .CR2 files
Created "C:\pictures\Dual ISO CR2"
Moving "C:\pictures\IMG_7361.CR2" to "C:\pictures\Dual ISO CR2\IMG_7361.CR2"

Moving any regular .CR2 files

Moving Dual ISO .DNG files
Created "C:\pictures\Dual ISO DNG"
Moving "C:\pictures\IMG_7361.DNG" to "C:\pictures\Dual ISO DNG\IMG_7361.DNG"

Moving log files

Processed 1 file(s). Converted 1 Dual ISO(s). Runtime: 19.61 seconds.

Created "C:\pictures\logs"

Just tried those folders and it works for me. It doesn't show the path at that point. Check to make sure that file is valid. Run cr2hdr on it from the command prompt manually.

There's also a couple other solutions to running multiple cr2hdrs in this section if you haven't tried them.
How about a plugin that logs usage and user feedback about stability? This plugin would generate a text file saved to cf/sd with the version of ML, functions used, maybe crashes, and then responses to a few questions about what worked (via camera GUI). As far as GUI, all it would need is a list of functions with three radio buttons (worked/didn't work/no response).

This could then be submitted to the site to generate a rating system. As more people rate a nightly positively, more people will download and use it, creating a situation where one nightly is fairly well-tested. This version can then be placed at the top of a download page.

Maybe ideas like this are going a little overboard, but it seems like less work than creating a separate stable version of ML. And once it's done, it should put the issue to bed for the foreseeable future.
Maybe there shouldn't be a "stable" build. It doesn't seem like that paradigm is really effective in this environment. Maybe just builds of lesser and greater rated stability via an automated system. I think most people would use a build for longer to contribute to stability testing.

I don't see why documentation is that important. If someone wants to do it, great. If not, you didn't lose anything--you simply gained undocumented features.
I was thinking that there could be a stability rating on the on the nightly page next to each build, perhaps with a few different categories for different functionality (raw video/bracketing/whatever else seems likely to break). That seemed like a lot of trouble though.

However, maybe something like that could lead to an actual release. If enough people get on board with testing a certain nightly and report back, you'd have a release candidate.

I decided today to keep an older version on another card before moving to the latest build.
Did you change the cr2hdr path in the script? Please check all the script options and make sure everything is set correctly. Also read all the directions above and comments in the script by all the settings. If you did all that, post your config (the top settings of the script).
QuoteThere's a big difference between warning users to expect rough edges, and willfully keeping code that was proven to be dangerous.


I have an engineering background, and I'm trying hard to build software that would not fall down when the first woodpecker comes along.

I feel like I should voice my deep appreciation for this development philosophy. I absolutely wouldn't be able to use ML otherwise. It's the difference between losing a few features, and losing all of them.
General Help Q&A / Re: Reading Waveform Monitor
March 30, 2014, 10:28:27 PM

(Actually, I should probably link to this:

Raw histogram is the best thing ever though.
QuoteMake sure all paths end with a "\", ie. "C:\cr2hdr\"

Try adding a slash to the end of all paths. It should work fine with long paths too.

I also just updated it to remove the tint adjustment. (It won't work with most cameras, and is incompatible with the latest cr2hdr.) Also a couple of other bugs that would prevent it from working for anyone but me probably.

I'll just add a date to the top of the script.
A work around I've discovered is to enable the creation of file lists/scripts in ML and then use this list to programmatically rename/move the files in post.
Modules Development / Re: Sensor cleaning module
March 30, 2014, 04:17:18 AM
I made a tiny squeegee-like implement with suede on the end. Very much like the kind from which Canon L pouches are made. (Didn't actually cut up an L pouch.) It's for dry use. Extremely effective, no streaks, no scratches.