PyQT for nuke - 64bit

Hi, here is a post about compiling pyqt 4 for python 2.5 - 64bit, that is required for current version of nuke (6.1). The next version, 6.2 will come with  python 2.6, but until then if you want to use pyqt with 64bit nuke, you have to compile from source, or download from this place as I did. Thanks to Ozgur!

Nuke-RV integration!

Whoaa, the sneak peek video was out yesterday, and the tools are now downloadable (for free of course)! The developers of RV are really great guys, thank you!
Now you can preview readnodes directly in rv, render to rv, set up checkpoints of your work, create multiple version quickly to review with the sup etc. Check the video here.
Now I really need a second monitor for work :)

New commercial!

Our latest finished work at Digitalapes, the Vilmos commercial is on air now, so you can check it out here.
There is a makingof video too. Hope you like it.

Extending camera projected image in nuke - quick tip

Imagine this situation: you have a tracked scene, got the camera, using it (on 1 frame) for projecting a mattepaint to a proxy geometry. Then you go on compositing, huge node-tree builds on this  projection. And then suddenly you notice (or worse, the sup notices) that on a few frames the matte not covering enough area, needs to be extended. Everything else should remain as is, but you have to paint a good 50pixels more, outside the current mattepaint's format. The problem is: if you scale/translate the matte and paint the needed area, the current projection will crawl away. If you paint using the current format, but outside the image, making the bounding box larger, that will be cropped off by projection, as it is ignoring the bounding box.
The solution is simple: use a reformat before projection, using scale parameter, and link that value to the focal length of the projector camera, using the expression (assuming the original focal length of projection camera was say 25mm):
1/Reformat1.scale*25
Reformat1 is the name of the reformat node before the projection. So when changing the scale value of that node, the proj. camera will change it's fov accordingly. Scale to 1.2, and everything will stay as it was, but extended part will appear, or at least will be in the bounding box. Important: the reformat's resize type knob should be none!
This way the new painted area can be revealed easily. If the camera still cropping the image, try to adjust the overscan parameter in the scanline renderer, as this can crop the image too.
I'm going to make a few images later to illustrate this process.

First timelapse

My first timelapse video, I'm really into this kind of photography, so be prepared, more to come...

Cloudy timelapse from Gabor Toth on Vimeo.

Xmarks to shutdown...

Oh, no! Xmarks (best bookmark, tab sync extension for firefox, chrome) announced to shutdown in a few weeks, unless enough people willing to pay a small amount (10$, annually) for this great app.

The whole story is here.

You can make pledge to offer money here.

And here are the alternatives to xmarks (not as good as far as I know).

I think I'm gonne pay for this great service, that served millions of people for 4 years, without charging them. I need this.

Preseter for nuke 1.0beta1

Hi,

here is s quick solution for having a few different variations of node setups in nuke, without saving different versions. So on a review session with the director sup etc., you don't need to always open/save scripts for considering different versions of color grading etc. You select the nodes need to change, press getNodes button. Then you can store all the knob values for these nodes, maximum in 4 different versions, when pressing set1-4, and these can be restored - what a surprise - with the restore1-4 buttons. Note that this version currently stores these in memory, so these aren't saved with the script. Next version will do that :) And because of this you may not want to have more than 1 preseter node in the script, they can be confused... :)
You can donwload it here

As usual, comments, feedback are welcome!
Gabor