Scheduled Program C...
 
Notifications
Clear all

Scheduled Program Crashing

18 Posts
7 Users
0 Reactions
4,450 Views
Posts: 57
Topic starter
(@jwilliams31)
Estimable Member
Joined: 18 years ago
[#9591]

I'm trying to run a scheduled program. It runs fine for awhile and then it fails with a COM error (see attached).

This happens whether I have my background sequence enabled or not.

This is happening on 2.1.4.

Thanks.

Jason

vixen error 2

17 Replies
RichF
Posts: 1356
(@richf)
Noble Member
Joined: 19 years ago

Check to make sure your sequences do not overlap.

Also if you can remove the plugins from each sequence and set up the program to use its own plug ins or use a profile.


Reply
Posts: 57
Topic starter
(@jwilliams31)
Estimable Member
Joined: 18 years ago

The program and all of the sequences were created using a profile. I will double check, but none of the sequences should have any plugins attached to them.

Also, how would I know if they overlap? I have 7 sequences all within one program and I set the program to wait 5 seconds between sequences.


Reply
RichF
Posts: 1356
(@richf)
Noble Member
Joined: 19 years ago

So you have selected 7 seconds of cross fade?

Or do you have a blank 5 sec sequence between each


Reply
Posts: 300
(@kiowamike)
Reputable Member
Joined: 18 years ago

I too am having similar problems, and a few questions. BTW I am using 2.5.0.
1. should the sequences be attached to the profile?
2. should I use the profile for program execution or the program plugin setup?
3 I am also running an LED Triks with current execution through the parallel port. The first two nights I had the show running without the Triks and no crashing. Then I added the Triks and started crashing. Also my comp seems to get hotter when the Triks is plugged in as the chassis fan kicks on often.

I currently have the program executing with the profile rather than the program set up and all the sequences have the profile attached to it.
Thanks,
Mike


Reply
Posts: 300
(@kiowamike)
Reputable Member
Joined: 18 years ago

And
4. could the parallel port be causing the program to crash?


Reply
Posts: 57
Topic starter
(@jwilliams31)
Estimable Member
Joined: 18 years ago

I'm using a 5 second cross-fade within the program. I'm not using blank sequences (should I be?).

I'm also using a USB DMX dongle, if it makes a difference.

Thanks.


Reply
Posts: 393
(@rkhanso)
Reputable Member
Joined: 18 years ago

Do you have 2 instances of Vixen running? Check the Windows Task manager and kill ALL the instances of Vixen. Then start it up again. I had this problem, but am not using DMX - so I don't know if it's the same solution.....but try it.

For me, there were 2 instances of vixen running because the previous one did not shut down properly and still had control of the com port. When the second one started up (the one I was trying to run the show with), it couldn't get access to the com port.
---------------------------------
Ignore this...I mis-interpreted your question.


Reply
cbell
Posts: 462
(@cbell)
Honorable Member
Joined: 18 years ago
jwilliams31 wrote:I'm using a 5 second cross-fade within the program. I'm not using blank sequences (should I be?).

I'm also using a USB DMX dongle, if it makes a difference.

Thanks.

I was under the impression that cross fading hasn't worked in a couple of versions. If you set it to zero, do you still get the crashes.


Reply
Posts: 57
Topic starter
(@jwilliams31)
Estimable Member
Joined: 18 years ago
I was under the impression that cross fading hasn't worked in a couple of versions. If you set it to zero, do you still get the crashes.

I did not know this. Ok, I set the crossfade to 0 and it seems to be working OK now.

Is there a way that I can make sure there is a few seconds of "quiet time" in between sequences in the program? There are a few extra seconds at the end of each sequence, but I just didn't want it to roll from one song right into the next. I thought a dramatic pause would be nice.

Thanks.

Jason


Reply
Page 1 / 2
Share: