Welcome to our community

Be a part of something great, join today!

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 :)

Why everyone is so painfully wrong about FCPX

conrad gaunt said:
You don't need layers or tracks to create an EDL, and their presence in your edit will likely cause your EDL to fail upon import into another app anyway since every app interprets the "non-existent" EDL standard differently..

All you need is some paper and a pencil.. its definately the most reliable system anyway
Click to expand...


FYI, I send XML's with plenty of layers to Smoke on a regular basis and haven't one issue. Same goes for EDL's or AAF's from Avid to Smoke, DS, EQ - you name it. Hell, I just bought Storm and sent an XML to it... And wow, can u believe it, it conformed the RED sequence. Pencil & paper... Please tell me you were joking because that's "painfully wrong" statement :rolleyes5:
 
Emery Wells said:
...Roughly 2 years ago someone at Apple did the following:

1. Launched Xcode
2. File > New Project
3. Stared at a blank white screen
Click to expand...

Emery Wells said:
Their decision to support iMovie and not FCP projects is dead simple. iMovie shared code and it's easy.
Click to expand...

So actually it went like this:

1. Launched Xcode
2. File > Open...
...iMovie
 
Jake Bastian said:
So actually it went like this:

1. Launched Xcode
2. File > Open...
...iMovie
Click to expand...

Haha, I'll give it to you Jake, that was funny. In reality that is probably very much what happened but from a development point of view, that's hardly noteworthy. Just because it shares code (it also shares the same AV Foundation framework) doesn't make it the same product. OSX is written on a foundation of Unix but they are clearly not the same product. Foundational code can bare very different children.

There has been some good healthy discussion in this thread and a few of you have made some very solid points that I do agree with. Apple made mistakes, some engineering, but mostly communication.
 
Here's the elephant *still* none of the defenders of FCPX are addressing:

Assuming that in a year we'll have most of the features we want (from the sound of it from 3rd parties but whatever).

How do we collaborate on an NLE that doesn't have set Tracks?

For me that's the big question, because that's something that I'm having a hard time envisioning.

I can imagine the rest of the missing functionality coming back, or finding workarounds, but without Tracks or even a "Track Mode", I can't imagine this in a serious post workflow right now.

EDIT: Maybe metadata can replace tracks, and maybe that's the "future", but I see that as a paradigm shift that may take a while, and should be eased into.
 
Jason Svatos said:
Don't you love it when new software comes out? ;)
Click to expand...

Especially when it's named as if it's an upgrade to old software.

If Microsoft decided to release a program called Microsoft Word 2012... that couldn't load old .Doc files... people would be pissed. Even if Microsoft used "Everything just changed" as its tagline.

Imagine if OS X couldn't read files made on OS 9.

You can't expect v1.0 sympathy and call it Final Cut Pro 10 (eg cashing in on the sales loyalty from the name Final Cut Pro).

It's a problem if a program called Final Cut Pro can't read Final Cut Pro projects.

If it were called Final Cut X or iMovie Pro or just something new altogether, and Apple had given people some advance warning I guarantee you that the outcry would be 1/10th of what it is now. But Apple would have lost sales - so they chose the cash grab instead and decided to take the heat. Their decision.

Jason Svatos said:
I find it interesting that out of everyone crying about the lack of native R3D support... the folks at RED aren't really part of them. Just an observation.
Click to expand...

If I were RED I'd be diplomatic. It's like working with North Korea - if you want them to implement something internally, you can't insult them at the same time. Also, I'm sure they're working on stuff together and have signed an NDA.

I mean come on... awesome R3D support in FCP X has to be coming at some point.

Carrot & stick is the right approach to getting results: the carrot of Red being very nice to Apple. The stick is all of the FCP users threatening to leave!

Bruce Allen
www.boacinema.com
 
I didn't think it was Final Cut Pro 10 - I thought it really was just an X this time. Didn't think they'd jump from 7 to 10. If there's actually a "FCP10" listed in there somewhere, though, please correct me.
 
