5dtorgb

Pro Res Encoding on Windows 7

Have you ever had to deliver an apple Prores file when you’re a PC user? For some reason, Apple decided to make Prores encoding somewhat, a pain in the arse for Windows users. Probably something to do with pure hatin.

In the past, before I knew any better, I had to render out an uncompressed quicktime, copy that to a hard-disk, take that to my girlfriend’s Macbook, and then render out a Prores file. Did I mention that was a pain in my arse.

Little did I know a FREE little program had always had this prores encoder built in. Let me introduce 5DtoRGB. I had heard a lot about this program previously but thought nothing of it because I thought it was just for Mac users shooting on 5Ds and editing in FCP 7.

Does Apple know about this? Why is Prores not platform agnostic? It really is a great high quality codec that plays and edits well in Premiere. It also plays nicely with Speedgrade and Resolve. I wished that Adobe had bought out Cineform and made it more open like Avid DNXHD. Unfortunately DNXHD doesn’t play too well in Premiere.

Enough ranting, download it before Apple finds out

broken tilt knob

DIY repairs with the Miller DS-10 head (Broken tilt knob)

Don’t you just love baggage handlers? Here’s what happened to the tilt knob on my Miller DS-10 head on a flight to a remote oil & gas construction site.

What was extra bad was that it happened on the way there and the tilt on the head was locked. The knob broke off flush with the side of the head and there was no way for me to release the tilt. The head was also locked in an uptilt position which meant panning was impossible. This meant that the tripod was as good as useless but lucky I had my Sony 18-200mm lens with image stabilizer and my Zacuto EVF with my FS100. I was able to get some relatively stable shots holding the camera like a Medium format camera whilst using the Zacuto EVF (mounted on the hotshoe) as an extra stabilizing contact point. I still needed to add extra stabilizing in post to get usable shots.

 

I wasn’t feeling like spending around 1k on a new DS-10 head so I figured it would just be a case of removing the broken screw and replacing it with some spare parts from Miller.

After some slow customer service via email, I was sent the replacement tilt knob ($23 inc shipping) and went about figuring out how to extract the broken screw bit.

After some googling I figured I needed:

  1. Drill bit – I needed to drill a pilot hole into the screw for the…
  2. Screw extractor – A reverse drill bit like thing that you hammer into the pilot hole and then unscrew out. As you unscrew, the screw extractor bites into the screw and then, well it unscrews it out.
  3. A tap wrench – to use with the screw extractor. I tried my hands, and I tried pliers but a tap wrench is just about the only suitable tool to grip the screw extractor.

Screw Extractor set

Here's me extracting the screw

So I guess if this happens in the future, it’s really no big drama and is quite an easy and cheap repair. I think if Miller actually got back to me in a timely manner about how much it would cost to send the head in and for them to repair it, it would have costed a lot more than the $50 or so I spent on the parts. Plus I’ve now got the tools in my toolbox for any similar mishaps that may come later on.

Lessons Learnt? The tilt knob on the Miller DS heads are hollow and seem to be a weak point in the design. Customer service from Miller could be A LOT more responsive. Sure it’s not one of their premium massive super expensive heads but I still use this stuff for a living and I expect a response in less than 3 days. Getting a response within 24 hours seems to be too difficult for the one guy who seems to be working the tripod service line. I think my next tripod will be something else…

camerastabilzer-blackbird

CMR Blackbird with the FS100

I’ve recently aquired the Blackbird stabilizer from Camera Motion Research to be used with my FS100. Here’s a brief overview of my thoughts on the purchase.

  • Despite it being a larger camera, the Blackbird suits the FS100 quite well. I just strip the camera down to just the body and the lens and use a couple of weights either side..
  • This thing is as easy as it gets to balance. After having tried and failed to balance glidecams in the past, the Blackbird can literally be set up, first time in under 15 minutes. Now it takes me less than 5 minutes to get it balanced.
  • It’s not as tiring as I thought it would be. With the glidecam, the center of balance is in front of the wrist so there is added strain. With the Blackbird, it’s directly above the handle and so there is less strain and fatigue on the wrists. So instead of tiring in 5 minutes, I could go for around 15.

So far I’m quite happy with the purchase and have found the learning process of getting a smooth “flight” a little challenging. As with most stabilizer’s, the quality of the shot is in the operator and a few tips from the included DVD have gone a long way. Such as using lots of steps and bending your knees while you walk or run. Sure I look like a bit of a dork but the results are worthwhile.

The only thing I regret is not getting the kit that comes with the resting stand so I can put the whole thing down to rest my wrist. The next step is to get a Steadicam merlin vest (which is compatible) to go with the Blackbird for that extra axis of stability and to help save my wrists.

Videos and pics to come soon.

Premiere Pro CS5.5 workarounds

Having used PPro CS5.5 for quite a few months now (on pc), I’ve noticed a few things regarding stability, especially when using the Cuda hardware mercury engine.

Problem
When I render out the timeline (by pressing enter), I sometimes come across an error pop-up with something along the lines of, “Error compiling movie”. Not only does the render stop dead in its tracks, once the error has come up for a certain area of the timeline, it will continue to pop-up repeatably.

Solution
The first thing I do in this situation is to empty the temp folder. Go to the windows start button and in the search bar on the bottom, type in %temp% to open the temp folder. Then select everything and delete. Skip the files that are currently in use.

If that doesnt’t work then go to projects settings and turn the mercury engine from hardware to software. I’m using a GTX285 which is on the supported card list BTW.

Problem
Rendering out a movie file out of Premiere with Adobe Media Encoder, the render would sometimes, (or everytime I use h264), just stop and not render any further. AME would still be responsive except for the fact that the render progress would just get stuck and not progress. This has frustratingly caused me countless hours of figuring out the solution. Turns out it is as simple as turning off the Cuda mercury hardware engine before exporting out to render.

The strange thing is on my partner’s editing station, we are using a “hacked” GTX 560 and that apears to have far less issues with stability. It still has rendering issues but about half as much as on my system with a certified card.

This just shows to me that the Cuda mercury hardware engine still has a bit of maturing to go through before it can be relied on for a solid input to output workflow. Adobe have done an awesome job in implementing this feature but from what I understand, the coding is complex and the bug fixes are not easy to do and implement.

Hopefully CS6 will bring these fixes along with ATI gpu support.

Update 7/3/12: I’ve since upgraded my graphics card to a GTX 570 and so far so good. None of the problems I’ve experienced with the GTX 280. It seems CS5.5′s compatibility with the older cards is not so good in this instance.