Alex Udell
1
Premiere Pro Coin
Forum Replies Created
-
I will add one other note…
As 32 bit OS’s…
Under Windows XP and Vista standard, memory does seem a bit of a limitation on the Windows platform and Premiere is a bit of a RAM glutton.
Apple has already gone thru the growing pains of moving to a 64 bit OS, so I can’t remember the last time I heard someone complaining about running out of RAM in FCP.
I expect this to change significatnly after everyone (Adobe and Matrox in my case) gets 64 bit compliant, which I don’t expect to be to much longer.
That’s the one knock I’d give Premiere Pro right now.
Alex
-
Hi…
I’ve talked about this before.
I recently re-joined the creative community after several years of working in a sales, training, and product demonstration capacity, so I’ve worked on every major editing platform.
Yes, Premiere does get it’s share of knocks from industry peers. I’m was guilty of it myself. Adobe has themselves to blame for some of this. Premiere wasn’t good for a long time. Endlessly crashy with an unconventional editing metaphor and early A/V sync (pre DV era) issues. Combine this with Adobe’s propencity to bundle Premiere for free with every capture device didn’t do them any favors in terms of building cache with the product.
That changed with the introduction of Premiere Pro. New guts, a more conventional editing approach, and some good press combined with better marketing really helped Adobe a lot. But it takes time for the word of the improvement to ripple thru the industry. So a lot of people hang on to the old notions of what Premiere was.
I was required to learn Premiere Pro with Matrox Axio for my last job. At first I was a bit snobby about it, but my attitude changed quickly.
The company I am with now is an entirely Adobe facility with multiple systems running on a SAN. I edit happily away on Premiere (and Matrox) every day, and it works really well.
Now looked at from a marketshare point of view….In some cases, Apple may be a better choice. Apple does have a hot hand right now in terms of industry attention. If the work you do is work you finish…Adobe is great. If clients expect to walk away with anything other than a finished master project or file, meaning they want Project assets to take to other facilities….well then Apple may be more appealing, simply because more facilities have it, people can take their assets more places. There is one exception to this this beyond Premiere. More Pros may be editing with FCP, but Adobe does own the rest of the pipeline. After Effects, and Photoshop are the norm in most facilities and Apple’s Motion (and other bundled products) have not displaced them.
As I have used both FCP and Premiere Pro, there are any number of things I can say I like better about Premiere Pro, but I have also sent many feature requests to Adobe regarding things I’ve seen in FCP that could be implemented in PPro to make it even better.
So Adobe is plenty capable. Don’t let that dissuade you. Take a look at the kind of work you want to do (self contained or shared) and let that guide you.
Good luck!
Alex
-
Hi…
If you do do go the export route…
you could always lay the continuous export edit over the clips on the original timeline. This will help you speed up navigating from shot to shot.
If you decide at any point you need to do a CC, you can use Control K to split the continuous clip based on the original editpoints.
Alex
Alex Udell
Editing, Motion Graphics, and Visual FX
See My Current Reel
visit the combustion exchange ftp
-
It might seem odd that Adobe chose to do this….
But I think it has to do with titles resolution independent when you move a project from say HD to SD or the other way around…
The ebbedded titles should recognize and vector scale themselves accordingly….
just a guess….
-
Grouping and subclipping doesn’t work together?
Yikes!I have used Timeline Nesting as source side color correction as well.
I do love that you can use mutliple timeline windows simultaneously….
Alex
-
Hi…
First, try temporarily setting it back to single monintor settings and then relaunch Premiere and see if the Titler behaves properly.
If it does, you can still use dual screens you just have to use it under a different mode.
Under the ATI card I’m using, I have it set to:
Extended desktop mode.In this mode Titler behaves fine, but I only get video overlay one one monitor, so my Source and Program monitors have to be on the same (primary) display (as well as capture).
When you first set this up, you might have a situation where Premiere wants to stretch across both displays. Double click the application title bar on your primary display and this will bring the application on to one monitor.
To make use of the second display, UNDOCK the primary funtion you want on the second display (for me it’s the timeline). drag it to the second monitor and resize it to fill the screen.
then dock and arrange an additional panels you want within that panel. (A trick I leanred on the COW 😉 )
One you get it all the way you want, save a workspace.
With this all set up, dialog boxes and splahses should also show up centered in your primary monitor (instead of across two monitors) which saves endless and needless clicking and dragging.
You should be good to go after that!
Lemme know if you have any questions!
Alex
-
From the Adobe website.
Alex
-
Hi Guys…
Are you using dual monitors?
Depending on your graphics card…
this seems to be related to whether you are using a spanned or dual desktop setup….
Not at my machine to confirm right now…
look at your desktop settings and see if this is the culprit…
Alex
-
Hi…
If this CS3 3.1…update to CS3 3.2.
This fixes thsi issue…
Alex