[David Lawrence]

[Bret Williams] “We’ve been able to shoot and edit broadcast video on laptops and small cameras for 12 or 13 years. Not sure how FCP X is any amazing leap forward in this realm.”

Bingo.

_______________________
David Lawrence
art~media~design~research
propaganda.com
publicmattersgroup.com
facebook.com/dlawrence
twitter.com/dhl

[David Lawrence]

Thanks, Walter.

Something I find interesting is that a couple of the Magnetic Timeline’s big selling points have been available in for years:

1) Ripple – Every NLE lets you ripple, but usually it’s just a tool. I see no advantage in FCPX making it the default timeline mode.

2) Clip connections – You can think of clip connections as a special type of grouping. Premiere Pro’s groups are actually more flexible because anything can be connected to anything, anywhere on the timeline. No artificial hierarchical constraints, no artificial “relationships”.

What FCPX brings that’s new to the game is floating, trackless, connected objects and collision avoidance behaviors. I think it’s possible to design this collision avoidance into a tracked system like Pr and get a much more powerful, flexible UI. I can imagine a couple different ways it could be implemented using groups. It would be the best of both worlds.

Really, relative time and everything that results from it seems to be the primary innovation in FCPX. For better or worse, depending on your POV.

_______________________
David Lawrence
art~media~design~research
propaganda.com
publicmattersgroup.com
facebook.com/dlawrence
twitter.com/dhl

[David Lawrence]

I think another key take away from the announcement is this:

“We evaluated every major editing solution on the market, and Adobe Premiere Pro provided the best-in-breed solution we needed,” says David Hoad, AP director of global video technology. “This was not only for its professional editing capabilities, but also for its integration with our Miranda and Gallery SIENNA asset management systems.”

Asset management is a huge deal for any large production enterprise, representing a major investment in time, money and infrastructure. It doesn’t matter how interesting or theoretically flexible Apple’s organization system in FCPX is. Enterprise customers will always demand an open system that works the way they want it to and connects to infrastructures of their own design. The risk of Apple’s proprietary system alone, likely makes it untenable for many enterprise users.

_______________________
David Lawrence
art~media~design~research
propaganda.com
publicmattersgroup.com
facebook.com/dlawrence
twitter.com/dhl

[David Lawrence]

[Jeremy Garchow] “I think what you would need to do now is dynamic link the footage with noise industries plug from Ae back to Pr, but I’m not 100% sure on that. “

This is exactly right. I did this on a recent project to bring in particular FxFactory effect that my client really liked. Dynamic link from AE made it simple. But working directly in the Pr timeline would be even better. As you can see, it’s loading, it just doesn’t work yet. FxFactory hasn’t given a date, but they’ve made recent statements hinting that they’re working on something.

_______________________
David Lawrence
art~media~design~research
propaganda.com
publicmattersgroup.com
facebook.com/dlawrence
twitter.com/dhl

[David Lawrence]

[craig slattery] “the magnetic timeline in FCPX is genius. I’d be really surprised if Avid and Adobe aren’t already developing their own versions.”

I wouldn’t hold my breath 😉

BTW, This just out tonight:

Associated Press standardizes on Adobe® Premiere® Pro CS6

_______________________
David Lawrence
art~media~design~research
propaganda.com
publicmattersgroup.com
facebook.com/dlawrence
twitter.com/dhl

[David Lawrence]

[Jeremy Garchow] “I don’t know how much you’ve worked with Pr, but the native aspect gets old very quickly depending on what formats you are working with. A solid and robust codec for the CS would offer all kinds of efficiencies from rendering/realtime effects/conform/archive/translation. It would allow the use of cheaper hardware and not tie every room to a multiple GPUd machine.”

Well said. Hopefully this is high on Adobe’s priority list.

_______________________
David Lawrence
art~media~design~research
propaganda.com
publicmattersgroup.com
facebook.com/dlawrence
twitter.com/dhl

[David Lawrence]

[Walter Soyka] “David, what would you envision a Mercury Render Engine doing?

I’ve been thinking a lot lately about the FCPX/Motion common renderer versus the distinct Ae/Pr renderers. I see major pros and cons with both approaches, so I’m at a bit of a loss about which one I want to write my rabid feature requests about!”

[Jeremy Garchow] “Personally, I tend to think that if they have one proprietary codec, this might be a part of other higher res codecs. I think Adobe is listening really well, and I think they might see value in not working natively all the time. It will also open up avenues between their own applications.”

Basically, I’m hoping for something like what Jeremy’s describing — a high-end finishing codec and a smart, efficient render/transcode process integrated into the application and workflow. I’d like to have better control over the render process and be able to use my render files for final output, like how it works in FCP legacy (or if not like FCP, then as efficiently as in FCP).

I understand Adobe’s difference in philosophy regarding rendering and output, but my experience is that the time saved up front doesn’t really get added back at the end. We all know how clients love to call at the very end with just one more little tweak… Really a bummer having to re-render every time for even the smallest change. This is probably my biggest feature request at the moment and I’d guess it would be for many other FCP converts as well.

_______________________
David Lawrence
art~media~design~research
propaganda.com
publicmattersgroup.com
facebook.com/dlawrence
twitter.com/dhl

[David Lawrence]

[Franz Bieberkopf] “Did I just hear something about the possible underpinnings of an Adobe “native-codec” for editing in there, … or is it wishful thinking? … or am I stuck in outmoded thinking?”

I was thinking the exact same thing.

They’ve already got:

Mercury Playback Engine – for playback
Mercury Transit Engine – for I/O

They’ve just announced the Mercury Streaming Engine for Adobe Anywhere.

So that leaves the one big gaping hole in the Mercury line-up…

How about:

Mercury Render Engine – for output

Wouldn’t that be sweet?

_______________________
David Lawrence
art~media~design~research
propaganda.com
publicmattersgroup.com
facebook.com/dlawrence
twitter.com/dhl

[David Lawrence]

[Jeremy Garchow] “What I find interesting about this little preview (and of course we will need more details) is that it seems Adobe is going to let you host your own server.

For those that have a “server”, this sounds very promising.”

This looks and sounds totally awesome. My partners and I have been wondering how we would collaborate when we finally leave FCP7 and lose iChat Theater Preview. We have our own servers and reasonable bandwidth so if this works as promised we should be happy campers. Looking forward!

_______________________
David Lawrence
art~media~design~research
propaganda.com
publicmattersgroup.com
facebook.com/dlawrence
twitter.com/dhl

[David Lawrence]

[Bill Davis] “I think it’s becoming a new global force. For decades we got what the networks fed us. Then we got what networks and cable fed us. Now we have a portal to a worldwide base of content that sinks or swims in a new global pond of possibility.”

Nonsense, Bill. Everyone knows it’s a series of tubes.

https://www.youtube.com/watch?v=_cZC67wXUTs

_______________________
David Lawrence
art~media~design~research
propaganda.com
publicmattersgroup.com
facebook.com/dlawrence
twitter.com/dhl

Some contents or functionalities here are not available due to your cookie preferences!

This happens because the functionality/content marked as “Google Youtube” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.