Dennis Radeke
Forum Replies Created
-
[Gary Pollard] “Premiere Pro CS 5.5 on Windows can open and work with projects created and edited in Premiere Elements. Premiere Pro CS 5.5 on Mac doesn’t.”
Ah, so I was right. My first answer applies.
[Gary Pollard] “Premiere Pro CS 5.5 on Windows has many more video transitions and video effects available than Premiere Pro CS 5.5 on Mac.”
Well, there are some more transitions on the PC than the Mac, but I would question how many of the extra PC ones you’d actually use in most productions. They’re mostly cheesy… When we rewrote Premiere Pro for Mac in the CS3 timeframe, we went through the transitions and made some decisions on which ones would be most useful to the pro editors. We actually made some assumptions that the Mac customer we would be targeting (new for us in CS3) would be on the average more professional than our historical PC customer. So, to pick a pun, we ‘cut the cheese.’ Had to say it – sorry!
Again, if there are reasons you feel they should be on the Mac, the feature request form I put out there in the previous reply is a great place to log them – we look at them every quarter and tabulate the findings and prioritize accordingly.
Dennis
-
Ah, then I’m not understanding your question. Could you elaborate please?
Thanks – Dennis
-
[Gary Pollard] “Hi Dennis, while you’re here, can you explain why Premiere has limited functionality in terms of importing from Elements, and in terms of transitions and effects on the Mac compared to Windows?
Is it an Apple issue or Adobe thumbing its nose at Steve Jobs?”
This is not an Apple issue or Adobe thumbing its nose. 😉
The reality here is this:
– I know very little about Elements so I’d take everything I say with a grain of salt!
– Premiere Elements on the Mac is new to the platform and a stated consumer product at that so I’m not surprised.
– The Premiere Elements code base (on the PC) is divergent from Premiere Pro. For example, it’s still a 32-bit application whereas Premiere Pro is a 64-bit version. So, while they share a name, the demands of a consumer/prosumer are different in some cases from the Pro. That is, not all consumers want to go to a 64-bit native application.
– If this is something you want, I would encourage you to submit a feature request here: https://www.adobe.com/cfusion/mmform/index.cfm?name=wishformThanks for your comment and input!
Dennis
-
Agreed on all points. 😉
-
[Andrew Richards] “Adobe only leapfrogged FCP capability-wise with its 64 bit CUDA PPro CS5 in 2010”
While this is absolutely true with regards to 64-bit, our commitment to metadata, file-based workflows, practical integration points between Adobe apps as well as competitive applications, all were happening well before CS5. These are things that FCP X is just now talking about and that only partially.
On top of that, it should be pointed out that Adobe created a native 64-bit cocoa application on the Mac before Apple did. How did that happen?
My only point is that Adobe was innovating and creating interesting workflows for the professional long before CS5. I think the release of FCP X created a greater awareness of Adobe’s capabilities.
Dennis – Adobe
-
[Bill Davis] “Sometimes remodeling is smart (as Avid, PP and Vegas continue to do. Sometimes people with a nice piece of property decide that the old house is getting long in the tooth and a scrape is required.”
A nice analogy Bill. To take it further, Adobe knocked Premiere Pro down and rebuilt it twice on the Mac platform in the last 5 years (CS3 and CS5). The key though is that we didn’t build something completely different that threw the owner of the house off. Adobe built a new house that fit within the confines of the property.
I think what has been a challenge for FCP users is that in one fell swoop, Apple changed the architecture, the interface and the workflow. And on top of that, they lost several very key features. It will be interesting to see what the next 6 months holds for the industry.
Dennis – Adobe
-
[Andrew Stone] “Dennis, similarly is their a desktop machine that would come down in the same category, as a good starting point for an editing workstation?”
Andrew, a desktop is a lot less of a clear proposition because a desktop is more commoditized – meaning that you have a lot of choices when it comes to spending your money on a desktop. Here are a few ideas.
Local VAR – there are almost certainly a regional or local dealer that can build you a system for a reasonable cost. I can recommend some if you want to tell me the area you live. The key is to know their support and how much they know about professional video editing. They are out there and can be a big help to a user.
Big Box – I’m an admitted fan of HP for a lot of reasons. Their tooless case design is clearly superior to the Mac Pro and it’s fit and finish is very strong. They also include a 3 year onsite warranty as standard, so figure that when making a purchase. I have both a Z600 and a Z800. Take a look at them. I also like Boxx and Alienware.
Build your own – I think this is potentially the most rewarding if you take the time to understand what you’re doing and are into this kind of thing. The advantage is you waste no money and can build a system that perfectly fits what you want to do. Building a CS5.5 box is all about balance – CPU, GPU, RAM are key things you need to consider and you don’t want to skimp on any. Building your own box allows you that flexibility. I liken it to building a model – if you’re into doing that thing (I do), then this can be a lot of fun.
Final thought for Mac people looking at a PC box – Windows 7 doesn’t smell at all…It’s quite good as a user of both…
Cheers,
Dennis -
[Andrew Stone] “Kevin are there any PC laptops that you could mention that are qualified to use with Adobe Premiere CS 5.x?”
While we don’t qualify systems per se, I assume that what you’re talking about is a good laptop that provides GPU hardware acceleration with Mercury Playback Engine. A lot of the field guys have HP 8740 Elitebook laptops. They are pricey but they are dreamy too.
The engineering in the laptop is really excellent (very apple like) but unlike the MacBookPro, it doesn’t compromise power for the sake of form factor. Like it or not, you have to obey the laws of physics and Apple chooses to worry about form factor to the detriment of processing power. HP forgoes form factor for power.
Practically speaking, this means that the HP has a limited battery life when doing real work – less than an hour for sure. It also has a big, honking power supply that is uncool. What you do get is a laptop that can take 16GB of RAM and has a Quadro 5000M GPU in it. Connect this laptop to some decent storage and you have a very nice system that gives you true desktop like power.
So, you have to decide what you’re really after. Both the MBP and the HP have a lot to offer, but they take different routes to the end result.
Dennis – Adobe
-
One thing not mentioned in this thread that I think valuable is that Premiere Pro CS5/5.5 has the Ultra keyer which is also quite good. It’s not as good as Keylight, but it gives you a lot of control and it’s real-time!
Download the trial and give it a go to see if it works for you.
I will also second and third the idea that understanding how to key is very important. I always go back to some tutorials to brush up when I actually need to do something hard with keying.
Dennis – Adobe guy.
-
[Steve Connor] “I’ll keep pushing the PPro thing a little further If I may, my facility was fully invested in Matrox Digisuite and Premiere 6.5 as were lots of people. PPro came out and was not usable with the hardware that some of us were actually making broadcast shows with.
In fact probably the ONLY people making Broadcast shows with Premiere used Matrox Digisuites, Adobe chose to dump them in the pursuit of their new code base.”
The problem there was Matrox, not Adobe. They chose not to support Premiere Pro – probably all the more since they were hard at work on newer hardware designs. Adobe is committed to its customers and have never intentionally abandoned any customer in the video space. I’m sure the same is to be said for Matrox, Apple, Avid, etc.
Change is a part of life, on that everyone can agree. I think what Herb and others are trying to say is that while FCP X may be a 1.0 product it shouldn’t be counted as an excuse for making a step backward for their daily work and missing features.
As Herb pointed out, when Adobe went to Premiere Pro, it didn’t lose features. When Adobe did a complete re-write just a few years later to make it 64-bit, they didn’t lose any features. At the Avid Media Composer 6.0 preview event, Avid went out of it’s way to say the same thing.
I think that Apple is to be applauded for it’s ambitious undertaking of tackling all three major focal points of a professional application in one shot: User Interface, 64-bit, Workflow. For some people, the net result isn’t satisfactory.
And in the effort of full disclosure….
Dennis – Adobe guy