Proposed fix: https://github.com/OpenImageIO/oiio/pull/3372
> On Mar 24, 2022, at 12:40 PM, Larry Gritz <[email protected]> wrote: > > I see: > https://stackoverflow.com/questions/21194530/what-does-mean-when-prepended-to-a-file-path > > <https://stackoverflow.com/questions/21194530/what-does-mean-when-prepended-to-a-file-path> > > >> On Mar 24, 2022, at 11:57 AM, Larry Gritz <[email protected] >> <mailto:[email protected]>> wrote: >> >> What does the \\? mean? Is there a reference you can send me about the exact >> syntax f these filenames? >> >> >>> On Mar 24, 2022, at 12:21 AM, Larry Gritz <[email protected] >>> <mailto:[email protected]>> wrote: >>> >>> I think I know what's going on here. At some point, we started recognizing >>> some "REST" like filename structures as ways to communicate parameters to >>> procedural image generators, and so I bet the "?" is throwing it off. I >>> will investigate. >>> >>> >>>> On Mar 23, 2022, at 9:23 AM, haggi <[email protected] >>>> <mailto:[email protected]>> wrote: >>>> >>>> Hi, >>>> >>>> we just encountered a problem working with maktetx and windows unc paths. >>>> We use UNC path notation for accessing the files in our network like this: >>>> >>>> maketx.exe -o C:\TextureCache\test1.tx \\produktion\dfs\images\Raumplan.png >>>> >>>> This works great. But sometimes the pathnames are too long and our usual >>>> solution was to use a windows naming convention: >>>> >>>> maketx.exe -o C:\TextureCache\test1.tx >>>> \\?\UNC\produktion\dfs\very...long...path\Raumplan.png >>>> >>>> This can be tested locally with this lines: >>>> maketx.exe -o C:\TextureCache\test1.tx \\?\C:\image.png >>>> maketx.exe -o C:\TextureCache\test2.tx C:\image.png >>>> >>>> The error message we get is: >>>> ImageInput::create() called with malformed filename >>>> >>>> Now comes the interesting part: >>>> Since we use the maketx from Arnold renderer, I only have these two >>>> versions to compare but: >>>> >>>> This was not a problem in maketx from OIIO 1.7.7 >>>> >>>> It is a problem in the version of OIIO 2.1 (or earlier somtime between >>>> 1.7.7 and 2.1) >>>> >>>> Any ideas? >>>> >>>> haggi >>>> _______________________________________________ >>>> 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]> >>> >>> >>> >>> >>> _______________________________________________ >>> 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]> >> >> >> >> >> _______________________________________________ >> Oiio-dev mailing list >> [email protected] <mailto:[email protected]> >> http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org > > -- > Larry Gritz > [email protected] <mailto:[email protected]> > > > > > _______________________________________________ > 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
