Welcome to our community

Be a part of something great, join today!

Register Log in
  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

Evidence of XML in FCPX

Dumbstruck?

Dumbstruck?

I have to admit, I find it curious that no one has commented on this yet. :w00t:
 
noahvolek said:
Everyone is too busy pushing pins into Steve Jobs voodoo dolls.
Click to expand...

Well, no room on my doll because legs and arms are missing and head is only half attached. However i did massage the stomach to hopefully help with keeping him around longer so he can feel all my pain he's caused.
 
Johnny Friday said:
Well, no room on my doll because legs and arms are missing and head is only half attached. However i did massage the stomach to hopefully help with keeping him around longer so he can feel all my pain he's caused.
Click to expand...

:cheers2::w00t:
 
Terry VerHaar said:
According to a report at MacRumors, XML is well on its way in FCPX as some code is already there but not yet activated.

http://www.macrumors.com/mac/

:thumbup1:
Click to expand...

Terry VerHaar said:
I have to admit, I find it curious that no one has commented on this yet. :w00t:
Click to expand...

Well this just kinda backs up Randy Ubilos's annoying email statment that "We never expected anyone to switch editing software in the middle of a project, so project migration was not a priority."

It doesn't piss you off that they decided to add in a Star Wars text crawl... and not finish frikkin' XML import?

I know that Apple is starved for cash so they couldn't have hired a guy to make XML work AND a guy to make that Star Wars crawl work. But if I were Apple, I would have fired the Star Wars text crawl guy and hired an extra "make XML import work" guy. As a gesture of good faith to pros, you know.

But I don't know, maybe they liked the reaction to iMovie 8 not loading older projects.

BTW I am beginning to think this report was perhaps on the money:
"Next version of Final Cut Studio faces setbacks due to resources and disagreements"
http://www.allnewsmac.com/2010/09/3...-setbacks-due-to-resources-and-disagreements/
http://www.hardmac.com/news/2010/09/30/rumour-the-new-final-cut-studio-could-be-delayed

"A few months ago we told you that Apple were hoping to release a new version of their Final Cut Studio suite in 2010. It now seems likely that this target has been missed according to one of our sources. The development of this software suite has suffered significant setbacks and it will be necessary to wait until 2011 to see its release; furthermore, the scope of the project has been reduced.
The idea of having a unified interface has been abandoned for the time being because of difficulties in reaching a satisfactory compromise among not only the various applications but above all between different development teams, those working on Shake the old team who used to work on Shake and those working on Motion. Some fundamental differences of opinion about the ideal interface have hamstrung this part of the project which has now been deferred to the next version, in 2013.
The other thing which has delayed the release of this suite so much is a structural issue. With the enormous development needs in the groups dedicated to iOS and the multiple devices which are now running this new operating system, Apple has reassigned a significant number of its most qualified engineers to work on iOS, drying up the teams working on projects considered less urgent: roughly speaking, all those related to Mac OS X and its associated applications.
Finally, but we're taking this claim with a pinch of salt, we've been told that this situation has really upset Randy Ubilos who's in charge of the Final Cut division."

Bruce Allen
www.boacinema.com
 
*sigh* Even when the pony shows up, there are grumbles that it is late, it isn't as pretty as we hoped and, sadly, it isn't a unicorn. :lol:
 
Bruce Allen said:
It doesn't piss you off that they decided to add in a Star Wars text crawl... and not finish frikkin' XML import?
Click to expand...

FCP X titles are Motion projects. This probably took five minutes.

I found this XML import stuff (and possible references to Python plugins) last week. It has been in my signature for days. It was discussed in the main FCP X thread many pages back, but word doesn't seem to have gotten around.
 
Chris Kenny said:
FCP X titles are Motion projects. This probably took five minutes.

I found this XML import stuff (and possible references to Python plugins) last week. It has been in my signature for days. It was discussed in the main FCP X thread many pages back, but word doesn't seem to have gotten around.
Click to expand...

We had a function in REDcineX called "ExecuteEvilPlanToTakeOverTheWorld" but it didn't actually do anything :)
 
Deanan said:
We had a function in REDcineX called "ExecuteEvilPlanToTakeOverTheWorld" but it didn't actually do anything :)
Click to expand...

I accidentally hit a certain combination of keys while rendering a project and all of a sudden people started raising a statue of Jim outside my window... I force quit the application before it was done -sorry
 
Chris Kenny said:
FCP X titles are Motion projects. This probably took five minutes.

I found this XML import stuff (and possible references to Python plugins) last week. It has been in my signature for days. It was discussed in the main FCP X thread many pages back, but word doesn't seem to have gotten around.
Click to expand...

Chris, I would have been EXTREMELY surprised if there wasn't some sort of XML import in FCP X, at the very least half-implemented.

Nobody is criticizing the idea of implementing Python or XML import, or having a nice database. We all agree with your that some elements of FCP X seem really well designed towards pros.

The issue is Apple's awful attitude.

Showing off at the Supermeet what a FCP 7 project looks like in FCP X... then not allowing the release version of FCP X to import 7 projects... is bordering on false advertising.

