Re: [Oiio-dev] oiio-dev mail list: trouble and future

I got kicked from the list a while back, but managed to join again (in a way I can't recall), but I'm fine either way. Mostly replied to confirm your email. On Tue, Jun 6, 2023, 21:11 Thiago Ize wrote: > I'm good with an immediate switch and here's confirmation I received your > email :) > > On

Re: [Oiio-dev] oiiotool slower than python - expected?

HI Simon! Not certain, but you might be running into something I've experienced before regarding image cache size(?). However, I experienced the opposite where Python was slower than oiiotool due to different defaults. For the long explanation from Larry please search for the email with this

Re: [Oiio-dev] OpenimageIO Resize Function Causes Unwanted Artifacts

Great! On Fri, Aug 12, 2022, 03:05 Max Shooster wrote: > Hi. I have successfully resolved the issue by normalizing the pixel values. > > Thanks! > ___ > Oiio-dev mailing list > Oiio-dev@lists.openimageio.org >

Re: [Oiio-dev] OpenimageIO Resize Function Causes Unwanted Artifacts

Hi! Have you tried doing the resize in log space? colorconvert to log -> resize -> colorconvert back to linear On Tue, Jul 19, 2022 at 7:46 PM Max Shooster wrote: > I was able to replicate a similar result using the sample multichannel exr > here -- >

Re: [Oiio-dev] Renaming channels and copying into another EXR

