AME Adobe Media Encoder Cuda GPU Acceleration not activated, How do I activate it

Mac Pro Early 2009 4.1, Processor 2.93 GHz Quad-Core Intel Xeon, Memory 16 GB 1066 MHz DDR3 ECC, Graphics NVIDIA GeForce GTX 680 2048 MB, Software OS X 10.9.2 (13C64)
Adobe CS6 suite up to date all programs as of 3-18-14
NVidia Cuda Driver 5.5.47 installed, Open CL and GL capable
I read this article http://blogs.adobe.com/kevinmonahan/2013/09/13/enabling-cuda-for-the-mercury-playback-engi ne-in-the-macbook-pro-retina/. it shows GPU acceleration through AME (see below). In my AME que window I do not see this

Todd:
(edit)
Just reread - sorry, CS6 vs CC.
What about AME CC?
http://blogs.adobe.com/kevinmonahan/2013/09/13/enabling-cuda-for-the-m ercury-playback-engine-in-the-macbook-pro-retina/
So, CUDA acceleration in AME and OpenCL is supported. Anyway to monitor this? I get FAILED when I try either (on a box with nVidia, or a box with AMD).
Found this: http://helpx.adobe.com/media-encoder/using/whats-new-media-encoder-7-1.html#gpu-accelerati on
GPU acceleration
Adobe Media Encoder now takes advantage of GPU for rendering purposes. Both CUDA and OpenCL are supported. The latest release of AME uses the GPU for the following renders:
Scaling (HD to SD; SD to HD)
Timecode filter
Pixel format conversions
Deinterlacing
Aspect ratio changes
All effects in the Effects tab
GPU accelerated effects in Premiere Pro
If you are rendering a Premiere Pro sequence, Adobe Media Encoder will use the GPU render preference you have set for the project. All GPU rendering capabilities of Premiere Pro are utilized.The limited set of GPU renderable tasks in Adobe Media Encoder is only for renders that originate in Adobe Media Encoder.
If you are rendering a sequence with native sequence support, the GPU setting in AME is used and the project setting is ignored. In this case, all GPU rendering capabilities of Premiere Pro are utilized directly in AME.
If your project uses 3rd party VSTs (Virtual Studio plugins), the GPU setting in the project is used. The sequence is encoded through headless Premiere Pro just as in earlier versions of Adobe Media Encoder. If Enable Native Premiere Pro Sequence Import option is unchecked, headless Premiere Pro will always be used and the GPU setting is used.

Similar Messages

Both After Effects & Adobe Media Encode CC giving are not letting me export.

Dear All,
Both After Effects & Adobe Media Encode CC giving are not letting me export movies.
Some times they will, but after one file both programs give me the following error messages.
After effects:
“[file path and name].mov. An output module failed. The file may be damaged or corrupted. (-1610153464)"
AME:
"Can't read from source."
I've went through the forum and found threads & pages discussing the problem.
E.g.
http://blogs.adobe.com/aftereffects/2013/08/solutions-for-problems-with-quicktime-files-in -after-effects-cc-12-0-because-of-conflict-with-dvcprohdvideoout-quicktime-component.html
http://forums.adobe.com/thread/1252092
After following all the tips and suggestions (from deinstalling quicktime components & audio components to completely reinstalling CC) I'm still experiencing the problems.
Which leaves me in a bit of a squeeze. I need to export over 144 movies in the coming 2 days and the only way to do this is to quit and open media encoder (or AE) after each single export.
Not really an option.
Both problems have the process Adobe QT sever in common, I took this from the console:
9/26/13 1:02:44.517 PM com.apple.launchd.peruser.501[171]: ([0x0-0x42042].com.adobe.Adobe QT32 Server.application[331]) Job appears to have crashed: Segmentation fault: 11
9/26/13 1:02:44.672 PM ReportCrash[354]: Saved crash report for Adobe QT32 Server[331] version 7.0.1 (7.0.1.0) to /Users/martijn/Library/Logs/DiagnosticReports/Adobe QT32 Server_2013-09-26-130244_martijns-MacBook-Pro-2.crash
System information:
Retina MacBook Pro (Mid 2012) (16gb ram)
Mac OS X 10.8.5 (12F37)
Running Adobe CC (for teams), all apps are up-to-date.
I don't no why Adobe puts out such a buggy piece of software (I know it has to with Apple's poor 32bit quicktime implimentation, but hey, this was known information no?).
Upgrading to CC has given our office nothing but problems.
Hope someone can help to find a work around until Adobe realeases a proper update and solves this problem once and for all.
All help is much appreciated.
Kind regards,
Martijn

