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

Similar Messages

Fix for crash in After Effects CS5 and Premiere Pro CS5 when Joesoft Hear audio enhancer installed

After Effects CS5 and Premiere Pro CS5 both can crash due to a conflict with the Joesoft Hear audio enhancer.
We've just gotten confirmation from Joesoft that they've released a beta version of Hear that doesn't conflict with After Effects CS5 and Premiere Pro CS5. We're recommending that our customers who also use Hear install the 1.0.5b2 (build 490) beta version of Hear.
Let us know on this forum thread whether this solution works for you. We on the After Effects and Premiere Pro teams will monitor this thread for feedback, and we'll make sure that the folks at Joesoft get the information that they need, too.
When reporting back, be sure to let us know whether you've installed the Premiere Pro CS5 (5.0.2) update and After Effects CS5 (10.0.1) update.

After 2 days trying to get AE and Premiere past the mediacore initialization message, I finally stumbled on this little message. Updating Hear definitely solves the problem!

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

After Effects CC and Premiere Pro CC don't play well together on new Mac Pros

Would love some insight from folks on this. We have welcomed 2 new mac pros w dual D700's into our edit suites and have found an issue we need some help finding a work around for.
With Creative Cloud we're used to rendering a large amount of graphics in After Effects, and while that's underway, our editors will often go on and work in Premiere on the edit. Unfortunately, with the new Mac Pros After Effects render process seems to freeze up the moment we open Premiere and start to work. Any fixes for this? Special Memory allocation? Patch? I've heard the lack of Cuda might be the issue, but can't imagine Adobe would not support something that keeps their product running smoothly.
Please let us know and we are grateful and thank you in advance...
[email protected]

This forum is actually about the Cloud, not about using individual programs
Once your program downloads and installs with no errors, you need the program forums
If you start at the Forums Index http://forums.adobe.com/index.jspa
You will be able to select a forum for the specific Adobe product(s) you use
Click the "down arrow" symbol on the right (where it says ALL FORUMS) to open the drop down list and scroll
http://forums.adobe.com/community/premiere
or
http://forums.adobe.com/community/aftereffects_general_discussion

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.

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

Purchased the master suite and premiere pro does not open

purchased the master suite and premiere pro does not open

Mac or Windows, and exactly which version of the operating system... which version of Master Suite (CS5 or CS6 or ???) and what error message do you see?

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!

After Effect CC and Flash Pro CC did not successfully update 19th June '14

After Effects CC and Flash Professional CC did not successfully update, even after several attempts. All other Apps are currently up to date with today's update release. 19th June '14

Hi Rob,
Did you get any error message when you tried to update After Effects CC? Can you share more details?
Thanks,
Jyothi

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

Similar Messages

Maybe you are looking for