-
Is Apple Being Misleading About Native Editing Support?
-
[Scott Sheriff] “[Craig Seeman] “FCPX has hooks that allows camera manufacturers to develop direct plugin support.”
Well that is not ‘native’. Native means inherent, or inclusive.
Needing a third party plugin would be neither. To claim a native capacity, while requiring a third party plugin to achieve this so called ‘native’ capacity is misleading.
This new shift to heavy use of third party plugins to make an app work as advertised is a convenient way to ‘blame shift’ for lack of development, bugs, or poor performance. I guess you get what you pay for with a $299 app.”What I think this is going to mean is that, you will be able to write your own plugin similar to what was happening with companies writing their own log and transfer plugs.
I wish FCPX had more true native support, even if that meant being able to make proxies. FCPx’s proxy making while you edit is actually pretty nice. Then it’s one click back to full resolution.
Time will tell, but it’s odd we haven’t seen anything from the camera SDK yet. There must be something that isn’t adding up.
Jeremy
-
[Jeremy Garchow] “but it’s odd we haven’t seen anything from the camera SDK yet. There must be something that isn’t adding up. “
This may be a two-step process. The supposition is that the Q1 2012 update featuring broadcast output had to wait for the appropriate AV Foundations hooks in the OS. This may also hinge on the same thing. In theory, it could mean that wider camera support via the SDK will coincide with that update. Of course, that’s simply a big guess.
OTOH, the people really interested in supporting that SDK are likely to be companies that sell into the pro market. They may also be on the fence waiting to see how FCP X market penetration is among pro users. Why put in the effort when no one will use it? Not saying that will be the case, but DaVinci has already stated that they really didn’t have anyone asking for FCP7/X XML roundtrips, but they did it based on anticipating the future. We’ll see if that was a correct guess.
If you are a pro-camera manufacturer, where would you put your development efforts: Adobe, Avid or Apple?
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
[Oliver Peters] “This may be a two-step process. The supposition is that the Q1 2012 update featuring broadcast output had to wait for the appropriate AV Foundations hooks in the OS. This may also hinge on the same thing. In theory, it could mean that wider camera support via the SDK will coincide with that update. Of course, that’s simply a big guess.”
Either that or there needs to be more XML support, probably both.
[Oliver Peters] “If you are a pro-camera manufacturer, where would you put your development efforts: Adobe, Avid or Apple?”
Everywhere, wouldn’t you? Can’t really afford not to, especially if you’re someone like Sony when Panasonic cameras work “out of the box” with X.
-
Everywhere, wouldn’t you? Can’t really afford not to, especially if you’re someone like Sony when Panasonic cameras work “out of the box” with X.
No, I wouldn’t. No one has unlimited engineering responses. Look at something like the SR codec. If you had to choose between FCP X or Avid AMA or Adobe, then I think FCP X goes to the back of the line. Not enough users of SR codec media will be cutting on FCP X by mid-2012. OTOH, AVCHD or EX may be an entirely different story.
Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
[Oliver Peters] “No, I wouldn’t. No one has unlimited engineering responses. Look at something like the SR codec. If you had to choose between FCP X or Avid AMA or Adobe, then I think FCP X goes to the back of the line. Not enough users of SR codec media will be cutting on FCP X by mid-2012. OTOH, AVCHD or EX may be an entirely different story.”
I wasn’t talking about the higher end editorial, really. X won’t be there for a bit. Even so, Sony would be silly not to offer support for whoever wants to use SR. Look at RedCineX, you can go anywhere from that app, even if your NLE doesn’t officially support R3D.
I was talking more about something like broadcast workflows with XDCam. If X gets video out and stabilizes, I could see X coming in handy in quick turnaround environs, like live events.
Jeremy
-
I was talking more about something like broadcast workflows with XDCam. If X gets video out and stabilizes, I could see X coming in handy in quick turnaround environs, like live events.
Yes, I could see that. But it sounds to me like the answer gets back to something that is more or less like L&T. Right now AVC-Intra is supported only through Import From Camera. This is native codec support but not true native camera support. The most “native” today is ProRes from an ALEXA, yet there is no support for embedded source ID numbers. I would suspect XDCAM support would also require Import From Camera, so you’d still lose time to copy/rewrap media.
Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
[Oliver Peters] “I would suspect XDCAM support would also require Import From Camera, so you’d still lose time to copy/rewrap media.”
That’s the thing though, you can start working right away with the media simply importing in the background. AVC-Intra gets the benefit of all the metadata too. You couldn’t have a native avc-i with MXF files as there’s no way to fire them over via XML quite yet, like you can with fcp legacy and an MXF component, or even a way to write a custom importer that I am aware of.
-
[Jeremy Garchow] “You couldn’t have a native avc-i with MXF files as there’s no way to fire them over via XML quite yet”
You can with Premiere Pro and Media Composer. That’s an Apple-induced limitation.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
You can with Legacy as well with third party help. It doesn’t currently work with X though as that infrastructure isn’t quite there yet.
-
[Jeremy Garchow] “You can with Legacy as well with third party help”
I think you are missing the point. You can’t simply drag and drop P2 AVC-Intra files into “legacy”. You have to go through L&T which copies the files. By contrast, Premiere Pro and Media Composer let you directly access and edit with the files without further conversion, transcodes, copying, etc. That’s true native editing. Likewise Premiere Pro and Media Composer allow direct access to RED .r3d files. I wouldn’t recommend working that way, but you do have the option.
Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com
Reply to this Discussion! Login or Sign Up