[Sidefx-houdini-list] Soho IFD Hooks
sandy.maillists at gmail.com
Fri Sep 30 05:19:45 EDT 2016
Yep in my investigations I also found that VEX code was generating paths
that we were not catching, so have looked at having deadline run a post
task script to fix the IFDs. I found that if you read the IFD like so =
with open(<ifdpath>, 'rb') as f: then python can handle the embedded
binary, then if you write out with 'wb' seems to work fine, and even with
the binary in the file, the paths appear to be ascii sections!
Thanks for all the help -
On Fri, Sep 30, 2016 at 5:58 AM, jon parker <parker.jon at gmail.com> wrote:
> There are a lot of places where file paths can be set and I'm not sure
> you can catch them all purely through Soho, because VEX code can also
> have file paths embedded as string variables.
> If you can, I think the most comprehensive way to change paths is to
> save your IFD as an ASCII file and run a shell/python script on it to
> find any bad paths and then pipe the result into mantra.
> On Thu, Sep 29, 2016 at 1:49 AM, Sandy Sutherland
> <sandy.maillists at gmail.com> wrote:
> > Hi All,
> > Quick flyer here - we are attempting to migrate our farm to LX from
> > Windows, and have found that there are a whole bunch of assets lurking
> > that are being used daily that have some way of generating or HAVE hard
> > coded windows paths in them.
> > We are using HOUDINI_PATHMAP and this does work to a point.
> > Does anyone here know how to maybe use the Soho callbacks to maybe check
> > and fix paths into the IFDs?
> > Thanks
> > Sandy
> > _______________________________________________
> > Sidefx-houdini-list mailing list
> > Sidefx-houdini-list at sidefx.com
> > https://lists.sidefx.com:443/mailman/listinfo/sidefx-houdini-list
> Sidefx-houdini-list mailing list
> Sidefx-houdini-list at sidefx.com
More information about the Sidefx-houdini-list