Thought I'd post an update since it's been a while since my last blog post. Wow, this semester at school was incredibly intense, the most work I've done all year long. Over a dozen of sleepless nights on supertight deadlines including Without delivery, mid-terms, Game Developer's Convention, the AAU Spring Show, and finals. I really poured my heart, sweat, blood, and tears into every single project this semester, and I have an under-appreciated lonely girlfriend to prove it. Now that I've had a bit of time to relax, and recuperate from such a strenuous semester, I'm enjoying my time off by watching season 1 of Star Trek: Voyager. Maybe I'll make it to the end of season 7, but I do plan to be a bit busy this summer, especially with my previously mentioned under-appreciated girlfriend.

Right now I'm in the process of fighting with financial aid to get enough to go to summer school and live out here in San Francisco for a couple more months. Hopefully I can also figure out my situation for next Fall and Spring as well.

Also working on giving my website a totally new facelift, integrating it more with the style of this blog, as I've really fallen in love with it. It just feels very simple, clean, and web2.0-ish. Wish it could just be a simple copy and paste and bam my site is done, but I'm having to go in deep and meticulously write some seriously complex code. Definitely glad I chose VFX as my career path and not web development. I can deal with web development for now, but there's no way I could do this 24/7. CSS was a bit frustrating to get a hang of at first, but now I'm loving it. It sped up my workflow considerably, and now I have more control over every single element in my layout.

I'm planning to have my website coincide with the launch of The Avenger, and I'll have many various streaming and downloading options available. I'll talk with the other ninja team after everything is finished and see if they would like me to put their video up. Both videos excel in different ways and both are a blast to watch. It would be awesome if I could, so people can see two totally different approaches to the same assignment.

Well, back to coding....

I just recently finished working on The Nailspot website during my free time. The Nailspot is a premier nail salon and spa located near the greater Houston metropolitan area in Kingwood, TX, next to Kingwood High School. It's a great, newly-opened, nail salon with luxorius Luxan tubs and Lonestar Spa Chairs and a great ambiance. Definitely an experience you don't want to miss.




On a side note, the Ninja project is coming along smoothly. Now titled, "The Avenger", my team managed to pull something together for the Spring Show. The other team, who interestingly enough called their piece "Ninja Avenger", managed to get together a nice good solid piece for the show. Our team still has a ways to go, and we have 3-4 weeks left to get it together for the final. Colin Sebestyen from MoveCraft and Cobra Creative, was there with us till the last minute of the deadline, midnight on Sunday. He definitely helped bring my piece together, and with his help I feel we got a decent amount of work done for the Spring Show. Thanks Colin for taking the time to help us out into the wee hours of the morning Saturday and Sunday night, definitely appreciate it.

With the consent of my team, I will try to post up the final version of The Avenger in 3-4 weeks when completed. I'll also talk to the other team, and see if I can get their work up here too, with credit where credit is due of course.

The week right before Spring Break, Catherine came into our motion graphics class and informed us of a new category being put into the Spring Show, VFX Motion Graphics. Sweet, seeing as how our motion graphics class is the first and only class in the VFX department, whatever we turn in will more than likely be in the show. We have no competition. Problem is, we were only given two more weeks to work on something amazing to knock the socks off of people, with the impending deadline of April 19th. So eight of us got together and formed Team CRYPTALBAYSPLOSIONOMICRON (later split into two teams for different concepts). One of our team members, the talented Roger Apolinar, is currently VFX Supervisor at Paralux Productions. He was able to get a hold of the RED cam for a night and managed to recruit some martial arts talent to shoot in the greenscreen studio. With martial artists Isiah Flores and Michael Gonzales showing off some sick moves in the studio, we managed to get some amazing, beautiful RED footage.

Speaking of which, if there are any of you using Windows right now, REDCINE seems to be the best option to handle any R3D files you can throw at it. Actually, I'm not sure but I think it's the only option right now, at least it was the only one that I could get to work. There was a solution to open it up in AE CS4 but I couldn't get the RED settings to pop-up. If you need some place to get started, I recommend watching the tuts from Final Cut User here. They'll give you a basic overlook on the app, and give you a better insight on just how awesome RED is.

I'm currently working on doing the roto and keying right now, so nothing new for my mograph buddies, but I thought I'd post up some my prev work in progress. This first pic is to be the intro of our project, a 2.5D matte painting depicting an ancient Asian landscape.



I made it in Photoshop, and then rendered out layers to switch to After Effects and displaced along the Z axis.



A styleframe/storyboard in which our hero character hides behind a wall. 3dsmax.








More to come soon, I promise, but there's still lots and lots of work to do!

Often times I find myself moving Nuke scripts back and forth between my computer at home and the labs in school. If you work on multiple computers with your Nuke scripts, you've more than likely experienced broken Read Nodes.

But fear not young padawan! There are ways to avoid spending 15 minutes redirecting Nuke to all your files. I've come across a couple of scripts to fix your Read Nodes, but by far the most jaw-droppingly easy one comes from The Foundry itself. If you haven't checked it out yet, the Nuke Master Class last January was extremely beneficial and I highly recommend everyone to check out their videos and source files.

In their Python videos, they quickly demonstrate fixPaths.py, which attempts to automatically fix the paths of all the missing files in your Nuke script. Here's a little excerpt from the second Python video showing the FixPaths script in action:



