Project

General

Profile

Camera Support #12205

Canon 5DS: mRaw/sRaw support

Added by Emre Safak over 1 year ago. Updated about 1 year ago.

Status:
Fixed
Priority:
Low
Assignee:
Category:
Darkroom
Target version:
Start date:
05/19/2018
Due date:
% Done:

100%

Estimated time:
Affected Version:
2.4.3

Description

I'm having trouble editing certain pictures taken with my 5Ds. I note that the lens is incorrectly identified as a 300mm f/2.8L IS II when they were taken with a Tamron 28-70mm f/2.8 G2.

IMG_0879.CR2 (33.2 MB) IMG_0879.CR2 Emre Safak, 05/19/2018 10:42 AM

Associated revisions

Revision 82bc887f (diff)
Added by Roman Lebedev about 1 year ago

RawSpeed submodule update: RW2 decompressor rewrite (20-30% faster),
Canon EOS 5DS[R] mRAW/sRAW support; 1-component LJPEG's support.

Fixes #12205.
Fixes #12242.

History

#1 Updated by Roman Lebedev about 1 year ago

  • % Done changed from 0 to 20
  • Assignee set to Roman Lebedev
  • Status changed from New to Incomplete
  • Subject changed from 5Ds: Failed to read camera white balance information to Canon 5DS: mRaw/sRaw support
  • Tracker changed from Bug to Camera Support

[rawspeed] (IMG_0879.CR2) bool rawspeed::RawDecoder::checkCameraSupported(const rawspeed::CameraMetaData *, const std::__cxx11::string &, const std::__cxx11::string &, const std::__cxx11::string &), line 168: Camera 'Canon' 'Canon EOS 5DS', mode 'sRaw1' not supported, and not allowed to guess. Sorry.

Please take one slightly overexposed raw shoot per each raw mode (RAW, mRAW, sRAW) per each ISO level you can set on that camera, including all sub-iso levels, and extended low/high iso if any, pack them into one archive, upload them somewhere, e.g. dropbox, and post the link.

I'll take it over from there.

#2 Updated by Emre Safak about 1 year ago

Here are the files. Thanks a lot!

#3 Updated by Roman Lebedev about 1 year ago

  • % Done changed from 20 to 50
  • Status changed from Incomplete to In Progress

Emre Safak wrote:

Here are the files. Thanks a lot!

Thanks for the samples.
For future reference, that is not what i meant by slightly over-exposed :)
I meant a normal, viewable image, but maybe with +1EV exp correction, at most.

#4 Updated by Emre Safak about 1 year ago

These have +2/3 EV correction. I just shot the wall in front of me; that's why they might look weird.

#5 Updated by Roman Lebedev about 1 year ago

Emre Safak wrote:

These have +2/3 EV correction.

I just shot the wall in front of me; that's why they might look weird.

That's the point, something less wall-y would be nice, but no need to reshoot, these will do.

#6 Updated by Emre Safak about 1 year ago

I have an IT8 calibration target, if it helps. Sorry for the trouble.

#7 Updated by Roman Lebedev about 1 year ago

Emre Safak wrote:

I note that the lens is incorrectly identified as a 300mm f/2.8L IS II when they were taken with a Tamron 28-70mm f/2.8 G2.

I'm afraid this i won't be fixing. It's quite typical problem with off-brand lenses.
Normally exiv2 would be handling that, but i think they just gave up on that..

#8 Updated by Roman Lebedev about 1 year ago

  • % Done changed from 50 to 100
  • Status changed from In Progress to Fixed

#9 Updated by Emre Safak about 1 year ago

If it gets fixed at their end, does it get fixed here too? I found their ticket.

#10 Updated by Roman Lebedev about 1 year ago

Emre Safak wrote:

If it gets fixed at their end, does it get fixed here too? I found their ticket.

Well, it should, but since exiv2 is a system library,
it will only get fixed for you once your distribution updates to that version.
And all that is assuming darktable is reading the right EXIF field.

#11 Updated by Roman Lebedev about 1 year ago

  • Target version set to 2.6.0

Also available in: Atom PDF

Go to top