Yes, you would add it as an array of uint8 (bytes), where the array length is
the size of the blob, in bytes.
Like this:
spec.attribute ("icc-profile", TypeDesc(TypeDesc::UINT8, blobsize), &blob);
This is assuming that an ICC profile can be unambiguously decoded "on the other
end" by knowin
For embedded icc profiles it would be a binary blob, is this even supported?
.malcolm
On 19/07/2013, at 12:33 AM, Larry Gritz wrote:
> I have to admit that my knowledge is sketchy as to precisely what data makes
> up an ICC profile.
>
> So anyway, the way that the ImageSpec is organized is tha
Thank you for rapid reply.
I completely deleted customized libjpeg and use system default libjpeg library.
Then it works fine.
Thank you so much for your help.
---
Kazuyo Mizuno
kazuyokoj...@gmail.com
2013/7/24 Larry Gritz :
> Another thing I thought of: It doesn't really have to be two diffe
Another thing I thought of: It doesn't really have to be two different
libjpeg's on the same computer. This could also happen if you built on one
computer, and tried running OIIO on a another computer, and the two computers
had different versions of libjpeg.
On Jul 24, 2013, at 12:27 AM, Larr
Hi
the issue in case 2 is that you are calling OIIO from a program linking
against libjpeg8, hence the mismatch message. Use the ldd command to
check the libraries used by your program, it should show libjpeg80 in
the list.
On 07/24/2013 05:41 AM, Kazuyo Mizuno wrote:
Hi, everyone.
I have
OIIO does not have a required libjpeg version, BUT the one it builds with needs
to match the one it's linked to at runtime.
Those messages look like what I would expect if your system had two different
libjpeg versions installed in different places, and somehow the include files
used when you b
