Kristin Leys
Forum Replies Created
-
What can I say. Not a fan of the design.
The pseudonym is very old, bit like me. Some handles you just keep using. Even if it does manage to mangle 2 languages at once.
-
Good to know. If the email thing doesn’t pan out soon I’ll make that call.
Thanks.
-
And this thread has perfectly illustrated why I’ll never trust Apple with my business again.
Someone from Adobe has chimed in.
When I have questions about Adobe or Avid products, I get to talk to people who can help me. People from the company making the products. And people who will influence the direction of future versions.
Apple is a blank wall. A sprinkling of the foulest PR spin. And nothing, absolutely nothing else.
So no, I wouldn’t wait for FCPx to ‘evolve’, since the people responsible refuse to explain where they’ve started from, let alone where they want to go.
-
No problems here.
2008 Octo Mac Pro, Lotsa Disks, lotsa messy data.
Cutting mixed format HD without issue.
-
I’ve thought about SSD myself.
Yes they are faster than HDD. By how much depends on what you’re doing.
RAID configurations of SSD can be insanely fast.
More recent versions of SSD have internal garbage collection, and do not suffer the slow down issues of earlier generations.
This makes OSX’s lack of TRIM a non-issue.
SSD is stonkingly, nose bleeding, expensive. Especially at larger capacities.
And to make a difference for most editing work you’ll want the extra speed on your media drives.
With SSD as expensive as it is, I don’t think it’s worth it given I don’t have a problem working from a healthy HDD RAID setup.
What we really need is for someone to give us the new, 64bit, rewritten, multi-threaded, stable, Final Cut. And when that comes along and uses more than 10% of my machines current potential. Then I’ll take another look at SSD. Maybe.
So basically, when hell freezes over.
-
Aside from the overly complex mixing of formats…
I think you have a problem with missing render files.
It’s what I first thought of when I read your post.
I’d toggle the monitoring off and on for the video tracks ( make fcp ‘lose’ any renders ) and see if the offline problem keeps happening at the transitions.
Just my humble 2 cents.
-
Final Cut goes 64 bit after Quicktime is given a complete overhaul.
Quicktime needs to be modernised, rewritten, replumbed, etc.
Quicktime X was the first part of that project.
Once that foundation is in place, possibly in 10.7 then Apple can release a 64bit Final Cut Pro.
Otherwise they could take the ‘Smoke’ route and write a dynamic 32-64bit translation engine. But that seems very un-apple.
Apple know it needs to happen, and the software engineers involved would love to be moving faster. But it’s a bloody big job.
-
I’m using latest versions of everything,
OS: 10.6.2 FCP 7.0.1 etc, etc… (soon to be 7.0.2)
All running on a 2008 Mac Pro, 2.8Ghz, 16GB, and a BlackMagic Decklink card.
Very stable and reliable for my projects which span DV through various HD formats.
I run a very lean machine, no extra software, very few plugins.
The problems I do encounter invariably lead back to Motion. But that was the case in my previous 10.5.8 setup as well.
Of course, I aim just one man and his machine, your milage may vary.
-
[Walter Soyka] “Because that’s cheating!
In all seriousness, I’ll play the devil’s advocate with a few good reasons to do this as an effect in post:”
Fair call. I love having options in post. I am an editor after all.
Of course you could just shot your DV footage off a monitor, with a cell phone. Best of both worlds.
All I wanted to point out is that it’s possibly to do a lot these ‘tricks’, ‘in camera’. You don’t have to do everything in post.
-
Umm… why not just shot it on a cellphone?
That’s what we did recently for a similar job. We did nothing in post except for a transcode to ProRes to avoid hassles in editing.
Worked a treat, client was blown away.
No render times either.