Dennis Radeke
Forum Replies Created
-
Scott,
Just my own well mannered opinion, but you might try to keep it classy. Anyone who monitors these forums knows where your opinion (and heart) is. And we’re all okay with that. However, you might do it in a way that is poignant rather than inflammatory. The old saying, “you get more bees with honey,” is probably appropriate here.
Sure, there are others who have a level of disrespect for your chosen tool, but I don’t seem to recall them calling it a PoS. And if they did, you needn’t stoop to that level.
Continue to be honest and voice your opinions and ideas – I just suggest a manner becoming of your intellect.
-
*i believe* Premiere Pro works in 32 bit YUV color space internally.
I would export YUV if going to Premiere Pro
-
Siobhan,
I am an Adobe guy, so will not weigh into the overall pros and cons of one NLE over another. My only comment is this: I think if you use Photoshop, After Effects, etc., you’re going to have Creative Cloud anyway, so the NLE is just icing on the cake as it were.
While I will obviously recommend Creative Cloud for you and I haven’t tested CS6 on yosemite at all, I will say that the first thing you might consider is trying to reinstall Yosemite again and seeing if perhaps something went awry the first time.
When I upgrade Mac OS, I NEVER EVER run an upgrade but rather wipe the machine and start building up from scratch. Yes, total pain, but I know I have a clean system. Long gone are the days when a Mac was bullet proof and an upgrade was as easy as clicking ‘install’. If you ran an upgrade, I would consider backing up everything, de-authorizing everything and then do a clean build.
For Mac/PC, I would probably stay Mac if you have a lot of Mac experience. PC’s are more powerful in choice and raw horsepower, but if you spend all of your time trying to figure out how Windows works, you might just be better off staying on the Mac platform and focusing on creating content.
hope this helps,
Dennis – Adobe guy -
First, why am I responding to a post at 5:50AM in the morning. There’s got to be a name for this sickness…
[Walter Soyka] “Ae’s 21 years old. It could have used a new architecture a decade ago. Why do you think it didn’t get that re-design sooner?”
My guess (truly) but probably an informed one is this: Ten years ago given the choice, users were choosing new features over speed and UI. The importance of UI was just beginning to come to the forefront too (look at UI’s of any program back then). Secondly, Adobe probably didn’t want to mess with AE because it was driving a much larger fraction of the overall video revenue back in the day. Premiere Pro was out there but didn’t have the reputation and capabilities that it does today.
[David Lawrence] “Now that they’re free of the CS model, what are the perverse incentives forcing them to do yearly full install releases, complete with big marketing features?””
David, just because we aren’t bound by a specific release schedule doesn’t mean we don’t want to market it and actively promote it in the best way possible. Today’s societies are media saturated and everyone is selling all of the time. As any for profit business, Adobe wants to position and present its products in the very best light possible. If you’re selling your services to a prospective client, you don’t bring out a 4×3 video you did 20 years ago, do you? Similarly, Adobe creates a good product and simultaneously spreads the message of why it will appeal to you.
To reiterate, major video apps have gotten as many as 4 updates in a year, two or more of those as major, feature bearing releases. Premiere Pro has had 4+ releases per year for the past few years. many hundreds of features large and small – more substantive IMO than any other similar application out there. Some will disagree and that’s okay – but I am personally very proud of our track record three releases into the Creative Cloud subscription model.
Dennis – Adobe Guy
-
Another response more for the general thread…
[Herb Sevush] “All too true, however what’s even slower than Colorista’s keyer is the LCS having no keyer at all. No keyer, no secondaries, no eyedropper, no thank you.”
Herb, you are so quotable…thank you! 😉
There is the Hue Saturation Curve control which does secondary type functions as someone else has pointed out.
The goal of the Lumetri Color workflow/effect is to bring a large part of the power of Speedgrade and make it more accessible to a wider range of users. I’ve used the comparison of making Color more inviting via Lightroom. For me the great experience of Lightroom, is that I start twiddling knobs and see results – often good results. It is inviting and dare I say, fun.
For a lot of people color grading/correcting is not fun, not intuitive and they don’t get the results they’re looking for easily. This is what we’ve attempted to fix with the Lumetri Color Effect.
For a lot of people this is going to be a great tool that helps them get farther in creating good content via color shaping than previously. It will hopefully be fun and instructive at the same time.
For some of the people here who are saying it needs this or that, I hear you but I would point you back to your tool of choice and in our case, Speedgrade where you have the full range (which is extremely extensive) of tools at your disposal.
For advanced users, this is another tool in the toolbox – one of a choice of tools. For other users, this will be a great tool that hopefully is revelatory.
My .2 (or 20) cents,
Dennis – Adobe guy -
Hi guys, I have been busy and have taken on an additional role at Adobe so not as active recently. Still trying to jump in when I can. I will just take Jeremy’s reply as typical in this thread (or at least part of it). Hope to jump in more soon.
[Jeremy Garchow] “I just want a faster Ae, is that so wrong? :)”
Well, wish fulfilled. This version of AE is faster in the key sense of disconnecting the UI and Render threads. you will find that you can add elements, effects, tweak parameters to a layer while the comp is previewing and it won’t stop. To me this is absolutely huge. They’re working on more too.
[Jeremy Garchow] “I see “CC 2015” right next to “CC 2014″, I see the big marketing blitz, I see the some of the features touted months ago, and……..yeah.”
We delivered what we showed at NAB, is that so wrong? I guess you would have preferred that we showed less and then surprised you? It’s like sneaking into to your parent’s closet and peeking at the Christmas gifts before Christmas? Well, if this is the penalty of Adobe being transparent and communicative, then I will choose it EVERY…SINGLE…TIME…
Dennis
Adobe guy -
Scott,
I’m not an expert around this, but wondering if you might be able to utilize either OMF or AAF since you mentioned Avid? Those are valid audio export options as well.
Here’s the help page on exporting projects: exporting projects
-
Well, you have a newer mac and newer OS and graphics card which CS6 doesn’t know.
1 – You would have to remove the .txt file from Premiere Pro in order to get your graphics card work.
2 – Make sure you’re on the latest version of Premiere Pro CS6 – not CS6.0
3 – make sure the amount of RAM assigned to Premiere Pro is somewhere between 50-70% or 16-22GB of RAM to Adobe.
4 – All of your footage is longGOP MPEG4 which is challenging to scrub and is something we improved a lot with Creative Cloud.Hopefully some of the above might help you.
Dennis – Adobe guy
-
Eden Young “Both composition settings are the same in both AA and AE.”
I’m still not sure what AA is in relation to AE in the above sentence.
As to your issue, what kind of media is giving you this problem, what versions of Creative Cloud are you using, what are the basic system specs of your editing platform? If you can give us some of this, I’m sure someone can help point you in the right direction.
Best,
Dennis – Adobe guy -
Victor,
Please supply some more information for users here at the forum. What camera media was captured? Could it have been a hi-speed camera? Are the video and audio the same length on the timeline? Have you tried any troubleshooting? What are your system specs? What version of Premiere Pro are you using. In short, you’ve described the problem but not provided any information. The amazing Kreskin we are not!
Perhaps the first thing to try is to trash your preferences and clean your media cache: https://blogs.adobe.com/genesisproject/2011/02/premiere-pro-cs5-maintenance-two-great-tips.html