OK, so this is super weird. We generally don’t publish directly from nuke. Usually the team will stick the output in RV and publish from there. I’m looking at the publisher now, as I essentially want to hack out some bits of it to make my own publishing and tagging system for a bunch of green screen stuff we’ll be ingesting soon - however I thought I’d just look at the normal publisher first, and I’m getting some crazy issues.
If you use the Shotgun Write Node to render some of your comp and then use the Publisher to publish the image sequecne (with out without the nk file being published too), it breaks, as it says it can’t publish empty files - and lo and behold, all the renders from the just rendered sequence are suddenly 0kb. That’s with our write ode having written Jpegs. If I have the write node doing EXRs instead, the publish doens;t fail, but it still turns the previously fine exr files to all be 0kb. I have absolutely no idea why this would be happening.
Has anyone else encountered this behaviour before?
I’m going to look through the actual publishing code and just strip out the code to publish the image sequence to use in my tool, but I fear that even when I’ve done that, this might still ocur as something in the Shotgrid publish process is causing this. I’m usng the latets version of tk-nuke ad writenode (and everything else).
Any help greatly appreciated!