This script reads an image into a pixel array, processes the pixels with a
LUT and then writes the data back to disk. It handles the 10, 12 or 16 bit
integer data as well as half-float and float data. The half-float data read
was a little trickier than one would hope.
so if people think it's helpful. First, if
>> you ask for HALF, I could have it return float. Second, I could collapse 2a
>> and 2b, and just say that if you ask for UNKNOWN, you get an array of uint8
>> back with the native raw data, even if it happened to be all channels of
>>
o true half type.
>>
>> * If you ask for UNKNOWN (explicitly "give me raw data"), it returns an
>> array of unsigned chars containing the raw data.
>>
>> Everybody can live with that?
>>
>>
>> On Feb 19, 2016, at 8:08 AM, Haarm-Pieter Duik
Hey Alex,
I've been looking at this code as well recently. If you check out the
RawInput::open method here:
https://github.com/OpenImageIO/oiio/blob/master/src/raw.imageio/rawinput.cpp#L139
it looks like a metadata field named "raw:ColorSpace" on the secondary
'config' ImageSpec will drive the
It looks like that 'adjust_maximum_thr' should be set to 0.0 generally. The
comment from the libRaw changelog is as follows:
"
* dcraw_emu's -c parameter now wants numeric (float) argument.
This value
is assigned to params.adjust_maximum_thr.
Use -c 0.0 for
e ALL the defaults set sensibly, with
> 'config' overrides for any particularly interesting functionality that it
> can do upon reading.
>
>
> On Sep 10, 2016, at 7:45 AM, Haarm-Pieter Duiker <l...@duikerresearch.com>
> wrote:
>
> Hello,
>
> I've been running in
e?
>
> If not, can oiiotool take input from stdin coming from dcraw?
>
> -Alex
> On Tue., 13 Sep. 2016 at 2:58 am, Larry Gritz <l...@larrygritz.com> wrote:
>
>> Python: it depends on the interface you are using to read the files --
>> raw ImageInput, or using ImageBu
Hello,
I've been running into an issue with the OIIO libRaw support and wanted to
see if anyone else had run into the same problem and found a workaround.
The issue
Raw files read and developed by OIIO using libRaw are automatically
brightened.
The potential cause tl;dr
The RawInput::open
se".
>
> I will have a patch forthcoming as soon as I also fix the other thing you
> report, which is that for filetransform, there is no need to issue an error
> message for missing config.
>
> -- lg
>
>
> On Oct 16, 2019, at 7:27 PM, Haarm-Pieter Duiker
> wrot
Hello,
I'm running into what appears to be a regression. The
ImageBufAlgo ociotransform used to work with only a LUT specified. It now
seems to require that the OCIO environment variable points to a valid
config, even if the LUT has nothing to do with the specified config. This
issue shows up
10 matches
Mail list logo
