Menu

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 - rudison

#1
Thanks a lot for the update!

I made a short test yesterday - seems to work fine. Also the new UI looks promising.
I will do more tests during the weekend.

How do you develop/debug your lua scripts?
Write code / remove SD card / copy to the SD card / insert card / test in camera: seems to be complicated. Is there an easier way?
#2
Thank you Garry for this script! It's very interesting for landscape focus stacking.

I've tried it with a Canon 650D + EF-S 10-18mm lens.

In the beginning I had some problems but I was able to solve them:

  • The filename was too long, Magic Lantern couldn't load the script. I had to change the filename (-> 8.3).
  • I activated the section for unknown lenses. But the check for a non existing lens was executed before, so this section was never active.
  • I don't need the 'bookend' exposures (it wears the shutter). The flag bookends = false solved it.

I will continue to test your focus bracketing script ...
#3
The tool dng_validate is able to convert the 32bit floating point dng into a 32bit floating point tiff (linearization, black/white level mapping, demosaic processing). This allows the following workflow:


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


Afterwards the tif file can be imported in Lightroom. The white balance / levels / tone curve needs to be changed, but with good quality (EV -10 ... 10). The tif file can also be processed with other tools for advanced tonemapping techniques.

Disadvantages:

  • The raw processing is not performed in Lightroom (no hotpixel removal, no white balance defaults, no automatic lens correction ...)
  • The filesizes are bigger

@ a1ex: Is it possible to make a version of CeroNoice that creates a 16 bit (32 bit?) integer dng (linear)? With or without a black level? Maybe this gives enough quality if it's not a scene with very high dynamic range (no extreme bracket).
#4
Ok, now I understand the problem.

I tried it with a more extreme bracket. In this case I had to set the exposure to +5 and shadows to +100. And I get ugly patterns/banding in the dark areas.

I suspect Lightroom will only use the higher bit depth if a debayered file is imported (I tried tiftest.dng from engardeknave).

   
#5
Oh my god!!!
What a great tool!

I tried it with 3 raw files from the 650D (AEB 2 EV). Size for each file ~ 18 MB.
CeroNoice creates a file of 71 MB (dng_validate tells me: 32 bit, FloatingPoint, uncompressed)
With DNGConverter (or import into LR 5.3) the filesize is 54 MB (32 bit, FloatingPointX2, deflate)
With DNGConverter (lossy) the filesize is reduced to 23 MB (16 bit, FloatingPointX2, deflate)

I think the last option is the best one. 16 bit FloatingPoint should be good enough.
(Adobe creates a 8 bit lossy jpg DNG file if you select lossy compression for a raw file directly from the camera. But a 32 bit FP DNG is converted into a 16 bit FP DNG!).

For the final image it is necessary to adjust the basic sliders in Lightroom (exposure, contrast, highlights, shadows, ...) The exposure limit (-5/+5) is not a problem for me. If one of the sliders reaches the limit (shadows?) I can also adjust the tone curve.

The final image seems to be as good or better than the image I got in the past with enfuse. I will continue testing.


Note: This is the correct link to the SDK 1.4: http://www.adobe.com/support/downloads/detail.jsp?ftpID=5475
#6
A question to the developers: Which tool do you use to edit the source code of ML? Is it a simple text editor / Emacs / vi (with or without syntax highlighting)? Together with find and find in files? Or do you use an IDE?

An IDE normally has several advantages: autocomplete, code navigation, calltips, code analysis, code folding, ...
Netbeans and Eclipse also have support für Mercurial (integrated/plugin).

Who has experience with an IDE? Is it worth a try?