Messages

Unrelated; on 60D it's a bug on the error handling code.

Noted.  I do get the same behaviour here ive just noticed.  No raw error when large raw files are used.

I can confirm what was likely already established - no raw error message with "press set" enabled, but as stated, the intervalometer forces Auto-ETTR to use "Always on" which produces the raw error.

It's from the photo raw backend: raw_update_params() fails for some reason.

To trace it, define RAW_DEBUG in raw.c to see some more error messages, but - more likely - raw_buffer_intercept_from_stateobj is either not called during a long exposure, or called at the wrong time.

And, of course, "Raw error" message means ETTR did not work at all for that picture. If it did change the exposure, that's a bug in the error handling code.

Seems to be a bug in the error handling code as on a single shot basis, the exposure does adjust.

It's just when i combine it with the intervalometer than i cannot rely on auto-ettr when the exposure requires constant adjusting (i.e a sunset). 

Hi A1ex, are you aware of the issues  some 6D owners are reporting in using the Auto-ETTR module in conjunction with the intervalometer?

When do you get these "Raw error" messages? Only after it stopped working for you, before, or even when not using the intervalometer? I just checked the ETTR code and there are a few scenarios where it would display this error message, one of them not being able to read the raw shooting parameters. It's just a wild guess, but maybe enabling Expo. Override helps?

Also make sure to put a clean ML installation on the SD card and not leave any stale TL files in the ML folder.

I get the RAW ERROR message every time i take a photo with Auto-ETTR enabled (even without using the intervalometer). 

Just did a fresh format of the SD card and put the latest nightly on, and still get the error.  Again, im not sure how important that is, or whether it has anything to do with the Auto-ETTR working inconsistently when the intervalometer is enabled.

For now, shooting sunset timelapses on the 6D with Auto-ETTR and the intervalometer doesnt seem possible.

In my experience raw is still buggy on the 6d, no matter TL or ML, the problem is that the raw dev (alex) doesn't have a 6d camera to test.

It helps if you at least turn off jpeg and *only* shoot raw, this at least is a known issue. For everything else, try to isolate the exact circumstances and make it reproducible, then post a bug ticket instead of cross-posting in the forum.

How do i post a bug ticket?

Do you shoot raw *only*? If not disable creating jpeg files, it's a known bug that leads to this error message.

Yep, Raw only here.

I should add - im also getting a 'RAW ERROR' every time i take a shot with auto-ETTR enabled (whether or not im using it with the intervalomter).

Im not sure if that is related to the problem i having, or the cause/effect of such error.

Im getting the RAW error and general ETTR inconsistent performance when used with the intervalometer too.  Problem hasnt rectified itself after i switched to ML nightlies either (6D).

Hi guys, i've been encountering an issue with previous TL and now ML nightly releases for the 6D.

Auto-ETTR (set to 'always on') appears to work just fine when used on a single shot basis, with the exposure adjusting as you would expect.

When i combine it with the intervalometer however, i notice inconsistent results.

For example, in my experiment with a sunset tonight - at f8, i get nice metering from shutter speeds of 1/4 (iso 100) to 0"6 (iso 100).  From that point on however, the exposure does not correct for the decreasing light and the photo gets darker and darker. 

Intervalometer was set to take a photo every 35 seconds.  Slowest shutter for Auto-ETTR was 32 seconds.  Camera is in manual mode.

Sometimes, i quit the intervalometer while leaving auto-ETTR on, ML will correct it itself, but switching the intervalometer back on will again lead to inconsistent results.

Im currently running magiclantern-Nightly.2014Mar23.6D113 although i have experienced similar issues with earlier nightlies.

Has anyone encountered this kind of thing?  I want to be able to trust ML to do its thing.