Talk:Radio Computing Services

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

I take note of the contention that this article was written like an advertisement. I also have to disclose, since I made a modification to the article that I used to work for Dr. Economos and RCS from 1979 to 1981 and made a modification only to state what I knew of the original system that was written at that time. Since then the only contact I had with Dr. Economos was one e-mail and around that time the company was bought by Clear Channel.

Much of what I know of RCS came from this article.

Chris 14:17, 17 October 2007 (UTC)Chris Ward[reply]

Prophet Systems acquisition[edit]

A disclaimer first: I am employed by a company related to the subject of the page. Although my information is first-hand, it is not an official statement on the part of any company or organization. Since I am involved, I will make no changes to the page itself.

Prophet Systems, Inc. has never had a system called 'prophet'. The automation programs were sometimes called 'the prophet thingy' by users. There were several early iterations of DOS-based programs that culminated in CFS (also called Audio Wizard or Wizard for Windows) which ran on DOS and later on Windows 3. A document exemplar of this title can be found here: ftp://ftp.rcsoga.com/anonymous/Documentation/CFSDaylightSavingsTimeClockSet.pdf The replacement Windows-based program is NexGen Digital. This title can be confirmed from the RCS website directly.

When Clear Channel bought RCS, the company was then merged with CC's existing automation subsidiary, Prophet Systems. The new company kept the RCS name due to international brand recognition. Management from both companies remain in place. The chain of command goes to Premiere first and then to CC. It's worth noting that the Clear Channel page makes no mention of RCS in it's holdings, although a large number of broadcasters not otherwise affiliated with CC use RCS software.

Freshgroundcoffee (talk) 18:53, 17 April 2009 (UTC)[reply]

The branded name of that automation system for Windows 3.1 was AudioWizard according to this article ( https://www.digitalbroadcasting.com/doc/prophet-systems-innovations-psi-a-division-of-0001) from 2001 which correctly identifies the writer as Kevin Lockhart and his father who sold it to Clear Channel for $25 1/2 cash and 1/2 stock. I know this to be true as I spent a day at the NAB with Kevin.

Products[edit]

Not sure if anyone is interested in a list of products offered by the company, but here it is. Hopefully these will be added to the article; some of this software is quite relevant to the state of modern radio.

The new list of products (and their origination) are listed here, or can be seen from the website (http://www.rcsworks.com/en/products/default.aspx). Support contact numbers depend on the original source of the product; White Plains, NJ for RCS and Ogallala, NE for PSi. This trend follows the location of development for new products as well. Note that RCS operates offices worldwide. PSi-sourced programs are supported 24/7 from Ogallala. RCS-sourced programs roll through the international offices to provide 24/7 support.

Studio automation: NexGen Digital (PSi) Player101 (PSi) Master Control (RCS) Zetta (new, prerelease)

Scheduling: GSelector (new) Selector (RCS) Linker (RCS)

'New Media': RCS RadioShow (RCS) RCS HD Importer (PSi) iSelector (RCS)

News Production: RCSNews (PSi)

Recording/Monitoring: Tracker (PSi) SmartRIPPER (RCS) Media Monitors (new, separate company/service)

Contest/Promotion: PrizeWatch (PSi)

Traffic scheduling: AQUIRA (RCS) Airwaves (RCS)

Freshgroundcoffee (talk) 18:56, 17 April 2009 (UTC)[reply]

Maintenance[edit]

I was paid by RCS to revise this page, which involved reorganization, reference checks, and rewriting content from a neutral point of view. After that, I removed the maintenance tag.Tlvernon (talk) 21:17, 17 July 2018 (UTC) Paid contribution. Added mention of Zetta Cloud Best of Show award, along with citation.Tlvernon (talk) 00:02, 8 July 2019 (UTC)[reply]