The link I gave you on the nVidia website is the driver for that video card. Just to be sure this is the correct display adapter, right click on My Computer, Properties, Device Manager, Display Adapter. Does it indeed say 9300M? I thought, but may be mistaken here, that the M version is the mobile version used in notebooks.

I see for the systems requirement for premiere: Open GL2 graphics driver. Is mine compatible with this?

One thing I keep noticing is that everytime I completely uninstall and reinstall chipset driver, The display settings become really messed up, but then Adobe Premiere Pro CS4 works perfectly. But then shortly later, my computer will update itself, my computer will revert back to the correct display settings, and then I am back to having the same problems with Adobe CS4...

What I am going to wind up doing is purchasing the NVIDIA Driver, but I might need a little helping making sure I am purchasing the right one. Do you know which one will work best for me? My computer is an HP Touchsmart IQ540 (if that helps)

Just so you know, if you wind up solving my problem, you will be dubbed king of Adobe.

Hi Rick- I recently ran into major driver issues with a new Acer 6930G notebook, when I decided that I wanted to install Windows XP on it, rather than the bundled Windows Vista (both 32 bit). Acer offered no support for the system if Windows XP was installed, and no bundled driver packs were available.

After installing XP I ended up with a somewhat crippled machine, until I got onto Driver Detective. It's a free download, and basically it scans your machine to determine the appropriate drivers your system needs to improve/restore its performance. From there you can do as I did and register, and direc download links are provided to all of the drivers your system requires. The license can be shared among 10 computers, and costs US$29 for a years worth of updates and scans. There's also a current promo where you can get an extra year's updates for an additional $10 too.

I highly recommend this program/service as a means to helping you out of your driver dramas!

What happens on very many laptops is that the Video (and often Audio) is setup in a proprietary way. In these cases, ONLY drivers from the manufacturer will work/install properly. Even if one has an nVidia, or other, graphics chip, they will often be unable to install the drivers from nVidia, even though the chips match up. In the case of Toshiba, for instance, only Toshiba drivers will work, and Toshiba is famous for NOT updating their drivers.

You might have some luck at Drivers2Go. That link is for nVidia, but you can navigate around the site to match up your exact GPU. One basically downloads the most recent driver from the GPU's manufacturer's site, and then runs it through a utility to make it match up to the laptop's manufacturer's specs., HP in your case.

The HP Touchsmart IQ540 is classed as a "desktop" but it is highly integrated and built with notebook/laptop components. The Intel® Graphics Media Accelerator X4500HD is OpenGL 2.0 compatible. There is no nVidia component in this system and therefore no reason to look for nVidia drivers!

I've got to hand it to you... You are a lot more patient than I am. These so called experts handing out the solutions thick & fast when REALLLY they've got NO IDEA how to solve this problem. I can only hope that none of them are being paid by Adobe to lead you up the garden path.. which has clearly happened by getting you to start updating display drivers that were operating perfectly ok. It just doesn't make sense that if the video works fine in WMP which is directly using your display drivers THEN THE DISPLAY DRIVERS MUST BE WORKING...

Its just a shame that certain people can't admit THEY DON'T KNOW THE ANSWER

clearly Adobe has a problem & they haven't solved it yet, and thats fine so long as they can admit it & update us when possible.

PS Anyone who suggests to use the likes of driver doctors should not be giving out advice... The only way to update drivers & to physically check the brand & model of your hardware device & download the exact drive necessary DIRECT from the manufacturer.

You need to consider that WMP interacts with the graphics adapter through DirectX. Premiere Pro does not. The fact that there are distinct "data pipelines" to the graphics adapter means that driver version and driver capabilities can have a very profound effect on Premiere and not on WMP.

You are taking this out on people who wanted to help and unfortunately, Rick first posted he had a nVidia card, which put all of us on the wrong foot. Only after he investigated, based on rather detailed instructions on how to do that, did he realize that that information was utterly wrong.

You make claims and accusations that show your lack of expertise in troubleshooting, especially remotely. I suggest you do not bite the hand that feeds you.

Have you ever contacted Adobe TS with a problem? Have you ever experienced the details you must provide for them to help you? Have you ever experienced the many mails with instructions on do this, then do that, send us the results, etc.? And then the next mail and the next one.

There is a reason for the troubleshooting guides which are linked to in this thread:

