Adobe Media Encoder Question

Hey everyone! So I just switched from using AE CS5.5 to AE CC, which now has me use the Media Encoder to render all my files, which frankly is AWESOME. However, I sometimes like to render out a piece of a long video I'm editing so I can get a glimpse at how it is looking so far without having to wait for it to completely finish. With CS5.5 I was able to just *stop* rendering, and the video would publish to my desktop and end wherever I had stopped it. With Media Encoder when I hit stop, the file is nowhere to be found as if the program just throws it away after canceling. Is there a way to make it still render what it already got through so I at least have a partial file to view??

On further inspection, Even still renders are interlaced like mad...
What's wrong?!
EDIT:
I fixed it!!! Apparently when speeding up or slowing down clips, it merges the frames together giving off that horrible look! So I turned off "frame blend" And it looks super awesome.

Similar Messages

  • Adobe media encoder cc has encountered an error

    can anyone help me about some problems with adobe media encoder cc ??
    adobe media encoder cc has encountered an error
    command.cpp-3302
    THIS IS NEW CRASH WHEN I TRY TO EXPORT MPEG2 VIDEO

    FAQ: What information should I provide when asking a question on this forum?

  • Adobe Media Encoder Unknown Error

    I'm trying to export an Adobe Premier Pro file on Adobe Media Encoder. Each time I try, it gets about halfway through, then this error message comes up:
    - Source File: /Users/A25/Library/Caches/TemporaryItems/Incubus Trailer Rough Cut.prproj
    - Output File: /Users/A25/Desktop/Odyne Theatrical Trailer.mp4
    - Preset Used: HDTV 1080p 25 High Quality
    - Video: PAL, 1920x1080, 25 [fps], Progressive
    - Audio: AAC, 160 [kbps], 48 kHz, Stereo
    - Bitrate: VBR, 1 Pass, Target 32.00, Max 40.00 [Mbps]
    - Encoding Time: 00:07:07
    Mon Apr 15 12:48:21 2013 : Encoding Failed
    Error compiling movie.
    Unknown error.
    I've tried different video presets (1440x1080, 1920x1080 etc), but this message has appeard every time. Any ideas how to export it?
    Thanks

    Please read here:
    "Error compiling movie" when rendering or exporting with Premiere Pro CS3, CS4, CS5, CS5.5, CS6
    and here:
    Adobe Forums: FAQ: What information should I provide when asking a question on this forum?
    Jeff

  • New PC, downloaded CC 2014. Flash not showing up as option to rip in Adobe Media Encoder or in After Effects. Help?

    Why is .flv not an option in Adobe Media Encoder or Adobe After Effects?
    Also, when Adobe Captivate converts the video it looses the Alpha channel.
    Help

    Thanks for taking the time to answer this question. Knowing this isn't possible at least narrows my options down. It would be helpful to provide some kind of list of what comp settings carry over into AME from After Effects. Is it essentially everything that is enabled in the Timeline? (I know that motion blur settings do.)
    I'll put this in a feature request, but yes, we need the other half of After Effects Render Queue in AME in order for AME to be a good replacement for rendering from AE. I'll give you my thoughts on why Render Settings are essential before you would actually want to render with AME instead of doing so because you have to (either because you want to render in the background, or need a codec that has been removed from AE.)
    1. Speed: Simply applying a Render Settings preset is much faster than manually setting motion blur, frame blending, work area, etc.
    2. Reliability: Not being able to apply a Render Settings preset at the time of render is a recipe for missing a crucial setting buried in a comp, then having to redo a render and wasting time.
    3. Features: As noted above, there is no way to approximate Render Queue's ability to change resolutions at render, which results in a lot of wasted time when that feature is needed.
    Render Settings I think are crucial to making AME rendering worthwhile for AE users:
    1. Rendering resolution
    2. Work Area/Entire Composition toggle
    3. Field Rendering (wait, does this mean AME can't currently render to fields?)
    4. And PRESET ability these settings, so I'm not doing them manually every time.
    I realize that your team clearly doesn't spend the same amount of time I do making low res H264 previews and sending final files out in H264 format, so you don't appreciate the impact of the changes you made. Moving to AME for that stuff is a real inconvenience, but implementing the settings above could help soften the blow.
    Thanks,
    Jerry

  • Exporting in Adobe Media Encoder fails in CS4 after CS3 is removed.

    There's an issue with Adobe Media Encoder in CS4 where encoding will fail after CS3 is uninstalled.
    If you never had CS3 installed on your machine - no problem.
    If you never had CS3 and CS4 installed at the same time - no problem.
    If you had CS3 and CS4 installed concurrently, then uninstalled CS3 - Houston, you have a problem.
    You will need to uninstall CS4 and then reinstall CS4.
    The error message is:
    Encoding Failed
    Could not read from the source. Please check if it has moved or been deleted.
    One more thing I forgot to mention, this is a Win-only issue.

    >Does anyone understand this?
    Simple:
    1. Open a Windows Explorer window and navigate to the folder that contains "dynamiclinkmanager.exe"
    2. Open a
    second Windows Explorer window and navigate to the folder that contains "Premiere.exe"
    3. Arrange the windows side by side.
    4. Right-click on "Premiere.exe" and drag to the first explorer window, targeting between the files so as to avoid any specific file.
    5. Release the right-hand mouse button.
    6. Select "create shortcut here" from the pop-up menu.
    Cheers
    Eddie
    PremiereProPedia   (
    RSS feed)
    - Over 300 frequently answered questions
    - Over 250 free tutorials
    - Maintained by editors like
    you
    Forum FAQ

  • Adobe Premiere Pro Won't Export To Adobe Media Encoder?

    I Work for a news company and we use Adobe for aeverything we need. But when we take a little break from doing videos while we where moving to a new office space, and suddenly we start again and It decided not to export to the Adobe Media Encoder. Usually it was a 5 second process and now it does not work at all. We have adobe premiere pro cs5.5 from the CC (We are currently not planning on upgrading to CS6 anytime soon.) We have no plugins for it and it works for everything else. When I use the Exporter it Exports in in too low of a quality for use. Help? If you need I work at better-community-news.com, Sooolutions (Seprate buisness same owner.) Glad Studios, (also same owner...all the places I work are the same guy), X.L.N.T Marketing and thats about it. Its a team of 3 guys and we would appricate any help! Thanks!
    ~ Better Community News

    Jan 21, 2014 12:51 PM -to- Jan 21, 2014 2:24 PM
    thanks nobody because nobody helped me solve this delima
    You do know that this is a user to user forum, not an official Adobe support site?
    Which means that there is NOT a full time group of people just waiting to answer questions
    Don't you think that complaining about nobody answering in less than 2 hours is a little unreasonable?

  • Just how hard it is to export using Adobe Media Encoder ?

    For those who have CS4 already, just how difficult is it to export
    to Adobe Media Encoder ?
    Right now it's very simple, you make up your work area for example, and export.
    So with CS4, I must do what exactly to do this ?
    Do I have to save the project with the work area selected, exit, now open Adobe Media Encoder and now select "open project" and now load this up and then export ?
    Please tell me it ain't so.
    I'd like to hear the steps to do this. I have to be honest, what once was an exciting time, has turned into a disappointing time now, reading all the things Adobe had changed ( for no good reason ). I just don't understand sometimes why they do things. I think they should get more input from poeple that use their products on a daily basis, so they know what they should touch, and what not to touch.
    I'm actually not looking forward to upgrading now, even though I will, because of a few things that look good in the new version.
    Dave.

    It ain't so.
    The workflow remains pretty much the same until you finally click the OK button. At that point the AME will open up and you can choose to start the queue immediately or switch back to PPro and do several more exports before starting the queue.
    Read all about exporting
    from the horse's mouth. ;)
    You will also find several
    CS4 tutorials that will show you how it's done.
    Cheers
    Eddie
    PremiereProPedia   (
    RSS feed)
    - Over 300 frequently answered questions
    - Over 250 free tutorials
    - Maintained by editors like
    you
    Forum FAQ

  • ProRes 422 MOV files offline in Adobe Media Encoder 2014 (but online in Premiere)

    The question is NOT about exporting PreRes files from a Windows PC, which is what I keep finding in my searches.
    My client gave me ProRes 422 MOV files. I imported them into Premiere Pro CC 2014. I could see and edit them fine. But when I export them via Adobe Media Encoder, they appear to be offline. BTW, other media sources exported fine, such as the PNGs and JPGs I cut to. (I don't think it matters, but I'm attempting to make h.462 mp4s, which I do all the time, and have done with ProRes sources before using CC 2014.)
    I tried exporting a short video clip (using same ProRes 422 source) from Premiere and it worked fine. Why not Adobe Media Encoder? I need to encode batches of videos with ProRes sources overnight, so exporting from Premiere is not a good option.
    I'm on a Win 7 PC and I have QT Pro and iTunes (which I think also installs codecs).

    Everything seems to be working fine now, though I don’t know why. I did update my iTunes (which I’d rather not even have installed on my PC because I never use it, but removing it seems to mess things up). I’ll also make sure to keep my QT updated. I thought it was because I upgraded to the paid version a couple months ago hoping to fix a similar problem, but again, it seemed to get fixed when I updated iTunes.
    Thanks for getting back to me!
    Bill

  • Adobe Media Encoder CS6 Random Crashing Mid-Render

    Hello -
    I've been dealing with this issue for enough months and across enough computers to finally seek out some advise here, hope it works out...
    Basically I've got a 2 hour long film that I've been trying to export using Adobe Media Encoder CS6. It's never made it all the way through. I can usually skim through the generated quicktime file up to the point where the crash occurred. I've tried using that as a reference to check out my sequence in Premiere but there is never anything suspicious going on there. Most frustratingly the crash occurs randomly. Sometimes it will go through 10 minutes of the film; sometimes an hour. Regardless I get a crash with a report that has no specific information.
    Footage:
    r3d - Various resolutions, all being cut in a 2048x1152 sequence.
    Quicktime mov - ProRes4444 for the most part.
    Machine(s):
    I had been attempting to render this for the past few months with a Macbook Pro running OSX 10.8.4 w/ 16GB RAM, 2.7 GHz Intel i7, NVIDIA GeForce GT 650M 1024MB - never made it through a render longer than 50 minutes of the 2 hours.
    We recently got one of the new 2013 Mac Pro systems running OSX 10.9 w/ 16GB RAM, 3.5 GHz 6-Core Intel Xeon E5, AMD FirePro D500 3072 MB
    The hope was that this new powerful machine would overcome the issues we were running into with these renders. Since I'm posting this now you can probably figure out that it didn't really work out that way...
    Software:
    AME- 6.0.2.81
    Premiere - 6.0
    I know there are updates to be used here, but whenever I update Premiere from just 6.0, the project itself becomes a buggy mess, crashing constantly. I also run Creative Cloud and have tried to just jump over to Premiere CC hoping all my problems would vanish, but instead, I again get a buggy project that constantly crashes. The only version of Premiere that seems to work with this project is 6.0, so general updates have not been useful (and instead damaging, I've wasted several days trying everything I possibly can to make the project work in the updates).
    Any help appreciated. Thanks.

    Thanks for the reply MMeguro.
    Last night I was able to get my first full render through by doing a combination of things (so I'm not sure what did the trick in the end).
    To answer some questions first, never attempted to do the FULL render directly out of Premiere, always switched over to AME for that, so that potentially could work too. Smaller renders have worked directly out of Premiere Pro, but they've also worked out of AME.
    The initial render attempts that had been failing for the last few months were on the MBP which did not support GPU accleration due to an incompatible graphics card. I assumed the issue must be tied to something else because of this and was using it on the renders with the new 2013 Mac Pro. Using the workflow of Pr6.0, AME 6.0 and GPU rendering turned ON, I was failing to render to both Quicktime h264 and ProRes 422.
    What worked for last night's render:
    1. Convert Pr6.0 project to PrCC project (when I've done actual editing in CC after converting this project it tends to crash, but I figured just generating the project itself without doing any editing in it might satisfy what I was attempting to do).
    2. Open AME CC and import PrCC Sequence. Used custom ProRes 422 setting.
    3. Turned OFF GPU acceleration.
    So as long as I the PrCC project I create stays stable long enough to save it (without crashing, which has been a problem with that Pr6.0 to PrCC conversion) then it seems like this will work. Kind of an annoying couple extra steps but I'm just out of my mind glad that I can actually render this thing finally. We're still in the rough stages so being able to turn around a review version within a day is very important.
    Wish I could do more tests to figure out exactly which combination actually made this work for the benefit of others, but can't afford to do multiple 10 hour+ renders with random crash times.
    Anyway, thanks again for the reply MMeguro much appreciated.

  • Adobe Media Encoder CC - You Need to Add Unsupported CUDA Cards to supported_cuda_cards.txt

    Hi Folks
    I'm running on a Mac Pro with an NVidia GTX 770 with 4GB. Premiere Pro CC utilizes the GPU for playback and export but will give you a warning when you first enable CUDA in Mercury Playback Engine. However...
    I was noticing that when I queued the export to Adobe Media Encoder CC, it was taking forever to encode simple queued sequences.
    After doing a bit of research on the internet and even in these forums I realized that while Premiere Pro was being ok with supporting a non-supported card, Media Encoder was not. I added the GTX 770 to the supported_cuda_cards.txt file locate here: /Applications/Adobe Premiere Pro CC/Adobe Premiere Pro CC.app/Contents/ (you will need to be slightly geeky to find and modify this file - more info than I care to provide in this post but you can look up how to locate files in Mac OS).
    Voila! AME now encodes super speedly, like 4 times as fast as before!!!
    Thought I'd just provide this little tip for people experiencing this problem.
    Adobe... can you do something about this? I know it's a corner case but really - maybe something in AME preferences or something... Like "Use CUDA capable card even if not on supported CUDA list" checkbox or something.
    Now I can get back to work.
    -Keith

    I just made this change in the AME ".txt" file for my GeForce GTX 670 (i7, WIn 7 Pro, 32 GB, and I know it's not "certified" for CUDA), and now have it in both the PPro and AME ".txt" files. While I'm waiting for AME to finish, this thread raises questions in my mind.
    It's been my understanding that AME was engineered to run in the background, allowing other work to be done in PPro without the 2 "getting in each other's way".
    I'm happy with the rendering speed in PPro, and I see that hardware rendering is working there.
    If AME now makes use of the GPU while I'm doing other work in PPro, (like maybe "rendering the selection", or an entire sequence in PPro), does that affect the performance of either the file that AME is currently processing, or does it affect what I can do/performance I'll get while concurrently working in PPro?
    Are CUDA/GPU resources  "shared" between PPro and AME? Or, are the apps likely to "trip over each other"?
    If AME does, in fact, make use of the GPU, is there something other than the ".txt file hack" that I must do to enable the renderer in AME to use MPE hardware? As I type this I have AME working on a PPro sequence but I see that the "Renderer" is showing "Mercury Playback Engine Software Only".
    I feel like I'm missing some important tidbir of information, but I don't know what that is.
    What am I missing?

  • Adobe Media Encoder CS5 hangs when adding files of varying HD resolutions.

    I've seen questions similar to this related to CS4 but never explained very well, and my CS4 for mac worked fine.  I am unsure if this is a new problem or a windows specific problem but here is the situation, if you need more information I will gladly provide it.
    For the past week or so I have been encoding 1920x1080i mov files (h.264/aac) to 1280x720p (vp6/mp3) flvs.  When I stick to that single HD format in the AMC processing que everything works great. However, when I add older HD content into the AMC que, content with non-standard presets, the program hangs.  I tried to import about 15 files last night and the program just sat there all night in a '...NOT RESPONDING' state.  The video's have different audio and video settings and it's little difficult to pinpoint exactly what they were.  Some are 1440x1080, some are 1280x900, some have PCM audio some of mp3. 
    Now I temporarily resolved this issue by simply using cs4 master on my mac pro which worked great.  However I have noticed a huge speed increase in CS5 64bit AMC.  It takes 2-3 hours to encode 1 flash video on my mac pro (dual quad core xeon 2.9Ghz/32GB ram) with CS4.  It takes ~20 minutes on my windows 7 station (single core 2 quad 3Ghz/8GB ram) with CS5.
    How to replicate:
    If I drop a single file into the AMC CS5 que, regardless of the resolution, frame rate, or sound codec; it will import.  If I then add another file with a different resolution AMC will hang and become non-responsive.  It never crashed but I can't wait 12+ hours to see if it accepted a job or not.  As I said before this problem was not observed on CS4 for mac - it worked flawlessly, albeit a little slow. 
    Software used:
    Adobe Media Encoder CS5 windows 64bit
    Adobe Media Encoder CS4 mac 32bit
    System specs:
    Windows 7 home:
    Core 2 quad 3Ghz
    8GB ram
    80GB SSD x25-m
    nVidia Quadro 580
    OSX 10.6.3:
    Dual Xeon 2.99Ghz
    32GB ram
    4 7200 disks in 4TB raid 0
    Radeon HD 2600
    Matrox MAX h.264 compressor card
    Any advice on this situation would be greatly appreciated.  Thank you for your time
    -Michael Emanuel

    Hi Michael,
    Sorry to hear you're having problems with Adobe Media Encoder.  I'd like to get some more information about the problem so I can better understand your workflow, and potentially try to recreate the problem.  For what it's worth, I often import files of different resolutions without any problem, so I want to find out what's different about how you're using AME.
    Apologies for the long list of questions; the small details can be important.
    -- After you import the first file, what else do you do in AME?  Change the preset?  Change the settings?  Change the output destination?
    -- What are the properties of the files that are causing the problem?  You said it happens on "non-standard" files, but can you describe the specifications for one or more files that cause the problem?  Please include file type, length, frame rate, frame dimensions, field order (if applicable), alpha mode (if applicable), and audio type and rate.  If you know more the bitrate, both video and audio, that would be nice, too.
    -- If any of the files are small enough, could you post a couple online that I could try on my machine?
    -- How were these files generated?  What application created them?
    -- Where are the files stored? A local drive, a network drive, a removeable drive (USB or Firewire), etc.?
    -- Which Adobe application or suite do you have installed?  AME a limited set of options if you're using Flash or Web Premium compared to Master Collection, Production Premium, Premiere Pro, or After Effects.
    -=TimK
    -=Adobe Media Encoder QE

  • Adobe Media Encoder CC: Can I export to Apple ProRes 422 on a Mac?

    Hi folks,
    I tried to find some information about it, but couldn't really find a definite answer on this.
    Unfortunately, my Mac is getting fixed  as we speak, so  I can't try this out either...
    I want to convert mxf files (XDCAM HD 422 1080i 50, 50 Mbit/s with multiple Audio channels) to Apple ProRes 422 using Adobe Media Encoder CC.
    Simple question: Is that possible or do I need to look for a different workflow/converter?
    Thanks for your help!
    Jens
    PS: OS is Mavericks...

    Hi DataWrangler,
    Thanks for posting on Adobe Forums.
    Please download proress presets for Adobe Media Encoder from here : http://www.adobe.com/support/downloads/detail.jsp?ftpID=5411
    Please update if this helps.
    Regards,
    Sandeep

  • 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

  • FLVs created with ADOBE MEDIA ENCODER CS6 do not display thumbnails in ADOBE BRIDGE CS6

    Could you please attempt to shed some light on why FLVs created with ADOBE MEDIA ENCODER CS6 do not display thumbnails in ADOBE BRIDGE CS6, yet apple finder is able to display thumbnails for these same FLVs without issue?
    I'm running CS6 Production Premium with ALL updates installed on 10.6.8
    I appreciate any input and help provided the input is provided by someone who either
    A) knows the answer because they actually work for adobe
    B) actually tried this themselves before attempting to provide a solution
    If the conclusion is that it is a codec issue or a header issue with the FLVs You'd have to present a very strong case to back that claim up as it makes no sense whatsoever that CS6 is unable to generate thumbnails for media encoded using CS6, yet Apple finder can without issue. NOT to mention the FLVs in question are CREATED on the same machine with the same codecs installed that is trying to generate previews in Bridge.
    Apologies if my frustration is showing, I've gotten and seen several... incompetent replies on this forum regarding this issue and it has never been actually addressed properly as far as I can tell by Adobe support.

    We are all just incompetent users here.  As pointed out before this is just a user to user forum, Adobe rarely checks in.
    I was hoping by now you would have gotten to the bottom of this problem and were offering a solution.

  • Queuing from Premiere Pro to Adobe Media Encoder no longer working? CS6

    Hi there,
    Just very recently adobe media encoder has stopped accepting que's from premiere. I choose export in premiere, setup the export details and hit que, adobe media encoder launches, but then it flashes once (like disappears reappears, very quickly) and then it just simply does nothing. No item appears in the que. I have tried opening the premiere sequence directly from adobe media encoder but it does nothing either. If I drag the premiere project directly onto a preset in adobe media encoder, it crashes every time. (though not sure if it would of done this previous to my problem arising)
    Anyway, very frustrating as I usually work on a different project whilst media encoder is rendering something out. Now i'm stuck with huge down times as I wait till the render is finished.
    Recently updated to Mac OSX 10.8.3 - I think this is when the problem began.
    Just updated the CUDA driver to 5.0.45 but this has not changed anything.
    Working on a Mac Pro 5,1, 2x2.4Ghz 24GB RAM, EVGA GTX 660 FTW,

    Some suggestions and answer at least the 16 questions at the end of the Wiki article.

Maybe you are looking for