This fix will be in v2.2.13.0, which is scheduled for release on Thursday. But I don't know how long it will be before vcpkg or any other package managers switch their default builds to the new version. Some do it within days, some wait weeks or maybe even until someone specifically requests it.
It would be great if some member of the OIIO community -- who works on Windows and uses and understands vcpkg deeply -- took on the task of keeping it up to date with our releases and making sure its option choices make sense (like, I think by default that it ought to build the command line tools and the python bindings, with most things opt-out rather than opt-in). So this patch merely skips to the next frame iteration when there is an error, producing no output for that frame (rather than exit immediately and not even try the remaining frames). I do like the idea of adding options for producing output when errors are encountered, though I think we need a concrete, detailed proposal for how it should behave. Consider that a set of commands (for a particular frame number) might involve reading multiple inputs, combining or modifying them in some way, then writing output. Is the substitution (of a checkerboard, black frame, or error card or something) at the level of each individual command? Like, does an individual nonexistent file get substituted with the error image, then things continue with that alternative input? Or is it that if any error occurs at any step, the -o outputs the error card image and not any piece of inputs that did exist? Or something else? If the error is reading a file, say it doesn't exist -- so you don't know what resolution it would have been or what channels it would have had -- how do you know how big the error card or output ought to be? > On Mar 30, 2021, at 9:25 AM, Gabor L. Toth <[email protected]> wrote: > > Hi, > > really thanks for the update! > A dev colleague built oiiotool with vcpkg, but the version number is > 2.2.10.0. I assume this is an older version, and doesn't have this commit? > Can we specify vcpkg to use the current master branch? Or do we need cmake > for that? > Another question: is there a chance to implement other options for missing > frames? (Black frame or checkerboard etc.) Also an option for skipping or > making the bad (incomplete) frames black (that are currently throwing error) > and finishing the task would be useful. For example sometimes a renderjob > marked as finished, thus the oiiotool is running, comping the rendered > layers, but 1-2 rendermachines still writing out frames for many aovs, so 1-2 > frame is incomplete. Or occasionally just simply having bad rendered frames. > :) > > Thanks, > Gabor > > > > On Sun, Mar 21, 2021 at 9:11 PM <[email protected] > <mailto:[email protected]>> wrote: > Send Oiio-dev mailing list submissions to > [email protected] <mailto:[email protected]> > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org > <http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org> > or, via email, send a message with subject or body 'help' to > [email protected] > <mailto:[email protected]> > > You can reach the person managing the list at > [email protected] > <mailto:[email protected]> > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Oiio-dev digest..." > > > Today's Topics: > > 1. Re: oiiotool: skipping bad frames (Larry Gritz) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sun, 21 Mar 2021 00:28:09 -0700 > From: Larry Gritz <[email protected] <mailto:[email protected]>> > To: OpenImageIO dev list <[email protected] > <mailto:[email protected]>> > Subject: Re: [Oiio-dev] oiiotool: skipping bad frames > Message-ID: <[email protected] > <mailto:[email protected]>> > Content-Type: text/plain; charset="us-ascii" > > I'm afraid I let that slip through the cracks, sorry. > > But I did think it was a good idea, so to make sure I had good news for you > after all, I implemented it tonight. > Here is the proposed fix: https://github.com/OpenImageIO/oiio/pull/2905 > <https://github.com/OpenImageIO/oiio/pull/2905> > > -- lg > > > > On Mar 20, 2021, at 12:26 PM, Gabor L. Toth <[email protected] > > <mailto:[email protected]>> wrote: > > > > Hi, > > > > any news on this feature? It would be very useful for any operation with > > image sequences, with occasionally missing frames, or having some bad > > frames. ;) > > > > Thanks, > > Gabor > > > > > > On Fri, Feb 5, 2021 at 10:12 PM <[email protected] > > <mailto:[email protected]> > > <mailto:[email protected] > > <mailto:[email protected]>>> wrote: > > > > Today's Topics: > > > > 1. Re: oiiotool: skipping bad frames (Larry Gritz) > > > > > > ---------------------------------------------------------------------- > > > > Message: 1 > > Date: Thu, 4 Feb 2021 23:33:07 -0800 > > From: Larry Gritz <[email protected] <mailto:[email protected]> > > <mailto:[email protected] <mailto:[email protected]>>> > > To: OpenImageIO dev list <[email protected] > > <mailto:[email protected]> > > <mailto:[email protected] > > <mailto:[email protected]>>> > > Subject: Re: [Oiio-dev] oiiotool: skipping bad frames > > Message-ID: <[email protected] > > <mailto:[email protected]> > > <mailto:[email protected] > > <mailto:[email protected]>>> > > Content-Type: text/plain; charset="us-ascii" > > > > Yeah, that does seem like a good idea. Let me see if I can cook something > > up for this over the weekend. > > > > -- lg > > > > > > > On Feb 4, 2021, at 3:01 AM, Gabor L. Toth <[email protected] > > > <mailto:[email protected]> <mailto:[email protected] > > > <mailto:[email protected]>>> wrote: > > > > > > Hi, > > > > > > I had this question a while ago, is there any update on this, or plans to > > > do it? The problem is oiiotool stops when a frame is missing from an > > > image sequence, or encounters a bad frame (like unfinished/corrupted > > > render from 3d). It should continue the operation, and replace the > > > missing/bad frame with either a black frame, a checkerboard or the > > > nearest frame (would be great to have the option to choose from these, > > > the default should be I think the black frame). And of course the error > > > throw should be another option. > > > > > > Thanks, > > > Gabor > > > > > > > > > > > > > > > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail > > > > > > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> > > > > > > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail > > > > > > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>>> > > > Virus-free. www.avast.com <http://www.avast.com/> > > > <http://www.avast.com/ <http://www.avast.com/>> > > > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail > > > > > > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> > > > > > > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail > > > > > > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>>> > > > > > > <x-msg://42/#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>_______________________________________________ > > > Oiio-dev mailing list > > > [email protected] <mailto:[email protected]> > > > <mailto:[email protected] > > > <mailto:[email protected]>> > > > http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org > > > <http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org> > > > <http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org > > > <http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org>> > > > > -- > > Larry Gritz > > [email protected] <mailto:[email protected]> > > <mailto:[email protected] <mailto:[email protected]>> > > > > > > > > > > -------------- next part -------------- > > An HTML attachment was scrubbed... > > URL: > > <http://lists.openimageio.org/pipermail/oiio-dev-openimageio.org/attachments/20210204/e73b8502/attachment-0001.html > > > > <http://lists.openimageio.org/pipermail/oiio-dev-openimageio.org/attachments/20210204/e73b8502/attachment-0001.html> > > > > <http://lists.openimageio.org/pipermail/oiio-dev-openimageio.org/attachments/20210204/e73b8502/attachment-0001.html > > > > <http://lists.openimageio.org/pipermail/oiio-dev-openimageio.org/attachments/20210204/e73b8502/attachment-0001.html>>> > > > > ------------------------------ > > > > Subject: Digest Footer > > > > _______________________________________________ > > Oiio-dev mailing list > > [email protected] <mailto:[email protected]> > > <mailto:[email protected] > > <mailto:[email protected]>> > > http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org > > <http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org> > > <http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org > > <http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org>> > > > > > > ------------------------------ > > > > End of Oiio-dev Digest, Vol 149, Issue 3 > > **************************************** > > > > > > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail > > > > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>> > > Virus-free. www.avast.com <http://www.avast.com/> > > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail > > > > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>> > > > > <x-msg://11/#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>_______________________________________________ > > Oiio-dev mailing list > > [email protected] <mailto:[email protected]> > > http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org > > <http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org> > > -- > Larry Gritz > [email protected] <mailto:[email protected]> > > > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > <http://lists.openimageio.org/pipermail/oiio-dev-openimageio.org/attachments/20210321/08c6539d/attachment-0001.html > > <http://lists.openimageio.org/pipermail/oiio-dev-openimageio.org/attachments/20210321/08c6539d/attachment-0001.html>> > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > Oiio-dev mailing list > [email protected] <mailto:[email protected]> > http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org > <http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org> > > > ------------------------------ > > End of Oiio-dev Digest, Vol 150, Issue 5 > **************************************** > > > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> > Virus-free. www.avast.com > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> > > <x-msg://4/#m_-319314960620912437_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>_______________________________________________ > Oiio-dev mailing list > [email protected] > http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org -- Larry Gritz [email protected]
_______________________________________________ Oiio-dev mailing list [email protected] http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
