Premiere CC lies to me.

When opening various old projects, it tells me this:
"This project was last used with Mercury Playback Engine GPU Accelleration (CUDA) which is either not available or not certified on this system.  Mercury Playback Engine Software Only will be used."
That's not true.  I've had a qualified CUDA card installed for years.  I dismiss the message and proceed to work as usual.  Sometimes, I have to throw the CUDA switch in General Preferences, but Pr works fine with my qualified CUDA card once I do so.
It's more of an annoyance than anything.  Might be related to the version of GPU or CUDA driver I have installed.  But, could also be a bug in Pr.
Anybody else?
MacPro 10.8.5 nVideo Quadro 4000 - not running the latest nVidia drivers, because there have been many reported job-stopping problems.
I'm running 313.01.03f02 & CUDA 5.5.28

I'm waiting for further answers on this as well.
Windows 8.1 (same sometimes happened on this computer on Windows 7)
Premiere Pro CC
NVIDIA GTX 765M (driver version 9.18.13.3221)
Same message "Premiere Pro could not find any capable video play modules. Please update your video display drivers and start again."
Drivers are up to date (even when an update is available it doesn't help)
PP CC worked last night but not today. Only update overnight was "Security Update for Internet Explorer Flash Player for Windows 8.1 for x64-based Systems (KB2934802)".
Sometimes recent updates relate to DivX
There's no option to uninstall these updates so I use recovery to go to a point I created called "Last Time Premiere worked"

Similar Messages

  • How can I properly export video w/ bars to Rec709 (16-235 in 8-bit) from Premiere's RGB (0-255)?

    I have hit some real frustrations in working with Premiere to meet broadcast Rec709 standards for DVD & Blu-Ray. Avid Symphony works in a Rec709 space and clearly operates with its video signal from 16-235 (which matches IRE 7.5 to 100), but Premiere doesn't seem to have this understanding in its programming and engineering. Here are my issues:
    1) I can't manually enter in the digital values in the RGB Curve tool's points. Why would Premiere's engineers lock this basic feature out? It's in Photoshop.
    2) I can't properly export Premiere's color bars. In order to export to Rec709 standards, to get around issue #1, I hack into the RGB Curves preset XML file to lift the Master Curve's point 1 from 0 to 16 and set the final white point from 255 to 235. If I use Premiere's bars, on the waveform, I can see the sub-black values, but when I lift the blacks with the curves preset, it clips all sub-black values upon export. WHY?! To get around this problem, I import bars generated by a camera (for example, by a Sony EX-350, i.e. XDCAM footage). All of this wouldn't be an issue if there were an export function that specifies exporting to rec709's 16-235 values instead of 0-255, as Avid does.
    3) Particularly, the Waveform scope lies to me. The 7.5 IRE setup button does NOTHING for me, it's just a preview option that causes more confusion than clarity. Does Premiere map 0 out of 0-255 as 0 IRE or 7.5 IRE? I think it does the former and just uses that setup button to make you think that it's at 7.5. so if you do set it to 7.5, how then do you export it to match that option? Also, why can't the waveform scope have multiple options for the units - not just IRE, but also digital values (8-bit, 10-bit, linearized, etc.)?!
    4) Speaking of importing the bars and footage. To continue the example of the Sony EX-350 - it imports the bars automatically by putting the black values at 0 IRE, not 7.5 IRE.
    If Adobe wants industry professionals to take Premiere seriously, it needs to open up these options and clearly present what happens to tonal values in the image. It's very frustrating to figure out all of these problems and create cockamamy work-arounds.
    http://www.avsforum.com/avs-vb/showthread.php?t=1090642
    http://www.glennchan.info/articles/technical/setup/75IREsetup.html

    Steve,
    Thanks for your reply! However, I hope you don't take my response the wrong way, but, with no meaning of disrespect to you personally, the notion that curves are the wrong tool for numeric adjustments extremely infuriates me and displays a real lack of understanding of why a colorist or cinematographer such as myself would want to use curves in the first place.
    First, any LUT generation program or coloring program, such as Apple Color, gives complete access to numerical control to give precise, repeatable changes that you cannot get with the drag of a mouse. Photoshop, Avid Symphony, etc. all have curves tools with the ability to manually enter points.
    Second, on a user level, there should be no wrong tool for numeric adjustments, especially curves - they are the most precise means to obtain a specific contrast response. Levels or RGB corrector will only give gamma, pedestal, and gain operations, but curves gives every possible shape of a contrast response in between. If I wanted to create a very specific S-curve, I must use the curves tool to do so.
    Third, the question at hand is not Premiere Pro's ability to process natively in Rec709 with signal from 16-235 - Premiere's native ability to process all types of video input is the sole reason why I've switched to it as a platform. 'Sub-black values are not necessarily clamped'?! How then can I export a TIFF, for example, of Premiere's bars, with the sub-black values left intact? How do I even access these sub-black values, when all footage clips below 0 IRE? The primary question is, how does Premiere handle and export these IRE values with respect to digital values, whether they are 8-bit, 10-bit, 12-bit, etc.?
    Adobe's video workflow lacks a concise, cohesive FAQ or explanation of its numerical signal chain. At least, I have missed it and can't find it anywhere. If I want to properly color grade footage with a proper final output in mind, I need to know my end goals to take the proper intermediary steps.
    SteveHoeg wrote:
    Hey Tim - Premiere Pro can process natively in Rec709 with signal from 16-235 you do not need special adjustments. Curves are the wrong tool for numeric adjustments, try Levels or RGB Corrector. Sub black values are not necessarily clamped on export.  --sh

  • After Effects CS5.5 will not open a Dynamically Linked Premiere Pro sequence in the comp. window

    Hi all,
    I'm trying to export a Premiere Pro sequence which is in 2K and the footage has been shot as RED 5K. Adobe Media Encoder will simply not work as I am having the quite widely discussed issue where it will just 'hang' at certain points and not complete the export.
    The most popular solution to this problem is to export via the Render Queue in After Effects instead. However, therein lies the problem.
    I go onto After Effects. Choose File -> Dynamic Link -> Import Premiere Pro Sequence.
    The box pops up, I choose the Premiere Pro Project File then select the sequence I want to export. It then appears in the After Effects project panel window like so:
    However - when I try and drag this to a new composition window, one of two things have happened. Either A) nothing happens (literally, NOTHING changes) or B) as the following example shows, it seems to add it to a new composition, but the video is entirely black. I have tried rendering it and it just produces a black video.
    The other thing people seem to suggest is to just import the entire Premiere Pro sequence into After Effects. I've tried this, but any titles I have added in PP force the video to fade out then back in, in the place where the title should be?? So I can't export the video this way either.
    My system is as follows:
    Thanks massively in advance for any help that is provided!

    This is months old but I'm now having the same problem with AE and Premiere CS6 after updating last night: Dynamic linked sequence shows up in the project window in AE and even plays video if previewed, but will not drag or alt-drag into any comps, including a new comp (makes a new comp with matching settings, but empty).
    Furthermore, I do actually have an earlier version of the same sequence placed in one of my AE comps, which I think was done using the same steps just prior to updating the apps last night. Did this break?
    I'm a little concerned since the biggest reason I'm trying to use premiere is to eliminate the exports when adding graphics in AE.

  • Premiere Pro CS3  (Version 3.0) will not start following upgrade to Windows 8-- rest of CS3 is fine

    Recently upgraded from Windows 7 Ultimate to Windows 8 Pro;
    next time I tried to open Premiere Pro 3.0 (Adobe Master Collection CS3), splash screen scrolled normally through files being loaded until "SolidComposite.AEX", where it white-screened & crashed. 
    Tried removing that file, it crashed on the next ".AEX" file; removed all ".AEX" files, it began crashing on ".dll" files;
    kept removing THEM, just for the heck of it, until the software loader couldn't even start.
    I popped in the CS3 disc to repair the installation-- on the entire suite, for good measure;
    re-booted & started Premiere-- crashed at the exact same point.
    Uninstalled and then re-installed Premiere-- the entire suite in fact, since there are so many common processes;
    couple of hours later, re-booted & started Premiere-- same exact thing at the same exact point.
    I found this same problem in at least a half-dozen threads, going back to '07--
    and several of them even mentioned the same exact file as the trigger for the crash!
    Unfortunately, not one of those threads has ever ended with an accurate diagnosis of the problem,
    nor a solution more insightful than reinstalling both the CS & the OS.
    I don't want to abandon Windows 8...
    but on the other hand, I just can't afford to pony up another grand to upgrade the CS Suite again, either...
    Besides: CS3 is everything I need, and it has worked wo well for so long--
    even now, Premiere Pro is the only software in the suite with a problem!!
    (I used Photoshop to create the above screencap)
    So I'm hoping against hope that one of you techno-gurus may have come across this ITRW--
    and actually SOLVED IT!!

    Thanks for your prompt reply, John-- and for NOT simply advising me to spend my kid's tuition on more of your company's products...
    Actually, I had tried the "Run as Administrator" option already, having found it in one of those other threads;
    there was no change in the sequence described above.
    I decided to try another possible solution which I read about in one of those other threads: opening Premiere from a different account. 
    Incredibly, it WORKED-- sort of...
    I got a couple of popups advising me that missing codecs had to be installed-- and upon completion, Premiere opened!
    Here's an interesting note: the last file to load was still "SolidComposite.AEX"-- and the "White Screen" I kept seeing was Premiere opening normally.  The next thing that displayed was the normal  dialog box "Open/New Project"-- I entered a new project name, and Premiere started normally. I even added a few video files as a test... all opened normally.
    I returned to the Admin account to see if the fix was in here, too;
    but clearly the war wasn't over, over here...
    It now appears that some personal setting in the Admin account is causing Premiere to close itself;
    I've been reading about the layered security measures embedded into Windows 8-- I'm suspecting the conflict lies there...
    I ran the Windows Troubleshooter & got this:
    both MS & Adobe confirm that CS3 is fully compatible--here's my sytem info:
    Since I seem to have established a fall-back position that lets me use Premiere, my crisis becomes a mere conundrum;
    but I know this is gonna gnaw at me anyway, & I'm hoping that this new information might suggest further troubleshooting options to someone who understands the Adobe software and/or the Windows software better than I do!
    Speaking as someone who has found many solutions on forums like this over the years, I assure you:
    for every person whose post you reply to, there are many more whom you will never know you have helped!!!

  • Is there any "simple" documentation on the steps to download and install Photoshop and Premiere Elements V13?  The downloads seems to work but there's nothing clear on what do you do next.

    I've been messing with computers since 1958 and I've never seen such a mess as trying to download and install the recently purchased copies of Photoshop and Premiere Elements Version 13.  Slow downloads?  Sure, but I can live with that.  But once downloaded, what next?  Look for a xxx.exe file somewhere in the pile?  Read the "ReadMe" file?  All I seem to get is unzipping some files with nothing leading me into the proper steps.  I can't even seem to get off the ground.  Everything I touch unzips and just lies there.  I hate to think I've gone dumb after all of these years, but "user friendly" this is not.  My "Your order confirmation" sheet gives me "Follow the instructions below to start using it today" and the first three steps work as you'd expect.  Step 4 states "After you have completed the download process, your serial number will be displayed in the download center."  Step 5 is "You can log back into 'Adobe Account Management' in the future to re-download your product or retrieve your serial number. ...."  I have no problem with my serial number but there seems to be a lot missing between Steps 4 and 5.  It would be nice to have this information as pretty standard "stuff.  Computers are supposed to do super stuff without a lot of time-consuming problems with a simple process like installing the software.  I'm feeling a bit hostile about this but it is a time-consuming, frustrating process.

    Justin created a guide to using Favorites. It will help you a lot with what you seek. He has a link to it in this thread.
    http://forums.verizon.com/t5/FiOS-TV-Technical-Assistance/Exploiting-FiOS-TV-Favorites/m-p/9935

  • Adobe Media Encoder for Premiere Pro CS4 stops working on the same frame every time...

    I currently have Adobe Premiere Pro CS4 and have never had these issues exporting before. My timeline is less than 3 minutes long, but it does deal with multiple big files. It rendered perfectly and it plays perfectly in the timeline. When I try to export it using Media Encoder, however, it freezes at the same frame every time (which is actually only a few seconds in!) and then crashes, so that I have to force quit. I have tried exporting it as many different codecs and the problem persists... same frame. I tried creating a new project entirely and whipping together a few titles and exporting that to see if it just won't export anything at all. The new project exported just fine, however, which I suppose is good news. But yeah, my work on that other project is very important to me and I reallllly want to export it. Please help!

    Hi Jim! Thank you for your reply. I think you are right -- and that it lies in the audio somehow!
    It turns out that if I choose to only export the video, and uncheck audio, it will export very well and smoothly. That's great news for me!
    However, now I am trying to work out how to get the audio exported without issues. I actually had the idea of just playing the audio in the timeline and recording it via Stereo Mix, but my Windows 7 driver has Stereo Mix disabled, so it's back to square one. Any ideas of what I can do about the corrupted audio not exporting, which works fine when played in the timeline?

  • Premiere Pro CC Crashes on Start-up

    Premiere Pro CC Crashes on Start-up
    (I have checked out the forms on here before posting.) CC was working great before my SSD died.
    My Previous SSD died and I had it replaced with a new Samsung SSD 840 Series
    and Premiere Pro CC started crashing on launch. I also have CS5.5 installed and that works fine. 
    Windows 7 Enterprise (service Pack 1)
    64bitProcessor: Intel Xeon CPU, W3670 @3.20 GHz 3.19GHz with  24 GB Ram
    Quadro 4000 Driver version 320.92 was 311.35
    Samsung SSD 840 Series
    What I have done to solve the problem:
    I have updated the drivers for both the intel cpu and the video card, I have also sign out of adobe creative cloud and signed back in. I have also un-installed premeire and re-installed it mulitple times.
    Premeire will run if I change the compatibiltiy setting to windows 7 or Windows server 2008(service Pack 1)  that works but it's super slow (and O mean unusable). I would like it to run as fast as it was before my harddrive died and not in a compatibiltiy setting.
    Currently the Premiere Pro CC hangs up when its "loading ImporterQuicktime.prm" then gives a "Adobe Premiere Pro Startup Error" - "Could not find any capable video play modules. Please update your video display drivers and start again" which I have tried updated the driver with no-luck.
    At a last resort I reformatted the harddrive and re-installed windows and went back to the old video drivers version 311.35 (which is the adobe approved drivers for CS6) but the same outcome accrued.
    Thanks for the Help.

    I have had almost exactly the same issue Kevin - I even got tot the point of re formatting my HD too. Seriously frustrating.
    I have a Samsung Chronos 7 i7 NoteBook.
    Intel(R) Core(TM) i7 - 2675QM CPU @2.20GHz
    8GB RAM
    64 bit Operating system
    Windows 7.
    My drivers are updated for: Intel / AMD Grpahics cards
    Java Updated and installed.
    SW Updated - Up to date
    All windows updates installed.
    Quicktime 7.7.4  Pro Installed.
    Google Chrome Web Browser.
    I was told by an Adobe Tech that the issue lies with the Intel and AMD cards conflicting. That Prem Pro CC only wants to use the AMD card but the Intel is being used first. Having spoken to Samsung techs they say that outside of using 'Catalyst Control Center' (which has aslo been updated) there's no way of doing that. : I
    PLEASE someone say there's a solution to all this. Prem pro is my primary source of income as a freelancer. Plus I've spent over 7 hours on the phone to both Samsung and Adobe and my head is about to melt.

  • Stuttery playback Premiere Pro CS6, I know this is a FAQ but I can't find a fix.

    I'm going to list as much as I can if I forget anything please don't be harsh, I will make sure to add/reply with what I missed. Please bare in mind I may add stuff that is not a cause of the issue but I'm just trying to give you as much background as possible.
         Basically I have been using Premiere Pro for quite a while (around 4-6 months with no issue) I came over from Sony Vegas and have never looked back, (I use Ps, Au, Ai & Ae also so the intergration is perfect) a couple of weeks ago I started havng issues with playback I will add my specs below and you can see I have quite a beefy PC which makes me think it's maybe a hard drive issue. Everytime I open Pr I hit the 'HDV 1080p 30fps' preset drag my clip in and hit 'change sequence settings' Screenshots: http://imgur.com/a/kXG8n
    Then as I mentioned about 2 weeks ago I started having stuttery playback (frames will stutter foward and after around 10 frames with jult back around 4-5 frames), I found a fix of copying & pasting my timeline into a new sequence but this fix is no longer working. One thing I have noticed is that the work area render bar used to be red and is now yellow when I add my footage, I am using the software MPE (I have an AMD GPU and as far as I'm aware I cannot do any different) I have 10gb of ram allocated to Adobe products in the 'memory' tab. I have tried 'optimizing rendering for' both performance & memory and giving it all 15gb of RAM that I can but it all makes no difference. Screenshots: http://imgur.com/a/Guanm
    I have been googling it every day for the past two weeks, I even have the search 'stuttery playback in premiere pro' bookmarked and have have tried every possible thing. I have been forced to go back to Vegas for the moment and I want to be using Premiere Pro again so can anyone help?
    i'm aware that it could be a hard drive issue as I only have one HDD, this has never been an issue before and I don't wanna go out and spend unnecessary money. I appciate any response, I'm not sure how these forums work with upvotiing or anything like that but if you could share this discussion with people that would be fantastic, thank you very much for your time.]
    My PC specs: (I have put all that I think is relevent, if anything else is needed please let me know).
    Processor: Intel® Core™i7-2700k Quad Core (3.50GHz, 8MB Cache) + HD Graphics
    Motherboard: ASUS® P8Z77-M: MICRO-ATX, USB 3.0, SATA 6GBs, ATI®CrossFireX
    Memory: 16GB SAMSUNG DUAL-DDR3 1333MHz (2 X 8GB)
    Graphics Card: 2GB AMD RADEON™ HD7850 - DVI,HDMI,2 mDP - DX® 11, Eyefinity 4 Capable
    Memory: 1TB 3.5" SATA-III 6GB/s HDD 7200RPM 32MB CACHE (Please note: this drive is currently writing at 183 MB/sec)
    Once again thank you for your time.

    Part of the reason for such stuttery playback performance lies with the limitations of the single SATA connection (channel) itself. You see, SATA is not full duplex, but only half-duplex. That means that a block of transfers going in one direction must be completed before a block of transfers can even begin in the opposite direction. Think of the SATA channel (single connection) as a single-lane stretch of highway with traffic signals at each end. What's worse, that single disk must also deal with the Windows pagefile, the media cache, previews and various other things all going on at the same time. As a result, the effective performance of that single disk can plummet by a factor of six: That single disk, after accounting for all of the tasks it must perform at the same time as video playback, is left with only about 32 MB/s of bandwidth available for Premiere Pro.
    In other words, that single disk is being severely overworked as it is.

  • Problem with Adobe Premiere pro cs3 3.0

    Hello there! I have this odd new problem in adobe premiere cs3 that i havent encountered before and ive tried to solve it but cant =/
    If i import a picture into the project it lies there like it should ready to be dragged onto the timeline, the problem is the preview of the picture and the screen when i drag it into the timeline is black.. i cannot get the picture to appear as it just keeps being black, ive tried diff sizes of pictures, the only pictures that ive found that works so far are the windows example ones..
    Answers Asap are appriciated, its a wedding movie and has to be done by tommorow night..

    Can you download and install G-SPOT and run those problem files through it. Tell us what G-Spot tells you. That article, that John T. linked to, should have some details on G-Spot, IIRC.
    It is likely that the CODEC is not one that is properly installed, or one that PrPro can use to edit. The good things about VLC Player is that it's free, good and carries most of its own CODEC's. The bad thing is that playing an AV file is not the same as editing that same file, and so a test in VLC will only tell you so much.
    This ARTICLE will give you some background on CODEC's.
    Good luck,
    Hunt

  • Problem encountered with Adobe premiere Element 4 et DVD sony Handicam

    I have a sony Handycam DCR/DVD203E . Window Vista edition familiale premium service pack 1 .Adobe Première Elements 4 .
    I take 10 rushes of 2 minutes each . I finalised the DVD for importing it on my computer under Adobe Elements 4 .
    When i do " add médias " , I only get two files , one called VTS_01_1.VOB which is the total of my 10 rushes but it's only one rush of 20 minutes .I get also an error message " C:\users\Videos\20081125\VIDEO_TS... FORMAT ERROR or file correupted/a component needed is may be not installed .
    I shoud get my 10 rushes of 2 minutes instead of one rush of 20 minutes film .

    Just a few clarifications first. Rushes, are the quick (hence the name rush) optical prints made from cine negative film. Their intention is for viewing, quickly, the results of the previous day's filming. They are not color corrected, or manipulated in any way. They are also not edited, other than being spliced together, take after take, so the crew and decision-makers can see what was captured. These are usually discarded soon after selections are made and decisions are finalized. The original negatives are then cut in the editing process and, when complete, are printed to positive projection stock with color and density corrections. Now, the final output is more often some digital format for commercial distribution.
    What we have are 2 min. Clips, in digital capture parlance. However, lets go back a moment to the first paragraph. Just like the negative film stock, this Sony camera shoots to DVD. Just like cine negative, with an editing workflow, something else has to be done. Unlike the negative film stock, the DVD can actually be viewed in an optically correct, albeit unedited, format.
    The .VOB files on the DVD are part of the inherent file structure of that medium, the DVD-video and are made up of MPEG-2 (DVD-spec) compressed files with very specific criteria. Unfortunately, the aspects that go into creating an instantly viewable medium, add some problems to doing any editing with it - first there is the structure .VOB, next, the initial compression to MPEG-2. Neither is ideal, if one plans on using an NLE (Non-Linear Editing) workflow. The .VOB structure will have to be converted at some point, and the MPEG-2 compression will have to be decompressed into another format, and most likely, be re-compressed back to MPEG-2, if the final output will go to DVD. Substitute that second MPEG-2 re-compression with Flash, WMV, or whatever, should the intent be streaming media.
    Steve has addressed the problem head-on, which is a good way to tackle it. This is intended to just add a bit, to what he has already written, not to correct anything, or change anything.
    With the proliferation of more and more non-tape capture devices, i.e. cameras, on the market, one must make a conscious decision, as to what they will ultimately wish to do with the footage captured. While it CAN be edited, with certain limitations, it is first designed to be viewed in its raw form. It handles this last job well - just pop the DVD/mini-DVD into a player and view, or hook the camera directly to the TV (or through other devices attached to the TV) and view. Editing, however, becomes a bit more complex, and needs to be well-thought out, and planned for.
    The FAQs, at the top of these pages, go a long way to helping make informed decisions, come editing time. The compromises are outlined pretty well. Yes, there
    b WILL
    be compromises, as the medium is not designed to be editable in the first place. It is a delivery/viewing medium. This should be a strong consideration, when shopping for a video, or still/video camera. What will I want to do with the material generated by that camera? Do I want to just record and view, or do I want to edit, before the final presentation of the material? If one is here, in the Adobe Premiere Elements (or Premiere Pro) forum, then it is likely that some editing is intended. If one has gone with a tape-based capture device, the editing path is clear - Capture, edit, Export. If one has gone with a HDD (hard drive), DVD, magnetic storage camera, decisions have to be made and some planning must go into the process of editing. Then is the time to learn the proper workflow (will differ dependant on the exact process of capture, that the device uses), and will pay dividends. Learning what compromises will have to be made and how best to keep these to a minimum, will be needed.
    The ease, with which these non-tape devices capture the footage, does not belie what lies ahead, should one wish to later edit. They seem so simple - shoot, then view. However, there the simplicity ends. It is later editing, that must be heavily contemplated. These forums, and especially the FAQs (remember, they are at the top of the main pages) are a good place to learn what comes next. The simplicity quickly peels away and a lot of new techniques need to be learned. As Dorothy commented, were not in Kansas anymore, Toto... If one wishes to get good results from the editing of this type of material, they need to be ready to learn. This might also be an instance, where learning by reading (first), is far preferable to learning by doing. It is far less frustrating. One also needs to be ready to dig deeply into their toolbox, which might well contain a lot of extra programs, to accomplish the task, in the best manner. Even for tape-based editing, one can never have enough tools in that toolbox, i.e. 3rd party utilities and programs.
    As an aside, I use PEs big brother, Premiere Pro, for my editing. However, I picked up PE as another tool in the process, as it does some things better than big brother does. Never be shy of using the right tools, even if it means that you have to go outside of PE and even Adobe.
    Hunt

  • Adobe Premiere Pro CS5.5 Crashing on Render/Encode

    So, this is a pretty non-complicated problem. I think I have narrowed it down.
    So basically it's this, I try and render footage that is about 10 minutes long. About 3/4's of the way through that Adobe Premiere Pro crashes. It just shuts down, no warning. Computer is still on, and the CPU Load reduces to about 10% from 80%-90%. I think I have narrowed it down to the problem of the CPU overheating. I got speedfan, lastest version and I look at it, pumped all the fans up to 100%. It still crashed along with the CPU heating up to about 52-55 degrees Celsius. Now you might be thinking that is extremeley low, but my CPU is usually at a resting temp. of 38 celsius.
    Please help, everything is updated. I think the problem is that I only have 3 fans. GPU fan, CPU fan, and a fan to suck air in. The problem lies with my case. It is so POORLY designed that with my MotherBoard it LITERALLY CANNOT FIT ANY MORE FANS IN THE CASE. Now, words cannot describe how angry I would get at the person who designed the case, but hey, you get what you pay for. Do you guys think this is purely Overheating - I'm sure if I tried hard enough I could fit another fan in there. Or something else - because I don't think it should shut down at 50 celsius.
    Specs..
    AMD Radeon Sapphire HD 6850 Graphics Card
    AMD FX(tm)-6100 Six-Core Processor
    ASUSTeK Computer Inc. M5A97 R2.0 (motherboard)

    Take the side off the computer case and put a small fan next to the computer to blow room air onto the CPU and motherboard
    If that works, you know you need better cooling (maybe use the furniture brush with your vacuum cleaner... computer power off, of course... to remove any dust bunnies)
    How are you with building a computer... so do you think you could move everything to a new case?
    I built a computer for my wife a couple months ago http://www.pacifier.com/~jtsmith/ADOBE.HTM and with options, the case has 4 fans and her CPU runs fairly cool

  • AVCHD Audio not importing correctly to Premiere

    Hey folks,
    I have some interviews in AVCHD files that I am editing for work. I correctly preserved the AVCHD file structure, and when I playback the interview in Quicktime, there is no issue with the audio. However, when imported into Premiere Pro, the final ~6 min of the interview has bugged audio which just repeats one sample over and over again. Image attached
    I have tried transcoding the clip to DNxHD but that did not solve the audio issue. I believe the problem lies with the Premiere software, or the file. But again, the audio playback in Quicktime is correct. Any help?

    This could be a cache problem ... first, you might try deleting the cache files and see if that fixes it ...
    Neil

  • Only one CPU core is working during video export from Premiere Media Encoder

    Windows Resource Monitor showed cores 'parked' at first. I was able to turn that feature off using regedit. They no longer say they are parked'. but still only one core is at 100% while the other seven cores are at close to zero %. Windows 7 Ultimate SP1 64-bit. i7-2600k processor 3.4 GHz running at 3.8 GHz XMP setting. ASUS P8Z77-V motherboard 32 GB RAM.
    I had this problem in the past and fixed when I turned off core parking. But, I recently clean installed Windows and problem has returned. I contacted Microsoft and they assured me that the problems lies with Premiere or AME.
    it just took over an hour to export a video that should have taken 10 minutes

    This has been driving me CRAZY... so going over the message boards from 2 to 5 am this morning I found the best explanation I have seen.   The problem is that Adobe Creative Cloud is NOT "Processor Group Aware".  Windows parses any more than 36 cores into "Processor Groups" and while the Pro version of Windows 7 & 8 can handle 256 threads they have to spread them across multiple processor groups.
    Simple Version:  AREA | How many cores does 3ds Max support?
    Microsoft's Explanation:  Processor Groups (Windows)
    Clearly, this is an Adobe Problem... If any engineers are reading this PLEASE review the below and incorporate it into your next build of Creative Cloud!!!
    https://msdn.microsoft.com/en-us/library/windows/hardware/dn653313%28v=vs.85%29.aspx
    Again, I bought a VERY expensive machine based on your white paper that recommended Dual Xeon Workstations.  Please, Please Give us the product you PROMISED!!!
    Michael

  • After Effects & Premiere CS5 HELP!

    I purchased Adobe CS5 Master Collection through my work. IT was already opened when I got it. When I installed it every program was there to install except After Effects and Premiere. This was on my macbook pro duel cor 2.16 running snow leopard.
    When I installed another copy for my pc the programs showed up but had a message saying I needed to update to run.
    Why would they not even show up in the" install options window" on apple???
    Isn't it true Adobe had after effects cs4 and premiere cs4 on the install cd if cs5 wouldn't run?
    Thanks
    -B

    "In response to stevevance- the Intel Core system requirements you listed are only for a PC. For a mac all it says is that we need a multicore Intel processor with a 64-bit support, and I think all Macs automatically run 64-bit."
    I believe you are mistaken Katherine and therein lies your problem, the Intel Core Duo is a 32-bit processor.  Requirements for CS5 Premier and After Effects are a 64-bit processor... while the Macbook Pro with Intel Core Duo's can run 64-bit programs, they run them at 32-bit, After Effects and Premier require to be run at 64-bit and cannot be run on a 32-bit processor. Such is the case with Intel Core Duo's which are 32-bit.  While you are correct when saying "all Macs automatically run 64-bit." they run 64-bit programs yes, but After Effects and Premier CS5 require the 64-bit processor.  Any Mac with all the system requirements but is missing the 64-bit processor will not be able to see the install option to install Premier and After Effects CS5.
    My MacBook Pro 17" (fully upgraded) with Intel Core Duo was unable to see the installation selection. But my recently acquired MacBook Pro 15" with intel i7 core was able to see the installation selection.  Intel Core Duo = 32-bit.... Intel i7 Core = 64-bit

  • Premiere Pro CS6 for Broadcast ProRes HQ Frame rate issues

    I switched from Avid to work on a quick project with DSLR footage shot on the 5D Mark III at 29.97 psf which is not to be confused with 29.97i, a standard frame rate necessary for broadcast.   So the commercial spot was cut together, I punched in the proper settings (the very same settings that work with Avid 6.0+ and Final Cut Pro 7), and hit export.  When exporting either a Quicktime Animation or Pro Res file from Premiere Pro CS6, premiere creates a file with a faulty framerate, it comes out as 28.4 instead of 29.97.  I thought I was going crazy, but no, there are tons of documented experiences with 23.94 being 20-something, and on an on.  It seems as if Adobe did not do a good enough job with integrating the Pro Res codec into their software.  The only way I could get around it was to export to something else (Blu-ray H.264 at 29.97), and then re-encode that file to Pro Res HQ with either compressor or adobe media encoder.   The problem lies in exporting progressive footage as interlaced, it just completely screws up the frame rate.    The worst bit is that, I need Pro Res HQ for the distribution house for the commercial spots, they require the ProRes HQ MOV at 29.97i and if anything is off, I get charged for it.
    Does anyone else have problems with Adobe Premiere lacking on the professional end? Or similar experience with this problem?
    Just do a search for pro res frame rate issue premiere and you will see a lot of other users with the same issue.
    Thanks,
    C
    System Config:
    Mac OSX 10.8.2
    2.7GHz Intel Core i7 MacBook Pro 15" Mid 2012
    NVIDIA GeForce GT 650M 1024MB
    16GB 1600 MHZ DDR3
    256GB SSD + 750GB SATA (no CD/DVD)
    Premiere Pro CS6 (latest)

    Read the Warning here: http://ppbm7.com/index.php/tweakers-page/85-raid-or-not-to-raid

Maybe you are looking for

  • Email Feature in Acrobat 9

    Hi Friends, I have been using acrobat 7 for long and recently upgrade to acrobat 9 reader. In Acrobat 7 there used to be a email icon on the toolbar which allows user to attched the pdf document as link/attachment in email and sent it via oulook from

  • Is there any way that I could get pages on to my iPhone without buying it again, through the app store? I already bought the computer software.

    Is there any way that I could get pages on to my iPhone without buying it again, through the app store? I already bought the computer software.

  • Playing multiple movies automatically

    I'm an iMovie/ iDVD neophyte, and I can't - for the life of me - figure out how to have the DVD automatically play the 4 iMovies I've imported to iDVD all in a row without first returning to the main menu. There's got to be a way to do this...HELP!

  • Call Fm dynamically

    Hi all, I am using FP_FUNCTION_MODULE_NAME    fm to get a fm name of a Interactive/PDF form. I want to know that when i get this FM name how to call it dynamically. Points will be sured for valuable answers. Thanks Sanket sethi

  • Overload a Package with Private Procedures

    Hello All, Is there a probelem if you Overload a Package with Private Procedures? In other words if I have two like named procedures in a package, neither of which is declared in the pacakge specification? It seems like I always overloaded a package