Hello Tim,
Thanks for the really quick response!
Regarding the crash log: it doesn't reference com.apple.audio.CoreAudio (though it did before, so I followed all the steps in your blog post before I posted to this forum).
I've uploaded the crashlog to:
http://martijnlambada.com/TMP/AdobeQT32servercrash.zip
If you want to inspect it. It mentions the DXV codec (which I also uninstalled), but the crash keeps occuring. Also I need to export to DXV since it's the only codec the d3 media
server accepts (http://d3technologies.com).
I followed all the steps in the troubleshooting steps.
Codecs used: I've tried everything from animation to Apple ProRes (including: h264/motion jpeg/uncompressed). With all codecs the Adobe QT32 server keeps crashing (though I can't always reproduce).
Export destination: Internal SSD (same as where the OS is installed on) + External raid (via firewire & thunderbolt) + external HD via usb 3.0 (tried everything).
When does the problem start: Really hard to specify, sometimes a day without crashes, sometimes every export for days on end. Sometime after restarting (tried logging out, restarting, switching off and on the computer). With other programs running and with out. Now checking every process active when exporting, and comparing log files.
Can you export to other formats: See question 1, sometimes I can, sometimes not.
When you launch AE and/or AME, is QT32 Server running? At what point does it stop running? Still runing when I open the program. It crashes when exporting (ofter after finishing the first export).
What component files are in your Library/QuickTime folder?: Currently the folowing:
AppleAVCIntraCodec
AppleHDVCodec.component
AppleIntermediateCodec.component
AppleMPEG2Codec.component
AppleProResCodec.component
DesktopVideoOut.component
DVCPROHDCodec.component
DVCPROHDMuxer.component
DVCPROHDVideoDigitizer.component
DVCPROHDVideoOutput.component
DVCPROHDVideoOutputClock.component
FCP Uncompressed 422.component
iChatTheaterPreview.component
IMXCodec.component
LiveType.component
Hope this helps.
Cheers,
Martijn

I was able to print with my acrobat before, but I can no longer do it. the error message says "adobe creation cannot continue because acrobat is not activated" How do I activate it?

i was able to print with my acrobat before, but I can no longer do it. the error message says "adobe creation cannot continue because acrobat is not activated" How do I activate it?

I have the exact same issue. I can print one document and then I get the error mentionned above ("adobe creation cannot continue because acrobat is not activated"). Then I need to reboot in order to be able to print a new document.
I have suite and went to Photoshop as suggested, but this program is already activated. I tried to launch Acrobat Pro but it won't.
I'm using the Design and Web Premium CS6 Suite on Windows Vista.
Thank you so much for your help.

Adobe Media Encoder CS5.5 does not preview video in Lion 10.7.3

