After Effects CS6 and Premiere Pro CS6 Long Startup and Application Hang

Problem:
After Effects and Premiere Pro CS5.5 and CS6 are very slow to start all of a sudden. Around 5 minutes to get to/by the intro dialogue box. For AE, the majority of the time is spent on the "initializing user interface." Then, if I can make a comp, and even a layer inside that comp, it will "Hang" if I attempt to open AE's General preferences for example (no preferences window ever comes up). This "hang" is what the Event Viewer in windows calls it, with the faulting module being afterfx.exe. Premiere is not much different. It makes it to the new project window fast, but after setting project parameters and creating the first sequence, I can't get into the preferences either and the application hangs. It is important to note that if I have another application open, like Chrome or Firefox for example at the time the application hangs, they will freeze as well. As soon as I kill the Afterfx.exe process, they come back to life.
I have read nearly all threads on the subject, and am struggling to find a solution:
Deleted preferences folder under my username's appdata.
Turned off Firewall (network traffic from dynamiclink, qtserver, etc was allowed, but what the hay)
ran windows system file checker/malwarebytes/rkill/rootkit detection.
checked for windows compatibility checkboxes under the file.
Uninstalled Wacom Tablet drivers
Disabled Aero
Started with ctrl-alt-shift to delete pref.
uninstalled video driver and replaced with one 6 months ago.
uninstalled, reinstalled, and tested various quicktime versions back to version 7.69
moved plugins folder
moved opengl's plugin out of the folder temporarily
Disabled all 3rd party codecs (xvid was the only one installed and for months)
reinitialized default directshow filters
checked for adobe font list (none found) and removed any fonts from 1 month ago to present.
used msconfig to selective startup without other applications/services running.
Uninstalled all adobe products, and reinstalled.
I performed all of these in a systematic manner, trying to solve the problem. None have fixed the problem.
So it doesn't seem to be a network issue, a codec issue, a plugin issue, a driver issue, font issue, or conflicting application. Any thoughts?
System Info:
PC Windows 7 pro 64-bit SP1
Core i7 - 960 24GB ram
AMD Radeon 6750 v12.10
Adobe CS6 Master Collection

Who's says that Microsoft can't debug?
I used msconfig, first disabling startup items, -same result.
Enabled all startup items, disabled all non-microsoft services - AE worked!
I re-enabled each service in turn until AE crashed.
The fault was related to an item for a video streaming device I have in my house. It was Monsoon-multimedia's Vulkano Service. Sometimes under the old name of Hava, this is an app that acts like a sling-box to send my Cable TV to my screen. It does load a couple of virtual devices in device manager, and uses a proprietary codec.
I uninstalled the vulkano streamer application and rebooted the external Vulkano device. I reinstalled the Vulkano and verified it connected to the device and could stream. Once it did, I tried AE again and IT WORKED!
I wonder if simply rebooting the Vulkano would have fixed it. Its like opening the garage door to turn on the refridgerator.
Thanks for the help!
Jim

Similar Messages

After Effects CS6 and Premiere Pro CS6 not available for installation for 32-bit systems

After Effects CS6 and Premiere Pro CS6 require a 64-bit operating system and processor to be installed and run.
If you subscribe to Creative Cloud but use a 32-bit computer system, you will not be able to download and install Premiere Pro CS6 or After Effects CS6.
This issue primarily affects users on the Windows operating system, since all supported versions of the Mac OSX operating system are able to run 64-bit applications.
See this document for details:
"64-bit Windows required for After Effects and Premiere Pro CS6"
In general, you can only download and use applications for which your computer system meets the minimum system requirements.
Premiere Pro system requirements
After Effects system requirements

Who's says that Microsoft can't debug?
I used msconfig, first disabling startup items, -same result.
Enabled all startup items, disabled all non-microsoft services - AE worked!
I re-enabled each service in turn until AE crashed.
The fault was related to an item for a video streaming device I have in my house. It was Monsoon-multimedia's Vulkano Service. Sometimes under the old name of Hava, this is an app that acts like a sling-box to send my Cable TV to my screen. It does load a couple of virtual devices in device manager, and uses a proprietary codec.
I uninstalled the vulkano streamer application and rebooted the external Vulkano device. I reinstalled the Vulkano and verified it connected to the device and could stream. Once it did, I tried AE again and IT WORKED!
I wonder if simply rebooting the Vulkano would have fixed it. Its like opening the garage door to turn on the refridgerator.
Thanks for the help!
Jim