The whole bunch of information requested (MSINFO, DXDIAG, PROCEXP, HWMONITOR etc.) is asked for because not everybody is a computer geek and mistakes like Rick initially made by claiming a nVidia mobile card and ultimately discovering an integrated Intel video card can be avoided. All this info goes way beyond video drivers. It is basic information in a structured way that helps to locate the problem.

If people do not want to supply that info and are not very structured and accurate in stating the problem, you may get threads like this one.

Its just a shame that certain people can't admit THEY DON'T KNOW THE ANSWER

How can people KNOW the answer if not all relevant details are supplied in a complete, accurate and structured way.

If you send a fax to your car dealer, stating "those four black things do not turn" and he admits he doesn't know the answer to your question, are you disappointed? You shouldn't be, because it is your fault that you didn't supply relevant information. Had you explained that the four black things you mentioned are usually called tires, and that you checked them this morning, because when arriving home last night you heard a strange noise while driving to the car porch, so you decided to check this morning and walked to the car porch, inspected the car as it was standing there and indeed the tires were not turning.

What you are obviously not aware of, is that many laptops use proprietary drivers. The video cards/chips used might carry a designation for, say an nVidia model, but in too many cases the nVidia driver for that designated card from nVidia will never install. If the mfgr. has an update to their rewritten driver, things are fine. Some mfgrs., such as Dell, do a good job of this. Others, like Toshiba do not. I do not know about the HP's, as I have never used them.

When faced with the prospect of the chip company's driver NOT installing, due to the rewrite by the computer mfgr, a custom driver is the only option. This is usually not at all necessary with cards directly from the mfgr., and your advice would hold true. In the case of too many laptops, it falls very short of being the least bit useful. If one has much experience with laptops, especially with higher-end graphics cards, they would have leaned these lessons early on, unless they were only dealing with Dells, or a very few mfgrs, who do offer good driver support. Unfortunately, most do not.

It is also a very popular misconception that because a video player will play a file fine, then everything on the system is perfect. The mistaken deduction often made is that it must be a problem specific to Adobe. Well, not so fast. There is a major difference between playing a file and being able to edit that same file. CODEC's that work in a player, might not be usable by an NLE. The differences in how the display sub-system is accessed and utilized can be great, between a player and an NLE. Jeff points this out quite well.

I realize that you are trying to help, though I must have missed this help you offer. Others are trying to help, as well. Their attempts are obvious. Unfortunately, none of us is sitting with the OP. None of us has the exact computer and file to work with. Some have tried with similar files and have had different degrees of success and failure. It is rather akin to a physician trying to diagnose a patient, when they can not see the patient, nor can they carry on a real-time dialog with the patient. Not that easy.

As we are but users, most of whom have never encountered the OP's exact problem, we're relying on years of experience with PrPro (and other NLE's), many different file formats and CODEC's, and all of the reading that we've done on this, and many other fora. In a perfect world, each of us would have the exact system that the OP has, and the exact same file to test with.

Your assistance is appreciated, but I'm not sure that you have contributed anything yet.

The reason for this "false positive" is because of the naming convention used by Adobe, when registering the MainConcept CODEC's. There are probably two reasons for this:

1.) the CS4 "trial" ships with the MPEG CODEC's disabled, due to licensing issues with MainConcept. Adobe would have to pay a royalty to MainConcept for every trial shipped if they were active, and this would cost a great deal of money, that Adobe would have to recoup someplace else, like from my (and your) pocket, when I buy the program. I'd wager that the MainConcept CODEC's install with the trial, but are disabled via code inside of the trial. By using a different naming convention, Adobe can be certain that the trial does not disable any other CODEC's on one's system. Pretty neat, if you think about it. Now, I've never had a trial, so I cannot verify this speculation. Adobe has been rather mum on exactly how they eliminate the MainConcept MPEG CODEC's in the trial.

2.) many programs install their own CODEC's. This can cause many problems. Adobe "protects" its CODEC's by using a slightly different naming convention, so they will NOT be overwritten by some other program. Pretty neat, if you think about it, again.

G-Spot, Sherlock the CODEC Detective, and some others, will throw false-positives for issues, because they are not smart enough to realize what Adobe has done.

I would guess that in your experience, you have not dealt with laptops. Had you done so, you would know more about the proprietary drivers. See, laptops differ from desktops and workstations in more ways, than just size.