Hi Hugh! You should be able to do this with ImageBufAlgo.channels() ( https://openimageio.readthedocs.io/en/latest/pythonbindings.html#image-transformations-and-data-movement ) import OpenImageIO as oiio buf = oiio.ImageBuf('/path/to/source.exr') new_buf = oiio.ImageBufAlgo.channels(buf, ('R',

Re: [Oiio-dev] OpenimageIO Resize Function Causes Unwanted Artifacts

Hi Max! I can't answer the cryptomatte question, but I think your pickle issue is related to shared objects in python's multiprocessing. Instead of passing the ImageBuf object you should pass the path to the image and create an ImageBuf in the worker process itself. Multiprocessing doesn't share

Re: [Oiio-dev] Editing just the header attribs

Great! On Thu, Aug 4, 2022, 11:53 Anders Langlands wrote: > Hi Daniel that looks like exactly what I’m after, thanks! > > On Thu, 4 Aug 2022 at 20:45, Daniel Flehner Heen > wrote: > >> Hi! >> >> I hope I didn't misunderstand your question, but this should work:

Re: [Oiio-dev] Editing just the header attribs

Hi! I hope I didn't misunderstand your question, but this should work: import OpenImageIO as oiio buf = oiio.ImageBuf('/path/to/imagefile.exr') buf.specmod().attribute('MyAttribute', 'my value') buf.write('/path/to/modified/imagefile.exr') Please note: I'm not sure you can avoid writing the

Re: [Oiio-dev] Unable to create scanline EXR, only tiled

utFile from a type-mismatched part." >> >> ...Getting closer. >> >> On Tue, Apr 12, 2022 at 11:19 AM Daniel Flehner Heen < >> flehnerhee...@gmail.com> wrote: >> >>> Hi, Jerome! >>> >>> I ran into the same issue a c

Re: [Oiio-dev] Unable to create scanline EXR, only tiled

Hi, Jerome! I ran into the same issue a couple of weeks back. Don't know if this is the best way, but setting the tile width and height to 0 directly on the ImageSpec worked for me. So before out.open(): # I created/adjusted the specs in advance and referenced them for each subimage, but this

Re: [Oiio-dev] Python - ImageBufAlgo.channels taking it's time (OIIO - 2.3.9.1)

Sorry for being the one breaking the 256MB barrier :/ At our studio we're transitioning to this workflow as it makes compositors' lives easier. The 1GB fix you gave me helped a lot, but if others are working the same way, option 1, increasing the default might make sense. I like option 2 and 4 as

Re: [Oiio-dev] Python - ImageBufAlgo.channels taking it's time (OIIO - 2.3.9.1)

ats, it's is still super fast, > a little more than 3 seconds, basically the same speed as when we used the > 4GB cache. So even in the pathological case and with the poor access > pattern of channels(), it's not critical to use a cache that's larger than > the images! Cache size 400 MB also is

Re: [Oiio-dev] Python - ImageBufAlgo.channels taking it's time (OIIO - 2.3.9.1)

a > that is messing with the performance! > > > On Nov 10, 2021, at 1:26 PM, Daniel Flehner Heen > wrote: > > I created the black exr and it is indeed small. Still takes a long time > extracting the channels, so it's good for testing. > My only concern is that some of th

Re: [Oiio-dev] Python - ImageBufAlgo.channels taking it's time (OIIO - 2.3.9.1)

eep or flat, so > "deep" is all or none of the channels in that part/subimage. > > > On Nov 10, 2021, at 12:30 PM, Daniel Flehner Heen > wrote: > > Hi, Larry! > > Thanks for looking into this. I created an image with IBA.noise() in 70 > channels and there

Re: [Oiio-dev] Python - ImageBufAlgo.channels taking it's time (OIIO - 2.3.9.1)

e and see a big speed disparity > like this? Or is it in any way specific to the particular image? > > Wednesdays are pretty packed, but I'l try to take a look at this today if > I can. > > > On Nov 10, 2021, at 4:08 AM, Daniel Flehner Heen > wrote: > > Hi! > > I'm attem

[Oiio-dev] Python - ImageBufAlgo.channels taking it's time (OIIO - 2.3.9.1)

Hi! I'm attempting to extract only the RGBA channels of an EXR with 70+ channels. Using: oiiotool -i:ch=R,G,B,A /path/to/gigantic.exr -o manageable.exr takes about 8 seconds. In python (2.7 !caugh..): buf = oiio.ImageBuf('/path/to/gigantic.exr') obuf = oiio.ImageBufAlgo.channels(buf, ('R', 'G',

Re: [Oiio-dev] unable to set ImageBufAlgo.render_text opacity

ked. It's just a mistake somewhere, I will try to find a fix. > > -- lg > > > On May 27, 2021, at 12:35 AM, Daniel Flehner Heen > wrote: > > Hi Larry! > > Apologize for the lack of response. > > Inspecting the values indeed show variations in the alpha channel, so it

Re: [Oiio-dev] unable to set ImageBufAlgo.render_text opacity

ot; will be exactly (1.0, ...) no matter what the something is. > Note that for both of those, if clamped to a max of 1.0, they will look the > same. > > > On May 25, 2021, at 12:18 PM, Daniel Flehner Heen > wrote: > > Hmmm. I've only checked visually, but when re

Re: [Oiio-dev] unable to set ImageBufAlgo.render_text opacity

appens, specifically? >> >> >> On May 25, 2021, at 6:31 AM, Daniel Flehner Heen >> wrote: >> >> Hi! >> >> I'm attempting to render text with 40% opacity in python without success. >> OIIO 2.2.10.1 >> >> ``` python >> import

Re: [Oiio-dev] unable to set ImageBufAlgo.render_text opacity

Sorry, should have been more specific. There seems to be no difference in the text's transparency for values between 0.1 and 1.0 for the alpha channel. On Tue, May 25, 2021, 20:48 Larry Gritz wrote: > What happens, specifically? > > > On May 25, 2021, at 6:31 AM, Daniel Flehner H

[Oiio-dev] unable to set ImageBufAlgo.render_text opacity

Hi! I'm attempting to render text with 40% opacity in python without success. OIIO 2.2.10.1 ``` python import OpenImageIO as oiio buf = oiio.ImageBuf(oiio.ImageSpec(640, 480, 4 oiio.FLOAT)) oiio.ImageBufAlgo.render_text(buf, 100, 200, "Hello, World!", 60, "FreeSans", (1, 1, 1, 0.4))

Re: [Oiio-dev] OIIO Tool requires to have a sRGB colorspace when converting a jpg file.

reason it still asks to have sRGB in the ocio config. > > *--* > > *Jose Alejandro Enriquez* > > > *Pipeline TD, PIXOMONDO Skype Name: live:.cid.90318dda1ebc48cf* > ------ > *From:* Oiio-dev on behalf of > Daniel Flehner Heen > *Sent:* Tue

Re: [Oiio-dev] OIIO Tool requires to have a sRGB colorspace when converting a jpg file.

I use Output - sRGB a.k.a out_srgb for sRGB and it gives a nice result. Please note that it behaves a bit different than sRGB in nuke for instance. It doesn't clip. On Tue, Apr 20, 2021, 23:00 Jose Alejandro Enriquez < jose.enriq...@pixomondo.com> wrote: > For sure: > > > > *--* > > *Jose

Re: [Oiio-dev] ImageBufAlgo.ociolook() seems to favor inverse

Great, thanks! On Wed, Jan 27, 2021, 20:34 Larry Gritz wrote: > https://github.com/OpenImageIO/oiio/pull/2844 > > > On Jan 27, 2021, at 10:11 AM, Daniel Flehner Heen > wrote: > > Haha, ok. Thanks! > > On Wed, Jan 27, 2021, 18:55 Larry Gritz wrote: > >> No,

Re: [Oiio-dev] ImageBufAlgo.ociolook() seems to favor inverse

Haha, ok. Thanks! On Wed, Jan 27, 2021, 18:55 Larry Gritz wrote: > No, I'll submit a PR right away, there's no need for a separate issue. > > Withhold judgment on my need to apologize until you see just how stupid > this bug is. :-) > > -- lg > > On Jan 27, 2021, at 9:19

