Alan Kushnir
Forum Replies Created
-
ok thanks. What I see now is that if the trimmer is open, it is previewed there, but if I close the trimmer, then the clip auto previews in the preview window. I’m guessing that in the past, I always had the trimmer closed when I was browsing clips in the explorer.
Anyway, thanks for the feedback it helped.
Alan -
Correction : I am getting audio; just no video.
Alan -
Thanks it worked. Downdated the driver and all is good now..
Alan -
I solved my own issue and maybe this will help someone else.
Right click on the vegas icon and choose “Troubleshoot compatibility”.
You get two choices; choose the “Troubleshoot Program” option.
You can then choose the version of Windows where Vegas worked for you. I picked XP SP3. Problem seems solved. No longer hangs on the Directx initialization.
Alan -
Thanks for the suggestions and input. I appreciate it. I’m away for a few days but will try some new things over the weekend and update on this thread.
Alan -
Thanks I knew it was something really silly.
Alan -
Thanks. I tried to find the setting in preferences but it eluded me, probably because it was late at night.
alan -
The clip was actually an ‘mp4’ NOT ‘mpg’. It was created by nero.
Sorry for the misinformation.
In any case I dropped it on Gspot, and the codec indicates ‘mp4v’.
I made sure again this clip plays in Win Media Player 11 and Nero Showtime but only the audio comes into Vegas 8.0
Is there anything else in the Gspot info you would like to know?
thanks for any help.
Alan -
>>And now for more information than you ever wanted to know:
Edward,
No, its not more. I also found on my system the two versions of twain_32.dll, and replaced the old one (dated 1996) with the new (smaller) one (2004).
This seems to be the real problem, because notwithstanding my renaming the “wowexec.exe” file, windows went and re-created it and it again starts up. But now, vegas has no problems starting even though wow is running.
I do appreciate greatly the references to the 2004 thread where this same problem was originally worked through.
I hope this thread helps somebody else solve this in the future.
Thanks again.
Alan -
Edward,
Wow. I am duly impressed. Thank you.
There was a process running called “wowexec.exe”. As soon as I killed it, Vegas starts up. I renamed the “wowexec” file, and now the issue is resolved.
Thanks so much.
My curiosity is working overdrive right now. Can I ask how you knew this, ie the specific file name? I guessed it was caused by something left behind after Vegas exited, but why should Vegas have initiated “wowexec.exe” in the first place? What application put “wowexec” in my system?
thanks again.
Alan