Again, please please please, I urge you to go visit the Nuke Master Class and view the entire video in higher res. It will be worth your while, I promise.

-------------------------------------------

This second method I learned from a good friend of mine, Devank, who put together a PDF based on another tutorial from The Foundry. You can download his original PDF here.

The rundown of his interpretation goes a little bit like this:

1. Create a NoOp node and set its name to Path.




2. Right-click on the NoOp node in the Properties panel and select Manage User Knobs. Add a Filename knob and rename it to Project_Path.
   



3. Enter or browse to the path of your project directory.
   



4. Now all you have to do is copy and paste this little code into all your Read nodes before the filename to insure it links to the Project directory.
   
   

   [value Path.Project_Path]

   
   
   
   


5. Now whenever you switch computers, all you need to do is change the Project path in the NoOp node and your Read nodes should fix themselves.

A friend of mine is currently working on a project in which there is a ball rolling on the floor and he needs to move the highlight in order to correspond to a light source in the distance. I came up with a quick solution, and I thought I'd share it in case you cross upon something similar, because I feel that this is something quite common, but I wasn't able to find anything on the net. You can download the AEP file here if needed.

Here is the result:


Basically, I created a null that acted as the fake position of our light. Then, I used this null's position to calculate the distance from the highlight on the X and Y axes and theoretically made a right triangle. Using each axis information, I plugged it all into an inverse tangent equation to give me the correct angle that I wanted. Then I just added a multiplier to increase/decrease the amount of rotation.

In this AEP file, I have 4 layers. The ground, the ball, the reflection, and the null. I animated the ball moving around in an arc that roughly imitates my friend's animation.

Want you want to do next is make sure that the Anchor Point for the highlight is in the center of the ball, that way when we rotate it, it will do so inside the ball. Then make sure to parent the highlight to the ball. Afterwards you want to Alt-Click on the Rotation stopwatch in the highlight layer to open up an expression box and type in the following code:

adjc = sub(thisComp.layer("nullLightSource").transform.position[0],thisComp.layer("ball").transform.position[0])
opp = sub(thisComp.layer("nullLightSource").transform.position[1],thisComp.layer("ball").transform.position[1])

sidesratio = div(opp,adjc)

inversetan = Math.atan(sidesratio)*25

Let's break this code down a little. The variable adjc takes the X axis info from the null called "nullLightSource" and subtracts it from the X pos of the layer called "ball". Similarly, opp takes the difference from the Y info. sidesratio then plugs these two correctly into the inverse tangent equation Math.atan().
Then I added a multiplier of 25 at the end of inversetan simply because it looked good.

And voila! You now have a highlight rotating based upon the position of a null. I'm sure somebody can come up with an even cooler application to this, maybe a giant axe blade attached to the end of a pendulum?

H.264 is one of the more beneficial codecs out there today, especially if your final delivery is to the web. It offers remarkable quality at a surprising small file size. It's one of my most used codecs. In fact, I rarely use anything else outputting to web, as Sorenson flash offers some really nice compression, but it often lacks at picking up the fine level of detail that I personally like to preserve. In my mind, it's so close to being the perfect codec, except for a problem that's been maddening people since its inception. I've been finding that when outputting from both After Effects and Nuke, the gamma is nearly always boosted, causing footage to look desaturated and milky, such as you might see when working in the wrong colorspace. The problem seems to lie with a hidden uneditable gamma tag within the movie file. There are plenty of solutions and "non-solutions" out there on teh interwebz, and all come with a mixed bag of results.

ProVideo Coalition's Chris Meyers article gives an excellent idea, pull H.264 to the side and use its free open-source alternative, x.264.
Mac users can get it via MacUpdate, and Windows users should try Free-codecs.com. Though I have been unsuccessful getting it to work in Windows, hopefully you will have some better luck.

Once installed, it should show up as another codec in your Standard Video Compression Settings.


Another article by PVC's Art Adams suggests rendering using an intermediate codec such as Animation and Photo-JPEG, and then exporting out of Quicktime using the open-source x.264 codec, in order to insure proper translation of the gamma tag, which I would highly recommend.

-----------------------

Another PVC writer, Mark Christiansen, points out that the gamma tag may be able to be stripped off with a neat little app from FuelVFX. "It requires a bit of hunting: hover your cursor over the red bar, select Software, and then click on the QTGammaStrip folder icon. Make sure you also download the ReadMe.txt file, as it includes (extremely) terse instructions on how to run it inside Terminal. " -Meyers.



-----------------------

Popularized by Andrew Kramer of VideoCopilot.net, this method involves altering some settings in Quicktime post-render, but comes with mixed results across the board. It seems that in VLC, the gamma will still be boosted, whereas in Quicktime, Safari, and Firefox the video shows up as it should.

H.264 Fix by AVillabon.


SOLUTION: After rendering into a QuickTime/h.264 file, open it up in QuickTime and select “Show Movie Properties.” Highlight the video track then click on the “Visual Settings” tab. Towards the bottom left you should see “Transparency” with a drop-down box next to it. Select “Blend” from the menu then move the “Transparency Level” slider to 100%. Choose “Straight Alpha” from the same drop-down and close the properties window and finally “Save.”

-----------------------

Hopefully the fine folks at Apple will fix this soon. Are there any other solutions that you would recommend?