Skip navigation
cullyeefas
Currently Being Moderated

HP 8770w and vVidia K5000m not capable of running Premiere CS6 - from HP

Dec 2, 2012 5:40 AM

Tags: #premiere_cs6 #k5000m #nvidi_ #cs6_not_compatitble_with_nvidia_cards #hp_8770w_problems

I wanted to post this asap - so no-one else wasted their time & $6600.00. After a bunch of looking, I ordered a HP 8770w. Rigged as follows.

 

32G Ram

3 hard drives. 1 SSD & 2 fast SATA drives.

nVidia k5000M

latest i7 chip.

 

Sounded great - nVidia recommends HP, Adobe recommends nVidia - the 8770w is advertised as a Video Editing Workstation. My entire life & business are based around CS6, has been that way for years - since the first version of Photoshop. I'm a Cinematographer/Photographer who works from Helicopters. THe HP Business office sold me the same line about high end Video Editing. I explained that while all HD now - we are moving to 4K Vid in the next couple months.

 

Ordered the machine on Oct 20th. It arrived from China Nov 28th. Unfortunately, it shipped with WIN 7 Pro 32 bit. This left me w/ 2.7G of usable RAM and no way to run Premeire (it's 64 bit).

 

HP had me try an online WIN update. WIN saw the installed 32 bit & gave me 32 bit Ultimate! HP overnighted in discs for WIN Pro 7 64bit. Installed all, had to pull the SATA drives to get the oS to land on the SSD. The updates did not go well with HP, I was given old BIOS links & many updater links were not working, or also old. I burned up 15 hours on the phone, many more on my own. HP maintained their end was only making the hardware work - beyond that it was all on Adobe and nVidia. Although I have freezes, screens that change constantly and had to disable some key features of the 8770w - HP says it's working fine now. I get a different start screen every third startup - but I guess that is normal.

 

HP told me last night that the K5000m may just not work with Adobe CS6 and it is not HP's problem. This came from a Supervisor. I was told to deal with Adobe and nVidia and there was nothing more HP could/would do. So, here I am. Will also be posting the same on nVidias Site.

 

What is weird is that Pshop CS6 picks up the K5000M. Premiere CS6 leaves me with the greyed out "mercury playback engine software only" w/ no pull down menu. Tried full version installs, trial version installs. For now, I'll go with what HP says is the reality - which is that the K5000m will NOT run Adobe CS6. I'm wondering why I bought one and why all the Ads on nVidias Site & Adobe's Site claim the K5000m is the way to go. I now have a $6600.00 usless computer. As I don't game - I'm not sure what to do with it.

 

Be careful - it all sounds great when you order the gear - but it does not work & there is NO support available. My mistake.

 
Replies
  • Currently Being Moderated
    Dec 2, 2012 7:50 AM   in reply to cullyeefas

    Your card may not be listed as a CUDA card by PPro. You may have to add to the list of CUDA cards by hacking a txt file.  For example, see: http://forums.adobe.com/message/4828989#4828989

     

    There are other discussions about the hack as well.; search the forum

     
    |
    Mark as:
  • Currently Being Moderated
    Dec 2, 2012 8:40 AM   in reply to cullyeefas

    Ordered the machine on Oct 20th. It arrived from China Nov 28th. Unfortunately, it shipped with WIN 7 Pro 32 bit. This left me w/ 2.7G of usable RAM and no way to run Premeire (it's 64 bit).

    This one mistake alone tells me that somebody dropped the ball from the get go....

    I would've asked for another machine immediately, or ordered from one of the other reputable machine builders on these forums...

     

    So sorry to hear about your situation.

    Good luck.

     
    |
    Mark as:
  • Currently Being Moderated
    Dec 2, 2012 9:18 AM   in reply to cullyeefas

    Yes, that card works... with the "hack" as posted - http://forums.adobe.com/thread/1058306

     
    |
    Mark as:
  • Currently Being Moderated
    Dec 2, 2012 4:56 PM   in reply to cullyeefas

    The updates did not go well with HP, I was given old BIOS links & many updater links were not working,

     

    That may have been another mistake.  I find it best to always go to the hardware manufacturers' site for drivers and updates, not the system builder's.

     

    That means the nVidia site for graphics drivers, the ASUS site for BIOS and other utilities (or whatever brand of motherboard is in there), etc.

     
    |
    Mark as:
  • Alex Gerulaitis
    490 posts
    Jun 9, 2009
    Currently Being Moderated
    Dec 2, 2012 6:10 PM   in reply to Jim Simon

    That may have been another mistake.  I find it best to always go to the hardware manufacturers' site for drivers and updates, not the system builder's.

     

    That means the nVidia site for graphics drivers, the ASUS site for BIOS and other utilities (or whatever brand of motherboard is in there), etc.

    Jim, have you ever worked with HP BIOS and driver updates?

     
    |
    Mark as:
  • Currently Being Moderated
    Dec 2, 2012 6:13 PM   in reply to Alex Gerulaitis

    Hmmm...I remember Dell and Compaq.  Not sure about HP.

     

    Still as a general principle, the hardware manufacturer will have the most up to date version.  That can't always be said of a system builder.

     
    |
    Mark as:
  • Alex Gerulaitis
    490 posts
    Jun 9, 2009
    Currently Being Moderated
    Dec 2, 2012 7:22 PM   in reply to Jim Simon

    Still as a general principle, the hardware manufacturer will have the most up to date version.  That can't always be said of a system builder.

    It may apply to graphics and other devices, never to BIOS and other system-specific devices, on Tier 1 systems.  Installing only OEM-certified drivers on non-critical devices also greatly simplifies support.

     
    |
    Mark as:
  • Currently Being Moderated
    Dec 3, 2012 7:30 AM   in reply to cullyeefas

    [moved to hardware forum]

     
    |
    Mark as:
  • Currently Being Moderated
    Dec 3, 2012 9:17 AM   in reply to cullyeefas

    >The Text hack worked fine. HP had no idea that it existed

     

    Unless you are dealing with a company that has experience is building for video editing, it is not at all surprising that they don't know "something" about setup for that specific purpose

     

    >tried to explain it & offered the link, they were not interested & said I was digressing

     

    That is too bad... now, the next time someone calls them with the same/similar problem, they will not have anything to offer

     

    >reminded that the Forums ALWAYS know what's up

     

    Yes... it is very rare that a question here does not result in a solution from someone... this forum is very literaly world wide, and the depth of experience is amazing

     
    |
    Mark as:
  • Alex Gerulaitis
    490 posts
    Jun 9, 2009
    Currently Being Moderated
    Dec 6, 2012 5:47 PM   in reply to cullyeefas

    and to clarify here too. when I say it works - I mean PPCS6 picks up the card. It will not run as any changes to sequence settings crashes PPCS6.

    Does it still crash when you change the acceleration to "software"?

     
    |
    Mark as:
  • Currently Being Moderated
    Dec 7, 2012 4:59 AM   in reply to cullyeefas

    Then, we ran an app to hack the card. Restart. Ran CS6 Premiere.

     

    What app did you use and what did you modify in or on the card?

     

    It comes as no surprise that Tier 1 companies cannot support application problems like you experienced. Their only interest is shoving boxes out of the door as fast as possible and they know zero about applications and are not interested to know. It is against company policy.

     

    Even though they assemble decent hardware, you can not rely on them to help solve application problems like in your case. For that you either need a custom builder who specializes in Adobe oriented machines and are experienced with the application or rely on a forum like this one.

     
    |
    Mark as:
  • Currently Being Moderated
    Dec 7, 2012 6:46 AM   in reply to cullyeefas

    You have to run gpusniffer.exe from the command prompt:

     

    GPU_ sniffer.png

    and you have all the time in the world to inspect it and get the info you need.

     
    |
    Mark as:
  • Currently Being Moderated
    Dec 7, 2012 8:03 AM   in reply to cullyeefas

    No problems with either Win7 or Win8, so there is something wrong with your configuration or your access rights.

     
    |
    Mark as:
  • Currently Being Moderated
    Dec 8, 2012 10:24 AM   in reply to cullyeefas

    Well goody for you! I guess all the people posting about GPU sniffer running too fast have bad configs/acess rights too.

     

    No, they are not using the correct steps to run the program.

     
    |
    Mark as:
  • Currently Being Moderated
    Dec 8, 2012 10:25 AM   in reply to cullyeefas

    I'll repeat what I have said before and shown with the screen shot in a previous post:

     

    1. Go to the Command prompt by using CMD.exe (preferably with administrator rights).

    2. Navigate to C:\Program Files\Adobe\Adobe Premiere Pro CS6, using 'cd' commands, well you know them.

    3. Type in 'gpusniffer.exe' (without the quotes) and press Enter.

    4. Read the info you need and if necessary make a note of that.

    5. Type 'exit' and press Enter.

     

    That's all.

     

    If you don't go to the command prompt first, then yes, it is way too fast to read.

     
    |
    Mark as:
  • Currently Being Moderated
    Dec 7, 2012 9:22 AM   in reply to cullyeefas

    Mr.  Cullyeefas.......Harm Millard has been one of the most knowledgeable and helpful people on this forum for years now. Those who read this forum regularly depend on his insight ,wealth of knowledge, and experience to avoid costly mistakes in buying hardware to edit video with PPRO. Harm has built the fastest edit machine yet, and he has generously shared all his info concerning its construction with all of us here. In addition,he and Bill Gehrke have built the PPBM5 website for testing the performance of an editing machine with benchmarks  that truly show how well,or badly, YOUR machine may able to complete various editing tasks.

     

    I can say that if you had read this forum,esp. Harm's articles, BEFORE making your purchase you may have spared yourself much grief. Now, if you continue to study this forum you may find helpful info as you go along which can save a lot of angst and even money by avoiding costly mistakes !!!

     
    |
    Mark as:
  • Currently Being Moderated
    Dec 7, 2012 3:28 PM   in reply to cullyeefas

    cullyeefas wrote

     

    If you folks are so well tied to Adobe. How bout getting them to certify the nVidia K5000M sooner than later so others can enjoy serious mobile GPU power?? I'm cool hacking though anything to get it to work - but it's Adobes call on certification.

     

    Just for your information all the folks who helped you here are not tied to Adobe in any way.  Many of us volunteers just enjoy helping others.  We have very little if any influence on Adobe's certification schedule.  Considing that this K5000m is only about 3 months old you are asking a lot since he last Adobe Premiere update (6.0.3) was just about that same timeframe--have a little patience. 

     
    |
    Mark as:
  • Alex Gerulaitis
    490 posts
    Jun 9, 2009
    Currently Being Moderated
    Dec 8, 2012 10:27 AM   in reply to Harm Millaard

    It comes as no surprise that Tier 1 companies cannot support application problems like you experienced. Their only interest is shoving boxes out of the door as fast as possible and they know zero about applications and are not interested to know. It is against company policy.

    That's true for any non-specialty computer maker.  Why'd you single out Tier 1 - again? Personal vendetta? Spoiled? Harm's company policy?

     

    That last piece about not being interested in knowing DCC apps - pure BS. Z820 Red wouldn't exist otherwise. While HP may not employ Adobe Premiere Pro specialists in their regular technical support staff (there're VARs for that), they sure do have the specialists to support ISVs like Adobe.

     

    Harm, seriously, you gotta quit knocking down Tier 1.

     
    |
    Mark as:
  • Currently Being Moderated
    Dec 8, 2012 7:08 AM   in reply to cullyeefas

    Simply renaming or deleting the cuda_supported_cards.txt file is a way faster to enable MPE on my CS5 system than going through the whole sniffer / edit routine that is so well documented and embraced by Adobe CS users on this forum as well as the rest of the www.

     

    Could some of you CS6 users please test this method and report back if simply renaming or deleting cuda_supported_cards.txt works on your system to enable MPE (assuming of course you do have the proper hardware loaded)?

     

    Thanks,

     

    Jim

     
    |
    Mark as:
  • Currently Being Moderated
    Dec 8, 2012 9:57 AM   in reply to JEShort01

    That's exactly what I did here and for each update of CS6.  Works well; lasts a long time.

     

    Jeff

     
    |
    Mark as:
  • Currently Being Moderated
    Dec 8, 2012 10:01 AM   in reply to cullyeefas

    Some of the posts above will be edited for content.  All parties to the conversation should understand why.  Disagreements voiced about what is helpful and what isn't are perfectly fine as long those comments don't involve insults (veiled or explicit), name calling and offensive language.

     

    Jeff

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 9, 2013 8:20 PM   in reply to JEShort01

    CS6 did not originally recognized my k5000m when I originally downloaded it. I merely update the drives from the Nvidia site and everything works like a charm. No sniffer needed.

     
    |
    Mark as:

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points