New Premiere Pro CC SDK

The new Premiere Pro CC SDK is now publicly posted to the DevNet site here: http://www.adobe.com/devnet/premiere.html
Some highlights:
New GPU Extensions for Effects and Transitions
New SDK_ProcAmp sample to demonstrate GPU acceleration of an After Effects-style effect
Closed Captioning support in Importer and Exporter APIs
Support for new Edit to Tape panel
XCode projects are now built for XCode 4.5
Refer to the What's New documentation for a complete list of changes.
Enjoy!

Release 2 of the SDK is available now:
http://www.adobe.com/devnet/premiere.html
The highlight for this new release:
New support for native transitions using the After Effects API
Enjoy!

Similar Messages

Will the new premiere pro edit and save changes to avchd losslessly?

Hi,
I want to buy a new premiere elements to replace my old one (vrsn 3), can I upgrade it still or is it too old? Or should I still stick to Premiere elements?
Also, will the new premiere pro edit and save changes to avchd files from Panasonic and Canon without losing any quality?
I came across 'provides native support for avchd'; what does it mean? Does it mean that I can edit and save avchd files with out losing quality?
Thanks,
H

For your several questions...
One... download and try the 30-day free trials
Two... read in the user guides
CS5 User Guides - online and PDF (see link in upper right corner at individual pages)
http://blogs.adobe.com/premiereprotraining/2010/08/help-documents-for-creative-suite-5-pdf -and-html.html
http://help.adobe.com/en_US/PremiereElements/8.0/Win/Using/index.html
P-Elements 9 http://help.adobe.com/en_US/premiereelements/using/index.html

Does new Premiere Pro CS 5.0.2 update solve hangup when clicking in and out of Premiere Pro?

I originally ran into the problem with Premiere Pro CS 5 (as part of the Production Premium CS 5 package) whereby on large projects, particularly with P2 media, Premiere Pro would hang up every time you clicked in and out of the application. What I mean by this is when you click your desktop or explorer or some other application, outside of premiere pro, and then you try to go back to premiere pro and click inside the application to get back to work, you get a blue wheel and it takes 10-30 seconds before premiere pro will re-engage and allow you to work.
I have installed the new 5.0.2 update and tested it on my original problematic project, having set up a new media cache file. The project prpro project file size is approx 30 mb and the reference media is approximately 300 GB on internal hard drive. The full data on the original problem,specs and tests can be found on this form at
http://forums.adobe.com/thread/639220?tstart=0,
Unfortunately, in my initial work and test with this as of today, this problem is not solved and the same hang up is occurring. When testing I have all other applications turned off, no internet connection and no firewall/anti-virus programs running (system mechanic).
I will be working extensively over the next few days with a new editing project and will reduce the project size and will report back if there are in fact any improvements or changes to this, but at this writing, this problem is not solved for me unfortunately. Possibly for others there is an improvement.

You know what it didn't work for me - but - and I only discovered the solution last night by happenstance - I wasn't trying all that hard to solve it as it wasn't as bad for me as apparently it is for you and others - but - anyway - for me the solution was my anti virus - I had it turned off when I installed the update - so once it was completed it appeared the problem had been solved by the update - but - then I turned the anti virus program back on - Avast free version BTW - and the problem was back - it was then I happened upon your thread and obviously I put two and two together - so - continuing - I have just now uninstalled Avast free version and installed AVG free version and - viola` - all is good - for now. Sorry to hear you are still suffering.
That has been my only nagging issue thus far with CS5 - all else - so far so good.
Best wishes,

Can't get GeForce GTX 560 Ti card CUDA to work with new Premiere Pro CC 2014 version

In the past I've been able to get CUDA on my GeForce GTX 560 Ti card to work with Mercury Playback engine by adding "GeForce GTX 560 Ti" to the cuda_supported_cards.txt file. But with the new CC 2014 version of Premiere, that file isn't in the Premiere Pro directory anymore. Is there a way to get my GTX 560 Ti to be listed as a CUDA-supported card with CC 2014?

