Google/Wide Orbit Automation

[CDJCD5]

Hey I don't post much on here but I always am checking up on the boards. My question is has anyone had much dealing with the Wide Orbit system and if so what kind of problems have you had? We have had the system in for a year and had some random issues with it and I was wondering what other people have had happen??

Thanks

CJ

 

[radiorob2.0]

I've been using WO since last summer and it works like a champ. Since what you are looking at on the screen is a web page built on java, it's worth it to exit and restart the application at least once a week and maybe rebooting the computer at least once a month. Since the audio servers and switchers will continue while the program is down it can be done while a song or long element is playing.

 

[ChiefOperator]

Since what you are looking at on the screen is a web page built on java, it's worth it to exit and restart the application at least once a week and maybe rebooting the computer at least once a month.

Does WO actually require these actions for the system to continue to run? Seems like a burden for such an expensive system. My less expensive automation is rebooted only every 3-4 months, just when we update the OS.

 

[radiorob2.0]

Since what you are looking at on the screen is a web page built on java, it's worth it to exit and restart the application at least once a week and maybe rebooting the computer at least once a month.

Does WO actually require these actions for the system to continue to run? Seems like a burden for such an expensive system. My less expensive automation is rebooted only every 3-4 months, just when we update the OS.

I'm not sure if is "required" but it has been suggested. Once in a while I've encountered an odd glitch and shutting down and restarting the application caused the glitch to disappear. Plus since the audio continues to operate until the next function it is rather painless.

 

[boiseengineer]

Every time there's a Jave (security) update, 'bout once a month lately, you have to close the WO program, patch it, then restart.

 

[OKCRadioGuy]

I can tell you this about that company though. Their support for their older product is nothing short of horrible. Maestro and Scotts support is nothing short of the worst. Based on that, I would be scared to death of upgrading to their current product.

 

[WEFWradio]

I can tell you this about that company though. Their support for their older product is nothing short of horrible. Maestro and Scotts support is nothing short of the worst. Based on that, I would be scared to death of upgrading to their current product.

It's been a while since I've worked with a Maestro, but support couldn't possibly be any worse than it was under Computer Concepts (I'm thinking 8-10 years ago). You'd be lucky if a tech even bothered to call you back the same day.

 

[OKCRadioGuy]

Amen to that. And, it was a "What the hell do you want?!" when and if they ever did. At least they don't have as much of the bad attitude problem these days. They are just hard to get real help from them.

 

[DoctorWu]

C'mon... really? Maestro and SS32 are a decade old. That's 70 in dog years, and about 140 in computer years! I understand that you've got old software that you want to keep using (I do, too), but you can't expect support forever on something that ancient. And anyway, WO didn't develop those programs! Look how many hands they've passed through: Scott, CC, dMarc, Google, now WO? C'mon. We've gotten our money's worth.

-- Doc.

 

[OKCRadioGuy]

Actually Doc, we really didn't. The service was horrible from day one, and never really got up to the quality of other vendors like BE, Prophet, or even BSI. They failed quite a bit at times, were hard to use, and basically just a huge glaring mistake on our choice of automation equipment years ago. Also, the fact that they have been through that many hands tells me I rather not bother, even if the current system is the best thing on earth. I want something that's going to be around for another 10 years. Stuff is too expensive and hard to change out to have anything less. I agree it's 70 in computer dog years, but in the broadcast world we have the need to keep things a bit longer.

 

[OKCRadioGuy]

Lucky me, I don't have to put up with the Shiestro system anymore. My friend's little small market that has the Scotts system will be dumping that POS in the junkpile in a year or so more in favor of Prophet, who answers their phones 24/7 with real help. It'll be worth the trouble of switching over and the cost for the reliablity. I know of a medium market cluster that "upgraded" their Scotts to the new version recently with some pretty ugly results. Based on the pure hell they had to deal with, I would rather just not bother with WideOrbit, or whatever they want to call themselves this week. With decent systems like Prophet, Audiovault and even BSI around for the cheap seats, why would I take a chance?

 

[Lazy J]

If you like AudioVault, them you can keep it.
Anything that requires me to edit ini files with cryptic command lines is a joke IMHO.

 

[chriscollins]

If you like AudioVault, them you can keep it.
Anything that requires me to edit ini files with cryptic command lines is a joke IMHO.

Audiovault is a very reliable system with good customer support. It is far from a 'joke'.

 

[bigtom101]

Hey I don't post much on here but I always am checking up on the boards. My question is has anyone had much dealing with the Wide Orbit system and if so what kind of problems have you had? We have had the system in for a year and had some random issues with it and I was wondering what other people have had happen??

Thanks

CJ

Where I worked, we went from SS32 to WO - and I hated it. Could never get it to sound "tight", voicetracking was a pain to do with levels, and the interface was slow as hell. Although it could have been the fact that NONE OF THE HARDWARE WAS UPGRADED when they switched everything over...and kept using the SS32 import software (WTF - using a new automation system...with bits of the old one?!)

Stick to Propehet or AudioVault for a professional sounding automation system if possible. WideOrbit looks nice, but fails to perform in my opinion. But I do like the search function and the hotkeys.

 

[OKCRadioGuy]

"Audiovault is a very reliable system with good customer support. It is far from a 'joke'."
Exactly. The fact some things ARE hidden in an ini file prevents some of the problems I've seen with Shiestro. I can't tell you how many times I used to get a phone call at 3 am in the morning because the damn jock closed the wrong window or moved it or minimized it into oblivia. Anyone that would build a system that can be that screwed up by jocks should have their head examined. The other thing that happened randomly with Shiestro was lock-ups and total crashes. Things like locked carts because someone had the cart up in another room when the thing wanted it to play out or the server would crash if a workstation was rebooted when a cart was locked in another room. I will happily take AV any day. Yeah, it's like an old tank, but it runs and runs without incident. My mean-time between failure is so low it's amazing. My stations run smooth as glass. I love being able to get a full 8 hours of sleep thanks to my current station's choice of automation.

 

[special ed]

If you have SS32's you want to keep running, try scottenco.com for support.

 

[ChiefOperator]

If you have SS32's you want to keep running, try scottenco.com for support.

Thanks, I didn't know about that option. Dave Scott certaintly doesn't beat around the bush. His comment, "They bought my source code, but they didn't buy my brain" made me laugh.

 

[DoctorWu]

Thanks, I didn't know about that option. Dave Scott certaintly doesn't beat around the bush. His comment, "They bought my source code, but they didn't buy my brain" made me laugh.

That's pretty great!

-- Doc

 

[DoctorWu]

I want something that's going to be around for another 10 years. Stuff is too expensive and hard to change out to have anything less. I agree it's 70 in computer dog years, but in the broadcast world we have the need to keep things a bit longer.

I understand the need to economize (brother, do I!) but I think any software that requires Windows XP to run these days has a very limited shelf life.

Example: I have a client that is such a cheapwad that he insists on using MusicMaster software to schedule his playlist. The program dates to 1995; it's recompiled code running in a DOS box in Windows 95SE. Won't run on anything newer. I have a call at least twice a week that the ancient Acer he's running it on needs attention. He's spent more on me fixing that verdammt machine than he would have to buy new software. Penny wise and pound foolish.

-- Doc

 

[radiogooroo]

Does WO actually require these actions for the system to continue to run? Seems like a burden for such an expensive system. My less expensive automation is rebooted only every 3-4 months, just when we update the OS.

Agreed. I'm running BSI's OpX and my last reboot was after 309 days, and that was purely to install an update with new features. I have no idea how long it would have run trouble free. I've been running for about 4 months with no restarts on the current version.