Re: [Oiio-dev] ImageBufAlgo.ociolook() seems to favor inverse

rry about that. > > -- lg > > > On Jan 27, 2021, at 5:51 AM, Daniel Flehner Heen > wrote: > > Hi! > > I'm attempting to implement the use of ImageBufAlgo.ociolook(), but keep > getting an error message "3D Luts can only be applied in the forward > direction

[Oiio-dev] ImageBufAlgo.ociolook() seems to favor inverse

Hi! I'm attempting to implement the use of ImageBufAlgo.ociolook(), but keep getting an error message "3D Luts can only be applied in the forward direction. (inverse) specified." even if I provide "inverse=False" oiio.ImageBufAlgo.ociolook( buf, buf, "Twin", "acescg",

Re: [Oiio-dev] Does oiiotool support piping?

the generate-dailies tool mentioned above just passes > raw 16 bit int byte data to ffmpeg and it works well, so maybe the > complexities around tiff output mentioned by Larry's response could be > avoided. > > > Hope this helps! > > -Jed > > > On 1/20/21 5:16

[Oiio-dev] Does oiiotool support piping?

Hi! Is oiiotool able to pipe output into another application? I can't see it mentioned in help or rtd. simplified example: oiiotool source_image_acescg.#.exr -colorconvert acescg out_srgb -o - | ffmpeg -i pipe:0 output_movie.mov Thanks! -- -Daniel

Re: [Oiio-dev] preserve alpha channel with ImageBufAlgo.paste()

nd of mis-wrote it C++ fingers, so it says > > ROI srcroi=ROI.All > > but that first "ROI" is a type, not another parameter. > > -- lg > > > On Jan 13, 2021, at 2:06 PM, Daniel Flehner Heen > wrote: > > Hi! > > I'm attempting to slim down s

[Oiio-dev] preserve alpha channel with ImageBufAlgo.paste()

Hi! I'm attempting to slim down some code and want to use ImageBufAlgo.paste() directly rather than ImageBufAlgo.over() to composite a logo with an alpha channel over an image. Is that even possible? I keep getting black where it should be transparent. I've made sure the alpha channel is

Re: [Oiio-dev] oiiotool : exr ACEScg to sRGB jpg ?

Try the aliases. out_srgb for instance On Fri, Jun 5, 2020, 23:33 spo...@toxixox.com wrote: > Yes I’m confused too, ‘Output - sRGB’ was also my best guess. > > I’m pretty confident with my Nuke settings, ocio config looks OK, oiiotool > syntax is correct… Now I think I’d better check the source

Re: [Oiio-dev] change in pybind11 setup

Hi! I welcome this as I'm one of the users behind a firewall etc. I've been meaning to address this as I've had to do some hacks to be able to build without the auto-download. Thanks! Looking forward to check it out. On Mon, Mar 2, 2020, 18:55 Larry Gritz wrote: >

Re: [Oiio-dev] ImageBufAlgo.max() ?