Okay, I figured it out. I installed the latest graphics driver and then opened the NVIDIA control panel. In there I selected "Manage 3D settings" and went to the "program settings" tab. I selected Adobe Premiere (adobe premiere pro.exe) from the list and under the "CUDA - GPUs" feature, I changed it to "Use these GPUs" and selected my GTX 560 Ti (which was the only one listed).
After doing that, I opened Premiere Pro CC 2014 and selected "Project Settings - General" and was then able to choose "Mercury Playback Engine GPU Acceleration" under Renderer (which had previously been unavailable).
Hopefully this will help someone else if they encounter the same problem.

Any more news of the new Premiere Pro/AE updates shown at NAB?

I'm sorry if this has been asked, but from googling, there hasn't been any recent news that I could find! Did they have an ETA on the new updates?

The short answer is No.
The most recent 'official Adobe' statement about PrPro next is here:
Revealing the next release of Premiere Pro: Creativity just got a lot more colorful. | Premiere Pro work area
But that was released pre-NAB so whatever you heard out of NAB is obviously more current.
Other than that, the most timely info often appear in places like this:
Adobe CC Video & Audio | Facebook
So I suggest staying tuned to something like that, twitter, or this forum and you will no doubt as soon as it's publicly announced.

How do you enable closed captioning in the new Premiere Pro CC 2014?

I just upgraded to the latest version of Premiere Pro CC 2014... I can't seem to find a way to "enable" closed captioning!

Look for the wrench icon in the monitors, above the playback area, to the right. Tooltip for it is "Settings..." -- the menu item is in the flag menu there: Closed Captioning Display...

New Premiere Pro Download Crashes Often

Since downloading the update for Premiere Pro CC last week, my program crashes all the time now.
Where with the old version of CC my computer was fine and had very few crashes.
Anyone else having this problem?

Hi Aircam Productions,
Can we get more info please? FAQ: What information should I provide when asking a question on this forum?
Thanks,
Kevin

New Premiere Pro CC Feature! Vote Now!

Here's a message from Premiere Pro Engineering Manager, David McGavran:
Hi All,
The Premiere Pro team has room for one more JDI in the October release! We asked for suggestions and got them! Now its time to vote on what feature we are going to program at IBC!
TWITTER:
https://twitter.com/AdobePremiere/status/377235035553681409
FACEBOOK:
https://www.facebook.com/photo.php?fbid=10151875206125619&set=a.43454190561...
Voting goes until 6pm tonight.
Thanks!

Kevin! Want a true JDI that should be added?!!!
Add at least a preference so that one can drag and drop clips (audio only, video only AND also audio/video together) from the source window to the timeline regardless of source patching. That's how it worked in CS6. Please give us the ability to do it again. As Jim Simon wrote in the link below: If you want only video, you can drag the film strip. If you want only audio, you can drag the waveform. But if you drag the image, you normally want both. Same track/different tracks can be handled with patching, but when dragging the image, ALWAYS bring down both REGARDLESS of patching.
http://forums.adobe.com/message/5572713#5572713
PLEASE!!!!!!!! Just do it! You asked for something small like a "preference" well here you go!

Adobe's move to a more "Final Cut" Premiere Pro is not all good.

