[Dennis Radeke]

A Creative Cloud subscription model is a very good model for the vast majority of users out there and I think we’ll see more and more of the industry move that way. In fact, I saw Microsoft do the same with Office 365, which is a pretty good deal.

[Dennis Radeke]

[David Roth Weiss] “Although I’m not privy to any of the secret sauce Adobe is releasing, I do know they very much intend to wow the industry and to further position themselves as a real contender for professional editors.”

On this I can agree and comment. Nothing else. 😉

[Dennis Radeke]

[Bernhard Grininger] “PP CS6 has some great special features and it benefits from the whole CS suite.
It’s consequent native format support it great! Because of this it is confusing, PP needs ‘render files’ at all. Mercury runs very well! Also confusing is the sequence setting by codec instead per video standard. I also get headache when I need to do rocket science to get full quality out of it (GPU yes/no, 32bit float yes/no, etc…) or hack my app for GPU support at all… WHY???

Too much of thinking…
Too many plugins and other CS-apps needed…”

I agree that sequence settings become somewhat superfluous because it doesn’t really matter what is on the timeline. Given that you don’t need to render until you’re ready to output a final, I don’t really worry much about preview renders. That said, if you do, it’s a simple matter of setting up your own custom sequence preset.

As for hacking for GPU – we want to be very careful about what we officially ‘white list’ because we a guaranteed experience. The fact that we’ve enabled people to find the ‘hack’ fairly easily and it works 99% of the time for any decent card is a bonus. Simply put – we want to make sure your experience is great and the GPU can be a variable. We’d rather you be mad at us for having to change the text file than not offer GPU support at all. Can we do better? Yes and we will.

[Bernhard Grininger] “To convince me, Adobe needs to implement all those boring features, no evangelist on this planet could convincingly praise as ‘awesome’, but that are extreme important for real professional workflows (100% 32bit float, motion-compensated de-interlacing, spline-masks, color-grading, etc…) so that 90% of work in 90% of the projects could be done within PP.”

We’ve done a lot of the ‘boring’ stuff already but there is always more. FCP7 keyboard shortcuts, change sequence preset to match first clip, basic editorial tasks like trimming and the list goes on. Most of our effects and process pipeline are 32 bit float already (just check out those icons to the right of many of the effects). Spine-masks – YES! I’m with you 100% on that one and I’ve asked for it for ages. There are workarounds and some free plugins, but yes… Color grading – we work with Resolve and others and we are working on better integration with Speedgrade for the future. I think we’re there and/or getting there.

[Dennis Radeke]

Thanks Steve, love to hear your input.

I’ll try to answer some of the comments on the thread and see where it goes. Apologies if I repeat what someone else has already said…

Premiere Pro and Speedgrade integration – yes, definitely something we all want to see get done.
XML – we work to keep the workflow with Resolve going. I think we had a dot release in the CS5.5 timeframe specifically for XML fixes to the REsolve workflow. We want people to have choices and integration with other software and hardware.

Dennis – Adobe guy

[Dennis Radeke]

Was there a Mac update that you ran? If so, I wonder if it updated your graphic drivers which might affect your second monitor experience. The other thing to perhaps try is run disk diagnostics and a restart.

Dennis

[Dennis Radeke]

Hi there, thanks for choosing Adobe Premiere Pro.

I think you’ve got a couple of issues going on here. First, as you mentioned, you’re playing off your system drive which is definitely going to slow you down. Second, as another Dennis pointed out, you’re a bit low on RAM. Seriously, a small investment in RAM will give a HUGE return on performance and stability. Thirdly, using MBL while fantastic for what it is, does slow performance down significantly inside of Premiere Pro. THis is because it is NOT GPU accelerated like many of the Premiere effects and therefore bottles up your CPU performance. This cascades back to your RAM and hence dropped frames.

One tip to consider is to pull down your playback resolution which you can find in the program monitor. If you see where it says ‘full’, you can select ‘1/2’ and see if that helps your playback performance.

Hope this helps,
Dennis – Adobe guy

[Dennis Radeke]

I assume that the answer to your question is yes, but I will check. When you select ‘transcode’, you are actually creating a job in AME. Let me ask engineering and if possible, get back to you.

Dennis – Adobe guy

[Dennis Radeke]

clean cache and trash prefs is one thing to do: Two tips

Also, if you have a large projects with hundreds or thousands of clips then you need to consider adding some more RAM. RAM is the solution for almost any 64-bit application….

Hope this helps.

[Dennis Radeke]

Also, while I’ve never done it myself, I hear that ingest speed is somewhat slow. Some people have used the Sony transfer tool to move/copy the media to a local hard drive and then edit from there.

Dennis

[Dennis Radeke]

Prelude is a file-based ingest, metadata logging, tagging and rough cut tool. I agree that it doesn’t make sense for one-man or small shops. This product was designed in tandem with two large broadcasters where hundreds of users are involved.

Prelude allows a shooter, producer or other non-editor type who has some skills with story telling to select clips, create relevance through metadata and then hand off a rough cut to an editor to add titles, graphics, voice-over, b-roll, etc.etc.

This is one of a couple of interesting workflows. Hope this creates some clarity for you.

Here’s the page link with a lot of info: Adobe Prelude

Dennis – Adobe guy