Ignore Bad Filein

[user_deleted]

I am using Shake from the commandline like so:

shake -exec myShakeScript.shk -node myFileOutNode -v

Shake gives error messages during rendering when there are filein nodes missing files, even if the fileout node I am explicitly rendering is not connected to the filein node with missing files. So Shake is reporting errors but there are no errors with the rendering. What can I do at the commandline so Shake ignores these missing files (I know I can set IgnoreNode from within the Shake GUI itself, but i need to do it from the command line. Also I don't want to specify each filein node to ignore...it would make more sense to specify which fileout node to render and ignore any fileins not connected to that.

[user_deleted]

i'm a pretty bad coder but i guess you could use a perl script or something to search through your script file and disable all but the specified selected node.

ask a script guru about this, i'm sure there are some very elegant solutions..
++ chris

[user_deleted]

i am a script guru
yeah i could write a script that will set fileIn nodes to ignore but the problem is to figure out which fileIn nodes to ignore. To work backwards from the fileOut node would require rebuilding the entire script tree structure to see if a fileIn is connected to a fileOut. Shake attempts to read in files from fileIn nodes that are unconnected to the fileOut node during rendering which is really really dumb behaviour...this is really bad programming logic. Is there no way around this?

[user_deleted]

actually to my knownledge shake will just warn you that there are missing fileins, but will render just nicely anyway.

did a short test script, deleted 2 unconnected files:

macpro:~ chris$ shake -v -exec /Users/chris/Desktop/test.shk
info: rendering frame 1
error: /Users/chris/Desktop/DSC00131.JPG: invalid header - couldn't open file
error: /Users/chris/Desktop/DSC00127.JPG: invalid header - couldn't open file
info: frame 1 rendered in 0.13s

the fileout gets rendered anyway and looks just like it should.
not sure if that's what you meant in your original post, but if you just want to ignore the error messages there might be a variable in the pref files.. but why bother?
++ chris

[user_deleted]

QUOTE(zem @ 05/21/07, 03:24 AM) [snapback]266387[/snapback]
actually to my knownledge shake will just warn you that there are missing fileins, but will render just nicely anyway.

did a short test script, deleted 2 unconnected files:

macpro:~ chris$ shake -v -exec /Users/chris/Desktop/test.shk
info: rendering frame 1
error: /Users/chris/Desktop/DSC00131.JPG: invalid header - couldn't open file
error: /Users/chris/Desktop/DSC00127.JPG: invalid header - couldn't open file
info: frame 1 rendered in 0.13s

the fileout gets rendered anyway and looks just like it should.
not sure if that's what you meant in your original post, but if you just want to ignore the error messages there might be a variable in the pref files.. but why bother?
++ chris

The reason is that if I'm rendering 100,000 frames, I want to reserve error messages for actual errors. On this scale it becomes a big waste of time to check the output to see which errors are real and which can be ignored.

[user_deleted]

ah, i somehow thought you were getting actual render errors..
so how about you write it to a log file and parse that with a perl expression to exclude filein errors?

as said i dont know about coding, but that should be a one liner (two absolute max! .
++ chris

[user_deleted]

QUOTE(zem @ 05/22/07, 04:51 PM) [snapback]266472[/snapback]
ah, i somehow thought you were getting actual render errors..
so how about you write it to a log file and parse that with a perl expression to exclude filein errors?

as said i dont know about coding, but that should be a one liner (two absolute max! .
++ chris

yeah no problem except there might be actual filein errors where fileins used in the comp are missing frames