Commercial advantages

[Michael Gissing]

[craig slattery] “Hey Bernard, folks get a bit carried away on this site. Both our initial threads have been hijacked by an army of vested interests pontificating in their own gravy”

This forum is all about pontification. I didn’t agree with your original pontification but starting a thread doesn’t make you the arbiter.

Yes clients want a result and don’t much care for the tools that get the result. Smart clients also care about workflows and have loyalties to editors and other post facilities that finish the grade, online & deliverables so they need to know that the people they want to work with can work together.

If you are doing it all in house then bravo. In broadcast that almost never happens so Bernard’s point about whether FCPX is a wise move for a facility is also valid. If a local edit facility chooses to go FCPX (and so far none have), then they need to talk to me and other post facilities to make sure our current cooperative workflow can continue.

I also take Jeremy’s point about backwards loyalty with old legacy projects so I am keeping a MacPro running with FCP7. Ironically it is CS6 that is more backwards compatible than X which is also a consideration.

[Walter Soyka]

[Bill Davis] “Well, in X – every thing in the Project library is dynamically connected to the Storyline that it’s a reflection of. The Share menu lets you express it out to the net via Vimeo, YouTube or to your own in-house server. As you make changes in the Storyline, those are expressed instantly to the repository in the Project Library. If you want to maintain a version, you just duplicate the project. This allows for pretty agile versioning. To switch from Verson A to Version B, you just share out the new one. It’s not so much connection to “publishing systems” as much as it’s that the entire program being designed to export directly to a export stream, rather than exclusively to the desktop as a standalone file – and having built- in tools to enable that (keyword attachment, etc) right inside the program. “

Adobe applications have a feature called Dynamic Link which allows you to pipe the output of these applications together without “disconnected” intermediate renders.

I can work on a graphic in After Effects, bring it into my timeline in Premiere via dynamic link, and then bring the Premiere project into Adobe Media Encoder via dynamic link.

If I go back and make a change in the graphic in AE, the change flows through to Pr and AME.

Adobe’s DVD/Blu-ray/Flash authoring app Encore is also tied in via dynamic link.

AME supports automatic FTP upload, but it does not auto-publish to Vimeo/YouTube (that I am aware of).

Walter Soyka
Principal & Designer at Keen Live
Motion Graphics, Widescreen Events, Presentation Design, and Consulting
RenderBreak Blog – What I’m thinking when my workstation’s thinking
Creative Cow Forum Host: Live & Stage Events

[Craig Slattery]

[Michael Gissing] “then they need to talk to me and other post facilities to make sure our current cooperative workflow can continue. “

Nice idea, might be a stretch getting the BBC folks down to Tasmania.