I think it might just have a little something to do with the Roman numeral X, like in OSX. Maybe? :idea:
 
Joseph Mastantuono said:
PS: Also, in playing with the software for a few hours literally just getting a couple clips in, futsing with them on a timeline that's under a minute, playing with one effect, I somehow have a project file of 2.5gb. I turned off all the "auto" stuff I'm aware of, and it's likely just background rendering or something, but it's highly disconcerting in terms of project/drive management over a big project..
Click to expand...

It's more than highly disconcerting. Wait until the first person attempts to a cut a full length feature on this app in it's current state - designed and tested for web videos.
 
Ben Rojas said:
FYI, I send XML's with plenty of layers to Smoke on a regular basis and haven't one issue. Same goes for EDL's or AAF's from Avid to Smoke, DS, EQ - you name it. Hell, I just bought Storm and sent an XML to it... And wow, can u believe it, it conformed the RED sequence. Pencil & paper... Please tell me you were joking because that's "painfully wrong" statement :rolleyes5:
Click to expand...

Its not painfully wrong, and I'm glad you have apps that are playing nicely, just don't rely on it with apps you haven't tried.

Paper and pencil never fails, thats how I do it, with burnt in timecodes, no joke. Its also how it was done for a long time. I tend to use more than two apps, some of which don't support anything other than image formats, and no EDL format at all, but I need to use them to side step weaknesses in some of the apps that do support EDL. I should add, I've never worked on anything that has required me to use a proxy workflow, and meet a tight time line. For those, I shake and bake to lossless formats and detach from source footage altogether.
 
Could someone who has played around in Final Cut Pro X answer this question for me? Because this is probably my only concern.
It looks like I will be locked down to a single time line for any given project and my current style of working is to edit a short scene by scene and then assemble them afterwards via nesting into another sequence is this even possible with the new FCP? Or am I expected to edit a short from start to finish in one timeline no matter how long the short, this method also allowed me to place my 2:35:1 mask on a scene instead of having to apply them one by one to every friggin shot and I could take it off or on much easier.
 
Why do we need YET ANOTHER run-away thread on FCPX???

Did the other one that's now like 1000 posts get too long or something?
 
Craig W. Bickerstaff said:
Could someone who has played around in Final Cut Pro X answer this question for me? Because this is probably my only concern.
It looks like I will be locked down to a single time line for any given project and my current style of working is to edit a short scene by scene and then assemble them afterwards via nesting into another sequence is this even possible with the new FCP? Or am I expected to edit a short from start to finish in one timeline no matter how long the short
Click to expand...

No nesting sequences. In fact, there is only 1 sequence per project as far as I can tell. You get alternate versions though. Not sure how to describe it - it's kinda different to everything else. Don't want to piss anyone off here but the best way to describe it is like iMovie 08.

The workaround is: you can group a chunk of clips together and work with them as a unit. So you could take your separate scenes and group them.

Craig W. Bickerstaff said:
this method also allowed me to place my 2:35:1 mask on a scene instead of having to apply them one by one to every friggin shot and I could take it off or on much easier.
Click to expand...

Well the way FCP did it WAS always backwards. In Avid, you had a Mask filter and could just put it on V10 or whatever and it would mask everything beneath it. That's the way to go IMHO.

In FCP X, I haven't figured out how to do 2.35 or 2.4 or any kind of different aspect ratio projects natively in FCP X. They also took out all of the non-standard resolution options. That NY Times guy says you can set any resolution but I think he's wrong - setting Custom resolution for me gives me only the option to select 960x540 or 640x480. There's option way to type anything in.

My guess is to create a black mask as an image file or in Motion and then kinda attach it to the first clip in your timeline (the 2-pop?) and let it float on top? Not a biggie but kinda ruins the beauty of the Magnetic Timeline :)

The only thing I can find within FCP X itself is to make 2 solids (one for the top and one for the bottom) crop them to fit, then float them on top.

Umm... help?

Bruce Allen
www.boacinema.com
 
You must log in or register to reply here.
Back
Top