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

#101
@a1ex: I uploaded a comparison (deleted, see #2059), where you can see what I speak about. I processed the cr2s (shooting -> M, Dual ISO: 100/1600, f8, 1/30s, wb: daylight) with the newest cr2hdr-20bit without --same-levels command and after that I imported them into Lightroom. On the histogram jpgs you can see, that the pieces of the sphere panorama has the same settings (wb, exp, shad, highl), I exported them as 16bit TIF and stiched them in PTGui, so I got the panorama_01.jpg (It is resized and I cut the bottom part of the panorama). You can see the dark part (computer desk, chair, window, couch, till door on the right and a part of the ceiling) on the panorama. Take a look at the panorama_02.jpg, at this processing I pushed up the exposure manually (let's say expose to the middle) at the darker pieces and the problematic part looks much better after the stiching.

So if I see the histogram at the second processing all of the pictures are shifted to the middle. Is there a way to analyze the full histogram + setup a base exposure shift for all dngs (let's say +1,5EV) + after that setup a reference picture manually (let's say, this picture is the perfect middle) + after that shift (+/-) the other pictures exposure to the middle automatically? Of course there will be some difference between the pictures after the export (at panorama_02.jpg I had minimal differences), but PTGui done the rest shift at blending/stiching.

Update: When I shoot this panorama, I metered the light in 2 directions at -1EV (to the lightest and to the darkest) in AV mode and after that I switched to M mode and setup the avarage between this two.
#102
@ShaunWoo: I just thought out the same as you, that there is no need for .bat file, it works with shortcut. :)

@a1ex: Thanks for the update. The same levels command works with the shortcut trick, but the results for a spherical panorama (situation: daylight, indoor: no electriclights, outdoor: full bright sunshine) isn't enough good. As I see the dngs, they should be analyzed again after the same levels algorithm and there should be a match overall brightness trick after that, which would be based on the same leveled dngs' histograms. This algorithm should find the middle one from the batch processed dngs and there should be an exposure compensation (something like deflicker). Now I make the matching manually and the result is verygood. Tomorrow (today) I have much to do, but as I have time, I will upload the a full set of the sphere pieces and I'll send a pm with a download link for testing.
#103
Thanks for the explanation a1ex.

I have this "cr2hdr-20bit-same-levels.bat" file
cr2hdr-20bit --same-levels %*
pause


in the folder, where my cr2s are and I setup the path environmental variable for the cr2hdr folder (cr2hdr-20bit.exe, exiftool.exe and dcraw.exe), so it should run well, but I get this:

Unknown option: --same-levels

update: I think I have to define the input and output somehow and after that run the "--same-levels" command only for the dngs or how?
#104
It happens with that cr2hdr bulid, where the same levels command is embeded.

QuoteFor anyone interested, here is the build from a1ex above, with the --same-levels command parameter set by default.
https://dl.dropboxusercontent.com/u/34113196/Dual-ISO/forum/cr2hdr-same-levels.zip
This will allow you to simply drag and drop files on the exe, for auto processing with --same-levels.

With the 20-bit version and with the version what is in the main post I can't see the stripes.

How to save the conversion log and how could I compile a 20-bit cr2hdr, where the same levels command is embeded? I'm on windows.
#105
yepp, it's here. (deleted file, problem solved see #2031)

sorry, the stripe is vertical if we see in landscape view, but my camera was in portrait direction because of the panoramic head. :P
#106
I tried the "cr2hdr same levels" build, what I found in this post to post process the pieces of a spherical panorama and 2 from the 7 dngs got vertical stripes after the drag and drop (all of the 7 cr2s).

My camera was in M mode, Dual ISO 100/1600, f8, 1/30 and -1 EV, I'm using the nighlty apr. 14.

In Lightroom: shadow +69 and highlight -69. Exported to jpg 100% quality, 300dpi produces this. (deleted file, problem solved see #2031)

Am I doing something wrong or is this a bug?
#107
General Chat / Re: Magic Lantern Mobile App
May 05, 2014, 11:16:48 PM
+1

After the next stable release we should make a donation round and find a mate who (maybe he will jump into it, dslrdashboard) can write a crossplatform (iOS + Android) mobile app to set up ML functions through Wi-Fi with a mobile device.
#108
Share Your Videos / Re: Auto ETTR Sunrise Timelapse
November 28, 2013, 01:54:16 PM
Thanks. :)
#109
Share Your Videos / Auto ETTR Sunrise Timelapse
November 26, 2013, 11:08:47 AM
I shoot my first sunrise timelapse in the last month with my Canon 550D (runing a nightly build from october) + Canon 18-55 mm.
The used functions: Auto ETTR + Intervalometer + Adobe XMP sidecar files.

#110
Share Your Videos / Re: Auto ETTR Sunset Timelapse
November 25, 2013, 06:16:12 PM
Yes, it worked very well and I used LRTimelapse too.
#111
Share Your Videos / Re: Auto ETTR Sunset Timelapse
November 24, 2013, 02:16:10 PM
Thanks for the advice.
#112
Share Your Videos / Auto ETTR Sunset Timelapse
November 23, 2013, 03:16:02 PM
I shoot my first sunset timelapse in the last month with my Canon 550D (runing a nightly build from october) + Canon 18-55 mm.
The used functions: Auto ETTR + Intervalometer + Adobe XMP sidecar files.



Lens: MF

Canon settings:
* RAW
* Image review: 2 seconds
* Max ISO: 1600
* Long exposure noise reduction: OFF
* High ISO speed noise reduction: Standard
* M mode + Liveview

ML settings:
* White balance: Sunny
* ISO: 100
* Shutter: 1/1000
* Aperture: F5.6
* Auto ETTR
- Trigger mode: Always ON
- Slowest shutter: 6 seconds
- Exposure target: -1 EV
- Highlight ignore: 0.1%
- Allow clipping: OFF
- Midtone SNR limit: 6 EV
- Shadow SNR limit: 2 EV
- Link to Canon shutter: OFF
- Link to Dual ISO: OFF
- Show metered areas: OFF
- Show debug info: OFF
* Exposure simulation: ON

* Global draw: ON
* Cropmarks: 16:9
* Histogram
- Color space: Luma
- Scaling: Log
- Clip warning: ON
- Use RAW histogram: Full histogram
- RAW EV indicator: ETTR hint

* Intervalometer
- Take a pic every: 10 seconds
- Start trigger: Leave menu
- Start after: 3 seconds
- Stop after: 400
- Manual focusramp: OFF

* Post deflicker
- Sidecar file type: Adobe XMP
- Deflicker percentile: 50%
- Deflicker target level: -4 EV
#113
Feature Requests / Re: Slower focus step in timelapses
August 01, 2012, 08:42:19 PM
I think we should start a big topic according to the timelapse feature requests/wishes.
- more advanced bulbramping
- more advanced focusramping
- stepper motor controll for multiple axis (dolly, pan & tilt)
- keyframing possibility
- etc.
and there we have to provide as much information as we can, I mean heaps of links.
#114
Feature Requests / Re: Slower focus step in timelapses
August 01, 2012, 08:28:42 PM
Timelapser's brains are on the same highway. :) I also started a similar topic.
#115
Could ML supported DSLRs control stepper motors through USB connected nanoMoCo board (nanoMoCo, MoCoBus)? I mean motion control on multiple axis. Do they have enough power in principle? It just came to my mind, because earlier I saw a timelapse video about focus ramping...

EDIT: Some additional information about nanoMoCo + connector board here and here.

Another future thought: The Canon 650D has a touchscreen, so it could be used as an input opportunity to use a keyframing option with curves... just like Dragonframe, but a simple version.