Hi everyone. I don't post very often and I decided to do so because I want to hear people's comments on this subject. I have been a premiere pro user since Premiere Pro 2.0 and I've a good handle on Final Cut and Media Composer. To this day, I've always preferred Premiere for a number of reasons.
As of late, many Final Cut users have been migrating to other NLEs and in response to that the latest iteration of Premiere (Premiere CC) has included some decidedly FCP-ish features (And some Media Composer-ish stuff too). In my opinion, some are rather welcome additions and some are not.
What prompted me to write this is the feeling I got when I started using CC. It felt like in the rush to welcome the newcomers, some things were lost for those of us who has stuck by adobe for years.
Here's my list of good and bad:
Good stuff:
1) Auto Locate - Premiere is now smarter at finding your files. Awesome!
2) You can now select clips and move them up and down in tracks with keyboard shortcuts. Great!
3) You can move target and source tracks with keyboard shortcuts! In fact there are many new things you can do with keyboard shortcuts! (Can you tell I like keyboard shortcuts?) I'll leave the keyboard alone now. Yay! Ok now I'll leave it alone.
4) Audio Clip mixer. Now, I really don't see when I would use this, but sure. Why not? It's not invasive and they kept my track mixer as awesome as ever. I'm sure final cut users could shed some light as to it's utility. Specifically, what can you do now, that you couldn't without the Clip Mixer?
5) There are a few cool ways to expand tracks. (I've heard it works a lot like Media Composer).
6) You can now customize the buttons on your audio tracks. Sweet! (Also feels a bit Media Composerlike)
Bad stuff:
1) Symmetrical transitions - This is meant as a feature for Final Cut users but it's actually horrible to me. I don't want my start point to mess with my end point. I want to put them both exactly where I need them and have them stay. I know you can hold shift to get the old behavior back but I find I'm holding shift a lot these days.
2) Transition icon changed to a suspiciously fcp looking transition. It's smaller. I don't see the advantage of changing the look. I certainly don't see the advantage of making it smaller. Not a big deal, but not a fan.
3) The "fx" box replaced the name of the parameter whose keyframes you are currently seeing inside the clip. Now you can't tell which parameter you are looking at. Is this an attempt at removing clutter? Cause I think allow for the user to customize clip info is a better approach than simply removing stuff.
4) The clips now turn white when selected. Again I remember complaints of clips not being obviously selected but now you lose the label color when you select a clip. This means that if you select a bunch of clips, you can't use the color to see if you picked up something that should've stayed unselected.
5) Audio display now shows half of the wave instead of the doubled mirrored wave it always showed before. This sucks. Every DAW I've ever used (Pro Tools, Digital Performer and Audition to name a few) shows the mirrored wave. It's kinda standard. This new view is actually harder to look at. The negative view of the wave (the part of the wave that isn't the sound) looks like the bottom part of a wave. It's very distracting and annoying.
6) Work area bar is gone. This isn't such a big deal since the functionality has been added to the in and out marks, but since the work area bar is also a part of After Effects, this makes Premiere work differently than it's family of apps. I would think that having overlapping or similar tasks performed similarly throughout the Creative Cloud Apps would make a lot of sense to Adobe.
Again, Adobe Premiere Pro has been and still is my NLE of choice. This isn't an angry rant. I simply felt it was an update that removed some great functionallity and wondered if others felt the same. I'm sure my list is both incomplete and of course simply an opinion. I'd love to hear people's reaction to the new Premiere Pro CC. Do try and be nice though.

Jim.
Agreed. You can't please everyone every time. Though user customization goes a long way I think. And I definitely feel like this release was not really targeting me.
shooternz - Too bad. I did know this. It's not such an imposition but it does change the way I work without gaining anything I wanted. Seems like a lot of people actually like the symmetrical transitions though. Me, I think it is only useful when you don't care about being very precise. Maybe not. Maybe there's a good use for it. I haven't found it. I just wish there was a way to make the default behavior what it used to be and the symmetrical transitions work with shift. I'm already getting used to holding shift all the time so I'm not worried. I just don't see much advantage.

Premiere Pro CS4: 64-Bit App or Not?

I read in the new Premiere Pro CS4 specs that it was "optimized for use on Win Vista 64-Bit..."
Using that language, is Adobe saying it's still a 32-bit app, but will work fine on the Vista 64-bit platform? Would appreciate somebody clarifying that point.
Bill Buchanan
Buchanan Film Co.

Good Marketing.
Dave

Premiere Elements project imported into Premiere Pro CS5.5 becomes unusable after first save

I have Premiere Pro CS5.5, and I have been trying for some time to successfuly edit an old project that was originally created in Premiere Elements (not sure which version--probably 7.0). It has the .prel extension. The project imports just fine, and I am able to edit it initially. However, if I save my new Premiere Pro project, close Pr and try to open the new project again, I get the "The project could not be loaded, it may be damaged or contain outdated elements." error message. I have tried many of the various project recovery suggestions people have made in this forum and elsewhere online, but none of them seem to work. I even opened the project in XML Wrench, but there were no errors returned when I clicked "check is well formed." Once I close the project after doing some initial editing, it is gone. Is this a known issue? Is there any way I can be able to edit the old project in Pr and save my work? Thanks!

