Alex Schwindt
Forum Replies Created
-
Hey Mario – adjusting GPU and OS settings is a bit “above my pay grade” unfortunately. Hopefully someone else here on the forum can point you in the right direction…
alex schwindt
alexschwindt.com
alexschwindt.typepad.com -
As long as you have some version of FCP running on your machine (including FCP X), Premiere WILL be able to read and edit ProRes files. You’ll also be able to encode Quicktime ProRes files directly out of Premiere or Media Encoder.
I just set up a new MacBook Pro (Lion), first installing FCP X/Motion/Compressor, then installing Adobe Production Premium CS5.5. I didn’t need to copy any files or codecs to new locations – ProRes was just waiting for me, ready to rock, inside of Premiere.
Hope that helps…
-
I’m in the same boat. Switching to Premiere CS5.5 has been a joy and I can’t ever see myself going back. Having said that, by far and away the biggest thing I miss is the Paste Attributes list from FCP. If this could show up in CS6 I would be absolutely thrilled.
Having the ability to open mulitple projects at the same time would be nice too, but that’s not nearly as big a deal.
-
Tom – he’s doing a modified mutlicam where he’s synced up some of the videos on overlaping tracks. Not the easiest solution, but his system’s knocking it out.
-
Ted – one of my best friends is a long-time Premiere user, and watching him undertake a 70-minute project in Premiere CS4 two years ago scared me off the program completely!
The difference between CS4 and CS5 really is huge in terms of stability. That same friend is currently working on a 75-minute multi-cam project shot simultaneously on six DSLRs and so far Premiere CS5 is performing like a champ.
With the demise of FCP I’ve actually migrated to CS5.5 myself, and I’m really enjoying the increased power and compatibility with AfterEffects. Keyboard shortcut customization really helps the transition.
Hope that helps…
-
my only hang up with that machine would be the screen resolution. When you’re running these Adobe apps the more pixels the better. If you could push that spec up I’d recommend doing it…
-
Neil, if I were you I’d check out the Lenovo ThinkPad W520. You can outfit it with up to –
Intel 2.5GHz i7 Quad processor
1920×1080 LED Screen
NVIDIA Quadro 2000M 2GB graphics card
16GB PC3-10600 SDRAM
Dual RAID 500GB HDDs @ 7200rpmIt not the cheapest machine around, but it ought to knock out some serious work…
-
Thanks Chris – that’s helpful.
Alex Schwindt
-
After what’s happened to FCP I’ve been in the process of learning Premiere CS5.5. I can’t say enough good things about this software. Like most other full-time editors I’d been really turned off by previous versions of Premiere, but Adobe has really turned things around with CS5. It’s stability is absolutely rock-solid.
For every minor annoyance I experience coming from FCP there are a host of things I like better about Premiere. Even basic things like titling and deinterlacing are heads and shoulders better. Add 64-bit speed and dynamic linking and it gets hard to make a compelling case to move back to FCP7.
I took a look at AVID as well, but the time investment it would take to get my head around the AVID way of doing things was a real deterrent. It only took me one afternoon and a 3×5 notecard to get going enough in Premiere to be able to knock out some actual work.
I haven’t totally given up on FCP (I just started messing with FCP X this week) but after a few days I can already tell you that it doesn’t meet my workflow needs at this point. Plus it’s somewhat crash-happy. There are somethings I really like about X (like skimming), but I have to agree with everyone else that it’s not ready for primetime.
Alex Schwindt
-
I’m actually with Peter on this. Apple should have released these videos on Day One. They do a much better job of communicating their vision for editing than anything that’s come before. (and you have to give them some credit for lumping their own FCP 7 in with Avid and Premiere)
I’ve been a full-time filmmaker who’s been using FCP for years. I’ll be the first to admit that when FCP X was released I immediately got busy learning Premiere CS5.5. Adobe’s really gotten it’s act together with Premiere, and at this point I’m not sure I’d go back to FCP 7 even if it was re-released today. Premiere is just so much faster and more powerful.
Having said that, after spending a couple of days with FCP X I’m starting to get what Apple is thinking with this. A fellow filmmaker and I spent most of today messing around with it and we had a blast! We even purposely shot some “problem footage” with a DSLR just to see how FCP X would handle it. Again, we were impressed.
I’ll agree that it might not be ready for the big leagues (we crashed it once just doing a color correction). The idea of editing a 90-minute project with FCP X makes me nervous, and while I dig the color tools the absence of Colorista II is definitely a bummer. Probably me biggest hang-up with it is they way they completely abandoned standard terminology. It’s going to be hard to communicate with other filmmakers if “project” doesn’t mean “project”.
So I’m going to keep kicking the tires some more. I have a number of short-form projects coming up that this might be perfect for. The problem is that I don’t have tons of spare time to keep learning new editors. At some point I’m going to need to start developing some muscle memory with one weapon-of-choice editor…