I’m reasonably sure it’s a Mavericks issue. If we never opened the script on the Mavericks workstation, it opened, saved and closed perfectly. Upon opening and saving on the Mavericks workstation, the script was toast.
That said, I built a _lot_ of scripts for this project under Mavericks, and experienced no problems whatsoever. I ripped apart the node trees to track down the problem, and it ended up being the rotospline nodes that came out of Mocha. I don’t know if this is a Mocha import issue, or maybe its an issue with high-keyframe rotospline nodes. The node that was causing the trouble had 230+ keyframes. On Nov 27, 2013, at 11:17 PM, Howard Jones <[email protected]> wrote: > Sounds like a failed save, had this with network issues on large scripts > before (rarely). The maverick compression is worrying though > > Howard > > On 28 Nov 2013, at 04:46, Craig Tozzi <[email protected]> wrote: > >> Maybe a text encoding thing? >> >> We searched the script in a text editor. It wasn’t a difference of one or >> two close braces missing - it was hundreds, maybe thousands. >> >> >> On Nov 27, 2013, at 12:13 PM, visfxsup <[email protected]> wrote: >> >>> Maverick s compresses ram on the fly. Maybe it doesn't do it very well. >>> >>> >>> Sent from my T-Mobile 4G LTE Device >>> >>> >>> >>> -------- Original message -------- >>> From: Nathan Rusch <[email protected]> >>> Date: 11/27/2013 3:04 PM (GMT-05:00) >>> To: Nuke user discussion <[email protected]> >>> Subject: Re: [Nuke-users] Mocha rotospline imports corrupt scripts on >>> Mavericks >>> >>> >>> Bad cloned nodes saved in a script will result in an error like "Nothing is >>> named $C423F412", and are easy to recover from. "Missing close brace" is a >>> different issue, and one that, in my experience, seems to occur most >>> frequently with node types that serialize to large strings (Roto/RotoPaint, >>> Tracker4, SplineWarp/GridWarp, etc). >>> >>> Pure speculation, but if it’s not a general Roto/RotoPaint bug (which I >>> would guess first and foremost), perhaps Mavericks includes some low-level >>> changes to the way files are buffered or written that is causing it to >>> forget to finish writing the script. >>> >>> -Nathan >>> >>> >>> From: Randy Little >>> Sent: Wednesday, November 27, 2013 9:42 AM >>> To: Nuke user discussion >>> Subject: Re: [Nuke-users] Mocha rotospline imports corrupt scripts on >>> Mavericks >>> >>> cloned nodes. You can work with cloned nodes for quit a while with no >>> problems. But sooner or later the likely hood of the CLONE WILL WIPE OUT >>> YOUR COMP bug will arise. >>> >>> >>> Randy S. Little >>> http://www.rslittle.com/ >>> http://www.imdb.com/name/nm2325729/ >>> >>> >>> >>> >>> On Wed, Nov 27, 2013 at 12:39 PM, Craig Tozzi <[email protected]> wrote: >>> Wait - are you referring to clone brushes or cloned nodes? We have the >>> former but not the latter. >>> >>> I was the artist on the Mavericks workstation and used clones a fair amount >>> through the project, without problems... >>> >>> >>> >>> On Nov 27, 2013, at 8:54 AM, Richard Bobo <[email protected]> wrote: >>> >>>> I have gotten into the habit of making sure to, first, De-Clone any nodes >>>> that I am copying and pasting from one script into another. Otherwise, >>>> it’s a sure way to screw things up.. >>>> >>>> Rich >>>> >>>> >>>> On Nov 27, 2013, at 11:38 AM, RsLittle <[email protected]> wrote: >>>> >>>>> Its the clones. Ones that did corrupt WILL at the worst possible time. >>>>> Clones are russian roulette. >>>>> >>>>> >>>>> From my Android phone on T-Mobile. The first nationwide 4G network. >>>>> >>>>> >>>>> >>>>> -------- Original message -------- >>>>> From: Craig Tozzi <[email protected]> >>>>> Date: 11/27/2013 11:28 AM (GMT-05:00) >>>>> To: Nuke user discussion <[email protected]> >>>>> Subject: Re: [Nuke-users] Mocha rotospline imports corrupt scripts on >>>>> Mavericks >>>>> >>>>> >>>>> He did, but there were other rotopaint nodes in the scripts from this >>>>> project that didn’t come from Mocha (also using clones) that didn’t cause >>>>> any problems. >>>>> >>>>> >>>>> >>>>> >>>>> On Nov 27, 2013, at 8:22 AM, Randy Little <[email protected]> wrote: >>>>> >>>>>> are you sure thats not the "CLONE Bug" Sure sounds like it. did the >>>>>> artist on Mavericks CLONE something. (anything) >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> On Wed, Nov 27, 2013 at 11:17 AM, Craig Tozzi <[email protected]> >>>>>> wrote: >>>>>> Discovered a weird bug on this project we’re wrapping up: >>>>>> >>>>>> An artist using a Mac workstation running Snow Leopard had used Mocha >>>>>> Pro and imported a rotospline into Nuke (7.09). He continued to work on >>>>>> the shot with no issues. >>>>>> >>>>>> That Nuke script was later loaded onto another workstation that was >>>>>> running Mavericks and Nuke 7.09. The shot was worked on further for >>>>>> about a half a day, with multiple versions being saved. >>>>>> >>>>>> The problem: once the script was closed, it was found corrupt upon >>>>>> reopening, with <missing close brace> and EOF errors. This ONLY >>>>>> occurred if the script was opened and saved under Mavericks. Earlier >>>>>> versions of the script that had only been used under Snow Leopard would >>>>>> open and close without problem. >>>>>> >>>>>> It’s an ugly thing to find out, as you can go for a time before >>>>>> discovering that your script has blown up. >>>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Nuke-users mailing list >>>>> [email protected], http://forums.thefoundry.co.uk/ >>>>> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users >>>> >>>> >>>> >>>> >>>> Rich Bobo >>>> Senior VFX Compositor >>>> Armstrong-White >>>> http://armstrong-white.com/ >>>> >>>> Email: [email protected] >>>> Mobile: (248) 840-2665 >>>> Web: http://richbobo.com/ >>>> >>>> "The greatest achievement of the human spirit is to live up to one's >>>> opportunities, and to make the most of one's resources." >>>> - Vauvenargues >>>> >>>> _______________________________________________ >>>> 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 >>> >>> >>> _______________________________________________ >>> 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 >> >> _______________________________________________ >> 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
_______________________________________________ Nuke-users mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