AMD FirePro D500 and Premiere Pro CS6 and After Effects CS6?

My company just recently purchased the new 2013 Mac Pro with the AMD FirePro D500 graphics cards. Everytime I try to open After Effects CS6 I get a GPUManager Sniffer Result Code: 3 error and Premiere Pro CS6 sits on the splash screen indefinitely. Does Adobe not play nice with the new card? Am I out of luck?

In effort to fix the problem while waiting for a response I unstalled both AE and PP CS6 but not I can't seem to reinstall them from anywhere.... so I don't know what version of After Effects I have/had.
My operating sysem is OS X 10.9.2 (13C64) . My graphics card information is:
AMD FirePro D500:
Chipset Model:          AMD FirePro D500
Type:          GPU
Bus:          PCIe
Slot:          Slot-1
PCIe Lane Width:          x16
VRAM (Total):          3072 MB
Vendor:          ATI (0x1002)
Device ID:          0x679e
Revision ID:          0x0000
ROM Revision:          113-C3861J-687
gMux Version:          4.0.11 [3.2.8]
EFI Driver Version:          01.00.687
As far as CUDA, I originally had an iMac that was using Time Machine and that is how I transfered my stuff over to the new Mac Pro. It had CUDA on there...

IMac and Premiere Pro CS6 compatability

Hi
I am currently importing HD footage off a DSLR Canon 60D (h.264) into an old macbook with PP CS4. I have to render every bit of footage before I can view it without juddering. Every time I add a transition or title etc, I have to render again to view it cleanly.
It's time to upgrade.
I'd like an iMac. I know the cost arguments, but I am not interested in buying a PC. An iMac is cheaper than a MacBook Pro, and I'd like the extra screen space.
But I'm getting confused about what will actually happen if I try and work Premiere Pro CS6 on an iMac.
1.Will it simply not work? Or will it just not have as good as performance as it could?
2.Does it mean I would only lose out on the GPU processing? With my DSLR footage, will I be able to watch it, judder free, without having to render it first?
3.If it does still fundamentally work, at what point would it start to falter? How much would I have to have going on in a project for it to need the power of the merucry playback engine?
4.Does anyone know IF a new iMac came out in the next two months, would it likely have the 1GB VRAM or would Adobe offer an update so that it worked with whatever the new iMac had. (eg the current top end iMac has AMD Radeon HD 6970M with 1GB, yet is not supported by CS6 - why?)
Finally, why do Apple and Adobe have to make this so difficult?
Many thanks for anyone's help.

nepmedia wrote:
We need to make CS6 compatible with AMD 6970M, on an IMAC, thats all there is to it. Any ideas?
You could do some experimentation and see if the OpenCL text file works the same way as the CUDA text file. I'm betting it does, but I have no direct experience. I think it's worth looking into tho...
Open a new Finder window and navigate to the Adobe Premiere Pro CS6 folder.
Right-click on the Adobe Premiere Pro CS6.app icon, and chose "Show Contents" from the menu.
A new window will pop open; open the Contents folder.
Double-click on the file named: opencl_supported_cards.txt. If it asks you what application to use to open it, select TextEdit.
Now... be VERY CAREFUL what you type here. Add a new line to the file and on it: ATI Radeon HD 6790M
That's it. COMMAND-S to save the file, COMMAND-W to close the file, and COMMAND-Q to quit TextEdit.
Alternatively, if you're comfortable in the UNIX environment like I am, open a Terminal.app window and do the following:
cd /Applications/Adobe\ Premiere\ Pro\ CS6/Adobe\ Premiere\ Pro\ CS6.app/Contents
sudo vi opencl_supported_cards.txt
Perform the above edit in vi, then save and close the file.
Start Premiere Pro back up and see if you have MPE available in hardware mode. Bear in mind: you're not going to be supported by Adobe if any issues pop up due to MPE stuff... this is an aftermarket "modification" to your software.
jas

AVCHD blown highlights in AE and Premiere Pro CS6