dd", to get a new ImageBuf composed from inputs > buffer, but instead of having > OUT = A + B > I would like > OUT = max(A, B) > > Cheers ! > > Le mer. 22 janv. 2020 à 16:12, Daniel Flehner Heen < > flehnerhee...@gmail.com> a écrit : > >> Hi! &

Re: [Oiio-dev] ImageBufAlgo.max() ?

Hi! I may have misunderstood your question, but have you looked at ImageBufAlgo.computePixelStats() ? On Wed, Jan 22, 2020 at 3:51 PM Alexis PRAYEZ wrote: > Hi all, > > I am looking for a way of doing a "max" operation on 2 or more ImageBuf, > in python. There are add(), sub() and over() but

Re: [Oiio-dev] OpenImageIO just crossed 1000 stars on GitHub

 On Mon, Dec 16, 2019, 20:29 Alex Suter wrote: > Congrats! It's a great project. > > On Mon, Dec 16, 2019 at 11:09 AM Larry Gritz wrote: > >> W00t! >> >> -- >> Larry Gritz >> l...@larrygritz.com >> >> >> >> >> ___ >> Oiio-dev mailing list >>

Re: [Oiio-dev] New documentation -- first look

This looks really good! Nice to have an online doc and I'm really glad you kept the pdf as well since it's so easy to read and handy in offline environments. On Sat, Jul 6, 2019, 22:18 Larry Gritz wrote: > I've spent the last several weekends and many evenings doing a great big > translation of

Re: [Oiio-dev] Issue building oiio - python dependency

Hi! Try setting the following in your build options: USE_PYTHON=0 There's a lot of good info in the INSTALL.md file :) On Thu, May 16, 2019 at 11:18 AM Etienne Sandré-Chardonnal < etienne.san...@m4x.org> wrote: > Hi, > > I am trying to build oiio on Ubuntu 18.04. > > I get the following error:

Re: [Oiio-dev] ImageIO tools

;>> >>>>>> I just simply run this code. >>>>>> #include >>>>>> #include >>>>>> >>>>>> using namespace OIIO; >>>>>> int main() { >>>>>> const char *filename = "fo

Re: [Oiio-dev] ImageIO tools

hrach.martirosyan...@gmail.com> wrote: > >> Hi >> Thank you for your quick response. >> Actually I need built version. Binaries include files and .so files. >> >> If you have already built version and can give me a link I would really >> appreciate it. >

Re: [Oiio-dev] ImageIO tools

Hi! Have you tried: "apt-cache search openimageio" in a terminal? It will list the correct name of the package(s). You then enter: "sudo apt-get install [PACKAGENAME(S)]" On Fri, Apr 26, 2019 at 9:44 AM Hrach Martirosyan < hrach.martirosyan...@gmail.com> wrote: > Hi > > > I want to find built

Re: [Oiio-dev] Issue with ImageBufAlgo ociodisplay in python

2.0 works for you :) On Wed, Nov 28, 2018 at 2:02 PM Etienne Fleurant wrote: > As far as I know, you can't bake an OCIO color profile using colorconvert. > You can only use aforementioned ociodisplay function to do that. > > Etienne > > On Nov 28, 2018, at 03:03, Daniel Flehner

Re: [Oiio-dev] Issue with ImageBufAlgo ociodisplay in python

Also.. I may be grasping at straws here, but are you sure OIIO was compiled with OCIO enabled? On Wed, Nov 28, 2018 at 9:03 AM Daniel Flehner Heen wrote: > Have you tried using ImageBufAlgo.colorconvert() instead? > > On Wed, Nov 28, 2018 at 4:14 AM Stephen Mackenzie > wrote: >

Re: [Oiio-dev] Issue with ImageBufAlgo ociodisplay in python

Have you tried using ImageBufAlgo.colorconvert() instead? On Wed, Nov 28, 2018 at 4:14 AM Stephen Mackenzie wrote: > Yes, I had the same issue described here. The pybind11 work being done for > then-oiio-1.9-alpha fixed it for me, so I've just been awaiting the oiio-2 > release as a solve. >

Re: [Oiio-dev] OpenImageIO 2.0 beta has landed!

Woohoo! Really looking froward to checking out the new Python bindings :) Thank you! On Sat, Nov 10, 2018 at 11:01 PM Thomas Mansencal < thomas.mansen...@gmail.com> wrote: > > The Python bindings are now all based on pybind11 (no more Boost.Python) > and have had a number of cleanups, one of

