katana, redshift, deadline


Hey eamsler,

Thanks for reply. I have attached here a scene file, job report and some chronological screen shots of what I did. hope it helps you. Thanks :slight_smile:

Job_2017-08-22_13-08-43_599b841b20540711ec35dbb6.txt (7.48 KB)

katana_testScene.rar (13.4 KB)



Hmm. Well, the job log isn’t very helpful as far as logging. It does spend about 10 minutes doing something as there’s a gap in the logs, but it’s not clear what that something is. I’ll ask the dev team what they think of it.

Relevant log info:

2017-08-22 12:58:20:  0: STDOUT: [INFO python.Main]: KATANA_RENDER_TILE_SIZE defaulting to 256x256
2017-08-22 12:58:20:  0: STDOUT: [INFO python.Main]: KATANA_IMAGE_MEMORY defaulting to 11726 MB
2017-08-22 12:58:20:  0: STDOUT: [INFO python.Main]: KATANA_IMAGE_DISK_MEMORY defaulting to 6948 MB
2017-08-22 12:58:20:  0: STDOUT: [INFO python.Main]: KATANA_SPEC_CACHE_ENABLED defaulting to 1
2017-08-22 12:58:24:  0: STDOUT: Using localhost
2017-08-22 12:58:25:  0: STDOUT: [WORKER] started
2017-08-22 13:08:42:  0: STDOUT: [INFO plugins.Redshift]: Closing the RS instance. End of the plugin log system.
2017-08-22 13:08:42:  0: STDOUT: [WORKER] shutdown
2017-08-22 13:08:43:  0: INFO: Process exit code: 0
2017-08-22 13:08:43:  0: Done executing plugin command of type 'Render Task'


Hmm. I’ve been informed that we don’t support Redshift with Katana as of yet, so I’ll add that to the dev system. I’m not quite sure what can be done if anything yet while you wait, but I’ll find out.


ah that’s good to know, thanks for chasing this up.

Cheers, Rou


No problem. Can you think of anything that might give us a leg up here? I’m kind of curious how Redshift is called within Katana under the hood. I guess as an end user that’s probably not something you’ve had to worry about up until now. :slight_smile:


Hey Folks,

By default the logging that is turned on for redshift is usually pretty minimal.
printing logs to the stdout slows down the render process :frowning:

Rou, can you try setting the Log Level to Verbose, see if that at least prints out some more details?


sorry for late reply, pretty busy these days,
Sure will do that asap.

Thanks guys


Ok, I have attached two logs here, one is deadline job report and the other one is redshift log itself when I rendered scene within katana, having log level set to debugVerbose
Job_2017-08-24_19-46-33_599e845920540721b8d58154.txt (7.41 KB)
katanaRenderLog_Render.0000.txt (12.3 KB)


So, from reading both logs everything seems to be normal. I’m assuming it’s just not saving somehow… How does Redshift know where to store its output? Is is something we’d have to control? It looks like we’re just running things via command line switches so I’m not sure what’s available for us to pass in (installing Katana now).


I don’t think its just not saving, because gpu is idle all the time. BTW it worth mentioning that I’m using a .bat file to run katana to set env variables.


Hey guys,
Just checking any news regarding this, is there any plan for katana-Redshift support


Just worth metioning, have you tried a simple scene running it through katana instead of launching katana from your .bat?

Also, you can add any env variables onto the job itself in the “environement” tab


Actually, the dev team requested a test scene which would be quite handy. Does anyone have some simple textured cube we could make use of?


Hi eamsler,
here is a simple scene for you guys. Please let me know if they want something specific for it.

Cheers, Rou
Desktop.rar (467 KB)


Thanks! Passed it along.


Any news on this?!


Not yet. What’s the urgency on your side? Features tend to take a backseat to fixes but we can discuss here if it’s becoming a problem on your side.


Thanks eamsler,
Nothing urgent about it at the moment, as we still working on pipeline,just wanted to check if it’s something still in your radar.
Cheers, Rou


Okay. I’ve suggested it as a possible project for an intern, but I’ll leave that in the hands of the dev team.