RED Tag

Matt Stratton turned me on to Clicky Stats awhile ago, and through Clicky, I’m able to see what web searches come up with my blog as a result. I also see when these searches lead them to my blog – but then they leave because they didn’t find the answer. I thought since the search engines think I already have it on my site, perhaps I should.   Below is a sampling of the search queries (that I can decipher from cryptic keyword searches) that my website supposedly already has the answers for.
Thousands of vendors, and hundreds of thousands of square feet later, I am back in SoCal, with some highlights from the 2009 NAB convention.
  Everyone has an encoder nowadays.  Final Cut Studio has shipped compressor for years.  Avid ships with Sorenson Squeeze, and I typically suggest some flavor of Telestream’s Episode family line.  All of these have varying degrees of quality and format support, and some go even above the call of duty with watch folders. One fatal flaw is that they all rely on someone else’s engine with which to encode through.  Quicktime.  Quicktime, while being the pipe which leads to all things NLE, becomes vary narrow when it comes to efficient processor usage.  In fact, it’s pretty bad. Ever viewed your system processing usage while encoding?  So much to be desired. Root6 Technology, a player in the encoding and media market for over 6 years now, (BeamTV) has taken an innovative approach to this problem thus created an intelligent workflow device.
The RED camera system has revolutionized the industry, however, with every revolution there are speed bumps. Decoding the REDCODE file (natively, or utilizing the camera generated wavelet proxy files) can be a lengthy process. A solution is to bring the bleeding edge down to cutting edge. Merge old with the new.

By following the diagram above, much of the data utilized in your RED filename can be deciphered by simply understanding the information contained within the filename. Many times, your...