First, thank you for a very well-written post. Nicely done.
Back to your G-Spot screen-shot, if you look in the lower-left of that screen, there is a matix of buttons. Under Vid and Aud, # 1 is active. Hit each of those, with the file in G-Spot. You should then get the other buttons become active. Hit those, as they become active. Report (probably a screen-cap, if you get any/many errors) on what happens. The last step is to play the rendered file in the little G-Spot player window, that you will see, when you have fully rendered the file.
Everything else looks good, with only one question. You state that you have the latest nVidia driver. Is that per the nVidia Web site, or from Windows, or a driver utility?
Thanks for your quick replies.
I ran Gspot on the .avi file as suggested and clicked on "1" under Gspot Vid.
I think it looks fine, so I pushed button "2"
That seemed fine (to me) as well. So I forged ahead and pushed "3".
Gspot crashed. I repeated it with the same results several times and with different files.
Under "MS A/V" everything worked fine and I was able to view the video with no problem.
I then copied the .avi file to my c: drive and the results were identical.
I tried a new project in Elements and results again were identical.
I installed the latest
Nvidia driver from the Nvidia website.
Any other ideas?
How do I look at the file? It's one of many files that I have on my system that seemed fine before.
Lets assume I have an improper or damaged Codec. In my case the codec name is "DVC/DV Video"
Can I unistall it and re-install? Any help doing this?
As far as looking at the system, I have no idea what to look at.
Let me explain what I'm trying to do: I have a ton of 8MM tapes that were all recorded on my Cannon Optura 300. I simply want to transfer the video's to my hard drive. Maybe some minimal editing to eliminate blanks, or times when I left the camera running unknowingly.
It seems to me I have pretty mainstream equipment, video Camera, PC, operating system and highly recommended SW. Yet it seems to be a massively complex and frustrating task. Am I missing something?
What are your Win7 compatibility settings for this old(er) program?
If you have Win7 64bit PRO or higher, try Microsoft's Virtual XP
This is only ONE example of using Virtual XP http://forums.adobe.com/thread/702693
I've run Elements in XP mode with identical results.
I've run as admin,
I've used the windows troubleshooting to try and solve compatibility issues with no results.
I'm really getting frustrated.
I can't imagine a more basic task with more mainstream equipment and yet I can't get it to work.
What is your opinion? Am I trying to do something unreasonable?
All I can do is echo Bill Hunt... if GSpot is crashing, you may have a system problem
In a case like this what **I** would do is make a copy of all my files to a USB drive, then DE-activate everything and WIPE the hard drive and start over by installling everything fresh, from Win7 on up
Before wiping, I would make a boot drive image... to be able to go back to where you are as a last resort
The product I use is at http://www.terabyteunlimited.com/image-for-linux.htm
Image runs off of a bootable CD via Linux (the Zip you download includes a program to
make the bootable CD) and it reads EVERYTHING on the drive, even the hidden
registration information, so everything is restored when needed... and you may restore
the image to a brand new drive in case of a crash, and not have to re-install anything
Please note that I own no part of Image, and I don't get a referral fee (that is just a
plain web link) but I use the program and it has saved me a LOT of trouble when I had a
hard drive die... and I was able to restore everything and not have to re-install or
re-activate a single program, from Windows on up
The irony is that this is a fresh install. My SSD crashed and I've just installed a new
OS and a few other programs, but my system is really clean right now. While I love the speed of my SSD it is the third one I've had and I was looking for a program like you mentioned above to make a system image in eventuality of another SSD failure. I guess I will try again.
If I was on a third SSD (I presume both previous ones crashed) I think I would give long thought to not using that type of device
Now, that makes me wonder if something about your SSD drive is the cause of your problems
Do be aware that the drive imaging program I use will NOT do a restore to a different size drive
My first SSD performed well but it was pretty small so I upgraded it. The second one crashed so I replaced it, so I've really only had one failure. I'm running SSD's on 3 desktops and 1 laptop. They are so fast that it would be pretty hard to go back to a spinning drive for my apps. PE 8.0 worked fine on my previous SSD so I doubt the actual drive is the issue. It would be pretty easy to test.
I find it curious that only my Adobe product doesn't work. I have two other Video editing programs that can read the 8mm videos just fine. I know your answer will be, "just use them" , but there are several other features of PE that I would like to use, and having purchased the SW I feel it should handle task like I'm having trouble with.
I all honesty the amount of grief that I have suffered because of my SSD is a tiny fraction of the amount of grief I have suffered using Adobe products.
Have you any message about 'incompatibility driver' when Premiere Elements start ?
You could search in this forum on these keywords. One method I use is to delete the
file named 'BadDrivers.txt' in ProgramData/Adobe/PremiereElements/9.0 (my release
number), and restarting PREL works well.
I use this method sometimes on my Vista laptop. Seems apparently linked to
Windows updates generating trouble on graphic drivers.
JM from France
I continue to try all the above suggestions and my troubles continue.
I reinstalled Windows 7 from the original DVD, and reinstalled PE8.
I plug in my Cannon optura 300 and the drivers install without problems. (As far as the dialogues go).
I start a new project in PE8 and get media "Microsoft DV Camera". The video seems to capture fine.
When I try and preview the video on the Timeline or Sceneline the Video is frozen but audio is fine.
If I use my mouse to drag the time bar the video changes properly.
Here is the analysis from Gspot
So the files seems fine and the only app that is having problems is PE8.
Please continue to send your suggestions.
I can understand your frustration.
With SD material, using the DV/DVC CODEC, your equipment should play and edit those files with ease.
It looks like your Seagate is 7200 RPM, and with SD material, the I/O is the main weak point, but you have 7200 RPM, which is just fine - a 5400 RPM could be a problem. Only thing that I can think of here is the connection (assume SATA), and its setting in the BIOS. Go to Setup from bootup (key/key combo can differ per the actual BIOS), and check there, that the Seagate is properly set up.
This might have been stated above, and I just missed it, so humor me. I assume that you have an NTSC 720 x 480 Project, into which you are Capturing your footage. Is that correct?
When you drag those Captured Clips to the Timeline, you should NOT have a red line above any, until you do something like use an overlay of some type, or add/adjust an Effect. Do you initially get a red line? You should not.
With your computer, if all things are set up properly, and updated to latest, you should NOT have any playback problems.
I do not think that I posted this link yet, but if so, ignore. See this article: http://forums.adobe.com/thread/792580?tstart=0
It starts with a general checklist for getting PrE set up and running best. It then goes into a section on tuning up one's system and the OS. Last, is an extensive troubleshooting section, with links to other articles, and to tools to check, or fix things. Might be something that we are all just missing.
Good luck, and please report,
I am unable to find a Baddrivers.txt anywhere on my system
My Project is NTSC 720X480
PE8 is installed on a OCZ SATA 3 SSD.
All of the temp files and data files are located on a Seagate 7200 which has been defragmented and has plenty of space. Im not sure how you can tell if it is installed properly. In the BIOS the only settings I can find is the "SATA MODE" which is set to AHCI.
There are no red lines on any of the clips.
I've been through the article you suggested and completed every step with no success.
Another update, another Failure.
I uninstalled PE8 from my SSD and re-installed it on one of my Seagage 7200 drives.
I started a new project, captured a small amount of video from my Cannon optura 300 and low and behold I was able to preview the video. I thought my problem was solved.
So, I captured the rest of the video. (Same everything).
Went to preview it and the Video was frozen...just like before.
Normally, this baddrivers.txt file is located somewhere in an Adobe directory. In Vista it is located in
Program Data, I don't know where it is for Win 7.
I have read the exact location under Win7 somewhere in this forum, 2 or 3 months ago.
You could try a keyword search in this forum with 'display driver' to find the discussion related.
I just have swithched to a new laptop Win7, my Vista one having a fatal mother board issue..
To have access to this Baddrivers.txt file, I had to use Steve's FAQ discussion : you need to
have access to the hiden files, then the folder 'program data' is visible, unless you can't see it.
That was my case with the brand new PC.
I have confirmed that my folder options are set to display hidden files. This is one of the first things I do when I install a version of Windows.
Here is a snapshot of my PE8 directory.
As you can see there is NO evidence of a Baddrivers.txt file. I've searched, and searched and searched using every combination of "Baddrivers.txt", and using 3 different engines with no evidence of that file or anything like it. It is not there!
Is it a file that only gets generated when a bad driver is detected, or should it always be there?
If so, any idea why I don't get that file showing up?
It might take a reply directly from Adobe, but it is MY understanding that it ONLY gets generated, when PrE encounters a bad, misbehaving, video driver, and that it is NOT generated under any other circumstances.
With the "video driver errors," one needs to do two things: update the video driver to the latest from the mfgr's. Web site, and then Delete the BadDrivers.TXT file.
Maybe others will have some more specific observations, and prove me wrong.
Bill, I encountered this issue without having modified anything in the display driver area...
And, with using the delete method only I obtained the return to the normal running of PREL.
I had this problem 2 or 3 times in the last 18 months, and this solution worked fine everytime.
As suggested by Steve Grisetti, it is suspected to windows updates in some drivers area,
only suppositions of course.
For Nuttu : when I change my rights to see hidden files, the program data folder becomes
visible, apart from the program files I can see in your screen, otherwise I can't see it.
And the baddrivers.txt file is in this 'program data' folder.
This file always exists, and if you read the content, you will find 'TRUE' or 'FALSE', depending
on the driver issue situation : I think it is a software switch used by PREL at start.
I don't know why you seem not to have access to this folder, but I can assure I had to unlock the
access to hidden to see it. I am a new Win7 user coming from Vista, I can't help you more.
As you can see I've been battling this issue for almost a month. I have put many many hours into trying to solve the issue.
I thank all of you for your suggestions and help.
Here is a recap:
I have one problem, albiet a serious one. The Video is frozein whenever I play it the preview screen, or from the timeline.
If I use the mouse to drag the timeline indicator the video moves appropriately.
Here is what I have done:
Implemeneted every item on the suggestion list for tuning PE8 and my PC.
Completely reinstalled Windows 7 from scratch and PR8.
Uninstalled PR8 from my SSD and installed it on a Seagate 7200
Here is what I know:
The media seems fine as evidenced from Gspot.
There is no evidence of a baddriver.txt directory.
Is there anything else anyone can think of? Is there anyway to contact Adobe for their help?
Is it time to move on and buy another program?
Past frustrated and moved on to resigned....
There is no Baddrivers.txt directory, it is a single file located in C/Program Data/Adobe/...
I suggest you try to have access to this directory which is hidden apparently for you,
by using Steve Grisetti link. Then you coud try to delete this file and see if
It took me several days, the first time I had this problem, to find the solution.
You can contact Adobe support on their site, I used recently a chat with a support
engineer with success to solve a re-install issue.
There is definitely not a file Baddrivers.txt anywhere on my computer!!!
I've searched with various search engines (which find hidden files), and there is nothing even close to that name. I suspect the file only gets created when a bad driver is detected. I really don't think this is my problem. Is it worth trying to contact Adobe support? I suspect I will be faced with many more hours of debugging, and I also suspect their response time will be slow compared to anything on here.
I think it's time to move on.
I just can't imagine how Adobe can get the reviews it recieves. I've yet to complete (or begin) a project using PE8 inspite of a massive effort.
Thanks for all you help.
Unfortunately, as what you describe is not a common complaint, there seems to be an issue, unique to your computer. You did try a new Project, with different Assets, that matched that new Project, with the same results, didn't you? With a unique situation, it can be tough to pinpoint the cause.
I have exhausted everything that I can think of, to no avail. I only hope that someone else has something helpful to add. I can say that PrE 8 was the most maligned version, that I can recall. Even with the updates (rare for PrE), some users never really got it working smoothly. Not sure what all the issues were, but it present headaches for many. For them, the final "fix" was to update to PrE 9, which seems to have been a good version. Same for PrE 10.
Good luck, and only wish that I had other suggestions,
As suggested by Steve Grisetti, it is suspected to windows updates in some drivers area, only suppositions of course.
As for video drivers being rendered obsolete by an OS update, or even a hot-fix, that is quite common. I have my Windows Update setting to full-manual, with only notification. That way, I know exactly what has been updated, and when. Then, I can plan on possibly heading to the nVidia Web site, to get a new video driver, if anything begins to not function properly.
I also will update my audio driver, at the same time.
Personally, though I recommend video (and audio) driver updates often, those recs. are when something ceases to work. I only update my drivers, when I encounter a problem. I do not do so monthly.
As I continue to debug my problem I thought I would try different IEEE cables. I serendipitously hit play on my preview screen while my camera was unplugged and........VOILA....the video played fine. I plug the IEEE back into the camera and the video freezes and the frozen image on my preview window ALSO appears on my video camera display. Does that make any sense???
On to another issue. When capturing my video I have deselected "auto analyzer", and yet when the capture is complete it attemps to "auto analyze". It hangs and I must manually cancel the process. It also leaves a process running on my computer that I must manually kill.
I HATE that "auto analyzer" both in PrE, and PS elements. It is the worst thing Adobe has ever done! Is there anyway to disable it forever, and ever?