Hello,
I am currently working on some general build instructions and expecially
x64 instructions, but its quite some work. Find here
http://piratepad.net/0rqEZFwrKg what I have now, actually the most
important step - OIIO itself - is missing, but will follow in the next
view days. If you want
On Thu, Jun 14, 2012 at 4:05 PM, Larry Gritz wrote:
> An excellent point. I'm quite happy to just live with the advice of "if
> you want to composite a weird 4-channel spectral image, it's your
> responsibility to affix an alpha channel and label it correctly."
>
+1. I didn't think of this obvi
On Jun 19, 2012, at 5:21 PM, Stefan Stavrev wrote:
> Not sure what to do with the caller for over, "action_over" in oiiotool.cpp:
>
> http://pastebin.com/kZ54PP0q
>
> Only lines 11 and 12 need to be changed, that is, we need to set resolution,
> number of channels and alpha channel, before ca
Not sure what to do with the caller for over, "action_over" in oiiotool.cpp:
http://pastebin.com/kZ54PP0q
Only lines 11 and 12 need to be changed, that is, we need to set
resolution, number of channels and alpha channel, before calling
ImageBufAlgo::over.
I could set the resolution to be the uni
Hello OIIO list,
Trying to build OIIO on windows. I followed the directions here
https://sites.google.com/site/openimageio/building-oiio-on-windows, but I'm
getting all sorts of errors in CMake.
Basically CMake can't find most of the external dependencies.
I'm starting the tedious process of addi
Sometimes people complain that our filtered texture looks "too blurry." It's
very hard to know, visually, except in the case of egregious errors. So I
tried to make a careful test to be sure that we are absolutely, positively
sampling the right MIPmap levels exactly for the derivatives we are
One step at a time.
Don't worry about this specialization. Just do "over" the way we talked about
before.
When we have "over" settled, I'll take a hard at what we have and think about
how to cleanly make a way to generalize it so we don't have to duplicate the
type specialization for every op
I am trying to put type specialization in one general function. I am not
sure how to implement variable size argument list, should I use features
from the new c++ standard, should I use va_list, or else ? Here is some
pseudo code for specializing 5 types:
http://ideone.com/pgLwk
The code is repea
Just use forwarding:
struct ROI; // don't include the full definition here
class ImageSpec {
...
ImageSpec (const ROI &roi); // don't include the implementation
here
...
};
But I'm not convinced you need an ImageSpec constructor fo
Oops, sorry I meant imagebuf.h includes imageio.h.
___
Oiio-dev mailing list
Oiio-dev@lists.openimageio.org
http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
I need a constructor ImageSpec(const ROI &roi, int nchans, int alpha_chan).
The problem is, ImageSpec class is in imageio.h and ROI class is in
imagebuf.h, and imageio.h includes imagebuf.h. So, ROI is not visible in
imageio.h and you can't include imagebuf.h in imageio.h, because of cyclic
depende
11 matches
Mail list logo