Hi Guys,
I have the NEX 5n and Premiere Pro CS6 on Windows 7 Workstation.
It seems as if Premiere is geting the 0-255 16-235 Levels kind of wrong. AVCHD files of all kinds have clipped highlights when exposure on the NEX or any other camcorder is set spot on before clipping.
In PP cs6 and cs5.5 you can just bring all the Information that is above 1.0 in the waveform down with any 32 bit Filter that deals with Levels. But it schouldnt be up there above 1.0 in the first place or am I wrong?
This also applies to the Canon XA10 camcorder
clipped whites:
[IMG]http://i46.tinypic.com/az9fm.jpg[/IMG]
Levels adjusted with 32 bit Filter in PP = No clipping in highlights
[IMG]http://i48.tinypic.com/ofrl86.jpg[/IMG]
In AfterEffects its different: You would have to work the whole AE Project in 32 bit to be able to save the clipped detail in the whites. If you work in 8bit (which is standard ae project) then AE will just cut off all the info above 1.0.
But the question is: Is Adobe getting it wrong in the second consecutive Version of PP that is supposed to deal nativly with AVCHD? Or why do highlights that are not clipped on any AVCHD camcorder, appear as clipped in PP cs5.5 and cs6
Even the opensource FFDSHOW codec gets it spot on when played with mpclassic (as Andrew Reid from EOSHD.com stated and I also can confirm this)
Also when I connect the nex 5n with hdmi to my Plasma everything plays just fine no clipping at all!

when exposure on the NEX or any other camcorder is set spot on
Are you saying the waveform on the camera is displaying the same image differently to the wfm in PPRO? I would be surprised if that were the case.
That paper kind of looks very "hot" and it doesnt surprise me what the wfm is showing here.
FWIW: I extensively monitor my AVCHD by using level, gray and color cards in my shots. The wfms in the camera, monitor and PPRO always correspond.
Try shooting a color chart and also checkout .some color bars generated by your camera.

Dynamic Link from After Effects CC to Premiere Pro CC Performance Issues

I just updated my After Effects and Premiere Pro to CC and since doing so I've found numerous performance issues. One that is seriously hurting my workflow is the poor performance of the dynamic link with After Effects compositions into Premiere Pro. In CS6, you could make a change to the AE composition, save it, click over to Premiere Pro and it would quickly update and you can play your timeline and preview your changes. You could also move the clips around and add cross dissolves and watch the changes quickly in Premiere Pro CS6. Now, since updating to CC, if you save the composition in AE and click over to Premiere Pro it won't update on its own. Sometimes it just shows a single frame of the AE composition. I found that if you right click and "Edit Original", go into AE and then click back over to Premiere Pro and it will finally update. But if you make any changes to the placement of the AE composition on the timeline, or add a cross dissolve, fade, etc. it again won't play the AE composition any longer. After you make any changes to the AE composition you have to right click and go to "Edit Original", go into AE, and then click back over to Premiere Pro.. Then it will finally update.
iMac
Quad Core 3.4GHz
32G RAM
OS X Mavericks

Thanks Kevin.
Unfortunately in my case the export doesn't solve the issue. The video only looks good while in the composition... I've tried exporting it in all the different formats with several codecs, but to no avail...
You can check my own post in the After Effects forum: AE linked composition looks different in Premiere

After Effects export as Premiere Pro project weird PAL/NTSC problem

This post is not a question. It's here, because I've found a solution and want to share with You.
I've noticed a strange problem during export from AE to PR.
Ok, here I go.
AE = After Effects CS3
PR = Premiere Pro CS3
My AE project is D1/DV PAL Widescreen. It is a sequence of slideshow with some video effects applied. I needed that sequence in PR. I was happy to find a new feature - export as premiere pro project (new for me - i am pretty rookie ;). Thaks to this feature I have saved most of my disk space that is always to low. But, like every first try, this one was not perfect too. I had two problems.
Problem no 1.
I opened exported project in PR and saw message like "video effect AE.CC COMPOSITE not present".
Whole composition was working perfectly except that one video effect that was fundamental for this project.
*Solution was as easy as it can be. I've just copied that effect from AE plugin folder to PR plugin folder. It worked for this.
Problem no 2
Like says AE Help "When you export an After Effects project as an Adobe Premiere Pro project, Adobe Premiere Pro uses the settings from the first composition in the After Effects project for all subsequent sequences."
Project settings in PR was exactly D1/DV PAL Widescreen. So where is the problem You ask?
Therefore why my Timeline works in NTSC 29,97 frame rate if all settings match PAL 25 frame rate?! I don't know.
*Solution to fix this annoying bug is to create a new project in PR with all settings for D1/DV PAL Widescreen in this case. Than just import that PR project exported from AE. Now timeline works like it should in PAL frame rate.
That's it.
I hope this post is helpful, because I didn't find any answer for this here in Adobe forum.
Adam

