Bill Davis
Forum Replies Created
-
[Herb Sevush] “I hate to tell you, but however it was that wrote the “mediaball” article you pointed too is an illiterate dunce. If his understanding of media content is no better than his misunderstanding of “Moneyball” than I don’t think his ideas should carry much weight.
Herb Sevush
Zebra Productions”Herb,
I’m trying to understand your post.
But I can’t find a reference to anyone mentioning “mediaball” or “moneyball” or anything similar in the posts above.
Am I missing something?
And who’s the “dunce” involved?
Something has clearly angered you, and I’m trying to decide whether or not to take your comment seriously, but without context I’m baffled.
“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
-
Honestly glad it worked out for you.
Take care.
“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
-
Olly,
You’re kinda over-thinking this.
FCP-X will run fine on any MacBook Pro from the past couple of years. Period.
The better the laptops specs, the faster it will run.
This is NOT something that’s all that “fragile”
As an example of that, I have one MacPro system with an incompatible graphics card that is NOT open Cl compatible. That system would NOT let us “download-install” FCP-X because of the card issue.
BUT.
When I used target disc mode to move a from my laptop to that old system for backup – and decided to try running it – FCP-X actually opened and ran pretty darn well!
I’m sure Apple doesn’t want people running the new code on old, tired hardware because we all know EXACTLY what would result – a flood of posts from people going “it’s SLOOOOOW” and “it’s a DOG.” when the REAL problem is they’re trying to use it in a setup it was NEVER intended to be used on.
So take a deep breath and relax. You’ll be fine.
“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
-
[Rafael Amador] “BTW: Beware of the beta-testers and trainers.
“Yep, gotta “beware” of those folks, cuz all they’ve ever done is help smooth the path toward the effective use of …
every single solitary piece of software that’s ever been used for anything by anyone.
useless gits.
: )
“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
-
Not sure I agree.
It’s so astonishingly easy to “red-x” ranges of your clips in X and achieve a very rough “first cleanup” (kinda a stage prior to SELECTS) and start building your initial database with EXCLUSION ranges – that I don’t think I’m EVER going to just send out “wall to wall” footage again.
Doing that is like doing an outline before you start writing. It focuses your attention. It also starts your editing database. Which encourages the editor to “think” like FCP-X rather than continue to look at the editing process through the old “build everything in the timeline” traditions.
I think that’s very useful. But YMMV.
“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
-
That’s kinda why FCP-X is so persnickety about you not “finder dragging” your source media around but using the internal MOVE PROJECT facility instead. The underlying database is happy to reach out and link to anything in a place it expects it to be, and even if it’s not there at first, it will toss up it’s REDSCREEN display and wait patiently, then when the stuff IS again available in the place it expects to find it (like when you mount the source card or drive or image) it’s really fast to re-establish the links…
but it is NOT the same process as the old “look around so that you can “reconnect media” that was the standard in Legacy.
Completely new process that needs a bit of getting used to if you’re accustomed to the old process.
“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
-
[Olly Lawer] ” I was just making sure that it wasn’t a glorified version of iMovie and not being able to complete some of the work I do.”
Ah the power of “memes”
Try this.
What if it IS a “glorified iMovie” – what’s exactly wrong with that?
iMovie, by ANY measure is a wonderful tool for the casual video editor. And it was released at a time when there were LEGIONS of people who wanted to do just that.
I bet in 20 years if you survey the TOP pros in editing, a serious percentage of them probably got their FIRST taste of editing via iMovie. In fact, in many ways it was a REVOLUTIONARY tool for people who just wanted to make a simple family movie or for a young person wanting to put their stuff on YouTube.
Want a better “meme” for your friends – try this.
FCP-X is “iMovie PRO, the same way a DUCATI is a “Bicycle Pro”
They are ignorance equivalencies to anyone who actually understands what each of those things are.
Simple as 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
-
[Daniel Frome] “I think FCPX team ought to give their testers a healthy dose of beta blockers. Maybe they’ll quiet down and get some work done this time around.”
(I assume from your post that you understand the development process deeply enough to prescribe heart meds for them ; )
So what insights into software development can you provide us about why the X dev team is so “inefficient” about this?
Or would you prefer that the moment they get a feature “rough-coded”, they should just distribute it to everyone and let the chips fall?
The one CLEAR message from this thread is that the “first quarter” update is firmly in its beta test cycle.
Good.
That”s what we all want, isn’t it?
“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
-
Why Neil?
Didn’t the guy from ABC Sports pop up here and say that the PROS working in the big network trucks initially were grumpy, but when they noticed how the database stuff could make their lives a LOT easier, they all started changing their tune and embracing what the new approach does really well?
Perhaps Outpost simple is having the same kind of experience.
Once they saw how the features fit in what they’re doing – they stopped focusing on what’s currently missing and found things that it DOES that helps them do their work?
That’s a little bit similar to what happened with me.
I was struggling my first few weeks with it, then when it “clicked” the hassles started to drop away. Then when I had to go back and cut something on Legacy, I found myself DEEPLY missing a whole LOT of what I’d suddenly become accustomed to in X.
Different strokes, for sure. But why presume that because it’s not working for you – that means it’s going to disappoint everyone. Isn’t that a bit short sighted?
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
-
It’s just another list concentrated on what X “doesn’t do” compared to Legacy.
That’s a pretty easy list to develop for any of the 2 million users who know legacy.But whenever you set your brain to that kind of “glass half empty” state, it’s easy to miss the other side.
FCP-X may not be a play to replace your entire editing workflow IMMEDIATELY (tho some like me will, and do so happily) it’s largely a play to get ready for a possible future of where editing may be going.
Let me expand, if I may.
I believe the engineers at Apple looked at where the industry is going – and built a product for that future. This means core assumptions that might be in conflict with how a LOT of editors are doing things right now.
If that’s your primary goal – to “fit in” to how things have been done (which is perfectly rational and may even be CRITICAL to a particular editor) then you should look at other tools.
If you have the ability to make an inexpensive bet on getting familiar with a NEW tool, that works quite differently from ALL of the old tools – and that was designed around what a team of extremely smart video professionals (who are known to have developed the most successful editing platforms of the previous era!) have seen as requirements for the future – then you probably should ignore what it CAN’T do now and start learning about what it CAN do for YOU, both now, and in whatever future you see for yourself.
What you decide is your business. None of us can tell you how adaptable to change you might be, how much time you have for personal development, or how well FCP-X will “fit” in your unique situation.
All we can tell you is that it’s a new tool. And many of us who have decided to learn it are seeing a whole lot that we feel is innovative and valuable for where we think editing is going.
We can tell you that it WORKS for most editing tasks right now. But not all. And right now, fewer at the esoteric top end of the professional space than in the vast “general editing” tasks area where it kinda ROCKS in my personal opinion.
It’s pretty much that simple.
Nobody knows the future.
All I personally know is my present – and X is doing GREAT as a big part of that. I’m getting my work done. My clients like that work. And I’m re-energized by the feeling that I’m moving my brain out of what I USED to do – and into something new and exciting.
I like that.
YMMV.
“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