..and its ill-named doppelgänger 'tshkx.exe' too. They're popping up, stealing cycles like mad, from some mis-behaving macros. Killing it off doesn't seem to have a negative effect on those renders so what on earth is it for? This is running on a very modern linux distro if it matters.
warm regards,
/p
ps: viva nuke
Add comment viewed 142 times Latest activity 11 months ago
Hugh Macdonald
[ Editor ]
tshake is the process that runs to generate thumbnails. It can often be found running in the background.
if you look at 'tshake', you'll see that it's actually just a wrapper script for 'tshkx.exe' (Why Nothing Real decided to keep their binaries with .exe on the end, I don't know)
Similarily, 'shake' is a wrapper for 'shkx.exe'. There's also 'shkv.exe' which is Shake's flipbook viewer.
To launch Shake in old-style Tremor mode, you launch it with:
shake -gui 1
PS Long live Nuke!
OK, I’m going to have to admit to knowing as little about Shake as I ask this, but: Shake makes thumbnails? Which thumbnails for for what? It sounds like I might be motivated to actually fixing this problem instead of symlinking tshake* to /usr/bin/true. :D
/p
If you watch someone working in Shake, you’ll see that they have thumbnails above the FileIn nodes (amongst others – you can customise which nodes have thumbnails, and turn them on and off whist working in Shake). If there’s a retime, it may be referencing 20-odd frames to generate that image – it will also be doing the same thing for the thumbnail.
Disabling tshake like that will probably severely piss off your compers. :D
piotr_44
ahh ….. right-o. Now why on earth is that caning my i/o. Hmm. A stack trace ought to be revealing. Thanks Piotr!
Paddy Eason
Er - nothing to do with "tremor" the short lived and unloved (except by Pete Connelly) Shake GUI variant is it? Tremor was Shake kind of pretending to be a Flame (and failing).
(Hugh - this is where you pop up and tell everyone the correct answer...)