Firefox crashes

Hi, just a quick note. I'm using firefox 3.5.9, on xp sp2, 32bit. I encountered occasional crashes, that was really annoying. So I tracked down which extension could do this. So first type of crashes was on google searches, this was caused by xmarks, especially the siteinfo feature. If this was turned off, it didn't crash. Second type of crash was with particular sites, like linkedin.com, this was caused by AVG safe search. I hope this helps for someone.

Loop with offset in nuke

Hi, I just needed to do a loop with offset, on an animation curve. That means that the cycle is continuously increasing or decreasing, depending the value of the first and last key of the loop. In maya, it is called cycle with offset. Unfortunately in nuke there is no option to do that from the menu. I solved this with a custom expression. For this I used 2 custom integer knobs on the node, called "LoopStart", "LoopEnd" (case sensitive!), marking the start and end key of the cycle. Later I will make an option built in the menu, but until that, here is the expression:

curve((((frame-LoopStart)%(LoopEnd-LoopStart))+LoopStart) ) + (floor(((frame-LoopStart)/(LoopEnd-LoopStart))) * (curve(LoopEnd)-(curve(LoopStart))))

How to apply that:
make animation you want to loop. With right click on the node/manage user knobs, make 2 integer knobs called LoopStart and LoopEnd. Set these to the frame of the first and last key of the loop. And then add this expression to the animated knob and that's it.
I made an additional option, because I needed to offset these animations in time many times, so making an extra knob called "TimeOffset", the expressions look like this:
curve((((frame-LoopStart- TimeOffset)%(LoopEnd-LoopStart))+LoopStart) ) + (floor(((frame-LoopStart-TimeOffset)/(LoopEnd-LoopStart))) * (curve(LoopEnd)-(curve(LoopStart))))

This is useful when the readnode is timeoffseted (with a separate node), so link the TimeOffset KNOB, to the timoffset NODE, so you have to adjust it only in 1 place.
With this, I did a lot of medusas floating upwards, each animating differently, but from only one readnode, many timeoffset nodes, and transformgeo nodes.
Hope this will be useful for somebody :)

reloadrange

Ok, long time no post, so here it is: I haven't posted this python script, that is already on creativecrash: glt_reloadrange. Basicly it checks the frame range of the selected readnode, and if it is different that was set in the node, updates it. It useful for example when you start using a 3d rendered sequence, before it is fully rendered. After the 3d render has finished, just select that readnode, and use this script.
Available here:

about me and nuke

In a nutshell a bit about me, and the tools I use. I work for Digitalapes, a vfx company in Hungary, as a 2d TD/compositor. As you may have guessed, we use Nuke for compositing. We were using Fusion back in 2005, and later Shake (in Cubeeffects Inc.) In my opinion, generally Nuke is far superior than these other two (but to be honest, each has its strength). After using Fusion, I found Shake very stable, and in the same time very basic. This is an advantage to learn and understand compositing, but i was also missing a lot of tools. Now Nuke has the speed, is multi-platformed, and well-designed from its basics, and has almost all the tools we need. Only thing that I miss, is Shake's previews and warps, and Fusion's particle system.

Lee Stranahan: Open Letter To James Cameron: Fairness For Visual Effects Artists

Lee Stranahan: Open Letter To James Cameron: Fairness For Visual Effects Artists

Heathaze gizmo

I always wanted to have a decent heathaze plugin for nuke. My problem with heathaze plugins in other composite softwares was they look so uniformly distort the image. For this reason I have put together one, that is not so uniform. So I'm releasing here my heathaze gizmo for nuke, you can download it from creativecrash.
Note that this gizmo is not a usual heathaze, as it doesn't distort the image, it just creates a red-green noisy image, that can be used with an idistort node as distortion channels. More explanation can be found in the tooltip of the node.

Welcome...

Hi All! So, I started this blog, because... I had a lot in my mind, that I would like to share - and I hope it's worth to share - with you. The posts will regard mainly my profession, that is vfx - mostly tips/tricks with softwares I use (Nuke, Maya etc.), scripts I've written. I hope it will be useful for some of you, and if it is, drop me an email or comment it.
One more thing: because I'm not a very advanced programmer, I take no responsibility if you use scripts/code/tips I've written, use on your own risk. But of course I'll upload such things only if I tested those through.
Best:
Gabor L. Toth