Monday, August 3, 2015

What I have been up to...

Finished work for feature film "Supilinna Salaselts". My tasks were different paint fixes and compositing.

Museum of Science and Technology in Stockholm will open a new exhibition in September 2015. I was involved with the multimedia part.

Made the upgrade to Nuke Studio!

Dug up my GIS related software project with new ideas. Successfully compiled PythonQt today, so I can use python scripting in my little program. I feel that scripting is essential part of making the tool flexible and powerful. Now the last piece of the puzzle has been found...

Tuesday, March 3, 2015

Long time no see

I have been quite busy during the last months, and have gathered quite some things to write about:
  • my work on feature film "1944" directed by Elmo NĂ¼ganen. See the trailer:

  • new NAS (Synology rackmount RS3614xs) and server cabinet standing in the corner
  • Amazon EC2 based rendering with James Yonan'is Brenda scripts
  • Blender animation baking and localisation of files for rendering (scripts in development)
I'll try to take some time to write about these topics in near future. Until then enjoy your bottom-hours (or buy a decent chair)!

Wednesday, September 24, 2014

Nuke 9 is pretty impressive!

I'm doing some projection based cleanup work and crunching through 4K exr plates is pretty slow with Nuke 8. Opened the same comp in Nuke 9 beta and voila, whole thing just flies! Not sure if it is the multi-threaded exr reading or improvements to scanlinerender but speed difference is definitely multiple times. Great work Foundry team!

Tuesday, September 16, 2014

Nuke - smart cloning with time offset

Just a little snippet I'm using right now. If you need to clone from a certain area in plate but don't want to stabilize it and use a tracker as clone transform base instead, changing time offset of clone source shifts the area you are cloning from. To keep the same relative clone source area while changing time offset, use this expression in clone shape or stroke source transform:


It allows easy changes in time offset and still clones from the same relative location.

Wednesday, July 23, 2014

Nuke get(channels=0xf) but request(channels=0x7) error

I'm doing some paint fix work and Nuke is getting pretty annoying with its get(channels=0xf) but request(channels=0x7) error. It randomly throws it on different nodes and while in viewer everything renders correctly, Write nodes crash with an error.

At first I searched the forums and Nuke release notes but found nothing very useful except the discussion about motion vector channels in The Foundry Nuke user forum. First suggestion was to copy all nodes to clean project, but this didn't help me. Another suggestion was to remove motion vectors related stuff so I turned m-vectors off on all ScanlineRender nodes. It didn't solve the problem, so I started testing different things. After some fumbling I removed all other channels except RGBA from all pipes that come from renderers and it seems that this removed the error, at least for now!

So if you get these cryptic get(channels= ....) errors, try removing all channels that are not used, especially the motionvector channels, this might fix the problem.

A little teaser also:

Monday, July 21, 2014

SanDisk Extreme PRO 240GB SSD

Bought new SSD drive to act as a cache & in-production project files drive. First impressions are that performance is pretty solid with both read and write speeds noticeably higher than 500 MB/s with all file sizes. Let's see how it performs as a cache disk for Nuke and AE.

Thursday, July 17, 2014

12 bit TIFF files in Nuke

Opened up a sequence one day and it looked very strange with false colors and some width lost. Found out that Nuke does not support 12-bit TIFF files:

At first I thought there was an issue with color encoding and tried some different stuff but as image was thinner it occurred that there was something else going on. Metadata viewer told that image has 12 bits per channel, but Nuke's tiffReader thinks it is 16-bit tiff and reads accross channel borders in byte array. This is why 1/4 of width was lost. Images originate from DVS Clipster DI soft, so they are not so rare probably.

I searched the internet for solution and made a support query to Foundry. Comes out that 12-bit tiffs are not supported yet, but the good part is that they turned it into feature request so we may see it implemented in future releases.

My workaround was to convert the sequences in AfterEffects, but as I used the "jump to Nuke" discount program with my AE serial code it is somewhat ironic.