[closed] VE and/or Overlay module lock in 1.04

[wiav8r]

Mike
Anyone reported VE or Overlay module lock ups when using multiples while streaming and recording?

I had 2 lock ups that were cleared by removing all the overlay and VE modules I had running (2 Overlay and 2 VE for queuing). Then got control back. Did this fix in 1.05? When it would lock I would loose all control via the drop-downs and other functions.

Like I said as soon as removed all the Overlays and VE modules I got control back and then could reload and reset modules. Happened 2 times.

I may go back to 1.0 till next release out. I just don't have the time during my broadcasts to fix these error when they pop up and m6y operators just freeze and walk away.

[Mike]

No problems were reported. I appreciate you don't have time to work out potential bugs, but please realize you may have to use v1.0 for the rest of your life :)

Anyone else been having problems with 1.01+?

[Mike]

Closing this topic.

[wiav8r]

Ok So Im the only one with this in 1.05. I will be watching in 1.06. I tried 1.05 but you saw the oteher problem I had with that so i cant use 1.05 or 1.03. I guess ill go back to 1.02 so i can keep the native stream.

I did have this happen again last Sunday running 1.04 . I was using VE side by side 3D using player 1 with a solid background. Complete lockup. I reved all my VE and overlays and got program and preview back and was able to save my recording that way

[wiav8r]

Need a copy of my profile to test this?

[Mike]

Sure, email or PM me. But if you can't reproduce it in any way on another machine and no one else sees this problem, it is very unlikely I will. It would be a lot more helpful if you can reproduce this with a minimum setup, and let me know what makes it go away (other than removing a bunch of modules, which is rather drastic). Maybe you can remember changing anything in your profile after v1.02 that might (indirectly) cause this?

[wiav8r]

Sure, email or PM me. But if you can't reproduce it in any way on another machine and no one else sees this problem, it is very unlikely I will. It would be a lot more helpful if you can reproduce this with a minimum setup, and let me know what makes it go away (other than removing a bunch of modules, which is rather drastic). Maybe you can remember changing anything in your profile after v1.02 that might (indirectly) cause this?


I will go out to my production machine and try some things tonight and see if can duplicate with some test profiles and let you know and will send copies of them along.

I have not changed a thing in my production profile except the native stream settings on the streamer and those worked in 1.02. since i have problem with 1.05 preview cant test in that

I will start at 1.04 and go backward. I will skip 1.03 as that has same problem as 1.05 and is unusable for me without preview module

[wiav8r]

Sure, email or PM me. But if you can't reproduce it in any way on another machine and no one else sees this problem, it is very unlikely I will. It would be a lot more helpful if you can reproduce this with a minimum setup, and let me know what makes it go away (other than removing a bunch of modules, which is rather drastic). Maybe you can remember changing anything in your profile after v1.02 that might (indirectly) cause this?


I will go out to my production machine and try some things tonight and see if can duplicate with some test profiles and let you know and will send copies of them along.

I have not changed a thing in my production profile except the native stream settings on the streamer and those worked in 1.02. since i have problem with 1.05 preview cant test in that

I will start at 1.04 and go backward. I will skip 1.03 as that has same problem as 1.05 and is unusable for me without preview module


Update-- I am now back to ver 1.04 and made a couple of changes and no lock-up since. maybe my system. I discovered I really don't need 2 VE modules at the same time, I have reduced my profile down to 1 and I run a couple extra overlays instead and seems to be working fine.

Thanks Mike

[djWHEAT]

For the record, I still experience this in 1.07. Thankfully Allan's workaround works and I have not had to END TASK Vidblaster at all lately (that was previously the only way I knew how to fix it).

Maybe when I upgrade to 1.08 this weekend I'll completely remake my profiles. See if that makes any difference. But I get this at least once or twice during a 2 hour show each time I run production.