Comments for postpost.tv

Comment on Dawn by Simon Walker

Simon Walker — Mon, 20 Feb 2012 12:50:02 +0000

This works really well, and thanks JET for spelling out the workflow process.
How much did Automatic Duck cost…?! When Philip and co can put out this much clever coding for under a tenner, I’m sure they’re going to sell bucket-loads.

Comment on Dawn by JET

JET — Thu, 02 Feb 2012 07:28:18 +0000

With 7toX for Final Cut Pro in the Top 10 Paid Apps, we can't be alone it that assessment!

Comment on Dawn by Chris Roberts

Chris Roberts — Thu, 02 Feb 2012 07:14:28 +0000

Hooray for Philip and Greg! Firstly it shows how third parties are having a huge impact in the FCP X ecosystem. However, it also highlights how much promise there is within FCP X as the software we have today is quite radically different from the software that was released in June 2011. I imagine there will be similar leaps forward before FCP X is one year old.
And at $9.99, 7toX for Final Cut Pro is, literally, a no-brainer!

Comment on FCPXML by Jonathan Eric Tyrrell @ postpost.tv

Jonathan Eric Tyrrell @ postpost.tv — Thu, 02 Feb 2012 01:27:15 +0000

[...] It’s certainly an area I’m acutely interested in and those of you who’ve read earlier posts will know that I’ve been experimenting for a while with the solutions brought forward by [...]

Comment on Legacy by Jonathan Eric Tyrrell @ postpost.tv

Jonathan Eric Tyrrell @ postpost.tv — Thu, 02 Feb 2012 01:25:33 +0000

[...] prospect of not being able to migrate projects from legacy FCP to FCP X was, shall we say, daunting. For some editors the ability to open FCP 7 [...]

Comment on FCPXML by Michael Rooney

Michael Rooney — Thu, 29 Sep 2011 14:46:35 +0000

Excellent article. You can count on fcpxml support being added to our popular AATranslator product

Comment on FCPXML by ben scott

ben scott — Wed, 28 Sep 2011 18:48:15 +0000

liked the article

is it that easy to write the XML seems very simple, but if simply written like this I could look into and try to write code for lots of workflows for delivering to different channels e.g. theres a lot of very specific timing for elements that are prone to human error, write once, publish and then the broadcasters get those leader and header elements at the correct levels they require

have either of you 2 checked out PPMULATOR I tried yesterday and the audio unit plugin works

suppose the eyeheight http://www.eyeheight.com/KARMAudio.asp plugin could be a good one

also looking at the way FCPX is creating presets/roles etc seems very odd but could be swapped in and out using automator or shell scripts, e.g. your set of presets for this workflow or that workflow

also think the motion plugin installs are too tricky for novice user, needs installers which should be very easy to create

these are the sort of useful research we should be sharing!

if this is as simple as implied I may contact a programmer friend to see what he can come up with

Comment on FCPXML by Chris Roberts

Chris Roberts — Wed, 28 Sep 2011 07:15:07 +0000

Stunning tutorial. Thanks for your hard work. I never thought I’d find a discussion on XML engrossing before!
So now we have FCPXML I think we can honestly say that FCP X is firmly on the path we believed it was on initially. However, do you see its variant of XML being widely adopted? I guess the naysayers will always have a voice until the day arrives when you can translate an FCP 7 project to FCP X and Philip Hodgetts makes good sense of the issues surrounding that particular process.

Comment on Safe by Patrice Freymond

Patrice Freymond — Thu, 14 Jul 2011 11:38:58 +0000

Thank you for this info. I also noticed that the BS filter invariably defaults to NTSC, even when applied to a PAL clip…

Comment on Safe by Patrick Inhofer

Patrick Inhofer — Thu, 14 Jul 2011 11:37:47 +0000

Jonathan – Good detective work! Thanks for taking the time to figure it out… maybe one day Apple will document this stuff.