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

Tragic Lantern / Re: Uncompressed 600D Raw Video
August 09, 2013, 12:31:22 AM
Quote from: a1ex on August 09, 2013, 12:24:46 AM
Auto Snap should work without LV. Deleting pics is not quite clean (can give err70).

Maybe a mod can move this post, since it's offtopic.

A1ex, I'm sorry for posting here... figured it was a somewhat relevant thread since Auto ETTR is only available in the RAW VIDEO nightly builds.

Just sorted the problem. The camera was set to continuous shooting which breaks the ability for ML to continue shooting. Returned to single shooting mode and it is now working.

Thanks for the additional clarification regarding the deleting err70 issues. Not worth risking that.
Tragic Lantern / Re: Uncompressed 600D Raw Video
August 09, 2013, 12:20:56 AM
Request for A1ex or 1%:

Would it be possible to allow Auto ETTR (still photos) to do the following:

1. Shutter triggered (via external camera trigger)
2. Auto ETTR reviews histogram and adjusts exposure (works as it currently does) WITHOUT LV enabled.
3. AUTOMATICALLY fire the next photo and so on until the exposure is accurate WITHOUT LV enabled.
4. Delete the photos with incorrect exposure, retain the final image correctly ETTR. This might be asking too much, but it's worth a shot.

I'm a time-lapse photographer running a solar-powered D-SLR rig for long-term landscape time-lapses. You can learn more about me and what I'm doing here:

I just got a permit at a local state park to capture 4 months of fall foliage change AND fluctuating water levels on a local river. The main subject of my shot is a small waterfall. I'm currently shooting on a 600D with a custom intervalometer in Av mode. All values are locked except shutter speed and ISO (100-800 Limit).

OK... so why does all this matter in regards to Auto ETTR?

