Jim Giberti
Forum Replies Created
-
[Don Walker] “You were one of the most positive advocates for X just a few short months ago. I was very encouraged reading your posts about the program.”
When the program works it has some great features, but it’s glaringly unrefined.
I’m actually stunned by how slow it is in almost every way since the “upgrade.
I can’t open a project or move to the open program without the mandatory beachball greeting.The program itself must be corrupt at this point because I’m not exaggerating when I say 15 minutes to render a 12 frame dissolve.
It was fun learning it but it’s been a disaster professionally speaking.
-
[Michael Sanders] “Blimey that’s serious! Did it corrupt the backup’s to?
“Well by the time I realized how bad it was I wasn’t able to work with any version that had al of the graphics and CCing and mastered audio.
It was a mess. I’m just now, having seen the project make it to the airport and with some sleep, about to drag one of the versions of the film project back into the project folder and see if there’s anything I can do with it.
Here’s how bad it was.
Everything, the whole edit and all finishing was done in a lovely organized Primary and a few neatly organized Compound Clips.
All that needed to be done was to add a stack of names in order to customize the film for different dealers around the country.
The promotional film, TV campaign, radio campaign and magazine campaign were all going on branded thumb drives to be given out after the showing at the big dealer conference.That was it – the last piece of months of work from our shop, all we needed was to output lot’s of versions of a 2:30 second promotional film for their showrooms and websites. It was a dealer name and url on a PS graphic. Two freaking layers over Pro Res footage.
If I try and open any version of the project now, with just those 5 seconds of graphics at the back, it will open fine, but the moment you try and click anywhere in the “timeline” the program freezes and crashes.
Say what you will, but I’ve never experienced this level of damage or instability from any version of any program we’ve ever run.
If it were a drug, the FDA would pull it from the shelves.
-
[Tom Wolsky] “None of these applications will run on your computer.
“That might be the best news he gets about FCPX.
As of our last lost week “working” with the buggy mess that is fcpx 1.0.3, I am officially advising anyone and everyone to stay clear of it until Apple makes it a professional, stable environment. -
Well Don, thanks a lot for writing my post for me – seriously.
Mine was going to be titled, “X eats it’s own children”When I got some sleep and recovered from my latest X disaster I was going to write what you did, almost verbatim – except “past my bedtime” actually meant almost 72 hours with no sleep.
Through it’s endless stream of bugs and crashes (remember I went for about 4 months without X crashing once before 1.0.3.) I dreamed of FCP7…sh*t I was dreaming of a circa 1980, linear, cable access facility.
Anyway, for the second project in the last three weeks, the “X Factor” (my new expression for the consideration one must have before risking serious work in this program) corrupted my projects, media and drive.
I have a project that’s been in edit for 4 months that is so corrupt that apparently anything associated with it is also wrecked.
It’s almost impossible to imagine how often and how many things will crash this turd, and then the impossible things that it does to your work and files.We got the film and two part TV campaign out through the worst professional/technical situation I’ve ever had to work through – and I’ve been in this business for a long time and could write a horror novel on just those types of stories.
I’ve never encountered, even in the earliest pioneer days of NLEs, the kind of bugs, corruption, lack of responsiveness of this mess of a program.
It literally chokes on simple titles over a properly resed photo. At times, it would take 15 minutes to render a 12 frame dissolve. And none of that begins to describe what it did to our work.Randy would not have wanted to be at Imagination Farm this weekend.
-
[Herb Sevush] “after 4 minutes of his voice and pacing I was willing to confess to anything. That presentation should be sold as a military interrogation weapon.
“Never in my entire freaking life did I think I’d type the dreaded LOL.
But I am. -
This could have been produced just for FCPX users.
I live at the beach now. -
[Lance Bachelder] “Ouch… that was embarrassingly pitiful. “
Ouch, that’s tow “ouches” in a short thread.
-
[Andy Field] “Like many FCP 7 editors, I would love to like FCP X…but with its trackless, still doesn’t play well with others (we need to Autoduck to go Avid every day which still works fine with FCP 7) No audio mixer (am I the only one who loved ability to mix and record keyframes with virtual faders in real time?)
…no tracks, no viewer for eyeline match edits…still no solid broadcast monitoring out…etc..etc..)
As much as it’s new and improved, it feels like a giant step backward for our work flow…Wish it wasn’t because it sure looks like it could be terrific if Apple had listened to editors who use this for broadcast and film every day”
I commiserate Andy. I really like the new program and yet don’t like it at the same time.
It’s schizophrenic.
I’ll do a project like I am right now and think how much I like the interface and so many of the new features.
But two days ago on a different project I was literally ready to forgo the improvements and go back to 7.At this stage in Apple’s development of FCP, they should absolutely be offering more options not less.
Tracks and mixers and magnets and meta data…they’re all good tools. Apple shouldn’t be reducing and limiting important tools at this stage.There would be no need for their professional users to even be considering migrating to another system if they hadn’t taken an exclusionary route in development.
No matter how smart your idea is, less is never more.
-
Ouch. I want to be kind and all, but that’s really poor stuff right down to the distorted audio.
-
I never experienced a corruption issue in any version of FCP like I’ve seen in X.
And you’re right Tom, you can’t shake it by creating new projects and copying content. I had a spot that I simply couldn’t rebuild from scratch and the agonizingly slow performance, plodding and crashing it took to fix what the bug caused was like working with 4k footage in PP 1.0 on a Quadra.
Even after I was able to output it, it actually showed random color blocks in the Pro Res master.
It’s an ugly X side effect.