It there a limit to Program size?

[dnesci]

I have 11 sequences that I want to play three at a time with static sequences in between. The three will be mixed up through out the night to make the shows seem different. To do what I want, I need a 5 hour program. It will be the 11 sequences and 10 or so static sequences in the order I choose. The static sequences will have voice overs and annoucements on when the next show will start. Can Vixen handle a 5 hour program? Or do some of you have any ideas on how to handle this? The idea of just repeating the same pattern of sequences seems as it would get boaring for the neighbors. By mixing them up, no two patterns will repeat in one night.

[XmasInGalt]

One possible solution is to make copies of your .vpr and .pro files under the programs & profiles sub directories. Rename them to whatever you want. Then go into the program management section in Vixen and change the order of your sequences for that program. Then set your schedule to run your programs back to back. I'm also testing to see if I can load 5 hours of sequences into a single program and get it to run. I loaded my 6 sequences over and over in a single program until I got 301 minutes of scheduled sequences stuffed into the program. I'm running the program now to see if Vixen handles it. I like your idea. I never considered it before now.

[fkostyun]

I haven't done a long program in Vixen 2 - but - For Christmas 2006 I did run a 5 hour program without any major glitches.

There were some "memory leaks" - so all I did was schedule an auto reboot every night. Since I haven't tried it with vixen 2, I would do a test sequences and run it all to make sure it works OK (which it should)

[Macrosill]

I ran 5 hours Sun-Thu and 7 hours Fri and Sat last year without issue.

[Wayne J]

One possible solution is to make copies of your .vpr and .pro files under the programs & profiles sub directories. Rename them to whatever you want. Then go into the program management section in Vixen and change the order of your sequences for that program. Then set your schedule to run your programs back to back. I'm also testing to see if I can load 5 hours of sequences into a single program and get it to run. I loaded my 6 sequences over and over in a single program until I got 301 minutes of scheduled sequences stuffed into the program. I'm running the program now to see if Vixen handles it. I like your idea. I never considered it before now.


Why are you doing this? If you have the program start time and stop time, it will repeat the the program (six sequences) over and over until stop time. Or am I misunderstanding something?

[XmasInGalt]

Why are you doing this? If you have the program start time and stop time, it will repeat the the program (six sequences) over and over until stop time. Or am I misunderstanding something?

Wayne,

I just loaded the sequences so I could get 5 hours worth of sequences in the program just to test and see if Vixen would have any problems with that many sequences in a single program.

[XmasInGalt]

If I understand dnesci's post correctly, he wanted to know if Vixen could handle a program with 5 hours of sequences in it. That way, he could set up the sequences within the program to run it three different sets (vary the order of the sequences). I may have misunderstood the intent of his post.

[dnesci]

If I understand dnesci's post correctly, he wanted to know if Vixen could handle a program with 5 hours of sequences in it. That way, he could set up the sequences within the program to run it three different sets (vary the order of the sequences). I may have misunderstood the intent of his post.

No you understood my question correctly. It seems, per Brian, that Vixen will not have a problem and the 5 hour program is do able. Thanks to all that have responded.

XmasInGalt did your 301 minute version work OK? I understood what you were doing.

There was a mention of memory leaks in Vixen 1.x. Has anyone seen this problem with 2.x.x.x.x? Is a reboot still necessary with this version?

[Wayne J]

There was a memory leak in 2.0 early on, but has long been fixed. ;)

[dnesci]

There was a memory leak in 2.0 early on, but has long been fixed. ;)

Thanks Wayne, now I don't have to write a shutdown program (I'm using ME) and it doen't have a good scheduler.