Ok computer gurus:, Any way possible to virtualize Scott Studios SS-32’s system and a dispatch server into new virtual machines. In other words, image the working drives and original OS, settings, etc into a new virtual computer that can run the original operating system and settings. Have a station where the mother boards, drives, etc are on borrowed time. Trying to save some $ and buy a few years before upgrading to new automation. Thanks....
-
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
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
Any way to virtualize old working Scott SS32 system to new life???
- Thread starter fm-engineer
- Start date
Take a machine and see... You can probably make all the non-audio functions work.
I got audiovault working in a vm using DirectX emulation, but it had some latency issues. For the other things (file sharing, etc...), it was reliable.
None of them support it, so it is a YMMV thing.
I got audiovault working in a vm using DirectX emulation, but it had some latency issues. For the other things (file sharing, etc...), it was reliable.
None of them support it, so it is a YMMV thing.
I've worked quite a bit wit Sun Microsystem's VirtualBox on Ubuntu Linux. The OS has limited exposure to actual hardware functionality in the real PCI bus, which is what the ASI driver needs to see in order to connect to the sound cards and read the serial numbers properly. Then SS32 looks for the serial number data from the ASI driver to verify the licensing on the software. In other words, if things aren't perfect, the SS32 won't get out the gate. Last time I tried, I couldn't get the driver to work with the sound cards in this scenario, I would imagine the same thing applies to Windows based hosts... Let alone the fact that ASI drivers are unstable on the best hardware from the get-go. Add to these another layer of emulation and it's a good recipe for instability.
If you are interested, I have an automation suite I've been developing for several years that would probably solve most of your issues, since you could run it on any Windows 2000 or XP OS. The price is very reasonable and I have a monthly contract-to-buy option that is less expensive than tech support alone for SS32/WOA. My system will work with all the files you already have, it will allow you to keep a repository of backups without the need for a "dispatch" application. All of the databases for the automation are maintained on the automation computer itself, so you could conceivably run a single automation system with a production room editor and a traffic/music scheduler, or expand it to as many stations as you want. It will work with all of the data exports for music and traffic that you already have. There are no extra charges for running simultaneous automation systems to cover HD streams, just one license per call letter. All upgrades are included with an annual tech support subscription, so you won't be forking out 20 grand to upgrade just because the manufacturer doesn't want to support the version you're running.
If you want more information, let me know what your e-mail address is.
If you are interested, I have an automation suite I've been developing for several years that would probably solve most of your issues, since you could run it on any Windows 2000 or XP OS. The price is very reasonable and I have a monthly contract-to-buy option that is less expensive than tech support alone for SS32/WOA. My system will work with all the files you already have, it will allow you to keep a repository of backups without the need for a "dispatch" application. All of the databases for the automation are maintained on the automation computer itself, so you could conceivably run a single automation system with a production room editor and a traffic/music scheduler, or expand it to as many stations as you want. It will work with all of the data exports for music and traffic that you already have. There are no extra charges for running simultaneous automation systems to cover HD streams, just one license per call letter. All upgrades are included with an annual tech support subscription, so you won't be forking out 20 grand to upgrade just because the manufacturer doesn't want to support the version you're running.
If you want more information, let me know what your e-mail address is.
"Jasonce66" - I admire your hijacking a thread to promote your soon-to-be-released software product(s). But the question was regarding how to redeploy the EXISTING SS32 system - not on what options are available to replace it.
And I'm sure the OP knows there are plenty of other well-established automation systems that could be deployed for as little as no cost (Rivendell & ZaraRadio) or for little cost (StationPlaylist, Simian et. al).
And I'm sure the OP knows there are plenty of other well-established automation systems that could be deployed for as little as no cost (Rivendell & ZaraRadio) or for little cost (StationPlaylist, Simian et. al).
You know, there probably isn't a real installer for SS32, just copy the folders that the program lives in and copy all its settings/audio folders and files to a new Windows XP box, setting up the partitions and drive letters to be identical to the old machine and making sure you put the folders exactly where they used to be. If you don't have Active Directory domain controller, you probably can get away with Home Edition. Install the same ASI sound card driver off the Audio Science website archive. If you are migrating from 2000 to XP, I don't suspect you'll have any issues.
Unless you had a need to pack more than one machine in a box, there isn't a need to virtualize anything. I don't think SS32 has anything but a few DLLs and the exe. Most of ours have a system partition, and two other partitions, one for the system logs and audio. I don't think anything but the partition with the system logs needs to be shared.
Make sure XP firewall is off, and set the computers name to a static IP and turn off simple file sharing. If you haven't changed the name of the SS32, then it should be a simple matter of refreshing the node table in dispatch. Go into the Config-IP page and make sure it connects to dispatch and away you go.
The ASI sound card "is" your security key. Don't mix up sound cards between systems and you should be fine. Create a shortcut to start SS32 up when the system starts (paste it into startup menu).
Unless you had a need to pack more than one machine in a box, there isn't a need to virtualize anything. I don't think SS32 has anything but a few DLLs and the exe. Most of ours have a system partition, and two other partitions, one for the system logs and audio. I don't think anything but the partition with the system logs needs to be shared.
Make sure XP firewall is off, and set the computers name to a static IP and turn off simple file sharing. If you haven't changed the name of the SS32, then it should be a simple matter of refreshing the node table in dispatch. Go into the Config-IP page and make sure it connects to dispatch and away you go.
The ASI sound card "is" your security key. Don't mix up sound cards between systems and you should be fine. Create a shortcut to start SS32 up when the system starts (paste it into startup menu).
Please don't take this the wrong way, but are you paying for support?
If so, they can help you. If you're going to use a system like this, prepare to pay for support. It's a necessary evil. It is what it is.
Please save any snarky comments about their support. It's true, it's not as good as it used to be, but nothing is.
If so, they can help you. If you're going to use a system like this, prepare to pay for support. It's a necessary evil. It is what it is.
Please save any snarky comments about their support. It's true, it's not as good as it used to be, but nothing is.
Sgeirk,
You're probably right, having some support on hand might be a good idea, at least when trying something tricky like this... The folks at WO (Wide Orbit) are quite good, I'm told. Personally, I've been using the product from ss16 through to the GRA (Google v6) model, so I'm pretty familiar with it (good and bad), although I haven't had any personal contact with the new guys.
I just wanted to encourage him that it "was" possible to do a migration and point him in a direction. I generally don't have a need for support these days as my knowledge has been accumulated over the last 20 years or so.
Tech support for this sort of project will cost him a few hundred $$$... They'll walk him through everything and tell him everything he needs to know to do more than one system migration - it is quite more involved than the "reader's digest" version outlined above, just a synopsis of how it's done. A few hours on the phone at $100 an hour is well worth the investment though, when you think about how much mileage the system gets and the lasting effects of getting off of worn out hardware. There are several engineers who know what I've just told him, so it isn't top secret. If anything, I've probably forgotten something important and he'll need support anyway. WO is the best equipped to take care of him and I respect that. They are good at what they do.
Although I am working on my own endeavors, I have a lot of respect for where SS32 came from, and where it's going in the future. There are a lot of cool things ahead in the future of radio automation and WO will be right there, I'm sure.
You're probably right, having some support on hand might be a good idea, at least when trying something tricky like this... The folks at WO (Wide Orbit) are quite good, I'm told. Personally, I've been using the product from ss16 through to the GRA (Google v6) model, so I'm pretty familiar with it (good and bad), although I haven't had any personal contact with the new guys.
I just wanted to encourage him that it "was" possible to do a migration and point him in a direction. I generally don't have a need for support these days as my knowledge has been accumulated over the last 20 years or so.
Tech support for this sort of project will cost him a few hundred $$$... They'll walk him through everything and tell him everything he needs to know to do more than one system migration - it is quite more involved than the "reader's digest" version outlined above, just a synopsis of how it's done. A few hours on the phone at $100 an hour is well worth the investment though, when you think about how much mileage the system gets and the lasting effects of getting off of worn out hardware. There are several engineers who know what I've just told him, so it isn't top secret. If anything, I've probably forgotten something important and he'll need support anyway. WO is the best equipped to take care of him and I respect that. They are good at what they do.
Although I am working on my own endeavors, I have a lot of respect for where SS32 came from, and where it's going in the future. There are a lot of cool things ahead in the future of radio automation and WO will be right there, I'm sure.
Thanks Jason66 for all the info! We are working with Enco SS support on a possible migration. Dave Scott and some of his former employees joined forces with Enco a while back and they offer older SS suport.
- Status
- This thread has been closed due to inactivity. You can create a new thread to discuss this topic.