Beats by Dr. Dre???

[David Lawrence]

[Steve Connor] “The only thing that happens is that the clip to the right of the gap is lengthened as the gap clip moves, the original edit frame in that clip stays in the same position. “

Right, but even though that doesn’t change picture, it changes sound. It’s now a different sound edit. Since picture is covered, sound is likely the reason why it’s there in the first place. Or maybe the connected clip above is compositing over it. Lots of reasons why you might not want the head to change.

[Steve Connor] “I will not agree with your statement that the entire timeline is “ripple only”, because apart from the gap behaviour, when you use the position tool, it isn’t.

What I can say, through my months of experience with FCPX on a range of projects, is that the issue doesn’t affect how I edit in FCPX at all.”

Fair enough, I won’t try to convince you. I believe you when you say it’s not a problem for the way you work. We’ll have to agree to disagree on this one. I find the bug interesting because I think it reveals something about the magnetic timeline’s programming logic and conceptual model. I believe the timeline is working exactly as designed. The bug is with the Position Tool. I do hope the next update addresses it. The fix seems pretty simple and once it’s fixed this is all moot.

[Steve Connor] “I may disagree with some of your logic but I have a great deal of respect for the way you approach things which makes me question and re-examine the way I work in FCPX, every time you pursue an argument like this I learn something new and that’s certainly a good thing.”

Thank you! It’s completely mutual. I really appreciate you pushing me to sharpen my arguments and especially appreciate learning more about FCPX from you. Even if we disagree, I really enjoy the dialogue. Thanks again!

_______________________
David Lawrence
art~media~design~research
propaganda.com
publicmattersgroup.com
facebook.com/dlawrence
twitter.com/dhl

[Mitch Ives]

[Don Walker] “If everybody on this forum would look at FCPX for what it really is, I think we could all sleep easier at night.

FCPX was / is a totally different but completely unfinished NLE that was pushed out the door at least a year early, by a leadership style, that wanted to upstage a competitor at a trade show.

When the big Q1 release comes out, I would suspect we will have a much better understanding of what X is supposed to be. I also suspect there will be a lot more than just external monitoring and multicam, out by the end of the year. “

My point exactly. At the risk of lowering the bar too far for people like Bill and Steve, my problem isn’t with the interface or the design criteria, it’s with the amateurishly unfinished nature of it. It was released with a titler bug that two guys writing software in a garage would have caught. Seriously?

The AutoSave doesn’t work, which wouldn’t be a problem if we had manual save, but we don’t. This is causing a lot of issues for a lot of people, as evidenced by the threads in this forum.

You can’t keyframe the color correction filter? Seriously?

And of course no external monitoring… and/or Multicam (which I acknowledge not everyone cares about).

For me, the next update will tell us a lot. It’ll tell us how serious Apple is about fixing defects and filling in the holes in the Swiss Cheese that is FCPX.

Mitch Ives
Insight Productions Corp.

“Criticism may not be agreeable, but it is necessary. It fulfills the same function as pain in the human body. It calls attention to an unhealthy state of things.” – Winston Churchill

[Bill Davis]

[Mitch Ives] “My point exactly. At the risk of lowering the bar too far for people like Bill and Steve, my problem isn’t with the interface or the design criteria, it’s with the amateurishly unfinished nature of it. It was released with a titler bug that two guys writing software in a garage would have caught. Seriously?”

BS. Pure and simple. Mitch, we’re friends. But you’re assessment here is just plain wrong. There’s nothing “unfinished’ about software that has let me meet five different delivery deadlines with paid work over the past month. It’s finished, it works fine on my hardware. Period. Features for the future is a reasonable issue of contention. But if it’s not “operating” for you – you’ve got something wrong. Because it’s operating for me fine.

[Mitch Ives] “The AutoSave doesn’t work, which wouldn’t be a problem if we had manual save, but we don’t. This is causing a lot of issues for a lot of people, as evidenced by the threads in this forum.
“