One consideration is that when you first started in the industry, I had been in it for over 20 years. I do not claim to know everything, and spend most of my time on these fora to learn even more.

As for Adobe needing to address the MainConcept CODEC's in the trial, well they do. The FAQ's and several KB's point this out clearly. That all people, who download a trial, do not read these is more a testiment to their personal proclivities, than to some deficiency on Adobe's part. How many people have ever read a Read_Me file in any program?

This problem is a licensing issues that Adobe needs to address. Stop

telling people to uninstall drivers when this is clearly not the answer & is

only creating problems not fixing them. You suggest I haven't contributed

anything & trust me if I had the answer I would have given it, but the

answer cannot come from myself nor yourself but Adobe.

As driver issues are very common problems, and drivers can be compromised, or rendered totally obsolete by a simple OS update, you'd be surprised at how many times display issues are fixed by this simple, but overlooked action. If MS issues an update to the OS, that breaks a video driver, I fail to see how Adobe could be held accountable. Maybe I am just missing something. When there are no more driver issues, I will cease to recommend that one updates their Audio and Video drivers. Not likely to happen. Same thing for the reliance on Adobe Flash for installation and the recommendation to get the latest update. Same for the reliance of many NLE's on Apple's QT Player (regardless of what one thinks about anything Apple). When NLE's rely on nothing else, I will cease. Until then, if it works, then maybe you should look beyond it.

If you doubt the validity of most of my recommendations, click my profile. Those "points" come from "right answers." Obviously, I have helped someone along the way. Also, note that the tally of hose points only started with the revamp of the Adobe fora, about 4 mos. ago. Can't tell you that some of those were not plain luck, some total guesses, but some must have been from posting "fixes." Now, enough about me, let's address some of the issues, shall we?

As for the conversion of file formats and CODEC's, I think that Harm Millard hit on this very early on in the thread. As many NLE's are still based closely around a DV-AVI Type II workflow, with emerging support for various HD formats and CODEC's, conversion will likely be with us for at least another 1-2 upgrades of PrPro. My clients hand me all sorts of "off-the-wall" Assets. I have never failed to get these "things" into PrPro, thorugh conversion. Now, I might well hate the quality, but that damage was done before I got my hands onto the footage.

Thank you for sharing your conversion program. I am not familar with it, but then have one that works fine for me, so I do not know most of the others. Mine happens to be a US$50 program, and many wish for a freeware program. Is your's freeware? Eddie Lotter works very hard to keep the PrPro Wiki updated and has several secitons on "conversion." Maybe he can incorporate your suggestion for a conversion program. Also, as new formats/CODEC's are introduced, some older conversion programs may well lack the capability to work with some of the newer stuff. TOD and MOD are fairly recent, and have posed some problems with PrPro and also PE. Any tips on handling those will be greatly appreciated. That info would be a great contribution.

I would purchase immeadiately if someone could show me a path to import into PPro

The issue is that you made a poor camera choice if editing is desired. Those cameras are better suited to the consumer shoot and watch crowd. For editing with a professional NLE, choosing a camera that records to a standard camera format (DVCPRO HD, HDV, AVCHD) should resolve your issue.

I have simply have too much stuff going on, so I had to take a break from this crap. But here is where I am currently at with this issue:

First HP told me that since I have a TouchSmart, The graphics driver is part of the chipset motherboard, and that screwing with it can make my computer permanently not function properly.

So first I thought I was simply out $1200 on this computer, so I was going to go buy a laptop that would have the correct driver already installed. Except get this: about 90% of all the laptops I found have the exact same chipset driver, the Intel(4) Chipset Family.

So I wonder: If so many different laptops have this same driver (and the rest of the system reqs. are compatible with Premiere), then howcome it seems like I am the only person in the world with this problem?... The math does not work there...

But here's another thing. I can simply disable the chipset driver, and when I do this, Premiere Pro works much better (The picture shows up, but the video does not play very smoothly) and also the display settings on my computer are large and distorted, and my computer wont run other applications unless this chipset driver is enabled again. So how am I able to play video on Premiere when my graphics driver is disabled??

Any suggestions? Thanks!

-Rick

(this post has gone on so long I should get a profile picture up or something...)

I have simply have too much stuff going on, so I had to take a break from this crap. But here is where I am currently at with this issue:

