New NVIDIA Driver issue with Premiere pro

Laptop
Windows 7 pro x64
Intel Core i7 2.7ghz
16 gig ram
NVIDIA GTX675MX driver version 314.07 2013.2.18
Hello, I had to update the driver due to premiere stating I had an outdated driver.  After installation everything seemed fine however today when I opened premiere my source and preview windows showed black, no video.  My edits and source files were all still there.  Sound from my clips played but no video.  I have Mercury playback set to hardware.  When I switch it to software the video images return.  Has anyone else had an issue with this driver in Premiere pro and did you find a solution?  I did a search and this seems to be an issue with drivers.  Hope they fix it in the next update. Thanks.

Thank you everyone,  I just figured it out.  For some reason in my NVIDIA Control panel-Manage 3d settings-Global settings Preferred Graphics processor drop down was set to Auto-Select.  I switched it to the NVIDIA card and everything seems back to normal.  Phew! 
Harm,  I used your system configuration guide to set up my system. That really helped take the confusion out of proper system configuration.  Thank you for writing that.

Similar Messages

  • Major Issues with Premiere Pro CC

    I am currently having some major issues with Premiere Pro CC running on my macbook pro(specs below).
    I am trying to export a 4 minute video using the vimeo 1080p export settings as I usually do, and it takes about 10 hours to export the video. On cs6, a similar project would take 5-10 minutes.
    Also, the video that was exported contained a lot of clips that came out choppy and low quality.
    I am currently on the phone with tech support, and they cannot seem to figure out what is wrong.
    I have seen a few post about CC having issues with amd cards, but nothing has been confirmed yet.
    Any help would be greatly appreciated since this job is past due due to these issues.
    2011 MacBook Pro
    i7 2.2
    16GB Ram
    256 SSD + 750GB HD
    AMD Radeon HD 6750M 1GB

    You neglected to specify exactly which release of PPro CC you are running. There have been 5 of them.
    If you're on CC7.2 or 7.2.1, then you may be hitting the same problem discussed in one of these threads:
    RGB Curves: http://forums.adobe.com/message/5929088?tstart=0#5929088
    http://forums.adobe.com/message/5934916?tstart=30#5934916
    http://forums.adobe.com/message/5935386?tstart=0#5935386
    The first thing to try is switching Renderer to Software Only.

  • Graphics Card issues with Premiere Pro CS4

    Hey there,
    I've placed the screenshot of my problem at the bottom of this post.
    I'm having lots of issues with premiere pro CS4 and editing videos since I upgraded to Windows 7. I have some .mpg and .MP4 videos. Both of which play fine in WMP, VLC, WinAmp, VirtualDJ etc. But when I load them into PPRO CS4, as you can see in the screenshot they go green and pink. And they don't move. I.e you see one still image and hear only audio.
    Now a fix I have found for this is to uninstall my graphics card. But this is no way an option to edit videos, as the resoultion goes from 1920 x 1080 to 1024 x 768.
    I should add that I am runnig the following system:
    Dell Vostro 1000 Latpop
    Windows 7 Ultimate 32Bit
    2.00Ghz AMD Sempron Processor
    2GB RAM
    ATI Radeon XPress 1150 Graphics card
    I have the latest graphics card drivers installed. I am just wondering what the problem is, and a potential fix. Would be great to hear any advice,
    Regards,
    Adam.

    OK, here are some other things to think about:
    ATI/AMD Catalyst seems to have an issue with one of the latest versions, maybe rollback to an earlier version.
    Depending on your OS, check Hardware Acceleration (though this usually affect smoothness of playback) in Control Panel>System>Hardware>Advanced.
    Check your OpenGL settings.
    In Catalyst, turn OFF any GPU Acceleration
    That's about all that I can think of for now, and those are shots in the dark.
    Good luck,
    Hunt

  • Asio Driver issue in Premiere Pro CC conflicting with all other media players on PC

    Whenever I have Premiere or audition or After effects opened---- should I want to play a media clip on J River Media center, or Windows Media Player, the Asio driver is locked by the Adobe products, so the other media players do not have access to it. This may be a new windows 8.1 phenomenon, as i never had this before with 64 bit Windows 7.
    I have had some success running the other media players on the lousey windows sound drivers, but they don't sound nearly as good as the Asio driver does, with its near zero latency.
    My sound card is a Lynx aes 16, and the Win 8.1 PC pushes the digital audio out to my Berkely DAC , then to separate mono bloc amps, into  Magnepan speakers as the reference audio system for my music and video editing....or for  entertainment listening :-)
    Does anyone have a solution that will force the Adobe CC software to release the Asio driver when I try to use J River Media center, or some other media player?

    I had this problem this evening 090813 after upgrading my Adobe Cloud Desktop. 
    I open Pro CC and had the  Dolby Audio Decode Licensing Restriction for (File name.......... )       Error
    Previous CC progs loaded and worked with problem.
    I uninstalled Pro CC - Restarted the computer - Re-installed Pro CC.
    Now working with no problem.
    Hope this helps.
    John

  • H.264 encoding issues with Premiere Pro CC 2014

    After updating to Premiere Pro CC 2014 yesterday, I see encoding artifacts on my H.264 exports.
    Same source video imported into CC v2014 and v7, and exported using the YouTube 1080p 29.97 fps settings. The artifacts manifests itself as softness/blurriness in parts of the image every few seconds, especially notice the area with a red circle below.
    Here are the source file (GoPro HERO3 Black Edition), the v2014 render and the v7 render.
    Original: https://drive.google.com/file/d/0B2rJe0xgMTxFYXJiMjZpZ0stUzQ/edit?usp=sharing
    CC v2014 render: https://drive.google.com/file/d/0B2rJe0xgMTxFQ1B0Z09GS3I0a1E/edit?usp=sharing
    CC v7 render: Premiere Pro CC.mp4 - Google Drive
    [Version numbers corrected.]
    Message was edited by: Jim Simon

    Mark Mapes wrote:
    This is a known issue introduced in CC2014.0. Some h.264 encodes have blurriness or noise periodically in some areas of the frame. The problem is most pronounced in regions of the frame with very little detail, like grass or pavement--or the T-shirt in the sample frame. We are working on a fix. Before you ask when the patch will be forthcoming, I'm not authorized to even hint at the timeframe.
    Unfortunately, the only real workaround is to export to a format other than h.264. If that's not an option for you, then your best bet is probably to keep working in CC7.2.2 until the patch is released.
    Sorry, but thats not completely true and by far not the correct answer:
    The problems with random artifacts occurred with the introduction of a new version of H264 in CS6 but there you still had the option to export with the previous H264 Version via Media Encoder. 
    Since the previous H264 version is not available in CC, using CC7.2.2 is not a solution either.
    BTW
    Updating to CC and using the new Mac Pros with Mavericks is currently a total mess - no open cl rendering, random crashes, no usable h264 ... thanks adobe!!
    ... but we can track masks in premiere now ... wow!

  • Massive Lagging and issues with Premiere Pro CC 2014

    For the last year we have been in post on our feature documentary. We have roughly 15TB of footage that is all stored on a raid coming into our edit suite via fibre (I don't know much of the technical information about it other than it's trustworthy and works for the other suites in our facility). We're in the final stretch and locking edit February 1. But the issues we're experiencing are making it very difficult to advance and fine tune the edit.
    Over the last month or two performance with Premiere has been getting worse and worse. We are experience lag in actions when editing. It could be as simple as moving the mouse, clicking or copy/paste which can result in freezing or lag where we have to wait a few seconds or minutes for the program to catch up with itself.
    We've been trying to figure out what is going on and if we can do anything to eliminate these issues. We have removed all cache files. We have eliminated any unnecessary or old sequences from our project file.
    I will note that our project file is massive. It's currently about 1.15gb in size. Our sequence is a little hairy also. Not sure if this could be causing issues, but it hasn't in the past. See image below.
    Running latest version of Adobe Premiere CC 2014.
    Mac Pro
    OSX Version 10.9.5
    Processor: 2.7 GHz 12-Core Intel Xeon E5
    Memory: 64GB 1867 MHz DDR3
    www.animaleast.com

    Mark Mapes wrote:
    This is a known issue introduced in CC2014.0. Some h.264 encodes have blurriness or noise periodically in some areas of the frame. The problem is most pronounced in regions of the frame with very little detail, like grass or pavement--or the T-shirt in the sample frame. We are working on a fix. Before you ask when the patch will be forthcoming, I'm not authorized to even hint at the timeframe.
    Unfortunately, the only real workaround is to export to a format other than h.264. If that's not an option for you, then your best bet is probably to keep working in CC7.2.2 until the patch is released.
    Sorry, but thats not completely true and by far not the correct answer:
    The problems with random artifacts occurred with the introduction of a new version of H264 in CS6 but there you still had the option to export with the previous H264 Version via Media Encoder. 
    Since the previous H264 version is not available in CC, using CC7.2.2 is not a solution either.
    BTW
    Updating to CC and using the new Mac Pros with Mavericks is currently a total mess - no open cl rendering, random crashes, no usable h264 ... thanks adobe!!
    ... but we can track masks in premiere now ... wow!

  • Internal hard drive issue with Mac Pro

    I work for two office that share information through a VPN. Each office has one Mac Pro being used as a server for data storage. The Pros have four internal hard drives (1TB each).
    Hard drives in the Pro for OFFICE 1 were configured like so:
    HD1 - OS/Boot drive
    HD2 - Time Machine backup of HD1/DATA1/DATA2
    DATA1 - Data storage
    DATA2 - Data storage
    Three weeks ago: Time Machine could not find HD2 and could not backup. I rebooted the machine and HD2 reappeared. However, after the reboot, DATA1 did not mount. I was unable to find DATA1 in Disk Utility. However, the drive could be accessed by all other Macs on the network. This machine was taken to the local Apple Store and we were told that HD2 was a bad drive and need to be replaced. We opted not to replaced the drive at this time and turned Time Machine backups off. We haven't had any problems with DATA1 since. (NOTE: During the weeks prior, the client machines intermittently lost connection with DATA1 and would have to reconnect)
    Last week: OFFICE 2 - Mac Pro hard drives configured the same as OFFICE 1; however, HD2 was not used for TM backups. TM was turned on and set to backup HD1/DATA1/DATA2 to HD2 (exactly like OFFICE 1). The next day, TM could not find HD2 and backups stopped running. I rebooted the machine, HD2 reappeared, but we did not restart the TM backups.
    Today: OFFICE 2 client machines have experienced intermittent disconnecting of DATA1.
    I wasn't extremely concerned with the situation at OFFICE 1 as these Pros are almost five years old and in constant use. We plan on purchasing an external drive for the TM backups. HOWEVER, with a similar situation now being experienced in OFFICE 2, I am perplexed.
    Could both machine be experiencing hard drive failures weeks apart? They were both purchased and installed at the same time.
    Is there a known issue with TM and internal drives?
    One difference between the two machines: OFFICE 1 is running OS X 10.8.5; OFFICE 2 runs 10.6.8
    Any suggestions/help is appreciated. Thanks!

    Relying on TimeMachine has some issues, along with only having one, I use at least two swapping TimeMachine so that they rotate AND I clone every drive (volume actually) so I can swap drives if need be, especially useful for t he system but good for any drive.
    Power issues in t he buildings?
    There are some programs that will scan for and report and./or attempt to reassign a failing sector ("fail" is qualitative, is 10 write failures a fail? then the 9th is not but it is a "weak sector.") Some run in the background.
    Mirror can be 2 or 3 ( I prefer 3, that way if one fails I STILL have a mirror array in place) where any failure is not acceptable, AND where the array data is backed up usually - less important  when using a three-drive configurations.
    How old, when last initialized (zero), and is it showing spare blocks being used? that last is the most indicative of failed drive.
    Rare but a bad SATA cable or power (seeing how the cables are tucked away) is only way generally for multiple failures in same drive bay or computer. Note: early on in 2006-7 there were reports of some customers having motherboard and trouble with a drive bay , and t he problems showed up early.
    Often though it is NVRAM or SMC related issue trigged by something else, a USB cable or device that is faulty, even a PCIe controller that is the culprit. And replacing cable, keyboard, device, and resetting SMC and NVRAM (often NVRAM needed to be done multiple times, but never keep resetting SMC) - unplugged and when you connect back up, do not install anything other than system, keyboard and mouse and see if that helps.
    With a drive, likely the drive in 85% or more, is fine, but the directory is not, or it needs to be erased to rebuild all the system partitions.
    1TB is small for TimeMachine. 350% of the amount of data, and always have free space for a full backup set of all the data. T.M. will try and prefers to automatically backup any and everything plugged in and connected, rather than my preference which is ASK FIRST to add a drive to TM backup set, otherwise leave it out. 600GB of data and system would mean 2.5TB drive, maybe 2TB minimum.

  • Using new Adove Media Encoder with Premiere pro cs4

    I have Premiere Pro Cs4 and Design&Web premium CS6 -  which comes with Adobe Media Encoder cs6. Can I get Premiere Pro CS4 to use the new encoder (and hopefully speed up)?

    I am on Window 7 32-bit that Premiere CS6 does not work. So I use CS4 for editing. For one specific project, I kept getting errors when using AME CS4 and it was extremely slow (8min of video estimated 20 hours). Someone said CS4 4.2 is really slow so I'd like to use AME CS6 to render project files from CS4. Tried that but got adobe dynamic link components error. I think it may be because I didn't include Premiere and After Effects when installing CS6.
    Do you have success using AME CS6 on CS4 project file? Is it likely to make it work without installing CS6 one more time?
    Thanks,

  • Any issues with Premiere Pro CC and Avid Media Composer on same system?

    Hi all:
    Searched around for this but couldn't find similar question.
    Am a long time Premiere Pro user, but have something coming up where I'm having to use Avid MC to collaborate with a staff editor for the duration of the job.  Am wondering if I should expect any conflicts or issues to installing both Premiere Pro CC and Media Composer on the same system?  Any insight would be most welcome.
    Running Adobe CC on a Windows 7 HP Z820, Dual Xeon Processors, 128Gb RAM.
    Thanks!

    hi Jim,
    well it turns out that Premiere update 7.2.2. put my computer into disarray, and caused my multi-camera monitor to lag (about 6 seconds) behind my program monitor .. so my my multi-cam monitor (with my 2 or 3 camera feeds) would  be playing footage that is 6 seconds or so BEHIND what was playing on the program monitor.
    that's the gist of it..
    anyway the fine folks at Adobe, talked me through the process of going back to premiere 7.2.0 and that fixed the issue.
    i hope future updates resolve this issue so that i can get back up to the minute on my software
    thanks
    jahZ

  • QTFC Issues with Premiere Pro CS4?

    Hello there.
    So recently, I have been having issues with my adobe programs. I have the Master Collection CS4 and when I launch programs like After Effects, it tells me the following.
    "QuickTime functions will be disabled because a compatible version of QuickTime could not be found"
    and here's my real issue. When I go to launch Premiere Pro CS4, I get the following error.
    "Adobe Premiere Pro.exe - Entry Point Not Found
    The procedure entry point QTCF_CFUniCharGetUnicodePropertyDataForPlane could not be located in the dynamic library link QTCF.dll"
    I click OK and it pops up again, then premiere launches. How do I get rid of this error? I have tried reinstalling Master Collection and Quicktime but that didn't help.
    I cannot afford to reformat computer as I'm very busy and need my programs to work.
    Thankyou for your time and support.
    -Matthew.

    To answer your question. I had the same problem that you had. I was using Quicktime 7. So I downgraded by downloading Quicktime 6.4
    Here's a link:
    http://docs.info.apple.com/article.html?artnum=120297
    So I installed QT 6.4, and the error message is no longer there. But there is another issue, I try to import or find a file that is a .mov and it says File format not supported. Which is weird because you get that if you don't have quicktime installed. That may be an entirely different problem. But hope this at least helps you answer your question.
    UDP&R Staff
    http://udpr.bluangelnet.com

  • Crashing issues with Premiere pro Cs6

    When I use Premiere Pro CS6 it tends to crash and it also tends tends to make the video pink and green looking, and it also sometimes flips it upside down and turns it black and white. So I was wondering if auto-saving had anything to do with it or if my camera or cpu had anything to do with it. I re-installed the program once, I also tried converting my video files to h264 before bringing them into Premiere. I use a Sony HXR MC1500p, and I am not using PAL by the way (or maybe I am and I am unaware), I really dont understand PAL and NTSC anyway.
    Camera Specs:
    http://www.bhphotovideo.com/c/product/759003-REG/Sony_HXR_MC1500E_HXR_MC1500E_Shoulder_Mou nt_PAL.html
    CPU Specs:
    http://www.tigerdirect.com/applications/SearchTools/item-details.asp?EdpNo=3844129&CatId=1 14
    Please Help me!
    Thanks, Ryan

    1st. You don't have convert you videofiles they are AVCHD so OK for Premiere Pro.
    2nd. The edit PC (with Pro pro) is far better off with Intel CPU, Nvidia GPU,  lots of harddiscs, >800 watt gold PSU, big CPU cooler etc etc..
    3rd. Read a few hours at the hardware department. And you could build a nice machine for $1500,- to $3000,- yourself or order at ADK.
    http://forums.adobe.com/community/premiere/hardware_forumhttp://

  • Is the latest 280.26 nvidia driver compatible with MacBook Pro 6,2 model?

    Is the latest nvidia driver (280.26) compatible with MacBook Pro 6,2 model)? Boot Camp 4.0 comes with the 262.41 nvidia driver, but I'd like to upgrade to the latest 280.26. The official 280.26 driver page on the nvidia site says that GeForce GT 330M is compatible, but in the footnote is written this thing:
    Notebooks supporting Hybrid Power technology with Intel chipsets are not supported by this release
    Do you think this is the case of MacBook Pro 6,2 model? Can I upgrade the driver without any problem?
    P.S.
    I've the nvidia geforce gt 330m 256 MB.

    Mac OS X 10.8.2.
    (77868)

  • Nvidia driver 305.93 & Premiere Pro CS5.5

    I am running CS5.5.2 on a Z400 Workstation Win7 64bit. with Matrox MX02 LE. I have a Quadro FX4800 graphics card.
    I have just updated the Nvidia driver to the latest version - 305.93. Now when I open a project in Premiere the program monitor shows just the bottom third of the picture and is broken up into blocks. If I roll back the driver to the previous one I was using (276.42) everything returns to normal.
    Has anypne else experienced this & is there a soution. Everything I read seems to say 'Install the latest driver' !!

    The advice will also say... If something isn't broken... don't try to fix a nonexistent problem!
    Unless something is not working with driver 276.42 there is no reason for YOU to update... someone else, with a different mix of hardware, may need to update
    My 1st video editing computer, a model year 2002 Alienware Pentium 3 with Premiere 6 and an nVidia card, would only work properly with ONE specific nVidia driver... anything earlier or later and I had problems with video editing... so I simply used that specific driver

  • MXF issues with Premiere Pro CS6

    Hello,
    I am having trouble using Canon XF300 MXF files in Premiere Pro CS6 v6.0.2. I am using the media browser (tried icon and list view) to import footage (first importing to internal HD via the Canon XF Utility). I can import and play audio and video for all files under 2.05 GB but PPro limits any file longer than 30 seconds to  30 seconds.
    Alos, Canon cameras cut files over 2.05 GB into separate MXFs. Most of my footage are interviews over 10 minutes long so I have 3 or 4 separate MXF spanned files for each clip. Premiere is having most trouble handling these files. First of all it limits them to 30 seconds each. Then, when I import them and drag them into a sequence it will only play audio from the first spanned file, even if video from the second sapnned file is playing.
    I have tried merging all spanned files using Canon XF Utility's 'Export to MXF' function. As a result I have one 10 minute long MXF file but when I import it to PPro it still limits it to 30 seconds.
    I made the change to PPro because of the ability to edit various formats in a single senqunce without tanscoding. I recently purchased a Sony FS700 and FCP7 couldn't really handle the MTS (or clipwrapped movs). Premiere handles them perfectly but can't handle the MXFs. So currently I am finding myself going into FCP7, logging and transfering the MXFs and transcoding them to .movs using the Canon XF plugin for FCP7 and then importing those to Premiere (they work fine this way)...but of course its a hassle to do with hundreds of clips per shoot.
    I also noted that VLC 2.0.x versions can't handle the MXFs so well (video plays fine, audio at double the speed) but VLC version 1.0.3 handles them ok as long as I dont forward the video.
    Any help is greatly appreciated.
    Computer specs: Mac Pro 2.66GHz 12 core, 16 GB RAM running latest Snow Leopard update.
    Clips shot at: 29.97 fps, 50 Mpbs, HD 1920x1080.

    (first importing to internal HD via the Canon XF Utility)
    Try skipping any special software and just use Windows Explorer (or Finder).

  • IMPORT ISSUES WITH PREMIERE PRO CC

    Ok so i open up premiere pro.....
    i double click the project folder to import a file, it does it without a problem...
    On my 2nd attempt when i double click the software stalls.. So the mouse moves but nothing in premiere pro is clickable, everything is kind of frozen.
    I went to task manager and end process. Then tried again this time through file > import same thing does the first one , stalls on the 2nd.
    I had problems sending to encore with the latest update 7.2.2 so i went back to the december update 7.2.1 everything has been fine for two weeks, now this just out of the blue. Not sure how something can stop working overnight !
    Im thinking if i go to to newest update it might work but then i wont be able to export via the queue in AME.
    So i either choose not to import or export..... what a great software premiere pro has become.... I use to praise it to all proffesionals in the industry now having the most pettiest of problems... !!!
    Some assistance would be great

    I dont understand why you
    double click the project folder to import a file
    I import footage to a Bin in the Project Window by selecting the media (clips) in the Media Browser.
    I dont understand this...
    Im thinking if i go to to newest update it might work but then i wont be able to export via the queue in AME.

Maybe you are looking for