SuperFreak3
I run version 2.1.4.0, there should not be any differences in C# scripting between Vixen versions.
The FADE for the BGS is set to slowly transition between a BGS and a Program/Show
The FADE for background music "should" be set to the same time as the BGS fade to avoid any confusion or issues.
I just dont understand WHY people are spending so much time creating complex scripts when they could use a sequence without music but with a voice recording announcing some tech facts about the display and your display times.
Step back, you have about 10 more months to tinker and toy with Vixen and its features. Figure out what each does and whether you need them.
Post what you already have for a BGS script and I'm sure many here will assist you in learning how to make the script do what you want.
Here is a start for you
void Start() {
//turn all lights off
Off(All);
//define your channel collections to make scripting easier
ChannelCollection MegaRed;
//now define what channels from your current profile or sequence is used in the collection
MegaRed= Channels(Mega1_Red,Mega2_Red,Mega3_Red);
//Mega1_Red,Mega2_Red etc are MY channel names, change them to match yours
//Turns a group ON and at which intensity
On (MegaRed, At(50)); //this is 50% intensity
//Turns off this group
Off(MegaRed);
//Ramp (Channel, start intensity, stop intensity, over a period of seconds, wait for it to happen before continuing
Ramp(MegaRed, 0,75, Over(8).Seconds, Wait);
Ramp(MegaRed, 75, 0, Over(8).Seconds, Wait);
//the above will start out off, and over 8 seconds increase its intensity to 75%.
//then it reverses from 75% to 0 over another 8 seconds.
// so you end up with a ramp on and ramp off from 0% to 75% and back to 0% over a period of 16 seconds.
}
Play with this script and see what happens.
Thanks A99!
A silent Vixen sequence, that is what I was using for background lighting for the past two years. Year one I was fine, but this year I was experiencing messages indicating something about a null object. It ocurred sporadically and its further explained in other posts, but I was trying to rule out the use of this sequence during downtime as a possible cause of the errors. It did not prove to be the case or I don't think it was the cause.
I don't want a very complex script, just something to turn the lights off and on basically between Program runs. As I've said, the only complexity would be the use of different color/channel configurations based on the times the BGS runs. I could live without that though.
I may still use the Vixen sequence as a filler this year, but I thought I'd give the scripts a try. If it turns out to be a pain, I'll go the route you suggest.
Thanks for the sample script. I'll give that a whirl.
Quick question, on the Ren24, what channels are the two LEDs associated with, 2 & 5? I'll use one channel for my show channel and one for my background testing.
Thanks Again!
I've been playing with Vixen (2.1.4.0) for many months now and am hoping someone can clear this up for me...
I've got 4 sequences in 1 program that works out to about 9 minutes long.
I've scheduled it to run from 6 till 10 pm nightly every 30 minutes.
Works great, but now I've got 'dead' time for about 21 minutes between each showing... I'm thinking a background script would fill this gap nicely (and I'm also thinking that's the point of the background script) correct?
So I disable my schedule and start work on a simple 'background project'.
It's a simple script with no loops or time checks, it just ramps up the house lights, and then ramps them off again. (weak, I know... but I'm testing right now)
I set it as my 'Background Sequence' and enable it with a 10 second delay.
I exit and restart Vixen, and after about 10 seconds, the background sequence runs once, then that's it... it doesn't keep getting restarted as I expected...
So I enable the schedule again, restart Vixen, and the background script runs once, then some dead air till the schedule timer runs my 9 minute program... 10 seconds after the end of the program, the background script runs again... once. All is well, but I've still got dead air.
Ok, I think... so I need to either make it run for exactly the right amount of time to fill the almost 21 minutes gap between shows, or I need to add a loop in the script to repeat ...as the examples in the wiki. I add in the loop because it's easy... and so now my background script runs, I enable the schedule and boom... I get the (router) error 'Value cannot be null'...which BTW, is the same error I get if I hit the stop button while testing the script execution. anyone else seen that error and have a way to fix it?
I get what Aurbo99 was saying about the script and the program fighting over resources... and here's where I think there might be a bug in Vixen (or perhaps it's a feature request)... if the background script was meant to work as the examples shown in the Wiki (with loops and time checks) then when a scheduled timer kicks off, the router should send a 'kill' signal to the background sequence to stop it ... and release the locks on the controllers/ports/etc before the scheduled program begins...but that doesn't appear to be happening.
So after all this, the question I have is how are you (any of you) getting around this? Is you background script exactly the right amount of time to fill the dead space between your program showings (and the BGS exits by itself normally before the schedule timer kicks off your program)? or do you use a 'forever looping' BGS and just not get any errors? or have I missed something else completely(like there's a script interrupt method I should be using)?
Baylor wrote:I've got 4 sequences in 1 program that works out to about 9 minutes long.
I've scheduled it to run from 6 till 10 pm nightly every 30 minutes.Works great, but now I've got 'dead' time for about 21 minutes between each showing...
I've posted this before and so I'm not beating up on you specifically, Baylor, but I just don't get this idea that shows need to start at a specific time ...
I've certainly driven around looking a Christmas lights a lot longer than I have been doing shows, so I think I'm something of an expert at it -- I've got the better part of 50 years under my belt doing it.
And here's what I do: I drive by a house. I look at the lights. I drive to the next house. I watch the lights. I drive away.
It isn't a stage show or a movie -- I don't look at my watch and say, "Oh, Christmas lights at the Smith's house in five minutes!" I drive from house-to-house, street-to-street, neighborhood-to-neighborhood. Pausing for a while or in some cases not even slowing down.
If I dropped by your house during those 21 minutes of down time and saw your background sequence, I'd say, "Great. I wonder why he didn't synchronize to music" and drive on.
Personally -- and this is all personal, so I understand if you think I'm nuts -- I run my 15-minute show back-to-back all night long. Somebody drives up. They see the show running. They stop for a while. If they listen to the radio, they'll hear me say, "Our show tonight is 15 minutes long," so after they've stayed for 16 minutes, they'll either decide to watch some stuff a second time or they'll drive away.
I can't control when a viewer enters the show and I can't control when they exit. What I can make a feeble attempt to do is to manage their expectations.
Just my double-shot of pennies.
\dmc
