[fixed] Vista 64 bit (was: v0.29 load bug & was: 64 bit install quits)

[merdave]

Hi, Mike.

When I'm loading VidBlaster on my Q4, SLI, windows vista ultimate machine, the Progress Bar gets to "Creating streams" and then an error dialog box titled "VidBlaster.exe" says "Abnormal program termination".

There are no cameras connected to the computer. Could that be a problem?

Any ideas what's going on?

dave

[Mike]

Assume that is Creating Streamer? Could be an error in DirectX, part of Windows. Uninstalling certain programs can remove vital files etc. You can check DirectX with utilities like DXDiag, or simply reinstall it. If that does not fix it, get back to me and I can build you a special debug version.

[rstroope]

I ran the install program and as VidBlaster started booting I got this message " Abnormal program termination" . VidBlaster was loading the VidBlaster Overlay.png. That's where it stopped. I'm running Vista 64 bit with SP1. Any ideas as to why this happened. Mike tells me he's testing VidBlaster on a Vista 64 bit machine without any problems? Ron

[merdave]

DirectX 10 checked out OK. I'm running vistax64.

Just ran VidBlaster again and it opens fine now! Very odd.

Thanks for your reply.

dave

[Mike]

I think this has nothing to do with the 64 bit version but is simply a bad install of DirectX, I see this a lot. In fact, even though I am very careful and for the most part know what I'm doing, I had the same thing the other day. I found out a file was missing as it had been removed when I uninstalled a program from a very respectable company. You can try running dxdiag to see if it reports any errors (it did not in my case) and/or reinstall DirectX. In my case, I also had to reinstall Windows Movie Maker.

I will also ask my Vista 64 beta tester to join this thread, he may have some additional pointers just in case it is 64 bit related.

[rstroope]

Mike,

I ran dxdiag and there were no problems reported. However, I noticed that this machine runs DirectX 10. Could that have something to do with it?

[Mike]

No. Note dxdiag does not catch all problems (as in my case). Maybe there are better diagnostic programs that also check for missing files closely related to DX, I've never looked for them.

[Podcaster123]

rstroope,

When I first installed v0.29 I also received the same error during installation. What fixed it for me was to un-install VIDBlaster reboot then I re-installed again. I did this a few times.

If you still receive an error, still start VIDBlaster, accept the error, then choose Camera 1. Close VIDBlaster and when you start VIDBLaster again it should work ok.

[rstroope]

Podcaster123,

I don't have the option to "still startVidBlaster". Once I get the error code that's all it will do. I've installed it several times. Thanks for trying.

rstroope

[Podcaster123]

Sorry about my explanation not beeing too clear... Here is what I mean to say.

1. If you still receive an error during installation, accept the error.
2. If VIDBlaster is still running (if not restart VIDBlaster and accept error), click on the Camera Menu and Select Camera 1.
3. Close VIDBlaster. Re-start VIDBlaster and hopefully it should work.

Please let us know how it helps.

[merdave]

Today, VidBlaster is back to the beginning problem again.

So I downloaded and installed the latest directx at http://www.gamesforwindows.com/en-US/AboutGFW/Pages/DirectX10-a.aspx.
Uninstalled and installed VidBlaster; still the same problem.
Windows Movie Maker 2.6 seems to be working.

I like this program when it's working. I am willing to do what I can to help solve this problem.

dave

[rstroope]

I understand what you are saying but VidBlaster will not open at all. It stops running and locks the machine...

[Mike]

Ron, please send me the log file. Also, did you try reinstalling DX and WMM?

[Mike]

Everyone, I merged 2 topics that both describe vague problems and both have Vista 64 bit in common. For now, I am treating these problems as caused by Vista 64 until I've proven otherwise. Please read each other messages, and send me the log files as I already requested. We'll have to take this on one step at a time.

[merdave]

So this is what I did today:

Uninstalled VidBlaster and went back to v0.16, tried it and when it worked, went to v0.18, etc.

The last version to run without this bug is v0.21; in v0.23 this bug appeared and also is in v0.24.

So it is a good bet that this bug was introduced in the new/changed code for v0.23.

Since v0.23 seems to have been a major revision, the bug may be hard to track down.

One other thing: whenever I was presented with the "ffdshow compatibility manager" dialog from vista, I picked "Use ffdshow (always)".