First HP told me that since I have a TouchSmart, The graphics driver is part of the chipset motherboard, and that screwing with it can make my computer permanently not function properly.

So first I thought I was simply out $1200 on this computer, so I was going to go buy a laptop that would have the correct driver already installed. Except get this: about 90% of all the laptops I found have the exact same chipset driver, the Intel(4) Chipset Family.

So I wonder: If so many different laptops have this same driver (and the rest of the system reqs. are compatible with Premiere), then howcome it seems like I am the only person in the world with this problem?... The math does not work there...

But here's another thing. I can simply disable the chipset driver, and when I do this, Premiere Pro works much better (The picture shows up, but the video does not play very smoothly) and also the display settings on my computer are large and distorted, and my computer wont run other applications unless this chipset driver is enabled again. So how am I able to play video on Premiere when my graphics driver is disabled??

Any suggestions? Thanks!

-Rick

(this post has gone on so long I should get a profile picture up or something...)

I have no idea if this USB to DVI gadget would work but maybe you could order one from them or some vendor on a trial basis. With the included software you apparently can make it the primary display. Check with them first if it is OpenGL 2.0 compatible. There are also other similar devices for interfaces like ExpressCard.

I do find it weird that this problem has not been addressed, as I meet all of the system requirements, yet no one seems to have any solutions. Just 'guesses'. Have you guys seriously not heard of this problem ever before? These folks who have so many years of experience with this particular program how no idea what can be causing Premiere to not play any video? even though I can play video on everything else?

Sorry Rik - I am too scared of being lambasted by Kris if I dare offer any other solutions or 'guess' solutions. Best to ask Kris why he decided to alienate those posters who genuinely wanted to offer assistance or indeed have offered solutions to you.

Since this thread has been going on so long, it may be a good moment to summarize:

Source material is DV AVI type2 from a Canon GL2. No problem.

PR CS4 has the right codec to edit this source material, nothing needs to done about that.

You have an integrated Intel graphics card that meets CS4 requirements and you need a HP supplied chipset/graphics driver. You have installed, with the help of HP, the latest driver and that did not resolve the issue. Disabling the chipset driver allows PR to run but disables other programs, so that is not a solution. You need the chipset driver loaded.

also the display settings on my computer are large and distorted, and my computer wont run other applications unless this chipset driver is enabled again.

This suggests that the display setup is not correct. That makes sense when the driver is not loaded, but the returning problem with PR when the driver is loaded, suggests that the display settings are causing this problem with the default settings from the driver.

I'm not familiar with the integrated graphics card or the HP driver, so it is rather difficult to suggest anything specific. What may help is running DXDIAG, run all the tests and attach the results in a TXT file.

I apologise if I have cause you any grief here. This Keano character definately has greviance with me but that shouldn't be taken out on you. I think you have to bite the bullet & post a small video online so it can be tested by those who have the experience... I'm not claiming to be that person, as my experience with PP in limited.. My experience with hardware (which drivers are closely associated) is extensive & I'm positive this is not a drive issue. Otherwise, like you've said, everyone from Timbucktoo to the black stump would have experienced these issues with their notebooks, in fact this integrated video driver is not only found on notebooks but many standard intel desktop motherboards also.

I don't eny you Rick as your genuinely asking for help here. Perhaps we should get back to basics without acting like teenage school kids. Step us through the exact steps you are taking to import or are you just playing thru media browser? & definately upload a sample file as without this we dont know what your dealing with.

I do find it weird that this problem has not been addressed, as I meet all of the system requirements, yet no one seems to have any solutions.

I can only guess here, but my first inclination would be:

1.) the HP TouchSmart is fairly new, so not that many have encountered your issue - yet

2.) those that might have, have just not posted here - yet

3.) there is some other issue with your system and the display on your computer

As we're just users, and none here works for either HP, or Adobe, to my knowlege, the answer might only come from an HP forum (though many/most probably do not run PrPro on their TouchSmart rigs), or from someone, who shows up later, with the same equipment and same problem. I know that it doesn't help you, and that is what we've tried to do, but it might just be time, and the right person finding your thread.

I'm not a MOD here, so the idea might get shot down by Jeff, or Jerry.K, but I think that I'd post the exact problem with a title that states the HP TouchSmart model in it. Through the attempts to solve your issue(s), the thread did take some turns, and you have been able to rule out most of the suggestions as not applying to your situation. With the right title, there would be greater likelihood that an HP TouchSmart user with PrPro would see it, and join in. I'd add a link back to this discussion, so that newcomers would be able to track all that you have tried, with no success.

