[Charlie Austin]

[Mark Morache] “Grrrr… this is frustrating. I tried it again and it got to frame 5109, which is a few seconds from the very end.”

Try deleting *all* the project render files, and don’t re render it before you export it. Sounds like corrupt render files, or (hopefully not) a corrupted master file. If that works, run disk warrior or at least disk utility and check your drives…

————————————————————-

~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~

[Charlie Austin]

[Bret Williams] “Yeah, this was a finished, consolidated project stil on the raid. I have the original camera files elsewhere, but it screwed up other stuff too, like AE renders and converted stock media. Going to be a pain in the a to repair it all. Probably 40 or 50 shots. One by one if the QTedit doesn’t work.”

Bummer. i’m of 2 minds about this… One mind says that FCPX is being ridiculously anal about relinking. Which is probably true. If I cut from offline pix with window burns etc, and then want to relink a cut to final picture, with exactly the same TC and duration but in a different format etc, is that even possible? it should be. The old “This may blow up in your face. Do it anyway?” dialog. ;-}

The other mind says… what kind of idiotic app writes data to a master file without at least warning you it’s doing so? At least FCP 7 would say “you’re about to modify a source file. are you sure you want to?”

Oh well… more things to complain to Apple about. 🙂

————————————————————-

~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~

[Charlie Austin]

[Oliver Peters] “There are way more workarounds with X than with “legacy” or PPro. None are as good as Avid Unity/ISIS/Interplay or apparently Lightworks. I think there’s still a lot of work to be done.”

While i agree with your assesment of Avid etc, I think that with the fix I mentioned above, it’s now pretty much on par with FCP Classic, with a couple added steps. I guess one can already do full Event/Project sharing with X using SAN locations/Sparse disks, though that belief is based on others experiences rather than my own. But as far as handing sequences back and forth in a centrally shared media environment (if files are local it’s a problem, but it would be in Classic as well), It seems like it’s pretty much the same.

In Classic to share an entire project just duplicate it and give the duplicate to the other editor who opens it and goes on their merry way. To share a sequence, make a new project, copy the sequence into it and hand the project off.

In X… .08 anyway… you can just duplicate the event, and hand it off. Editor 2 puts it in their FCP events folder, and opens it up. To share projects associated with that event as well, duplicate them. put them in a folder (all from within FCP X of course, not the Finder!), and give that to editor 2 as well, who puts it in their projects folder. 2 or 3 extra steps, same result.

To hand off a sequence, duplicate + used clips (no render files), hand off duplicate project and new “used clips” event. Done.

So, while not quite as idiot proof as 7, not wildly different now either… Unless I’m missing something.

————————————————————-

~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~

[Charlie Austin]

[Steve Connor] “Thanks, I hadn’t realised that had been fixed”

Me neither, Saw it on Alex4d’s blog the other day and tried it out. Very nice, and very useful fix.

————————————————————-

~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~

[Charlie Austin]

[Chris Harlan] “I think the potential for collaboration in X is just fine, especially with some of the stuff John has shown. Its just not up to the industrial strength that ISIS can bring, but far fewer people need that. “

True. And i may be repeating a post I made in another thread here… But previously, duplicating a project + used clips, or duplicating an event, copied all the original source media to the duplicate… even if the original project/event was using referenced media. This made the duplicates A-gigantic, and B-broke all connection to shared media. This sucked . :-/ However, As of .08 that’s no longer the case, it will just copy the symlinks. Huge improvement that facilitates basic bay to bay project sharing – pretty much just like duplicating a project in 7 and handing it to someone else. Getting there…

————————————————————-

~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~

[Charlie Austin]

[Jeremy Garchow] “QTEdit can strip XMP metadata out of Qt files.
“

Just tried it on a file… didn’t seem to work. Fortunately it’s from a project that’s done, but if this had happened in mid job, I would be completely f*cked. Hope everyones sending feedback to apple about this, I have… Oh, and Bret, it’s part of Digital Rebellions’ pro media tools. a free trail is downloadable…

