Wakeup call to makers of post production tools
Friday, January 27, 2012 at 02:11PM There are amazing tools on the market, from NLEs (non linear editors) to advanced compositing/animation programs. No doubt they have come a long way. My first real job in the industry was working in a machine room at a production company that specialized in documentary and museum interactive video. I got introduced to the world of 1", 3/4", betaSP, digibeta, etc. I began there in 1995, and it wasn't long before I became interested in the edit rooms which housed some fairly new technology at the time, Avid Media Composer editing systems. It didn't take long before I got a chance to try them out, and moved my way out of the machine room and into the role of an assistant editor, digitizing footage into the Avids. A lot has changed since those early days of Avid, but in some ways I sometimes feel we're still stuck in the 1990s. Let me explain.
In an industry that prides itself on innovation, it's hard to deny that media production and post production has taken giant leaps over the past twenty years. Editing has never been easier (the physical joining of two shots that is. Editing itself is an art.), the VFX tools have become incredibly advanced, and sound processing technology has taken digital audio to a whole new level. So, what do I have to complain about?
We've entered an era which I'm referring to as BetaWorld. Companies are being forced to innovate at rapid pace, packing new features in to hold off the competition and selling what sometimes equates to a beta version of a product. There are bugs, workarounds, disabled features, etc. Although Avids in the 1990s weren't perfect, they were generally stable. New versions didn't come out every week. They were developed over time, tested, and released when they were production ready. I worry that we've moved into an era where the emphasis is on new whiz bang features that keep the marketing teams at these companies happy, but leave the users feeling like lab rats. In my opinion, the number one thing as an enduser is stability and an easy to navigate UI(user interface). In an ideal world, the tools should become invisible as much as possible so that our focus is on creating. Yes, some of what we do is technical, but it's creating that is at the heart of why we got into this.
So, why in the year 2011 are we still dealing with the following.
- Gamma shifts
- Color inconsistency when moving files around
- Excessive amounts of rendering
- Misinterpretation of files
- Lack of standards across the various tools
- I/O monitoring issues
- Bit depth issues such as banding
- General bugs in software
The list goes on and on. If I could ask one thing from the people that make these tools. Take a careful look at what the enduser's needs are. Look at their challenges. Understand how people work, what other tools they use,what kind of hardware they run, and find ways to put a huge emphasis on stability and production ready releases. Random bugs do nothing but slow down the creative process. Tools that handle a standard different than is intended with that standard do nothing but frustrate the end user. I understand the challenges to making this happen. I understand there are agendas that collide. I understand that the world is cutthroat and that sometimes making a deadline is more important than making the product 100% right. But in the end it doesn't change what I have to accomplish at the end of the day. I need tools that work for me, not against me. Anything that introduces a workaround, works against me. All I ask is that all of you work towards making tools that work for us, that help us achievve our goals without worrying whether something we do will be affacted by some random bug, a piece of code that can make the diffrence between a job getting done or not getting done on time. Maybe I'm asking for the impossible. I'm asking for the refrigerator that you buy knowing that you can store it with food, it will keep it cold, it will do it's job. Yes, it's a machine, and it could eventually have a problem, but for the most part does exactly what it says it does. That's what I'm getting at.
Avid,
bugs,
post production,
workarounds in
Workflow 
