• Get involved.
    We want your input!
    Apply for Membership and join the conversations about everything related to broadcasting.

    After we receive your registration, a moderator will review it. After your registration is approved, you will be permitted to post.
    If you use a disposable or false email address, your registration will be rejected.

    After your membership is approved, please take a minute to tell us a little bit about yourself.
    https://www.radiodiscussions.com/forums/introduce-yourself.1088/

    Thanks in advance and have fun!
    RadioDiscussions Administrators

Simian/XP PRo issues

T

TomT

We have two stations, both using Simian installed on recent vintage computers (a Compaq and a Dell Optiplex), with plenty of RAM and both running XP-Pro. Both stations are ABC satellite programmed, using the Measurement Computing GPIO USB devices to take closures (triggers) from the Starguides.

A problem that seems to crop up with increasing frequency is that Simian seems to "forget" to recognize incoming triggers. Not all the triggers, just some, and not all the time. Which, on initial observation, seems to be a problem originating with ABC, not locally. (And, I suspect, sometimes is a problem with them).

My ops mgr, who is a whiz on anything virtual (but gets lost if you ask him about anything actually involving real wiring) claims this is a problem that will occur if the machines are not defragged on a weekly basis. This seems excessive to me--the predecessor set-up for both stations used Windows 2000 machines and the PCI card style GPIO made by Measurement Computing. Didn't seem to have these problems.

When this occurs on a Monday morning --and the missing trigger is for the (mostly sold-out) "optional" breaks, I am in a mood to "frag" somebody or something (as in the Vietnam era use of the terms, for those old enough to get my drift). Anyone else come across this? Is this an XP quirk? Problem with the USB devices?
 
TomT said:
We have two stations, both using Simian installed on recent vintage computers (a Compaq and a Dell Optiplex), with plenty of RAM and both running XP-Pro. Both stations are ABC satellite programmed, using the Measurement Computing GPIO USB devices to take closures (triggers) from the Starguides.

A problem that seems to crop up with increasing frequency is that Simian seems to "forget" to recognize incoming triggers. Not all the triggers, just some, and not all the time. Which, on initial observation, seems to be a problem originating with ABC, not locally. (And, I suspect, sometimes is a problem with them).

My ops mgr, who is a whiz on anything virtual (but gets lost if you ask him about anything actually involving real wiring) claims this is a problem that will occur if the machines are not defragged on a weekly basis. This seems excessive to me--the predecessor set-up for both stations used Windows 2000 machines and the PCI card style GPIO made by Measurement Computing. Didn't seem to have these problems.

When this occurs on a Monday morning --and the missing trigger is for the (mostly sold-out) "optional" breaks, I am in a mood to "frag" somebody or something (as in the Vietnam era use of the terms, for those old enough to get my drift). Anyone else come across this? Is this an XP quirk? Problem with the USB devices?
Click to expand...

You didn't say which version of Simian you're running - perhaps the issue has been addressed in a later release. You might want to open a support ticket with BSI (you don't need a Tech Care Plan to do that) or check out the Simian user forum at bsiusa.com for help.
 
Two of my stations use ABC programming, and I have not had a problem with missing closures. Occasionally I will have an issue on when they fire, however, and when I do, I adjust the window tolerance. Could the window tolerance be an issue?
 
Power saving is off, except for screen saver. Don't remember version numbers (at home now) but believe one is 1.6, the other 1.7--know that they are two different versions.

ABC will miss closures...we use the AC and classic rock formats, classic rock is usually voice tracked, AC sometimes is for an hour or two. Made me suspicious Monday when the optional breaks were missed from 6:00 AM on & they had a long segment with an interview with Pete Sampras on his new book. (Which was probably recorded Friday). Especially when they had to do a live bit on a contest call-in later in the 8:00 hour--and the optional break ran perfectly.

"window tolerance"--what window? With Simian, each closure is assigned to a different function or result (play liner, play macro to start a break, etc.). Closures are then assembled into different trigger sets, which are then opened up for each "shift" or show as needed. Once a particular trigger set is loaded, every trigger line that is used for that program is open all the time--so if the "wrong" trigger is fired (e.g., break cue, instead of a jingle) by the net that will trigger the action at that time. Here we are not getting, for whatever reason, the "right" trigger (the break cue for the optional break), and the programming gets out of sequence. But the other triggers (liner between songs, for example) are firing.
 
Check the trigger card itself. Remove the input and use the self test on the card. Sometime static discarge from lighting in the area can play havoc with these cards and cause damage. The key is the self test, see what that shows. We use Simian and have very little trouble even though we are in Florida. Several year ago I went with their triggers card that has extra protection on it.
 
This is a software, not hardware, issue, because either the triggers will resume normal behavior or, after defrag, everything will settle down. Don't need to touch the USB device.

What I don't understand is why these computers needs this constant defrag. (H.P./Compaq and a DEll, both XP-pro). As I mentioned, we used computers running Windows 2000 before, that were much more stable. Assuming, of course, it is the defrag that cures the problem, and it is not some kind of sporadic Simian issue.
 
Status
This thread has been closed due to inactivity. You can create a new thread to discuss this topic.


Back
Top Bottom