Cue Advances Stopped Working in 3.5

[bteacutter]

We have been using MS 3.5 for over a month. When I was setting up the announcement loop for worship this coming Sunday (I open the previous week's, make changes and save it with the coming Sunday's date) it wouldn't work. I checked and rechecked the timing on each cue, checked the script control even checked a previous Sunday's script and it didn't work! I don't know if something has been accidentally changed in the program without my knowledge (I'm not the only person who uses it) or it I accidentally hit a shortcut key or what but I am extremely frustrated. Any help????

[bteacutter]

A little clarification...all of the cues are built in MediaShout. There are video cues at the beginning and the end of the announcement script and the rest are "static" cues...some with a single cue only, others with multiple cues (I hope this makes sense - I'm new to the terminology), each timed at various lengths. There is a script control at the end set to loop back to the first cue (video cue to video cue). I generally add music to this looped script to play during the time when the congregation is entering the sanctuary. It is the same every week. After that is a series of cues which are advanced manually for worship (hymns, prayers, etc.). I save each week's script. When I realized the announcement script for this week would not advance on its own, I opened scripts from previous weeks and NONE of them worked. I hope this is a bit clearer.

[ministrytech]

That's an interesting one that I've never heard of before. Do none of the timed advances or the script control work?

An easy one to check is that you are in "normal" mode. The "mode" is in a little drop-down box above the script. If you have that in "manual" instead of "normal" that may be a problem.

You are using V3.5, not V4, right? I know V4 had an issue with script controls.

What build of MediaShout are you using? The first thing I would try is checking for an updated build (help> check for updates.)

You could also try a system restore to a point prior to when the problem started.

Let us know if any of that helps.