I want to use a 6-stop ND filter to ensure silky smooth water movement in all my shots throughout the day (the unit doesn't shoot after dark). As most of you know, in-camera metering is worthless AFTER applying such a dark ND to the lens. As a result, Auto Av metering is not possible to use if I want to run this unattended, multi-month time-lapse with a 6-stop ND filter for silky water exposures.

I have performed tests running the [600D] release (the latest posted by 1% for 600D) and Auto ETTR in photo mode plays extremely nice with the ND filter because it's obviously only looking at the histogram. The downside is that I have to manually shoot the subsequent photos after the histogram is reviewed by ML Auto ETTR which is not possible when the camera is unattended. I can only trigger it once per sequence via my custom, external intervalometer unit. If ML could know to continue shooting the scene until the histogram value offers a correct exposure, that would solve the problem.

Auto Snap ALMOST works as-is, but I cannot run the camera in LV due to battery limits on the unattended solar configuration. Technically, I COULD run LV with auto-off enabled after 30 seconds from the photo being shot (camera wake provided by my intervalometer controller) but that will definitely be wasting unnecessary power.

Secondary to the above request, it would be incredible if the incorrectly exposed images from the auto ETTR calculations could be auto deleted after they are shot and examined by the ML Auto ETTR algorithm to free up space on the 128GB SD card since I'm shooting RAW. I can only return to the camera every 3-4 weeks to dump the card and free up space. I'll find a way to work around this space limit if it's too much to implement.

Thanks for taking the time to consider my request. It sure would make for an interesting long-term ML stability test. I should add that I'm doing these long term time-lapses to eventually share with others online for free, this is not a client job that I'm being paid for.
Raw Video / Raw File Recovery - Auto Power Off
July 06, 2013, 05:56:33 PM
Although I was aware of the auto-power off issue when recording with the RAW module, I had my 5D3 set to 8 minutes because most shots average less than a minute or two. However, I recently shot a clip that was over 8 minutes not thinking about my power settings. As you would imagine, the camera powered off mid-recording and I'm left with a 20+gb raw file that doesn't load into RAWMagic.

Although I already consider this shot lost as a result of user error, I wanted to reach out to the community to see if there are any ways to extract the data. I imagine it would be possible if I could somehow edit and embed the correct header and footer information into the file that was severed during the auto power off.

Auto-power off is now fully disabled.  ;D

Thanks in advance.
I would like to add a feature request:

Can the DNG sequence include the .RAW clip name in the naming structure? Right now, I just get a folder (properly named) and a DNG sequence going from 0000.dng through the final frame. As a result, I cannot easily batch process the sequences in After Effects without first manually making comps with unique naming. If I import 100 different image sequences in AE, they all look the same and it's tedious to rename to keep everything organized.

it would be best if it renamed like so:

...and so on

Based on some earlier posts, it looked as though this might have been working at one point in time. ?

Thanks for the great work, guys!
Quote from: bashi on June 12, 2013, 07:36:07 PM
can the ones of you that have issues please do the following:

-right-click on and select "Show Package Contents"
go to
and double-click raw2dng there

this will start raw2dng together with a terminal console

now drag-drop your .raw file on it
look at the Terminal Console and copy/paste the stuff that is output there into here as a comment

this gives  at least the chance of seeing where the problem is.

I'm having the same issue with 0.11. I opened through terminal as you have instructed, but I only get feedback in the raw2dng GUI. Here's what it says:

raw2dng converter GUI for OsX
Beta ver.0.11

M11-2220 File Supported
Generating jpg preview
dyld: Library not loaded: /usr/local/lib/libexiv2.10.dylib
  Referenced from: /Applications/
  Reason: image not found
/Applications/ line 31:  2925 Trace/BPT trap: 5       "$UFRAW" --out-type=jpg --out-path=../"$FILE_NAME"_jpg *.dng >> "$LOG"
Generating avi preview
dyld: Library not loaded: /usr/local/Cellar/ffmpeg/1.1.3/lib/libavdevice.54.dylib
  Referenced from: /Applications/
  Reason: image not found
/Applications/ line 31:  2927 Trace/BPT trap: 5       "$FFMPEG" -i ../"$FILE_NAME"_jpg/%6d.jpg -vcodec mjpeg -qscale 1 ../"$FILE_NAME".avi >> "$LOG"
@ 3FPS 1920x1080 only 10mb/s is required to record RAW. With the lower bandwidth, would it be possible to pull higher resolution (above 1920)?

I was able to go much higher at low FPS on an earlier 1% compile using a 6D.
Quote from: a1ex on June 12, 2013, 05:09:19 PM
Optimize for low light.

I'll give that a try now. I was set to HiJello to get a slightly faster shutter speed since the 5D3 is in continuous motion on the moco rig. I'll report back after testing in "Low Light" mode.

If you don't mind me asking (I know you're busy with more important issues), but how does the faster shutter speed in FPS override affect the LV image to create the vertical banding? Is there anyway around this in future code?

EDIT: Confirmed, Optimize for Low Light removes vertical banding in DNG sequence.
I expanded my testing with the June 11th (4d1420a) build this morning using FPS override at lower frame rates. Once I drop the 5D3 below 6FPS I get noticeable vertical banding in the resulting DNG sequence. At 6FPS it looks good, at 2FPS the vertical banding is extremely visible without any additional post processing in camera RAW.

I'm using a 3 axis motion control rig (running steppers at top speed, continuous) to experiment with a hybrid approach to quick time-lapse style video using the new RAW module. I'm pleased with the results (even with the slight mBlur due to the continuous motion and slow shutter), but the banding makes it unusable for now.

Vertical Banding - JPG
example 1 -
example 2 -

Vertical Banding - DNG
example 1 -
example 2 -

Can anyone else replicate this?
Update: The problem was that the SD card was not properly reformatted (i.e. using Disk Utility). Upon a proper format using OSX, everything is working again. What a relief. ;-)

Apologies if I scared anyone.
After installing the Canon firmware 102 (per ML directions) to allow the install of ML v2.3.5, the camera will no longer boot with a SD card installed. If I remove the card, it will boot just fine and I can confirm the 102 firmware is properly installed. However, whenever a SD card is inserted, it will not boot and flashes the red light. Removing the battery resets, but the problem continues. I have tried with 5 different SD cards, so the SD doesn't seem to be the problem.

Has anyone else experienced this? I was excited to try the new v2.3.5 for the Perseid show this weekend, but now it feels like my T3i is bricked.