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.
Last week on my POST Magazine blog, I briefly discussed Encoding in Post: The Four Hot Spots. I figured, “Why not elaborate on one of those areas?” Thus far, I’ve discussed the concept of Pre-encoding, and various facets of the final encode. Let’s talk about the most vital and often overlooked area: During Editorial.
Last week, we covered the concept of Conditional Encoding (KCM: Kammes Compression Methodology, still looking for investors) and you may have noticed that I put an odd node on the graphic workflow. The LOGIN. Why? Because the next phase of this workflow is going to piggyback on not only the Internet, but on your LAN as well.
The post industry lives and dies around the concept of deliverables. What specifications have to met to appease the viewer, server, or engineer on the other end. Many times, just getting the deliverable out is a chore in itself. The last encoding format sheet I read from a leading encoding manufacturer had 5 pages of supported input / output formats. Being able to decipher these often cryptic encoding acronyms and numeric values appears to need a degree in engineering.
Off and on for several years, I was involved with a post facility that had what they referred to as “The Money Room” Quite apropos, not only for the greenish hue to the walls, but what they *did* in that room. Unbeknownst to them (but now beknownst to me) the so-called castoff activities and backroom chores which took place in that space are now the new(er) ways to make money at your post facility…and even be a marketable service.
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.