————————————————————-

~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~

[Charlie Austin]

[Oliver Peters] “[Charlie Austin] “I guess you’re right… I’m getting a little thin-skinned lately, which is probably not the best skin type to have. LOL FWIW, I find your posts to be informative and reasonable. :-)”

Thanks. I do realize some of these points sound like a litany of complaints. Obviously if I weren’t using the app productively, I wouldn’t put it in front of clients. That’s far from the case, as I’ve done almost every session through it for months. There are times where I have to tap-dance around some of these items, but on balance, there are way more pros than cons. For me – and others on this list – at least that’s been the experience.”

Agreed. I do think that, in some cases, problems with people’s installations are attributed to problems with X, but that’s understandable. As you point out, for a lot of people, myself included, the pro’s outweigh the cons. And there certainly are cons, but no deal breakers for me. I have to do the tap dance now and again, and I need to keep a copy of FCP 7 around to do things like capture to tape. Which I could do in X with a 3’rd party app, but it’s all going to a central server so why not use 7, since it works.

That’s sort of an example of how I see X’s shortcomings. I know that lack of tape based capabilities is a big deal for some folks. I guess I just look at it differently. The last 2 jobs I’ve started in X have had DV CAM sources. But my reaction isn’t disappointment that X doesn’t do this well, it’s more like “what the hell is wrong with this dept. of this studio?!” They’re kind of in the minority now. We get features from the same studio (and most others FWIW) as nice HD files on drives, but these guys still send tapes? Which have to be captured in real time, sometimes have TC breaks and, my favorite… get eaten by the deck (knock wood) etc etc. Oh well… they’ll change eventually and I’ll work around it ’til they do.

Sorry for that OT rant… i’m just digitizing crap when i could be cutting it so it’s on my little mind. 🙂

————————————————————-

~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~

[Charlie Austin]

[Oliver Peters] “Wow!!!! You are reading a whole lot more into that comment than intended. I would say that about any software. It’s generic. There was no implication at all – please don’t make it as if there was.
“

I guess you’re right… I’m getting a little thin-skinned lately, which is probably not the best skin type to have. LOL FWIW, I find your posts to be informative and reasonable. 🙂

————————————————————-

~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~

[Charlie Austin]

[Oliver Peters] “These happen to be the cons that affect many FCP X users to varying degrees. But they do exist and need to be addressed by Apple.”

This is a reasonable and helpful statement. This: “Aah… But the next version will be soooooooo much better ;-)” really isn’t. The implication being that people who aren’t having these problems, or who have experienced them occasionally at one time or other but aren’t terribly bothered by them, are somehow brainwashed, uncritical rubes who think Apple and FCP X are perfect. That’s kind of a broad brush, don’t you think?

————————————————————-

~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~

[Charlie Austin]

[Julian Bowman] “Sorry, I just hit reply, I wasn’t aiming my post at you per se, but at those whom it describes. As I tried to express there is some good debate on here and I have learnt from it… In fact without this forum and following the sensible threads I wouldn’t currently be using FCP10.0.7. But there are also some right frustrating fan boys on here too.

No problem, I actually share your disdain for “everything is perfect, you’re doing it wrong!” posts myself. They’re as unhelpful as the “it’s iMovie Pro and Apple hates pros!” posts… Which have been getting under my skin a lot recently for some reason… (and that wasn’t directed at you by the way, just to pre-clear up any potential misunderstanding) 🙂

[Julian Bowman] And yes, I am jealous of those with similar set ups having no lag issues. I want to see them running to see how much better they are than mine and I’d love for a tech person to fix my set up but I don’t know who to look for to try and hire someone to do it. So my experience is currently frustrating beyond belief.”

Well, I understand the frustration. And as a self certified geek, I’d be happy to help, but as I’m 6000 miles away here in LA I guess that won’t work. 😉

————————————————————-

~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~