Good luck, and sorry that most of the suggestions did not work for you. Bound to be some way to get it all working together. I'm just out of ideas.

Hi Rick, I've just been in another forum that sounds very similar to yours. I'm also using HP laptops that are doing the same thing. Intel chipsets etc. Can you tell me how much ram you have for dedicated video?

Just asking because the laptops that work for me have over 512mb and the ones that aren't have less, and there is very little difference between the machines otherwise. I'm trying to get a techie to unlock the bios for me (stupid user restrictions) so I can change the amount of allocated ram (if it allows me to). I'll post my findings here too.

Rick, I experienced something similar that happened with you (black video/only audio) in premiere CS4. I'm using now Windows 7 RTM. When I was using the RC1 release, premiere worked just fine. But seems the driver that the new version has installed messed -up the things. After many trial and error, with codecs, drivers, I discovered a driver for intel g965 that works with windows 7 and premiere. Is the version 15.9.64.1472 for windows vista x64. Now everything works! Hope it helps. If you want this driver, you could ask me for a link, then I'll upload it.

the driver is here. However, since the driver is from a previous version, windows try everytime to updates this. These annoying messages really are boring me. So, I've trying a way to use the last updated driver with same configuration of this old one (that works!). What I discovered is that if you extract the archive that I'm sending to you, will be there a folder called "Graphics". Inside this folder, there are some .dll files. What I did wast to copy these files do adobe premiere cs4 root directory. Remember that I have updated the Graphics drivers of system. When I started premiere and load a project, surprise, that works! I think that even with a new graphics driver installed, when you copy this .dlls from the old driver to the root of premiere, it assumes and uses those files to acess graphics functions. Now I'll try, one by one of the .dll to discovery which file is the essencial for this.

Hi guys, I've had a breakthrough now on the HP's that weren't working under XP. Again, it is a driver issue for the intel graphics chipset. from my testing, things seem to be working fine (and I have a giant smile on my face as my 150+ laptops can now be used). I rolled the drivers back to version 6.14.10.4957 and all is well with the world. Thought I'd share as there are still many people out there with the problem.

Wow! I am really happy now! Im glad this isnt a hardware issue. Sometimes the newer things are the less compatible lol. It worked! I downgraded to driver. I assure you that this thread has been the only one to provide the answer! Gotta love the internet.

I am trying to import video and get an error message stating it's an unsupported Format or damaged file (which isn't the case as it works just fine with Movie Maker. Adobe TS made me install CODEC's from some free site when i was using Premiere elements a month ago before switching to Pro which when i originally downloaded it it worked w/o a hitch-no changes to my system. i did update my graphics cards ATI Radeon 5770 but it was doing this before the update. i so far behind on this project due to serious issues with Adobe; the big one was just resolved but now some minor issues are in the way. this is for my sons school and his wrestling team-i've missed the awards dinner and am missing all deadlines so i must get it done. any help would greatly be appreciated, the files range from AVCHD to MOD.

Also, take a look at this ARTICLE. I know that you are not working with AVI, but it discusses file format "wrappers," and will give you tips on gathering up the full details of these files. Where you should pay special attention is the info that G-Spot will give you. Also, part of what it does is survey one's system for installed CODEC's. Those can also be seen from Tables (in the Toolbar). Do not be alarmed if it tells you that the Adobe MainConcept CODEC's have a problem, as that is a false-positive, due to Adobe's naming convention to protect and hide their CODEC's so that they do not get overwritten.

Adobe TS made me install CODEC's from some free site when i was using Premiere elements a month ago before switching to Pro which when i originally downloaded it it worked w/o a hitch-no changes to my system.

Which CODEC's did T/S instruct you to install? Was it a CODEC "pack," like K-Lite? Did you also install FFDShow, which is included? If so, do you still have that installed? FFDShow has caused no end to grief with Adobe programs. It is also very difficult to remove completely. I would not let it within a mile of any of my computers. However, I feel the exact same way about CODEC packs, as they usually cause more problems, than they have ever solved.

Right now, I am leaning toward your CS4 "reverting" to the "trial" version, because both MOD and AVCHD are MPEG variations, and the "trial" version will not support ANYTHING MPEG.