PDA

View Full Version : [fixed] Studio crashes when using Effects module


wiav8r
24 Apr 2009, 03:00
Mike I have a new one for you.
My VB Studio crashes when using Effects module. If I load PiP fixed aspect, it causes crash. It doesn't have to be active or selected to do this just have any of the drop down options loaded. Tried on v.45, 46, and 47. Happens with ext mon on or off, recorder on or off, streamer on or off. FME running or not and sometimes doesn't crash until cut or trans but sometimes just sitting there loaded. I tried it with several different profiles and it happened when I was running full frame. I found it by using the auto-switcher(works great by the way) and used and camcorder and shot the screen the old fashioned way and went to dinner. Came back and it was frozen about 13 min into 1 hr recording on camcorder. At first sign of crash the streamer stops. If try to restart VB stops responding and get hourglass and task manager says "Not responding" I saved some screen shots if you need them. Log file just stops and then resets when restart.

The good news is if I clear the effects module or just remove it completely, Crashing stops. So for now I am up and running without it.

Let me know if yo need some screen caps. Everything else is working great!

I loves VidBlaster!

Mike
24 Apr 2009, 06:58
To exclude some other factors, can you please make a test profile (which you can later recall) with just 2 Camera modules, one Program and one VE module. Do this by loading the HomeStreamer profile and removing/adding, that way I am sure all options are on their default setting. In both camera modules select Screen Capture and choose a 1:1 area where at least one of the modules shows the time. In the VE module, select PiP and both cameras, and click Cut to it will show up in Program. Now leave it running and see how long it takes to hang, then send me a screen shot. Don't forget to save this profile for later testing.

One more thing.. If you are testing unmanned, make sure power saving does not kick in. This could be a CPU throttle down (which basically creates an overload), attempt to shut down or sleep the PC, or a monitor off (which I have seen can cause problems when doing screen capture on certain video cards). So make sure all power saving features are disabled.

Mike
24 Apr 2009, 15:25
PS: I've run this test myself today on 4 different PCs for 8 hours straight and had no problems.

wiav8r
24 Apr 2009, 16:42
To exclude some other factors, can you please make a test profile (which you can later recall) with just 2 Camera modules, one Program and one VE module. Do this by loading the HomeStreamer profile and removing/adding, that way I am sure all options are on their default setting. In both camera modules select Screen Capture and choose a 1:1 area where at least one of the modules shows the time. In the VE module, select PiP and both cameras, and click Cut to it will show up in Program. Now leave it running and see how long it takes to hang, then send me a screen shot. Don't forget to save this profile for later testing.


Mike do you want screen cap of this? or ustream stream recording? Home streamer doesnt load recorder does it?

Want me to uses auto switcher between 2 cams and VE? Wait! Never mind, home streamer doesnt use switcher

BTW I never use screen cap for my shows so that will be new.

What is best way to capture lof file? before fault?. during fault? or after fault?

Mike
24 Apr 2009, 16:49
I think you should reread my suggestion ???

wiav8r
24 Apr 2009, 17:51
I got it Mike.

Static PiP with no streaming and send you a screen cap after overnight. I can do that.

Or will 4 or 5 hours be enough? I am 15 miles away from that PC right now and wont get there till after 4 PM. I will set up and leave it till Saturday after 4 PM

Mike
25 Apr 2009, 12:00
By cross correlating your info with that of Roland who reported a similar problem by email, I have managed to recreate the problem. So far it looks like it is local to the VE module and happens only during a cut or transition. Also, I can only make it happen when running 640*480, but that may be timing related. Another factor is that it only happens in the release version (which is all you have access to).

wiav8r
25 Apr 2009, 18:46
By cross correlating your info with that of Roland who reported a similar problem by email, I have managed to recreate the problem. So far it looks like it is local to the VE module and happens only during a cut or transition. Also, I can only make it happen when running 640*480, but that may be timing related. Another factor is that it only happens in the release version (which is all you have access to).


Thanks Mike
Yes I run 640 by 480. and would experience the problem during a cut or trans.

My test is still running with profile you suggested . Last time I checked last night was into 4 hours without problem. But I left it run and will recheck today 4-25-09 after 4:30 pm CDT and let you know.

Again thanks Mike for your vigilance!

wiav8r
26 Apr 2009, 16:31
To exclude some other factors, can you please make a test profile (which you can later recall) with just 2 Camera modules, one Program and one VE module. Do this by loading the HomeStreamer profile and removing/adding, that way I am sure all options are on their default setting. In both camera modules select Screen Capture and choose a 1:1 area where at least one of the modules shows the time. In the VE module, select PiP and both cameras, and click Cut to it will show up in Program. Now leave it running and see how long it takes to hang, then send me a screen shot. Don't forget to save this profile for later testing.


My test results for "test" profile. No lockups in 5 hours. I dont have any data after that as I had a power failure and PC was shut down when I cam back to check it on Saturday. Friday after 5 hours was still running.

What is next step?

I ran a stream today with everything except VE module loaded and ran fine today.

Again Thanks Mike

Mike
26 Apr 2009, 17:56
If possible I'd like you to continue using the program without VE module loaded, just to confirm there are no other problems at your end.

wiav8r
28 Apr 2009, 19:20
I was able to stream and record 640X480 fault free on Sunday 4-26-09. Here (http://bit.ly/mC0Cf) is the result. 

Just in case you are wondering I use audacity for the audio podcast.

blueridgebruce
28 Apr 2009, 21:55
Great job Allen... gotta love it when it all works right and Mr. Murphy stays away. LOL

Mike
29 Apr 2009, 08:13
Found the bug. It will be fixed in the next release.

wiav8r
08 May 2009, 02:33
Appears fixed Mike

But I will confirm on next broadcast on Sunday @ http://1goodshepherd.org/live

wiav8r
11 May 2009, 12:41
Appears fixed Mike

But I will confirm on next broadcast on Sunday @ http://1goodshepherd.org/live


I am confirming all fixed Mike. I streamed and recorded 2 services on 5-10-09 almost 2 hours worth witout a single hitch! 4 cams. 2 VE. 2 overlay and 2 players. PERFECT!

I LOVE VidBlaster!

Mike
11 May 2009, 12:42
Thanks for letting me know Allan. Looks like Friday is a go!

Mike
12 May 2009, 08:21
BTW: when you say recorded you mean via the external monitor option, right? I.e. you do not use the Recorder module? I know it's possible to stream and record simultaneously (and I designed it as such), but officially it's still an undocumented feature and it's on my list to look into.

wiav8r
12 May 2009, 13:08
Mike
Yes I did use the recorder module(WMV) and the streamer and the external monitor function! They work great now. luckily I have the CPU and memory to handle it. I don't think it would work with a duel core or less than 4 gb ram. The highest CPU usage I am seeing is about 37%

Works perfectly now!

Mike
12 May 2009, 13:50
Thanks, good to know. You have a setup many will want to copy. How can I get you to do a making-of video? Nothing fancy, just the basic tech description of what you use and how you connected everything. Or do you know anyone in your area that can do it (I'll pay him), if that's okay with you of course. It would be terrific pr for you, but I realize that means little in your case :)