Patrick Sheffield
Forum Replies Created
-
FxFactory is more than a showroom, plugins are developed IN FxFactory Pro (available as a watermarked demo).
You can make your plugins in Quartz Composer (looks something like this):
These are available in FCP, FCX, Motion, After Effects, and Premier.
Some developers elect to do their plugins in Motion, however those are only available in FCX.
FxFactory handles downloads, payments, watermarks, etc.
does that help?
best,
Patrick Sheffield
Sheffield Softworks -
I agree – doesn’t sound hackintosh specific…
Patrick Sheffield
Sheffield Softworks -
So, do I take it that Apple, thru Pogue is telling the truth when they say they have no intention of ever supporting prior versions of Final Cut Pro projects?
’cause I know they are, at best, stretching the truth about some of what Pogue is saying for them.
Patrick Sheffield
Sheffield Softworks -
“Such an API would allow anyone to write an app or plug-in to export sequence data from FCP X in any format, and would almost certainly result in FCP X having a far more robust set of export options than FCP 7 ever had.”
At what cost? If Automatic Duck is taken as an example, gonna get pretty expensive at $500 a pop… These were supported in the past by Apple themselves. Sure, Apple should make the API available, but perhaps they could use their own API to deliver some of the stuff they left out.
Patrick Sheffield
Sheffield Softworks -
You don’t think this is a slightly… melodramatic way to react to the absence of about four features, which Apple has independently told several media outlets are being added back in?
At the FCPUG in London the other night, reportedly the Apple representative stated that Apple is not interested in pursuing XML support…
Even David Pogue, speaking supposedly for Apple, said FCX would never support import of Final Cut Pro projects, and that Apple thought EDLs were crude and should be dropped.
How does that equate to adding back those features?
Patrick
-
“You can’t watch a video and know what the editor’s timeline looked like exactly: you can only make an educated guess.”
But we’re not asking FCX to infer the timeline from the video out. The relationships between the Audio and Video are explicit in the FCP timeline. Either the audio is linked with the video, or it is free floating. That’s how it should be carried over. There’s no need to look for further “intent”. And if you want to, you can always link them after the fact, can’t you?
Unless you’re saying there’s no way to put audio in a FCX timeline without linking it to some video. This is not my perception of how FCX works.
Some translation problems are probably inherent in FCX’s design flaw/limitation of no Audio/Video tracks (Yes, it’s a limitation… I use Tracks for a reason. They are not something I was saddled with and looking to rid myself of – I don’t find timecode pesky either).
Do I sometimes grab a section of my FCP timeline and miss a bit of audio? I suppose, but it’s pretty rare. I usually lasso the section I want to move and slide it where I want. On my list of Annoying Problems Manipulating The Timeline, that doesn’t even make the top 20. To redesign an entire paradigm to remove that problem seems misplaced in the extreme.
Patrick Sheffield
Sheffield Softworks -
It’s too bad the Motion templates can’t be locked or protected in some way. I could think of some awesome development opportunities, but no way to protect them from piracy.
Patrick Sheffield
Sheffield Softworks -
With all due respect, Jerry, and thats a lot, you can’t call FCX a 1.0 release. It’s not. It says so right here on the splash screen. Final Cut Pro 10 – unless you think they misplaced the decimal point? If it’s version 1.0, then call it Whizzy Editor Pro 1.0 or something else.
You can’t have it both ways. If you’re going to claim it’s Final Cut 10, then you can’t excuse the removal of those features and say cross your fingers and hope they come back in Final Cut 11. The fact is, they released this and killed the old version. It’s a new release, not a new program. It really doesn’t matter how much of the code they replaced.
What’s so surprising about this is that Apple have always been so smart about major transitions in the past. Witness 68000->PPC, OS9->OSX, PPC->Intel. Heck when they released the considerably feature reduced iMovie 08 (sound familiar anyone?), they gave people a free download of iMovie 06 to ease the changeover until they added back the missing functionality.
All of those transitions were handled with far more finesse than this FCX debacle.
Patrick
-
Yes, all plugins are now based around FxPlug2 – an expansion of the first FxPlug SDK. They must be re-compiled or re-built, and “Rigs” must be constructed for them in Motion 5, and these must be married to an installer. There are still outstanding questions amongst developers, but none of this should have been top secret. If Apple had provided a very small amount of information, vendors could have been prepared at FCX release.
FxScript plugins, of course, have been dropped completely. Apple could have supplied an FxScript interpreter FxPlug plugin, but why worry about that? Why worry about anything legacy? Like maybe FCS7 projects?
Patrick Sheffield
Sheffield Softworks -
Speaking as a developer, we asked for months for any info about support for FCX. We were told by Apple engineers, “We can’t say”.
And yet – as others have pointed out, FxFactory obviously knew.
The info’s out there now, but personally, I will require some time to evaluate the best way to support both FCP7 and FCX clients.
Patrick Sheffield
Sheffield Softworks