In response to a question in the Adobe Forums about this [ http://forums.adobe.com/message/4302817#4302817 ], Adobe said:
Apple changed something in 10.7.3 and we thought we worked with them to find all the fall out. This one slipped through. We will work with Apple to determine how we can address this.
Are there any updates on when this will be fixed? Not being able to preview video in AME5.5/MacOS 10.7.3 is a serious bug. I have to go back to an earlier version of AME on a Windows machine to encode FLVs.
Adobe Media Encoder CS 5.5.1.12 (64-bit)
Mac Lion 10.7.3

I have the same problem since I update my mac book pro Mac Lion 10.7.3
Adobe Media Encoder CS5.5 doesn't have a preview

Adobe media encoder export error "writer not found"

When trying to export to wmv using adobe media encoder I get an export error of "writer not found". I did a search and found others having the same issue with no fix as far as I can see. Just wondering if anyone has any more iformation on this. I'm using Vista Ultimate and Premiere CS3.
Thanks

I registered the WMEncoderHelper.exe file with regserv, but I still get
the "writer not found error". I wish I knew what codec it is trying to find and use.

Adobe Media Encoder CC renders do not reflect changes to Dynamically Linked After Effects Comps

When rendering a Premiere timeline with a dynamically linked After Effects composition, Adobe Media Encoder will sometimes use an older version of the linked composition (even after I have saved changes in the After Effects comp).
For example, if I correct a spelling mistake on some text in After Effects, save the composition, and then add the sequence to the render queue in Premiere, the final output from media encoder still has the old spelling.
If I do a straight export from Premiere instead of adding to render queue, the output is always correct. I've noticed this problem on several different Windows 8.1 systems.
All versions of the software are up to date as of today.
Why is this? Is it something to do with the disk cache in After Effects? Does media encoder have it's own cache that I need to clear?

Hi, I've been having this same issue. Here are some additional things I've noticed about it:
Changes are reflected properly when played back on timeline in Pr CC 2014.
Happens regardless if the dynamic link file was rendered or not, thus deleting the render files does not fix the issue.
The issue can persist through saving, closing, and reopening both AE and Pr.
I'm using OSX 10.9.4, so this is not just a PC issue.
Other than manually watching for every change to be reflected in the render, there is no way to know a problem has occurred. Needless to say this can be incredibly costly.
Please address this quickly, it's completely unacceptable that what we render out could be a different version from what we see on the timeline.
PS Some additional things I will be testing:
Does the issue persist through closing all CC apps, including Media Encoder.
Does rendering directly out of Pr, i.e. not using Media Encoder, fix the issue.

Really need help with AME Adobe Media Encoder crash on startup.

Hey all, this is my first time posting in these forums.
I have Adobe Design Premium and need to use the included Media Encoder for a project I'm working on. It opened well the first time, and I started converting a file - at which point it crashed. Since then, when I start it, it shows the startup / loading image, but once finished opening disappears and closes itself. I've tried reinstallig, no dice. I also read the plugin log files (My Documents > Adobe > Adobe Media Encoder > Log Files) - nothing out of the ordinary.
Very stuck and very frustrated - any suggestions would be really appreciated.
Thanks!

Hi Michael. Without more information about output settings, the project, the computer, etc, I can't speculate on the cause of the initial crash. I can, however, offer a suggestion as to why the app is now failing to launch: the initial crash may have corrupted the application settings. If you delete those settings, or otherwise hide them from AME, then the app will create fresh settings on the next launch.
Windows Vista & Win 7: C:\Users\<<yourUserName>>\AppData\Roaming\Adobe\Adobe Media Encoder\<<yourCreativeSuiteVersion>>*
Windows XP (from distant memory): C:\Documents and Settings\<<yourUserName>>\Local Settings\Application Data\Adobe\Adobe Media Encoder\<<yourCreativeSuiteVersion>>
Mac: <<partition>>\Library\Preferences\Adobe\Adobe Media Encoder\<<yourCreativeSuiteVersion>>
*On Windows 7 & Vista, if you can't see the App Data folder, you'll need to set Windows Explorer to show hidden files and folders: Tools>Folder Options>View tab.
If this does the trick to get AME running again, and if it again crashes on you, please provide as much information as you can about the project, export settings, system, etc.

GPU acceleration not activated on linux/intelivybridge

Firefox has alaways been slow on my intel ivybridge celeron ( ubuntu 14.04) and here is what I get from the about:support
How could I activate the GPU acceleration ? it works on Chrome.
Graphics
Adapter Description Intel Open Source Technology Center -- Mesa DRI Intel(R) Ivybridge Mobile
Device ID Mesa DRI Intel(R) Ivybridge Mobile
Driver Version 3.0 Mesa 10.1.3
GPU Accelerated Windows 0/1 Basic
Vendor ID Intel Open Source Technology Center
WebGL Renderer Intel Open Source Technology Center -- Mesa DRI Intel(R) Ivybridge Mobile
windowLayerManagerRemote false
AzureCanvasBackend cairo
AzureContentBackend cairo
AzureFallbackCanvasBackend none
AzureSkiaAccelerated 0

Todd:
(edit)
Just reread - sorry, CS6 vs CC.
What about AME CC?
http://blogs.adobe.com/kevinmonahan/2013/09/13/enabling-cuda-for-the-m ercury-playback-engine-in-the-macbook-pro-retina/
So, CUDA acceleration in AME and OpenCL is supported. Anyway to monitor this? I get FAILED when I try either (on a box with nVidia, or a box with AMD).
Found this: http://helpx.adobe.com/media-encoder/using/whats-new-media-encoder-7-1.html#gpu-accelerati on
GPU acceleration
Adobe Media Encoder now takes advantage of GPU for rendering purposes. Both CUDA and OpenCL are supported. The latest release of AME uses the GPU for the following renders:
Scaling (HD to SD; SD to HD)
Timecode filter
Pixel format conversions
Deinterlacing
Aspect ratio changes
All effects in the Effects tab
GPU accelerated effects in Premiere Pro
If you are rendering a Premiere Pro sequence, Adobe Media Encoder will use the GPU render preference you have set for the project. All GPU rendering capabilities of Premiere Pro are utilized.The limited set of GPU renderable tasks in Adobe Media Encoder is only for renders that originate in Adobe Media Encoder.
If you are rendering a sequence with native sequence support, the GPU setting in AME is used and the project setting is ignored. In this case, all GPU rendering capabilities of Premiere Pro are utilized directly in AME.
If your project uses 3rd party VSTs (Virtual Studio plugins), the GPU setting in the project is used. The sequence is encoded through headless Premiere Pro just as in earlier versions of Adobe Media Encoder. If Enable Native Premiere Pro Sequence Import option is unchecked, headless Premiere Pro will always be used and the GPU setting is used.

CUDA GPU Acceleration not working on Dell 4700 K2000M

Hello,
I have a new Dell 4700 laptop that was outfitted with the NVIDIA Quadro K2000M and my CS6 Premiere Pro does not allow me to choose GPU Acceleration as the option is grayed out for new files. I searched the web and tried several things suggested such as turning OPTIMUS off in the laptop BIOS, uploading the latest drivers for the NVIDIA card and still the Premeire Pro refuses to allow hardware acceleration.
Am I missing something? I really want this to work. Please help!!
Thanks,
Charles

Cuda Hack
CS6 - minimum 1GB video ram
PC - add:
(Your card name) example: GeForce GTX 680
to this list:
C:\Program Files\Adobe\Adobe Premiere Pro CS6\cuda_supported_cards.txt
(or simply delete the cuda_supported_cards.txt file)
mac:
How To Enable GPU Cuda in Adobe CS6 for Mac
http://www.vidmuze.com/how-to-enable-gpu-cuda-in-adobe-cs6-for-mac/

Adobe Media Encoder Dynamic Link Server NOT CONNECTING to Premiere Pro

I have Media Encoder CS5, as part of the Creative Suite 5. My programs say that I have no updates to install, so everything is up to date.
I am having an issue with the dynamic link server.
Here's what has happened thus far.
Recently when I have tried to encode a project sequence from Adobe Premiere Pro it DOES NOT work. This is the first time that has happened.
I repeated the process and again, it still happened, unable to connect to the Dynamic Link.
The Error messages that I was getting was "could not read from source. Check if it has been moved or been deleted"
Once, I received this, I went to check to see if all files were linked properly, and they were. Everything was rendered and all was good in the timeline and the project itself.
Yet, again, the error message appeared.
Then I tested a previous project that I knew had been exported and worked through Adobe to Media Encoder. And all the files were linked properly and yet again received the error message I wrote above.
Then I thought the Dynamic Link itself wasn't working properly, so I tested importing an Adobe After Effects Comp into a Premiere Timeline and it DID WORK.
Then I went and tested if a video file of an already exported project would be able to sync to Media Encoder. And this WORKED.
I then went to add the file directly from Media Encoder and when I went to add a sequence from a saved Premeire File, it would take about 5 minutes "Connecting to Dynamic Link Server", to then state, "Connecting to Dynamic Link Server Failed"
My question is, how do I fix the dynamic link between Media Encoder and Premiere? Because, additionally, importing and After Effects Sequence works with Media Encoder.

I've been searching/troubleshooting for days, none of the firewall, new shortcuts in folder, antivirus, you name it I tried it even wiped my system which seemed to work at first..
What did it for me in the end was I had Dxtory (a software recorder, for recording gameplay) running on startup, and somehow it interfered with only Premiere projects in Media Encoder, I could still import AE projects go figure.
Check all the programs you have running or use sometimes, if they have some sort of hook into other programs/deal with video/codecs this could be your problem too!
Thanks to everyone trying to solve this problem!
-JonOfAllGames

Adobe Media Encoder... Not encoding

So I got my video all said and done.
I export the media.
The encoder pops up, and I start the queue.
...and this is where my problem starts.
The job will sit there and not start what so ever... I left it for an hour and came back to 00:00's...
I notice PPROHEADLESS.exe is running and pretty much maxing out my cpu.
When I kill it, the conversion job starts, but only for a few seconds.
Then I kill pproheadless again, and another few seconds will convert.
If I kill the process to many times, it stops converting all together...
Help?!

Here is a link to another recent POST on this issue. I'm doing this to keep references to recent PProheadless posts together.
Good luck to all,
Hunt

Adobe Media Encoder CS5.5 crashing (not responding) when adding files

Hello,
I am running AME CS5.5 on a late 2010 MacBook Pro. I have been trying to create some broadcast quality .mpg files for my local cable provider's Video On Demand service but AME keeps crashing on me whenever I add a .mov file to the queue. I am using Final Cut Pro and Adobe After Effects CS5.5 to edit video and create animations. I have been able to encode a few files into the required .mpg specs, but now I can't even add a file into the queue without it freezing up. I then have to force quit the application to shut it down. I have recently repaired my disk permissions and used DiskWarior to clean up and create a new directory. Is this a known bug? Is Adobe working on a fix. I hope so because I have some projects due in mid-September and would hate to have to resort to using Apple's Compressor instead of AME since AME is faster. Any help would be much appreciated.
Here are my Mac specs:
Model Name: MacBook Pro
Model Identifier: MacBookPro6,1
Processor Name: Intel Core i5
Processor Speed: 2.53 GHz
Number Of Processors: 1
Total Number Of Cores: 2
L2 Cache (per core): 256 KB
L3 Cache: 3 MB
Memory: 8 GB
Processor Interconnect Speed: 4.8 GT/s
Boot ROM Version: MBP61.0057.B0C
SMC Version (system): 1.57f17
Operating System:
OS X Snow Leopard 10.6.8
Software:
Adobe Master Collection CS5.5
Apple FInal Cut Studio 3
Apple Final Cut Pro X
Apple Motion 5
Apple Compressor 4

Is this happening with all files? Just QuickTime files? Just QuickTime files using a certain codec?
I'm taking a shot in the dark, but any time that someeone mentions hangs and QuickTime, I suspect the problems described here:
http://kb2.adobe.com/cps/857/cpsid_85711.html

Adobe Media Encoder Update for Mac not working?

Hey!
My Premiere says that there is an update available for the AME.
When i open the PatchInstaller it says: "This Patch is not suitable for you."
In a normal case AME is installed together with Adobe Premiere, isn't it?

>> In a normal case AME is installed together with Adobe Premiere, isn't it?
The above comment has been true for stand alone installation of major releases. But when it comes to patch release, each product is on its own. Generally speaking, PPro and AME products release patches on the same day. There have been a few cases where PPro had a patch (like 7.2.1) and there was no AME corresponding patch.
>> My Premiere says that there is an update available for the AME.
>> When i open the PatchInstaller it says: "This Patch is not suitable for you."
What versions of PPro and AME do you currently have on your system?
What version does PatchInstaller wants to install on your system?
The latest released versions of PPro and AME patches are 7.2.2.

Adobe Media Encoder CC - I Can Not Download.

http://www.adobe.com/support/downloads/product.jsp?platform=Windows&product=160
JUST DOİNG UPDATE...
CAN NOT İNSTALL....
PLEASE HELP.....

Without system information and otehr details nobody can say anything. Chances are you will have to run the cleaner tool and start from scratch.
http://www.adobe.com/support/contact/cscleanertool.html
Mylenium

Is there a way to assign Color Spaces in AME (Adobe Media Encoder) CC?

I am trying to output h.264 video for a web project and cannot seem to get sRGB color match when rendering out from AE.
I see it in AE's native renderer, but not in AME.
Thanks.

AME (and Premiere Pro) does not support color management in the way that After Effects does. Via Dynamic Link, which is how AME reads After Effects comps, the color-space-adjusted pixels are not corrected for screen display.
To get the results you want, add an adjustment layer to the top of the layer stack in the comp and apply the Color Profile Converter effect. Set the Output Profile to Rec.709 (sRGB is practically identical and will also work, but Dynamic Link uses Rec.709 internally so is a better match). This forces After Effects to transform the adjusted pixels into a non-linearized color space that looks correct.
Note that while the CPC effect is active and View > Display Color Management is enabled (it is enabled by default), this extra layer of color transforms will make the comp appear incorrect in After Effects, at the same time the comp will now look correct in AME or Premiere Pro. Disable Display Color Management to make the appearance of the comp in After Effects match what you see in AME or Premiere Pro. While working on the comp, however, you probably want to work with Display Color Management enabled and the adjustment layer disabled.
Under the hood, when color management is enabled in After Effects, the pixels it writes into the cache include the appropriate color transforms for the settings you have chosen. When the comp is displayed in the Composition panel in After Effects, an additional transform is added to the screen buffer pixels (not the pixels in the cache) to make it look correct on your computer screen, or not if you have disabled Display Color Management. When the pixels are read through Dynamic Link, no display color management happens, nor does AME or Premiere Pro apply any, so you get the same appearance as having Display Color Management disabled in After Effects.
Make sense?

AME Adobe Media Encoder Cuda GPU Acceleration not activated, How do I activate it

Similar Messages

Maybe you are looking for