Erik Lindahl
Forum Replies Created
-
Nice to see the 2012/2013 iMac being on-par with the almost 3 year old MacPro! 😉
Nah, but as you say – bang for the buck or “small formfactor” computer and the iMac is an interesting choice. It even beats the Quadro-cards in After Effects. I wonder how this machine fairs against the HP Z1. I also wonder how a real 2012/2013 MacPro would stand against this machine.
-
The handling of projects and sequences clearly is one of FCPX’s “Achilles Heels”. It clearly wasn’t design with TVC versioning in mind. Just the simple fact at how hard it is to visualize say 30 edits is hard, if not impossible.
This is really something they need to look into on top of the fact being able to have multiple sequences open at once. Very limited now. But that’s, I guess, part of 10.0 being 1.0 (or well 1.7 now I guess).
It almost seems more efficient using one single timeline and FCPX index-feature for some work. Much like its done in Protools. Very confusing way of working IMO but it might get the jobb done.
-
Ah, yes, the Fusion Drive seems like a great option. It’s on the pricey side but again – worth it for a work machine. It does make backups even more important though since you basically double your chances of a drive-failure. You’d probably want some kind of external RAID for media also.
-
I’d imagine the i7 with it’s hyper threading (8 virtual cores) and the almost 10% faster MHz will benefit an app like FCPX quite a ot. As a work-machine it’s defiantly worth it.
Don’t forget about the 680MX card – it’s a powerhouse (relatively speaking). But people are comparing it to a desktop GTX670 which by all accounts is a great card. It’s also recommend at least 16GB of RAM. 32GB wouldn’t be bad though (64-bit apps like FCPX and AE are memory hogs).
-
The T-Tap is great value. Do note it doesn’t support hardware downscale however.
-
Very interesting thread. I was battling this exact issue yesterday. I’ll second the request of better conform-tools and image sequence support across AE / Premier. Speed Grade does seems to have promise for sure though. Hopefully Adobe can integrate it’s image-support-bits to its other tools.
GlueTools was awesome back in the day. I think however its development is dead as it heavily relies on QuickTime and as of 10.7 and 10.8 it’s not something Apple is developing. It would IMO be best to have image sequence support in the OS if possible.
-
If you just want to render clip with TC burnt in Compressor can do that for you as well.
25s 1080p25 ProRes 422HQ clip to an “Apple Device 5 Mbps” on my MacPro 2008 8-core we’re talking:
– 78 seconds with TC filter on
– 68 seconds with TC filter offNot the fastest encoder on the planet I’ll give you that but roughly 3X realtime. 29 minutes would take around 90 minutes if the above math is correct. But then you have a small reference file ready to go.
Running TC filter ON but with-out multi-pass H264 and you’ve got about 42 seconds rendering time for 25 seconds HD-video. Here 29 mins would take around 50 mins and would hold more than enough quality for selecting shots.
-
Haha, well I’d called FCPX “simple” in regards to they tried to go for a completely fresh start and fresh view at editing. In true Apple-faschion they try their best to slim things down to the bare minimum yet keeping it “just powerful enough”. Here I get that if you aren’t an experience editor or possibly an editor dealing with strict time in projects for example, well, that kind of info isn’t priority. And the legacy way of dealing with things was maybe (I can’t say just yet) “too much information”. It’s just a bit to little info at the moment for a lot of things.
If Apple keep the development-cycle up we should have a very impressive app by next year looking how far it’s come in the year and a half it’s been on the market.
-
True, but a lot of these simple things are way to hidden.
The buggy film-strips are quite a source of irritation also. I fid the idea of them good, but it’s no good when they don’t show the correct frame of the clip. There should also be an option of only showing the first frame of each clip in the timeline.
But, with 10.0.6 like the thread starter I’m getting interested in FCPX I have to say.
-
The main thing I lack in FCPX at the moment is solid timecode support. It’s hard to se things like:
– where am I in clip X
– how long is clip Y or Z on the timelineThis is a fundamental issue when one has to deal with time / timecode. The lack of “mini timelines” makes this a greater issue IMO.
That said, sometimes it’s not so important knowing this when editing so this issue might not be a problem for all. I’d however be interested to hear how other people cope with the problem of FCPX and time / timecode.