Mike Jackson
Forum Replies Created
-
One thing I’d add – If you’re talking Canon DSLR footage, in my experience NOTHING does a better job of interpreting Canon footage than the Canon EOS plug-in for FCP7. Premiere (and After Effects) tend to leave artifacting and banding in the Canon H264s, (as does Compressor and MPEG Streamclip), but the EOS plug-in, transcoding to ProRes, gives much smoother gradients, and images that will color-correct much better.
It also gives the closest match to the color/gamma you see on your camera’s viewfinder.
So that’s another advantage of transcoding.
-
Oh, one other tidbit – I’ve watched my CPU usage during this ‘silent’ stretch, and it’s definitely doing SOMETHING. Once the CPU indicators all flatline, Premiere is ready to edit.
-
Nope. That would be crazy ; )
As I say, this only happens when I first open the (now enormous) project. Once it finishes doing whatever it’s doing (for 5-7 minutes), it’s smooth sailing from then on.
-
Yeah, and that kind of walled garden approach is another thing that ticks me off. Resolve won’t play nice with my graphics card (which I need for ray-traced rendering in After Effects), and Blackmagic won’t support Adobe Speedgrade, so I can’t use EITHER.
Thankfully I’ve been happily using SA Color Finesse for years and have been very happy with it, and it runs in FCP and AE (and I guess Premiere if I buy ANOTHER license for it).
-
10 and up, as far as I can tell from various forums. And evidently BM has simply responded “FCP 7 is no longer supported. It says so in the documents.”
-
I recently ran into this myself. Are you using the same iterations of both programs? ie: I’ve been using Premiere CC2014 and AE CC (not 2014), and they won’t talk to each other.
I’m kind of stuck, too, because my Blackmagic decklink won’t do video previews in AE CC 2014 unless I update my drivers to versions that kill FCP 7.
At any rate, if both programs are up to date (or from the same older date), that *should* work…?
-
Have you been importing your clips using the Media Browser, or other methods? Only the Media Browser will import spanned clips correctly, combining multiple files into a single clip.
-
Thanks for your in-depth response. I think it’s mostly a question of web-page design. To my thinking, the second you open ‘help’ you should go somewhere that has the most NEEDED things front and center: Like ‘Documentation’ (or whatever you want to call it these days, I still think ‘help.pdf’ isn’t very informative), search Adobe documents, search community forums.
Right now it’s a rat’s nest of links, with ‘what’s new’, ‘get started’, and a whole bunch of other topics dominating the page. If I’m picking up Premiere for the first time and want to walk through an overview of getting started with the program, it’s GREAT… but not for much else.
Just my two cents. Figuring out what a few of the effects did shouldn’t have turned into a timesuck like it did, imho.
Alllll that said, this is the first time I’ve worked with Premiere since CS6, and the improvements in capability and performance are tremendous!
-
Hi Kevin, thanks for the response. Opening that help menu was of course the first thing I did. Which takes me to an incredibly busy webpage full of links, none of which say something simple like “Manual”. (I see now it’s labelled ‘help pdf’, which didn’t sound like what I was looking for).
And of course the most obvious ‘search’ field takes you into adobe community, rather than searching Adobe’s own documents.
Like I implied, it’s actually something that’s been picking at me for a while (and I guess Larry Jordan too) – Finding straight simple answers to even the simplest questions can be frustratingly difficult. A difficulty I didn’t have back when there was a button in the Help menu that *opened the manual* ; )
-
That’s great… but from Premiere, what course of action leads me to that document?