Who's says that Microsoft can't debug?
I used msconfig, first disabling startup items, -same result.
Enabled all startup items, disabled all non-microsoft services - AE worked!
I re-enabled each service in turn until AE crashed.
The fault was related to an item for a video streaming device I have in my house. It was Monsoon-multimedia's Vulkano Service. Sometimes under the old name of Hava, this is an app that acts like a sling-box to send my Cable TV to my screen. It does load a couple of virtual devices in device manager, and uses a proprietary codec.
I uninstalled the vulkano streamer application and rebooted the external Vulkano device. I reinstalled the Vulkano and verified it connected to the device and could stream. Once it did, I tried AE again and IT WORKED!
I wonder if simply rebooting the Vulkano would have fixed it. Its like opening the garage door to turn on the refridgerator.
Thanks for the help!
Jim

After Effects project into Premiere Pro

I am having trouble importing my After Effects project into Premiere. It isn't playing once I bring it in to my premiere.

What versions of After Effects and Premiere Pro? What operating system? What kinds of source footage?
What exactly are you doing? What menu commands are you choosing, and what things are you clicking, and in what order?
Here is a page that describes ways to move things from After Effects and Premiere Pro and vice versa:
"Working with Premiere Pro and After Effects
There are many ways to move things between these applications, but importing an After Effects project into Premiere Pro is not one of them, so I'm confused by your issue as you've stated it.

CC and Premiere Pro CS6 will not open

I have downloaded and installed the app twice.
I go into Creative Cloud and I can see Premiere Pro CS6 is an installed app but i can not click on it to run it.
At this point is have spent an hour trying to run one app.
I get no error it just does nothing.......
Just want to try it... So far it is not looking good....

What about the Program Files location? If you don't see it there, use the CC cleaner tool to uninstall the apps and then reinstall again. Use the CC Cleaner Tool to solve installation problems | CC, CS3-CS6
Thanks,
Rameez

Red Rocket and Premiere Pro CS6

So what I want to know is what exactly does the Red Rocket add to Premiere Pro CS6? I have one installed in my Mac Pro and have found similiar performance with it off and on in terms of playback and rendering. I found this post from Adobe employee Will Renczes in another thread:
To the OP: I think you need to unravel the complexity. You should also be able to get 4K RED files playing back @ 1/4 res without a Rocket - the only thing the Rocket brings to the table is realtime debayering @ full res. There's plenty of people editing 4K footage on macbooks @ 1/4 res...
Is that really the only advantage to this $5000 card in Premiere? I won't see any increase in performance unless the playback resolution is set to full? I just tried a test and my computer definately lags playing it back in full res without the RR, but it still stutters a bit even with the RR activated. I guess I wish it helped the playback at lower resolutions, as well as during the export process.
Do any other Adobe CS6 apps make use of it better (Speedgrade perhaps)? If this card really isn't doing all that much, might just try to sell it. Darn you Adobe for being able to edit RED footage without a crazy expensive card!
-sam

Look at the preview resolution for your Red Timeline in Adobe. If you want to play 4K and 5K out to a monitoring solution able to handle that via Redcine-X then the Red Rocket is the way to go right now. If your transcoding red files constantly via Redcine-X then it also speeds that up. This is the case atleast till you start seeing HDMi 1.4 monitors that support 4K res.
Eric
ADK

Adobe story and premiere pro CS6

There apparently is an incompatiblity between Abobe Story Plus and Premiere Pro. How do I "number the scenes" in PP6? In the project window, there is no "number." Nor in Adobe story, there is no "number" either. I've looked all the way through both. Help!

Subbi - It is still not working. Let me start from the beginning.
I have uploaded .m2t files in PP6.
I start Story, hit New, then hit Create.
Then I hit Production>Manage Scene Numbers. Then a new window pops up. I click OK.
Still in Story, in hit File>ExportAs>Adobe Export Interchange Format (.astx)
Then I hit SAVE.
Tab over to PP6.
In PROJECT, find the Scene column. Set it to 1. Left click out.
In PROJECT, with the clip selected, right click, scroll down to ATTACH SCRIPT FILE and click.
A new box comes up. Select the .astx file, and click OK.
It works up to here.
In the Metadata Panel, I don't find the "Embedded Script Metadata," or the Metadata Display. One problem may be part of the old post was referring to PP5.5. I am using PP6.
Help again!

