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 <apra...@brunchstudio.tv>
> Hi all,
> New around here, even thou I worked with oiio occasionally over the last
> years, but I'am kinda stuck.
> Someone asked almost the same question a while ago (
> openimageio.org/2016-December/000832.html ) and the bottom line was
>> You can't "get an ImageBuf from an ImageInput", but you shouldn't need to
> So it means I am probably doing something wrong:
> I am generating jpeg previews from hundreds of textures (exr, tx ...) and
> this is painfully slow (the process is bound by network, as reading a 200mb
> texture from the server is 10 times slower than doing the resizing.
> Since most of these textures have already been mipmapped, I would like to
> only load the 512*512 mipmap level and write it back. But from what I
> understood only ImageInput allows you choose what to load.
> If I read all pixels from the ImageInput then "manually" create an
> ImageBuf from it (requiring an extra numpy convert of the data) it works
> but feel a bit convoluted.
> Is there a better way to do this ?
> Alexis Prayez
> 41 rue de l'Echiquier - 75010 PARIS
> STATEMENT OF CONFIDENTIALITY
> The information contained in this electronic message and any attachments
> to this message are intended for the exclusive use of the addressee(s) and
> may contain confidential or privileged information.
> If you are not the intended recipient, you are hereby notified that any
> dissemination, distribution or copying of this e-mail and any attachment(s)
> is strictly prohibited. Please reply to the sender and destroy all copies
> of this message and any attachments from your system.
> Please consider the environment before printing this e-mail.
> Oiio-dev mailing list
Oiio-dev mailing list