Again, sorry, but I have to disagree totally. AutoSave has not just worked well for me, it’s worked AMAZINGLY well. Whenever I start doing really complex or fast operations (particularly when I start chaining my mind rapidly, doing, undoing, then re-doing things – which yes, sometimes causes it to crash.) X recovers about as flawlessly as any software I’ve ever seen.

I”ve done that half a dozen times in the past month of high pressure work. And each and every time when the software re-loads, I’m back to almost the EXACT state of the project the second before the crash.

I’m NEVER seen “auto save” work like this before. And I think it’s one of the best features of the whole product.

I suppose it requires some consistently in setup, system config, and hardware – but as you know, I’m not the best hardware guy on the planet and I’m running nothing but Apple Store basic rigs here. Nothing hot-rodded. I’m on a stock i7 MacBook Pro 15 running Lion – And X under Lion is the most graceful crash recovery construct I’ve ever seen.

FWIW.

“Before speaking out ask yourself whether your words are true, whether they are respectful and whether they are needed in our civil discussions.”-Justice O’Connor

[Mitch Ives]

[Bill Davis] “BS. Pure and simple. Mitch, we’re friends. But you’re assessment here is just plain wrong. There’s nothing “unfinished’ about software that has let me meet five different delivery deadlines with paid work over the past month. It’s finished, it works fine on my hardware. Period. Features for the future is a reasonable issue of contention. But if it’s not “operating” for you – you’ve got something wrong. Because it’s operating for me fine. “

So you’re saying that they didn’t ship FCPX with a Titler that didn’t save your changes and instead defaulted back to the defaults? Why are there threads discussing this then? Why did Apple fix it after 4 months then?

[Bill Davis] “[Mitch Ives] “The AutoSave doesn’t work, which wouldn’t be a problem if we had manual save, but we don’t. This is causing a lot of issues for a lot of people, as evidenced by the threads in this forum.
”

Again, sorry, but I have to disagree totally. AutoSave has not just worked well for me, it’s worked AMAZINGLY well. Whenever I start doing really complex or fast operations (particularly when I start chaining my mind rapidly, doing, undoing, then re-doing things – which yes, sometimes causes it to crash.) X recovers about as flawlessly as any software I’ve ever seen.

I”ve done that half a dozen times in the past month of high pressure work. And each and every time when the software re-loads, I’m back to almost the EXACT state of the project the second before the crash.

I’m NEVER seen “auto save” work like this before. And I think it’s one of the best features of the whole product.”

So any of us that shut down and then when we re-launch some of the work we had done is gone are some how delusional? Jeez Bill, even Steve Connor admits its a problem (to his credit).

[Bill Davis] “I suppose it requires some consistently in setup, system config, and hardware – but as you know, I’m not the best hardware guy on the planet and I’m running nothing but Apple Store basic rigs here. Nothing hot-rodded. I’m on a stock i7 MacBook Pro 15 running Lion – And X under Lion is the most graceful crash recovery construct I’ve ever seen.”

It recovers from crashes better than any other program… maybe that’s because it has to?

Mitch Ives
Insight Productions Corp.

“Criticism may not be agreeable, but it is necessary. It fulfills the same function as pain in the human body. It calls attention to an unhealthy state of things.” – Winston Churchill

[Don Walker]

Bill,
I LOVE, editing in FCPX, but there is no way in the world that you or anybody else would convince me that Randy and crew thought the software was ready to be released when it was. They were behind the power curb getting this done and the whole editing world was clamoring for something……. The highest levels of management found out about Avid dominating the Final Cut SuperMeet, and because it wasn’t a flagship product where Steve would present it, It was done in a very sloppy manner.
Now I admit this is a lot of conjecture, but a good percentage of the stuff on this forum is.
In the past couple of days after reading this thread, I think one of the reasons they killed all support of 7, was the need for an “all hands on deck” emergency emphasis on bug fixes and feature upgrades to get X where it needs to be. IMHO

don walker
texarkana, texas

John 3:16

[Steve Connor]

[Mitch Ives] “So any of us that shut down and then when we re-launch some of the work we had done is gone are some how delusional? Jeez Bill, even Steve Connor admits its a problem (to his credit).
“

