AWS Thinkbox Discussion Forums

Nuke plugin STDout

Deprecated Deadline 6 Beta Discussion
#1

Hi,
I think something a little funky happens in one of the STDout handlers in the Nuke plugin, but it only occurs sometimes, ie: whenever this “.9” decides to be displayed from Nuke.

0: STDOUT: Writing C:/nuke_renders/teapot_0001.png .9 0: STDOUT: Writing C:/nuke_renders/teapot_0001.png took 0.49 seconds 0: STDOUT: Frame 1 (1 of 1) 0: STDOUT: Total render time: 0.49 seconds 0: STDOUT: Allocated 3.55MiB, 0% of usage limit of 1GiB.

0: STDOUT: Writing C:/nuke_renders/teapot_0002.png 0: STDOUT: Writing C:/nuke_renders/teapot_0002.png took 0.11 seconds 0: STDOUT: Frame 2 (1 of 1) 0: STDOUT: Total render time: 0.11 seconds 0: STDOUT: .9Allocated 3.55MiB, 0% of usage limit of 1GiB.

Note the “.9” text shift, which is always happening around the same time as the STDout handler which grabs the “Frame # (# of #)”. But the handler looks ok? Strange!

If I manually execute my Nuke script render via the command line, I’m unable to get this magical “.9” text to appear?!

And here’s the full job reports to put it into more context:
Reports_Job.zip (2.6 KB)

Mike

#2

Yeah, we’re really not sure why this happens. It doesn’t seem to affect anything, so we’ve never bothered to look into it. :slight_smile:

#3

I believe it should actually be putting .1.2.3.4…9 all the way out there. Its the per frame progress, shown for slower frames afaik.

This i think also affects error handling sometimes, because some error messages are missed the same way those numbers are.

I think nuke does not flush its stdout properly on windows,… would be nice if deadline could force it

#4

Unfortunately, that isn’t possible. All we can do is flush the standard out reader to immediately capture what Nuke has already written to stdout. We can’t force another application to flush it’s own buffer to stdout. So if Nuke isn’t flushing stdout properly on windows, that’s something the foundry would have to address.

#5

Well, im guessing that’s never gonna happen. I sent them msdn instructions on how to do that 3-4 years ago, and since then, no change.

#6

STDout works fine on OSX but not on Windows.
I’ve logged a bug ticket with the Foundry. I’ll let you know if I make progress :slight_smile:

Privacy | Site terms | Cookie preferences