Have you tried using the project manager to re-copy all elements and timeline etc into a totally new directory. I'm just curious to see if that would make a difference. I'd be intrested to see if when making a new project in this manor if it would because as you have stated the normal save methods haven't.

Nikon D7000 .MOV files in Premiere Pro and After Effects CS5.5

I recently upgraded from Production Premium CS5 to CS5.5. Initially Nikon D7000 .MOV files used in previous CS5 Premiere Pro project would not play well in CS5.5. Now .MOV files do work in both PP and AE CS5.5. Here are the steps I followed. Not recommending you follow my steps exactly, just providing info for those that are interested.
1.       Launch Premiere Pro CS5.5 and open previous PP CS5 project, convert project to CS5.5 and rename project file as not to replace previous CS5 project file.
a.       At this point .MOV files do not play in new project or in AE CS5.5
b.      Close Premiere Pro and After Effect if still running.
2.       Using Adobe Bridge CS5.5, batch rename;
a.       Make copies of original files to new folder location while renaming file extension from .MOV to .mpg
b.      Let Adobe Bridge finish creating all new thumbnail previews.
c.       Leave Bridge running in background.
3.       Launch Premiere Pro CS5.5, let Premiere finish recreating thumbnail previews if needed.
a.       Attempt to preview existing .MOV file in project. It worked for me.
b.      Attempt to play sequence containing .MOV files. It worked for me.
c.       Attempt to play or modify sequence .MOV files in AE CS5.5 via Dynamic Link within Premiere. It worked for me.
d.      Close Premiere Pro project and AE projects if open.
4.       Create new Premiere Pro project and sequence
a.       Import a different Nikon D7000 .MOV file not previously used or renamed.
b.      Attempt to play this newly imported .MOV file. This worked for me as well.
c.       The new, previously un-renamed .MOV file also worked in AE CS5.5 for me.
I will perform additional tests but at the moment Nikon D7000 .MOV files are working for me in CS5.5 after initially performing a batch rename in Bridge CS5.5 from .MOV to .mpg and letting Bridge create preview files. Even .MOV files not renamed now work.
An example of Nikon D7000 footage edited with Adobe Premiere Pro CS5.5, After Effects CS5.5, and Sound Booth CS5 can be seen on my blog, http://stevelandonsmyth.typepad.com/steve-landon-smyths-blog/2011/07/my-first-hd -video-shoot-with-nikon-d7000.html
My system: MacBook Pro 17" 2.3 GHz i7 quad core, 8GB RAM, 500MB SSD
Message was edited by: Steve Landon-Smyth

Hello,
I see 2 post in this thread from Todd that say they are working on a fix and it should be out soon. One is from July, the other from August. It is now Sept 7th and I still see no patches or fixes for any bugs. I spent 400 dollars on an upgrade, but is this upgrade going to be supported?
This is making me rethink upgrading to the .5's in the future.
It is a minor bug to most, but in that sense it should be an easy quick fix. Am I wrong? Is this really a complicated issue?
I apologize if this comes off like a rant, but thats kinda what it is. It is not hard to batch rename files, but its a pain to have to relink all those files in PP.

Blackmagic ultra studio sdi not working with Premiere Pro 8cc or A.E.cc(2014) on win7 GT630m i7 laptop - But works in A.E.cc(12.2.1.5)

There's a problem with the new update, as I no longer can use my BM Ultra Stdio SDI for monitoring. It let me select it but no image just black frame, with the new premiere pro cc 8 or a.e. cc (2014)
But i have No Problem in A.E. cc (12.2.1.5) work find just like it should, So what has happen here ? My system is Win7 Ultmate Laptop i7 Toshiba Satellite p850, dual gpu's GT630m & Intel HD 4000
With the latest blalckmagic drivers installed (10.1.1) This needs to be looked into, there is no way of monitoring accurately .