dave

[Mike]

Thanks. Version 0.23 is a long time ago, but I'll keep it in mind.

You have ffdshow installed on your system? That may be the source of the problems, it's very buggy. And difficult to uninstall :( If it's not the source, it will be a source of problems. See if you can (completely) remove it and try again. Also try v0.30 (soon out) as it puts some more info in the log file.

[Mike]

Oh, still waiting for you current log file. Maybe it gives me an idea and I can include it in the upcoming release (if you're quick).

[merdave]

uninstalled ffdshow; no change.

Mike, are you asking me for a log file or someone else?

If it's me, what the file name?

[Mike]

Are you sure it is uninstalled? I remember doing that once and the codecs were still there.. Not good!

Easiest way to find the log is to click Start|VidBlaster|VidBlaster Log and copy the text.

[merdave]

Mike, here is the current status of VidBlaster on my machine.

I ran a search for "ffdshow" using search and removed all references - files and dir.
Did the search for "VidBlaster" and removed everything except the installer.

Installed VidBlaster on the D: drive.

Worked fine the first time.
But the 2nd time through, I changed from Pro to Home layout and program hung before completing re-display of panels.
Here's the log file for this event:

11:44:41 AM Monitor 0: 1680*1050 0,0
11:44:41 AM TClock::TClock
11:44:42 AM TUpload::TUpload
11:44:42 AM VidBlaster 0.290
11:44:42 AM TMn::TMn
11:44:43 AM QuickTime 7+ found
11:44:43 AM TClock::StopPreview
11:44:43 AM TClock::StopProgram
11:44:43 AM Creating program monitor
11:44:43 AM TMon::TMon
11:44:43 AM Creating graphics overlay
11:44:43 AM Creating audio
11:44:43 AM TAudio::TAudio
11:44:43 AM Creating player 1
11:44:43 AM Creating player 2
11:44:43 AM Creating player 3
11:44:43 AM Creating player 4
11:44:43 AM Creating player 5
11:44:43 AM Creating player 6
11:44:43 AM Creating player 7
11:44:43 AM Creating player 8
11:44:43 AM Creating player 9
11:44:43 AM Creating player 10
11:44:43 AM Creating player 11
11:44:43 AM Creating player 12
11:44:43 AM Creating recorder
11:44:43 AM TRecorder::TRecorder
11:44:43 AM Creating streamer
11:44:43 AM TStreamer::TStreamer
11:44:43 AM TClock::StartProgram
11:44:51 AM TClock::StopPreview
11:44:51 AM TClock::StopProgram
11:44:51 AM Creating program monitor
11:44:51 AM TMon::TMon
11:44:51 AM Creating audio
11:44:51 AM TAudio::TAudio
11:44:51 AM Creating player 1
11:44:51 AM Creating player 2
11:44:51 AM Creating player 3
11:44:51 AM Creating player 4
11:44:51 AM Creating recorder
11:44:51 AM TRecorder::TRecorder

However, I was able to end the task with TaskManager.
Exited and loaded the program several times: it seems to be working normally.


Then I rebooted the computer and started VidBlaster which then displayed the "abnormal program termination" dialog.
Here's the log.

12:10:22 PM Monitor 0: 1680*1050 0,0
12:10:23 PM TClock::TClock
12:10:23 PM TUpload::TUpload
12:10:23 PM VidBlaster 0.290
12:10:23 PM TMn::TMn
12:10:24 PM QuickTime 7+ found
12:10:24 PM TClock::StopPreview
12:10:24 PM TClock::StopProgram
12:10:24 PM Creating program monitor
12:10:25 PM TMon::TMon
12:10:25 PM Creating graphics overlay
12:10:25 PM Creating audio
12:10:25 PM TAudio::TAudio
12:10:25 PM Creating player 1
12:10:25 PM Creating player 2
12:10:25 PM Creating player 3
12:10:25 PM Creating player 4
12:10:25 PM Creating player 5
12:10:25 PM Creating player 6
12:10:25 PM Creating player 7
12:10:25 PM Creating player 8
12:10:25 PM Creating player 9
12:10:25 PM Creating player 10
12:10:25 PM Creating player 11
12:10:25 PM Creating player 12
12:10:25 PM Creating recorder
12:10:25 PM TRecorder::TRecorder
12:10:25 PM Creating streamer
12:10:25 PM TStreamer::TStreamer


Maybe a problem in the creation of the TStreamer object?
Maybe the state of TRecorder is causing a problem for TStreamer creation?


dave

[Mike]

Hi Dave,

No need to remove any of VidBlaster's files, in fact if you want to do that for any reason always use the uninstall function.

The first problem you describe has already been discussed in another topic and will be fixed.

The second one definitely is a Vista 64 bit related problem, but I don't know yet what it is. I made some small changes and added a few extra log calls in upcoming v0.30. Please check if you can cause the problem again, and mail me the log file.

Thanks.

[merdave]

Hi, Mike.

1. Uninstalled v.0.29 and installed v0.30 on the D; drive. Immediately got the "abnormal program terination" dialog.
2. Uninstalled v.0.30 and installed v0.30 on the C; drive. Worked several times but I did't do anything within the program.
3. Rebooted. Got the "abnormal program termination" dialog.

Log:
1:57:11 PM Monitor 0: 1680*1050 0,0
1:57:11 PM TClock::TClock
1:57:12 PM TUpload::TUpload
1:57:12 PM VidBlaster 0.300
1:57:12 PM TMn::TMn
1:57:13 PM QuickTime 7+ found
1:57:13 PM TClock::StopPreview
1:57:13 PM TClock::StopProgram
1:57:13 PM Creating program monitor
1:57:13 PM TMon::TMon
1:57:13 PM Creating graphics overlay
1:57:13 PM TGraphicOverlay::LoadFile
1:57:13 PM TGraphicOverlay::LoadFile End
1:57:13 PM Creating audio
1:57:13 PM TAudio::TAudio
1:57:13 PM Creating player 1
1:57:13 PM Creating player 2
1:57:13 PM Creating player 3
1:57:13 PM Creating player 4
1:57:13 PM Creating player 5
1:57:13 PM Creating player 6
1:57:13 PM Creating player 7
1:57:13 PM Creating player 8
1:57:13 PM Creating player 9
1:57:13 PM Creating player 10
1:57:13 PM Creating player 11
1:57:13 PM Creating player 12
1:57:13 PM Creating recorder
1:57:13 PM TRecorder::TRecorder
1:57:13 PM Creating streamer
1:57:13 PM TStreamer::TStreamer

Is anyone else running x64 having this bug or is it just me?

dave

[Mike]

There is someone else having similar but not the same problem on Vista 64.

Are you saying the program works fine on the C drive, but not on the D drive? Both are Vista 64, or do they have different OSs?

[merdave]

Everything is running on vista x64 ultimate.

VidBlaster runs fine on the C: drive until I reboot; then the bug appears.

[Henley]

hey there,

Im running vista 64x and i get this message once i start up your program

Access violation at address 00452915 in module 'VidBlaster.exe'. Read of address FFFFFFFC.

Any help would be great!

[topic merged by Admin]

[Mike]

Is anyone up for a little test? If so I will make a special VB exe which you need to try under Vista 64 (as I do not own a copy).

[Henley]

yeah ill give it a go

[Mike]

Thanks. Please download a new exe from here (http://vidblaster.com/download/beta/VidBlaster.exe), and overwrite the old one in your VidBlaster folder with this new one. Then try to start the program. If you still get the error, please mail me the log file.

[Henley]

holy shit nice work mate works straight off the bat, maybe you could make a new release?

[Mike]

:)

Actually this tells me in which module the problem lies, I now need to fix it. I'll come back here for another test version shortly.

[Mike]

Can you repeat the procedure? I uploaded a new exe for you.

[Henley]

yeah it works and now the overlay is back, good work.

[Mike]

There's still a small bug (overlay is not visible upon startup) but that will be fixed in the next release. Thanks for your help.

[Henley]

hey just downloaded the new version, and it is having the same problem again.

[Mike]

There is no newer version than I did for you. Check the version number!

[merdave]

Bravo, Mike. 0.37 works! All aspects of audio that I can test work. Can't test video yet; have to wait until I'm finished paying for the audio programs (mixer, sequencer, vsti, etc.) that I've bought before I can start on video.

You definitely have a potential buyer here. Keep up the good work!

Dave

[Mike]

Thanks for letting me know Dave :)