Re: [Oiio-dev] PSD Layers in Python

unately that code snippet doesn't work for me on version 1.8.11. >> I'll check to see if it's a problem with the version or with the Photoshop >> file I'm using. >> >> On Tue, 30 Oct 2018 at 11:56, Daniel Flehner Heen < >> flehnerhee...@gmail.com> wrote: >> >

Re: [Oiio-dev] oiio-Release-1.8.14: using PKG_CONFIG_PATH to find dependencies.

ust don't know > enough about pckconfig to implement it myself (without sinking a whole > bunch of time into learning it). > > I assume things wouldn't break anything for people/systems who don't have > the pkgconfig stuff set up for openexr. > > > On Sep 13, 2018, at 11:00 AM, D

Re: [Oiio-dev] oiio-Release-1.8.14: using PKG_CONFIG_PATH to find dependencies.

gt; > On Sep 13, 2018, at 4:11 AM, Daniel Flehner Heen > wrote: > > Hi! > > Is there a reason why OIIO doesn't use "pkg_check_modules" and the > PKG_CONFIG_PATH environment variable to locate OpenEXR, IlmBase, etc. like > it does with LibRaw and FFmpeg? > > I'm w

[Oiio-dev] oiio-Release-1.8.14: using PKG_CONFIG_PATH to find dependencies.

Hi! Is there a reason why OIIO doesn't use "pkg_check_modules" and the PKG_CONFIG_PATH environment variable to locate OpenEXR, IlmBase, etc. like it does with LibRaw and FFmpeg? I'm writing a build script which aims to be as dynamic as possible and want to avoid hard coding paths to

Re: [Oiio-dev] latest dcraw help

I'm not sure, but you might also find dcraw/libraw in your linux distro's package repository. Building oiio with libraw is also fairly straight forward if you want an updated oiiotool. Good luck! On Mon, Aug 27, 2018, 21:26 Will Anielewicz wrote: > Hi Larry and Daniel sorry Im being lazy about

Re: [Oiio-dev] latest dcraw help

Hi! Have you tried here: https://www.cybercom.net/~dcoffin/dcraw/ It shouldn't be hard to build. On Mon, Aug 27, 2018, 18:17 Will Anielewicz wrote: > I have an old dcraw compiled for linux buit it doesnt support the camera > Im using a nikon d810. > Does anyone have a link to a more recent

Re: [Oiio-dev] OpenImageIO EXR Change

Sorry for the double reply guys. For some reason your email @larry got caught by my SPAM filter. On Tue, May 15, 2018 at 9:17 AM, Daniel Flehner Heen < flehnerhee...@gmail.com> wrote: > Hi, Matthew! > > When you say half sizing, do you mean half resolution or half file s

Re: [Oiio-dev] OpenImageIO EXR Change

Hi, Matthew! When you say half sizing, do you mean half resolution or half file size? For half resolution you could do as follows: BEGIN## import OpenImageIO as oiio buf = oiio.ImageBuf('/path/to/fullsize.exr') # Get the specs for original image to use

Re: [Oiio-dev] Places where OIIO is used

We, as in Storm Studios, use OIIO in our dailies and delivery tools. On Thu, May 3, 2018 at 8:45 AM, Thomas Mansencal wrote: > Hi Larry, > > Colour and Colour - HDRI > use it as a soft >

Re: [Oiio-dev] Happy birthday, OpenImageIO

people the erroneous impression that no help is wanted or needed. There's > no crisis brewing, it's just that there is SO MUCH we could do even better > with more hands on a regular basis. > > -- lg > > On Apr 23, 2018, at 12:19 PM, Daniel Flehner Heen <flehnerhee...@gmail.com&

Re: [Oiio-dev] Happy birthday, OpenImageIO

Mazel tov!!! Wow! 10 years! I really appreciate all the time and effort you and the other core developers put into OIIO. Thank you so much! I'll try to contribute as much as I can on the mailing list with small python snippets and also have an ambition of developing the skills needed to

Re: [Oiio-dev] OIIO - Python - ImageInput to ImageBuf