Problem Solved! (with a small catch)
While searching crashing issues I came across this thread,"Premiere Pro random crashing since update to 2014.2"
Marc_Lec Answered (and I paraphrase here)"...I had the same problem and this is what I did. In 'Preferences Memory' I increased the memory reserved for other application to at least half the installed and changed the optimize render from 'performance' to 'memory."
Thank You Marc_Lec for what has been a game changer for me since my last computer and the beginning of PremiereCC problems.
I changed my Memory reserved for Other Applications from the default 7gigs to 1/2 of my approx.31 available Gigs = 16Gigs. Viola!
No more crashing what-so-ever!
I still have to purchase an older GTX 980 graphics card to take advantage of Adobe's approved code to utilize X=Cuda Cores and GPU, but I think I'll hang onto my new TitanX, in hopes that Adobe will write code and approve it someday in the near future.
Now why doesn't Adobe say this officially about Memory Settings? (I don't know maybe they do and I missed I somewhere)
Mine and probably many peoples computers problems here on this board may be attributed to a simple Memory adjustment, because the computer needs more than 7Gigs to run itself, not to mention Premiere.

Audio balance greatly different in Encore CS3 after encoding 5.1 master track in Premiere Pro CS3

Hello! I'm wondering if anyone can offer some advice for my DVD audio problem.
I have a Premiere Pro CS3 project with a 5.1 master track that appears to behave correctly judging by the meters when I play it in PP. It also sounds reasonable (in a mixed-down fashion, I guess) on my PC system's speakers (L,R,LFE), and all rebalancing and panning seems to work well. However, once I export the master track to Encore using PP's SurCode Dolby Digital codec, the resulting audio mix is totally off. Here's what I get: both front channels play mainly out of the right front and center speakers, and the rear channels play mainly out of the left front speaker. I've tried all different settings, but I can't seem to change this. Well I've read that Encore just sends the audio mix straight through (the DVD trancode status is "Don't transcode"), but when I build the DVD and play it on both of my 5.1 surround systems, the results are just as bad as what my desktop PC speakers were hinting at. [Actually all DVDs that Encore builds are UNSUPPORTED on one of my set-top DVD players and they're both Panasonic! So first, I first have to copy the DVD using Nero and then the copy is accepted by all. That seems to have no bearing on my audio dilemma but I thought I'd mention it. I would love to know what Nero is doing right that Encore is doing wrong!)
Anyway, here's some background: I began to notice this problem with the audio balancing whenever a .wav music source is imported into PP as a stereo source. [A side issue here - I don't seem to be able to explain - or control - how one .wav file gets imported as stereo while another is imported as 5.1!] Anyway, as one would expect, since my master track is 5.1, the stereo track is automatically set up with a rebalancing tray with the puck set in the middle. The meters show that the source is stereo and the sound has been rebalanced across the master track. If I drag the puck around, the master meters behave accordingly. Then I import my video (.avi video clip) and that sound is imported as a stereo track. For that track, I drag the puck to the rear. Again, the master meters respond correctly. So far so good. But when I export to Encore, the resulting audio mix so completely wrong it can't even be explained as a 5.1-to-stereo downmix situation. The sounds that were supposed to come out of the rear channels are in front left and center (and deafening), overpowering the music that is only coming out of front right. And the rear speakers are silent unless I turn on Pro-Logic on my amplifier, which just confuses the issue. I didn't bother to check LFE as things were bad enough.
Where I DO NOT have the problem is when the audio file is imported as a 5.1 source (although it is just a stereo CD track ripped using Sony CD Architect). In that case, there is no rebalancing tray and the track meter shows only the L and R channels active, as expected. Ditto for the master track. Now if I go ahead and send the music to a stereo submix track and let that rebalance to the master, I see all channels active. But that results in the problem above after exporting to Adobe Media Encoder using SurCode and then importing the audio into Encore. If I don't remix to 5.1, the audio on the DVD is OK. But I would like to have the music come out of all speakers when there isn't a video soundtrack as there are many still pictures in the presentation.
So the question is, if I can rebalance and pan channels in PP CS3, why are the results coming out all wrong in Encore using SurCode? And how can I hear my project on DVD the same way I mixed in PP?
Any help would be greatly appreciated!
Doug Herbst
Holmdel NJ