I don’t get it very often, but it does happen. Instead of doing a safety “save” every hour (which you can’t do in FCPX of course” just check your “undo” is working every hour. That way you don’t risk any more than an hours work.

Hopefully the next release will see versions implemented.

Steve Connor
“FCPX Agitator”
Adrenalin Television

[David Roth weiss]

[Steve Connor] “Hopefully the next release will see versions implemented.”

Nike’s mantra is “Just do it.”

Apple’s mantra is “Just hope!”

David Roth Weiss
Director/Editor/Colorist
David Weiss Productions, Inc.
Los Angeles
https://www.drwfilms.com

Don’t miss my new Creative Cow Podcast: Bringing “The Whale” to the Big Screen:
https://library.creativecow.net/weiss_roth_david/Podcast-Series-2-MikeParfitandSuzanneChisholm/1

POST-PRODUCTION WITHOUT THE USUAL INSANITY ™

Creative COW contributing editor and a forum host of the Business & Marketing and Apple Final Cut Pro forums.

[Mitch Ives]

[Steve Connor] “I don’t get it very often, but it does happen. Instead of doing a safety “save” every hour (which you can’t do in FCPX of course” just check your “undo” is working every hour. That way you don’t risk any more than an hours work.”

Yes Steve, I read your tip on the other forum. It’s encouraging to see people coming up with work-a-rounds. Still, that’s not as good as not having the problem.

The point I was trying to make, which Bill doesn’t seem to appreciate, is not that I don’t like FCPX. I do. There, let me say it again… I do. I see some real brilliance in what they are doing with FCPX.

No, my point is that this product is very “un-Apple”, in that they don’t usually release anything with things like an unworkable titler (fixed 4 months later)… an AutoSave that lets you loose work occasionally (because we can’t manual save)… etc. I expect more from Apple, that was my point… but then I can since I’ve been buying their products for over three decades.

Clearly this was rushed out… I don’t know if it’s because Steve was nearing the end, whether there was some legal issues with FCP7 (as others have suggested). I don’t know the reason, I just know that those of us that have Apple products since the late 70’s are accustomed to better dialed in solutions.

And I still maintain that my point is valid…

Mitch Ives
Insight Productions Corp.

“Criticism may not be agreeable, but it is necessary. It fulfills the same function as pain in the human body. It calls attention to an unhealthy state of things.” – Winston Churchill

[Bill Davis]

[Mitch Ives] “So you’re saying that they didn’t ship FCPX with a Titler that didn’t save your changes and instead defaulted back to the defaults? Why are there threads discussing this then? Why did Apple fix it after 4 months then?”

Legacy shipped without JKL transport functions. They fixed it. We moved on. Same old.

[Mitch Ives] “So any of us that shut down and then when we re-launch some of the work we had done is gone are some how delusional? Jeez Bill, even Steve Connor admits its a problem (to his credit).”

I didn’t say it never happened to anybody. I said it’s never happened to me. And I’m a pretty heavy user these days. My largest FCP-X management problem is clearing off my previous projects to free up render space for the next ones. (Hint: Clear Render Cache is contextual and works for Events when you invoke it from the Event Browser – and clears the cache of Projects when you invoke it under the Project Library – took me a bit of fiddling to realize that.)

[Mitch Ives] “It recovers from crashes better than any other program… maybe that’s because it has to?
“

Some of my timelines have crashed as many as half a dozen times – causing me to slow down my operaion and not “undo” so much. (they tend to be more deadline intensive jobs.

OTOH, I’ve had projects go start to finish without a single crash.

I’m not saying its flawless. Just that it’s effectively getting my work done and I haven’t missed a deadline since I adopted it for all my work.

Nothing more than that.

For me, it’s TOTALLY ready for every day money on the line work.

But I freely acknowledge I’m not everyone. But I’m also not some kind of super user who uniquely knows how to make it work with twine, spit and bailing wire. I’m just a guy with a lot of work right now who cuts most every day on it. And it’s working really well for me.

No more than that.

“Before speaking out ask yourself whether your words are true, whether they are respectful and whether they are needed in our civil discussions.”-Justice O’Connor