Messages

SX70HS

... running EOS firmware!

While kinda off-topic here, i wonder if someone could help us @ darktable / pixls.us with providing a full raw sample set from that "Powershot SX70 HS" camera for https://raw.pixls.us/
RPU is used e.g. by RawSpeed fast raw decoding library for integration testing.
Total of 8 samples needed: {RAW, CRAW} x {16:9, 4:3, 3:2, 1:1}.

Yet still looking

Up, still looking

Just learned about this through rawtherapee.

So the word about RPU is spreading. Good

I have a Canon 5DS and will provide some rawfiles shortly.

\0/
*Please* do note the "What samples are needed:" in the first post

I also have a Pentax 645z and will provide files from that camera as well.

Awesome!
It can produce DNG and PEF, and we want *both*, with same restrictions for the scene/camera as in canon's case.

Up. Still looking.
Anyone?

Hi!

For the needs of raw image decoding libraries, and whoever else might need it, there is a repository of free (CC0) raw files.
You can read about it here and here.

Currently, we would love to get the raw sample set for these two cameras (Canon EOS 5DS / Canon EOS 5DSR).
Since Magic Lantern is for Canon cameras, i figured it is worth a try asking here

What samples are needed:

• The camera needs to be stable (tripod), in the landscape orientation, and the scene should be as static as possible (i.e. all the raws must contain the same content).
• There are just three samples: RAW, mRAW, sRAW.
  

And then just upload them to https://raw.pixls.us/ ideally, rename them before that though

@Simonwb
Thank you for the samples!
Base support has been added into darktable: https://github.com/darktable-org/darktable/commit/4c61a0b8725f34eb73d7d88828f4c1712e661ab9
If you want, you could take the same per-iso (please do enable extended iso range for this in camera ) set for mRaw and sRaw, and then i could add support for these modes too.

As for DualIso, at least for now, in darktable the base subimage is used, and any other sub-images are silently dropped.

[darktable 2.0 or newer]

Did not know this forum existed before, so here it is.

The implementation in darktable is pretty much the same as in ml's deflick.mo module.

You will need darktable 2.0 or newer. (2.0.4 is highly recommended)

Video explanation on how to use it:
https://youtu.be/VJbJ0btlui0?t=8m10s  (from 8m10s to 11m17s)

Textual explanation:

• Start darktable
• Import images
• Open one image in darkroom
• Edit it to your liking
• In exposure module in the right sidebar:


• set mode to automatic
• set the two very same parameters: percentile and target. they have exactly the same meaning as in deflick.mo
• Switch to lighttable
• Copy history stack of the image you edited
• Select all the images
• Paste history stack to the selected images
• Export images. That is all.

Exported images will have pretty similar exposure.
Now you can do whatever you want with them - e.g. assemble them into a video.

IMPORTANT: only available for raw (not even SRAW!) files, i.e. .CR2, .NEF, etc; NOT FOR ANYTHING ELSE (ldr/hdr - jpg, tiff, png, etc)

Roman.

Some explanation on how to use it:
https://youtu.be/VJbJ0btlui0?t=8m10s  (from 8m10s to 11m17s)

IMPORTANT: only available for raw (not even SRAW!) files, i.e. .CR2, .NEF, etc; NOT FOR ANYTHING ELSE (ldr/hdr - jpg, tiff, png, etc)

darktable 2.0 was just released.
This is the first darktable release, in which deflicker is available, (in exposure module) and can be used.
(it got pulled out of 1.6 for some internal reasons.)

Once we'll have a fully open source post-processing tool that uses this algorithm, I believe this feature can be removed completely from ML (and free the resources for things that can't be done in post).

As of this moment, this feature has been ported into darktable, and avaliable in exposure module

Commit: f0a71c60b08291395bbdc6a9f31d243cf3605d05
Merged pull request: https://github.com/darktable-org/darktable/pull/433

Added 550D GetSizeOfMaxRegion from mk11174.

550D.109

ISO: https://www.dropbox.com/s/sifq319w4533bpu/ISO.LOG
Aperture(f/2.8 ... f/32): https://www.dropbox.com/s/p5f508ds249l3cq/Aperture.LOG
Shutter(30" ... 1/4000): https://www.dropbox.com/s/5dtntvhsahv7wqr/Shutter.LOG

5D3.113

ISO: https://www.dropbox.com/s/ltxk0117up6eb9h/iso.log
Aperture(f/2.8 ... f/8): https://www.dropbox.com/s/c59d874jibzw7bw/av.log
(Is shutter log needed?)

Will do same for 550D when stub for GetSizeOfMaxRegion is added.

I don't think control of the mirror swing has been discovered. It's possibly hardwired in.

Shutter can be opened without taking shot in two ways:

• Sensor cleaning -> Clean now
• Enabling Mirror lockup and pressing Shutter first time (second press will take pic & close shutter)

Why would this be useful: taking picture with closed shutter equals to taking picture with body cap on, but without necessity to disconnect lens, put lens & body caps on.
It also will help in not killing shutter too yearly.

Purpose of this is to take a so-called Black Frame.
They used mainly in astrophotography.
Usually, several(!) of them are taken, averaged and subtracted from actual Light Frames.

Canon can automatically take them after taking image, and subtract them ("Long-Exp noise reduction"), but only resulting file is stored.

>What's so bad about the sidecar files?
They can be lost.

Anyway, i've almost finished porting Deflicker algorithm into my preferred RAW develop application - darktable
For now, code is located in my branch: https://github.com/LebedevRI/darktable/tree/iop-exposure-deflicker

Currently Deflicker stores data in sidecar file.
Is there any way to store same data directly in CR2, in some metadata tag?
Or in Copyright notes, that can be inputted through canon menu?

... but you will only ettr the parts lit by the flash, not the background with the ambient light (you need to change shutter or iso for that), so you will get proper exposure using your ettr idea, but of a different shot :-p

Yes, that was my point.

You can experiment with the ETTR indicator (manual adjustments), but I doubt it will be exact (though better than nothing).

Well, yes, i can manually experiment with that.
This is why i'm asking is it possible to implement such a behaviour in ETTR module?
Or, more correctly, is there any hope to see this implemented in nearest future?

The most obvious example of the use:
Camera is in M mode, flash mounted in Hot-Shoe and powered on.
The camera shutter speed, aperture and iso are manually set not to "auto" value.
To reach proper exposure, flash output is changing.
Flash Exposure Compensation is flash analog of camera's standart EC (in non-M modes), so by changing FEC we can do ETTR.

I think that ETTR computation of FEC is possible only by shot, not in Live View.

Would it be possible to have such a modification of ETTR?