Problem solved everyone!!!
Rebecca of Adobe support helped me identify the root cause: project was originally set up as standard (2-channel) and although it had evolved to a 5.1 project over time, it could never grow up to be anything other than a standard audio project. After you set up the new project, the setting that controls your audio is buried in the project somewhere. Changing your project settings to set up new 5.1 audio tracks for new timelines does NOT make the project 5.1! The real audio identity attribute set at birth is not alterable OR EVEN VISIBLE (even as a grayed-out project setting) although PP will allow you to set up and mix 5.1 audio tracks at will. So you may think you're working on a 5.1 project now, but you're only fooling yourself and PP goes right along with it. Even the .ac3 files you create via export are 5.1! But dare to build your DVD in Encore and all of your timelines are transcoded back to 2.0 instantly. Resistance is futile.
A new feature in PP CS4 will allow you to view, and even CHANGE, your project's audio identify from standard to 5.1. How sweet!
Well, I've devised a way to dig out myself out of this deep hole in CS3 and it worked, but I can't promise that it will work for everyone. (This assumes you own the Dolby Digital 5.1 codec from Minnetonka.)
1. Create a new Premiere Pro project as 5.1 audio from the get-go.
2. Import your suspected 2.0 project into this new 5.1 project and click each sequence to flesh out the timeline.
3. Re-export all audio as elemental streams using Adobe Media Encoder. Make sure you export the audio component of each timeline as Dolby Digital 5.1 and exactly - and I mean EXACTLY - the same way. To deviate the audio settings for each timeline is to ask for trouble, so I recommend setting up an audio pre-set that you can just click when you need it.
4. Create a new Encore project and import all original video assets and your new replaced and, hopefully, 5.1 audio assets into it.
5. In Encore, create a separate timeline for each pair of assets (.m2v and .ac3 for example). DO NOT ATTEMPT TO PLACE MULTIPLE PAIRS OF ASSETS ON THE SAME TIMELINE! For some unexplained reason, the build process will transcode the audio back to 2.0, and if you continue pack new 5.1 audio assets on the same timeline, you will get an error message "an input contract violation has occurred" because you now have 2.0 and 5.1 assets on the same timeline, even though you really don't know that and didn't ask for that to happen anyway. (Thanks to Bill Hunt who mentioned his habit of keeping the asset pairs on separate timelines in another thread - that suggestion was absolutely essential to the solution here.)
6. In Encore, check to make sure that all of your original video sychs up correctly with the new, true 5.1 audio. Link the end actions of each timeline with the next timeline to play in the correct sequence. Check your project for orphan timelines and other errors. Then, before you start building menus and start getting fancy, build a DVD and make sure it plays as 5.1 on your system.
Tip #1: while you're re-exporting and replacing the audio files, don't have Encore running. I've seen it gracefully and automatically re-import the replaced file once the export is done, but I have also seen it choke with the terribly descriptive "Encore has encountered a problem" message upon discovered the asset is not available while it is being replaced. Encore then continues to mark the asset as offline.
Tip #2: when re-exporting and replacing files, always select audio and video separately. For some reason, Encore will allow you to replace an .ac3 file when you perform an elemental audio export, but when you try to combine video and audio and both files exist, Encore will prompt you to replace the video, but immediately abort with an error that it cannot replace the .ac3 file, thus forcing you to delete the .ac3 component manually before trying again.
Doug

Cannot install update on Premiere Pro cc

2 days ago i've bnee noticed of new Premiere Pro cc update. Tryed to install but fails: gives me an error istalling the patch.
Then unistalled Premiere Pro Cc and just installed again, but got the same problem. The system is able to install Premiere Pro cc but not the patch.
The additonal problem is that the version of Premiere Pro CC i've been installed now seems to be eralier than the one i had before. So it cannot open my most recent project. I'm in big troubles!!!!
I got Premiere Pro Cc in spring and months ago i already have installed a previous update without any problem. It seems that the actual Premiere Pro CC version i can download is the oler one without that update.
Help me please.

The error i receive is : U44M1I210

New Premiere Pro CC SDK

Similar Messages

Maybe you are looking for