Great! On Mar 12, 2018 17:05, "Alexis PRAYEZ" <apra...@brunchstudio.tv> wrote: > You're right, works perfectly ! > Thumbnail generation is down from 180s to 14s on a decent size asset :) > > Thx for the help, > Alexis > > 2018-03-12 13:25 GMT+01:00 Daniel

Re: [Oiio-dev] OIIO - Python - ImageInput to ImageBuf

ss afterwards" > > Cheers, > > 2018-03-12 10:31 GMT+01:00 Daniel Flehner Heen <flehnerhee...@gmail.com>: > >> Hi! >> >> I haven't done this my self, but in the docs for 1.8.x it says that >> ImageBuf may be initialized with defined subimage and/or

Re: [Oiio-dev] OIIO - Python - ImageInput to ImageBuf

Hi! I haven't done this my self, but in the docs for 1.8.x it says that ImageBuf may be initialized with defined subimage and/or miplevel. buf = oiio.ImageBuf(filename, subimage, miplevel) Hope this helps On Mon, Mar 12, 2018 at 10:22 AM, Alexis PRAYEZ wrote: > Hi

Re: [Oiio-dev] How to properly composite two images?

Hi again! Got it working. Must have messed up something in my earlier attempts. Had to paste logo in the correct position in an empty buffer the size of my background first and then over that buffer over the background. Have a nice weekend! On Fri, Feb 9, 2018 at 10:47 AM, Daniel Flehner Heen

Re: [Oiio-dev] How to properly composite two images?

Oh, and it's python and OIIO version 1.8.5 Thanks On Fri, Feb 9, 2018 at 10:16 AM, Daniel Flehner Heen < flehnerhee...@gmail.com> wrote: > Hi! > > I'm attempting to composite two images, but having a hard time getting the > result I'm after. > It's a simple logo with al

[Oiio-dev] How to properly composite two images?

Hi! I'm attempting to composite two images, but having a hard time getting the result I'm after. It's a simple logo with alpha over a background situation. I've tried both ImageBufAlgo.paste() and ImageBufAlgo.over() with varying results. None of them yields the result I expected. The logo

Re: [Oiio-dev] Layout of build & dist

This would have no big impact on how we build OIIO and it sounds like a good idea to adapt to convention. I have faith in your judgement! On Tue, Jan 30, 2018 at 8:16 AM, Larry Gritz wrote: > So you may have noticed that OIIO (and OSL) do something slightly weird -- > the

Re: [Oiio-dev] reading videos/movs in OpenImageIO

Great! Glad to be of assistance. -Daniel On Dec 22, 2017 18:08, "Yegor Swarovski" wrote: Hey Daniel, actually that simple explanation was exactly what I needed. Thanks for that! On Thu, Dec 21, 2017 at 5:04 PM, Troy Sobotka wrote: > On Thu, Dec 21,

Re: [Oiio-dev] Python add timecode to EXR

style works by adding frame rate meta to a buffer like so: buf.specmod().attribute('framesPerSecond', oiio.TypeRational, (24000, 1000)) Thanks! -Daniel On Sat, Dec 2, 2017 at 8:08 PM, Daniel Flehner Heen <flehnerhee...@gmail.com > wrote: > Hi again! > > Ok, so I tried and got

Re: [Oiio-dev] Python add timecode to EXR

ImageIO_v1_8::ImageSpec {lvalue}, std::string, int) attribute(OpenImageIO_v1_8::ImageSpec {lvalue}, std::string, float) On Sat, Dec 2, 2017 at 7:51 PM, Daniel Flehner Heen <flehnerhee...@gmail.com > wrote: > Thank you so much! I'll try it and report back! > > On Dec 2, 2

Re: [Oiio-dev] Python add timecode to EXR

ld add the timecode to the imagespec. You then have to write a > file with it, of course. > > > On Dec 2, 2017, at 10:40 AM, Daniel Flehner Heen <flehnerhee...@gmail.com> > wrote: > > OK, so could I pass a list or tuple with the timecode (BCD) in index 0 and > something else in

[Oiio-dev] Python add timecode to EXR

Hi! Apologize if this is the wrong mail list for this, but is there a way to add a timecode to EXR's in python? I read a thread once discussing a way of adding timecode to all supported formats, but I'm not sure how it ended. I've tried specmod().attribute("smpte:timecode", ) without success