Importing After Effects document to Premiere Pro errors: "The importer reported a generic error."

I´m using Premiere Pro CC ver 2014.1. and After Effets 2014.1.1. in OS X Yosemite. I can't import After Effects project to Premiere.
There is always same error message: "The importer reported a generic error."
I have tryed to save After document several different names and greate new ones. Always same error. Whats wrong in my workflow?

Okay so I've searched around most of this forum and as much of Google as I could find - I have found similar problems, but nothing exactly the same; and none of the solutions I've found have worked for me. I've seen a lot of people having trouble connecting to the DL server on the file-selection window, but I don't even get that far - an error message just pops up in the middle of my screen - and my error doesn't mention a server, just that it can't connect to AE DL.
I changed firewall software (which I've wanted to do for months, anyway) and still to no avail.
As for the "The importer reported a generic error" problem also, I can't find any problems or solutions with After Effects files not being able to be imported.

Need help with Go Pro Hero 3 and Premiere Pro CS6

Hello,
I recently acquired PP CS6. I put my clip (30 seconds long) and I go to preview while editing, for the first 1.5 seconds it is fine but then it is very choppy. The audio is fine but the video does not play smoothly. When I save and process the video it is fine. It is frustrating to try to edit video this way. I'm sure I'm missing a step when creating the project but I haven't used Premiere Pro since CS6. This is only happening with Go Pro Hero 3 videos, any of my other cameras are fine. Any ideas? Thanks

There's a lot of confusion over how video encoding affects subsequent editing performance - a higher data rate has no direct relation to how much effort is required to decode and play the footage, in fact a higher data rate often makes playback easier - which is why transcoding to AVI can help with playback even though the files can be hundreds of times larger. Data rates with the same codec depend on the frame contents and recording quality, but for playback and editing what matters is the GOP (group-of-pictures) structure and the complexity of the encoding algorithm. Provided your disks are fast enough the data rate is immaterial to Premiere.
With long-GOP files (as typically created by consumer DSLRs and helmet cams) we have keyframes (I-frames) with a complete set of pixel data, then a series of intervening P- and B-frames which only store the difference between 'now' and 'one frame before' or 'one frame after'. Unless you're on an I-frame you have to calculate the chain of differences from the nearest I-frame, and when editing or applying an effect we must re-calculate the entire GOP, so Premiere has to hold a lot of data in the buffer. Remember all timelines in Premiere are internally transcoded to 32-bit floating point, so it's more work to 'play' the footage in the monitors than would be done by a simple playback-only application such as VLC, or in some other brands of NLE that only work in the footage's color space. Premiere's hardware acceleration (MPE) only kicks in once the buffer has been ingested, all the decoding of the original H.264 frames happens in your CPU.
With digital cinema cameras and some hacked DSLRs, we record "all-I" footage - so there's no GOP overhead and playback/editing is massively smoother. I can scrub all-I footage from a hacked 7D no problem on my relatively-ancient spare laptop, but the long-GOP files from a factory 7D struggle to play at all. Our all-I 7D footage can hit 300MBit/s compared to 35 for long-GOP. Helmet cams such as the GoPro do all they possibly can to squeeze data onto their storage cards, which means they have long-GOP codecs that have some of the most complicated compression algorithms out there. The Hero3's implementation of H.264 uses the Ambarella chip, whose files are very small but an utter nightmare to decode - hence far more of a demand on your CPU than an equivalent clip from a DSLR.
Jim Simon wrote:
Might be the 35 Mbps that is causing the choppy playback.
It shouldn't, assuming sufficient hardware. My GH2 clips often get up to over 90 Mb/s and play just fine on an older i7 920.

W530 Quadro K2000m and Premiere Pro CS6

Hi all,
I have a W530 with i7, Q K2000m, 32gb ram and 3 interal drives (1msata ssd, 2 hgst 7k1000 1tb in the other two bays). I don't know whether I have an issue or not, but:
1) CUDA acceleration is enabled. So we're OK in this.
2) When I assemble a few clips together, although the render line is yellow, after a few seconds, the videos start becoming choppy. So, I was wondering how can this because I am only editing a 720p timeline and I have not graded anything yet. Just warp stabilizer on some clips and some of them (since I shot at 60p) are slowed down to 24p.
3) When I run GPU-Z, I am only seeing a 8-15% GPU load rate.
4) Because I can't reverse time and stabilize at the same time, I stabilized a clip on another sequence and then nested that sequence in my main sequence. Now, when I reverse that nested sequence...I get a blank screen UNLESS I kill the hardware acceleration and switch to CPU only (this seems to be a Premiere Pro issue)
5) I did everything possible to make sure that the Quadro card was working. I turned everything to "Performance NVIDIA graphics) in the NVIDIA control panel. I installed the latest drivers from NVIDIA the day before yesterday. I even flashed my BIOS to the latest downloadabale from Lenovo's System Update.
Am I missing something? Or is the card just underclocked and under-powered on purpose? Why can it not run at beyond 15% load when the clips are choppy on playback?
You may noticed I am a bit frustrated...but hey...I love the machine so I hope I am missing something that I can set up to make it all run smoothly again.
Many thanks for any ideas, guidance.
PS: All captured clips are in the 1st HDD on the main bay and the scratch/preview disk is the 2nd HDD on the CD drive. Premiere is running from the mSATA SSD (Plextor M5M 256GB)
Solved!
Go to Solution.

