I was under the assumption that the GS file needed to stay local to the system nuke/framecycler resided on. If this isn't the case then the docs weren't clear on putting this file in a network configured location.
Care to share your flipbook code? :-) Thanks, Dan On Oct 7, 2011 12:44 PM, "Lewis Saunders" <[email protected]> wrote: > Nathan Rusch wrote: >> Well, to be fair, FrameCycler is probably the black sheep in this conversation > > Always so much love for FrameCycler on this list :-] > > You can set it to use a central settings file or LUT folder (see > http://doc.iridas.com/index.php/Category:Customize), it's just the > GlobalSettings.xml that ships with Nuke that has it set to the local > temp folder. > > For what it's worth I've handled all this stuff on the Nuke end, by > implementing a custom flipbook module which modifies the FrameCycler > settings file appropriately each time you flipbook something. Took 30 > lines of Python or so. > > Figuring out how to split my LUTs into 1D linear-to-log and 3D > log-to-display pieces to work around FrameCycler's lack of a combined > LUT format was, however, a pain in the ass. Houdini's MPlay is much > easier to deal with for that and I'd imagine RV is too. > > -- > Lewis Saunders > Comp TD and serial XML abuser > London > _______________________________________________ > Nuke-users mailing list > [email protected], http://forums.thefoundry.co.uk/ > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
_______________________________________________ Nuke-users mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