Please name another app that couldn't import the project files of its previous version at release.

If they didn't want to implement XML import they could have simply Final Cut Pro X something else.

Bruce Allen
www.boacinema.com
 
Bruce Allen said:
Chris, I would have been EXTREMELY surprised if there wasn't some sort of XML import in FCP X, at the very least half-implemented.

Nobody is criticizing the idea of implementing Python or XML import, or having a nice database. We all agree with your that some elements of FCP X seem really well designed towards pros.

The issue is Apple's awful attitude.

Showing off at the Supermeet what a FCP 7 project looks like in FCP X... then not allowing the release version of FCP X to import 7 projects... is bordering on false advertising.

Please name another app that couldn't import the project files of its previous version at release.

If they didn't want to implement XML import they could have simply Final Cut Pro X something else.
Click to expand...

My take is that Apple wanted to get some version of FCP X out there as early as possible, was aware the initial release was more suitable for prosumers than pros, and just didn't bother to communicate effectively about this. It's a little hard to figure out why. Part of it might be that they thought they were being more obvious about the "prosumers now, pros soon" thing, and didn't expect people to read as much of an "Apple is abandoning pros" message into it as some people have. Part if might be that certain features were cut late in the game because they weren't quite release quality, and there wasn't time to put together an explanation fit for public release.

The information passed out to Pogue, Studio Daily, etc. is almost unprecedented for Apple. It really does look to me like they're trying to communicate, but their extreme corporate caution about releasing information on future plans is getting in the way. Any formal statement probably has to be crafted extremely carefully and approved all the way up to Tim Cook (maybe Steve Jobs). And if they're planning a significant update soonish, say around the release of Lion, I could easily see them saying "Screw it, we'll just let the update speak for itself, a couple of extra weeks of Internet freak-outs won't mean anything in the long run".
 
Chris Kenny said:
My take is that Apple wanted to get some version of FCP X out there as early as possible, was aware the initial release was more suitable for prosumers than pros, and just didn't bother to communicate effectively about this. It's a little hard to figure out why. Part of it might be that they thought they were being more obvious about the "prosumers now, pros soon" thing, and didn't expect people to read as much of an "Apple is abandoning pros" message into it as some people have. Part if might be that certain features were cut late in the game because they weren't quite release quality, and there wasn't time to put together an explanation fit for public release.

The information passed out to Pogue, Studio Daily, etc. is almost unprecedented for Apple. It really does look to me like they're trying to communicate, but their extreme corporate caution about releasing information on future plans is getting in the way. Any formal statement probably has to be crafted extremely carefully and approved all the way up to Tim Cook (maybe Steve Jobs). And if they're planning a significant update soonish, say around the release of Lion, I could easily see them saying "Screw it, we'll just let the update speak for itself, a couple of extra weeks of Internet freak-outs won't mean anything in the long run".
Click to expand...

Chris, I think your and my takes are 100% in agreement (although from different perspectives!). Anyway, it's nice to have a civil chat! Only took 3 threads and a week for the interwebrage to subside!

Anyway, we'll see what Apple does. For now though, I am getting a refund on FCP X and using the cash to buy an Avid Transport. We have one at work and it's a really nice responsive jog/shuttle - not like those other ones which emulate keyboard commands. *For now*, for what I do, it speeds my editing up more than the magnetic timeline.

Will keep an eye on FCP X of course and am very happy to repurchase it the moment they add features that make it useful in my workflow.

And for the record I really really hope that Apple just make FCP X awesome soon. It would make the post world more fun and only lead to good things and new innovations from not only Apple but their competitors.

And Chris - if you find more info on the Python stuff, let us know!

When I onlined a Red feature in Premiere from an FCP 7 offline, I ended up having to write a bunch of scripts - eg to parse EDLs and collect R3Ds across drives so that Premiere can re-link, etc. Also to handle VFX versions.

Having scripting integrated into the editing app would be the logical step forward and something I've been asking Avid to do for a long time. They have a console built in already, for heavens' sake! And Adobe has scripting in After Effects but not Premiere. If they are not prepared to go the last step of the way and Apple is, more power to Apple.

Bruce Allen
www.boacinema.com
 
Thanks for posting this, there is hope...
 
Chris Kenny said:
The information passed out to Pogue, Studio Daily, etc. is almost unprecedented for Apple. It really does look to me like they're trying to communicate, .
Click to expand...
I would disagree. That was PR damage control.

- Oliver
 
It's been said ad nauseam, but Apple would have avoided 90% of this by not withdrawing 7 from sale. For me, it's still the best product. Apart from their usual, bullish " no looking back" attitude, it makes little sense.

Support for 7 under Lion, and renewed web support is a huge step back for a company as pigheaded as Apple. I seriously doubt they'll swallow their pride enough to recommence selling it, but here's an idea: Give it away as a download with every sale of X. They did this with iMovie when 8 came out - after an outcry. It's not perfect, but it would have one big side effect - it'd sell a lot of copies of X...
 
You must log in or register to reply here.
Back
Top