I don't have Premiere, so I can't see by comparison what happens on my own W530 which only has a K1000m. I also don't know if your symptoms are due to hardware or sofware (i.e. Premiere itself). Do you have another machine of your own to try the same experiment against, to see what GPU usage measures at and whether the visual results are seemingly as poor as you describe on your W530, or are they much better visual results and much higher performing as measured?
Aside from our both doing something in common, to compare results, I just took a look at two video applications on my own W530: (a) VideoReDo TV Suite 5 editing both 720p and 1080i copy-freely WTV recorded videos made by Windows Media Center (on my HTPC), and (b) Windows Media Center running on the W530 and playing both of these 720p and 1080i WTV recordings. I opened GPU-Z while the video apps were running to monitor the GPU load. I also have Aida64 running, which also displays presumably the same "GPU utilization". I expect VRD to use less GPU horsepower than Windows Media Center uses.
Also, here is my Lenovo Power Manager setup, with my i7-3720QM 8GB W530/K1000m 512GB Samsung 840 Pro SSD powered into the wall. The display is external 24" Eizo S2433W monitor (miniDP->DP from the W530), 1920x1200, laptop screen OFF. I'm running "discrete graphics" in the BIOS, using "retail" nVidia driver 347.88.
And here's Windows Media Center playing a 1080i video (which involves hardware de-interlacing), and showing 57% GPU load through GPU-Z. Note that with Aida64 (on the right side of the image) it also shows 55% GPU utilization, so this number is clearly correct.
And the same clip being "edited" using VideoRedo. Note that GPU usage is now down to 35% (at least at this instant), as I expected. I'm quite sure hardware de-interlacing is also taking place.
Video performance with both apps is superb.
Anyway, without our being able to duplicate the other's test situation, I don't know what to suggest that you haven't already done. Unfortunately I don't have Premiere to try.

Problem importing XDCAM-EX IN After Effects CC or Premiere Pro

We have recently installed CC in our labs, and now we can't import XDCAM-EX, using the media browser neither in Premiere Pro nor in After effects.
We get "Usupported format or damaged file" error
I have made all the last upgrades, but still getting the problem.
The AE version is: 12.1.0.168
PP version is 7.1.0 (141)
I have a machine where kept the CS6 installation, in this machine in CS6 everithing works OK , in the same machine CC gives the error.
All the labs where freshly installed Windows 7 (no upgrades or reminecnts of old programs or codecs)
The file structure of the memory card hasn't been touched and with programs like SONY XDCAM Clip Browser, the clip looks fine and with no errors.
Ruben Zilzer
Sapir College
Israel

I seems that the problem is with the Premiere Pro CC update (7.1.0)
This is what i have done to solve the problem:
Using the Creative Cloud packager I prepared a new build containing only Premiere Pro CC with no updates, only the basic application.
I ran the new msi on top of the Creative cloud installation (without previosly removing any program) and now Premiere Pro CC, After Effects CC and Prelude CC ingest/import the XDCAM-ex files correctly
Now I have to do this in the 65 machines of the labs...

After Effects CS6 and Premiere Pro CS6 Long Startup and Application Hang

Similar Messages

Maybe you are looking for