Difference between revisions of "Dr.Octo"

== Version 4.0 ==

== Version 4.0 ==

In early 2011, Dr.Octo Version 4.0 was hatched, so to speak. An unusual case of an entire re-write from scratch (as the original code had been lost). In V4, the primary program source resides on hard disk, making it much easier and more efficient to work with than the CD carousels. The ability to insert and schedule streams as if they were static program sources was also added. This version is implemented on Ubuntu Linux, with some instances also running on Debian (and variants thereof). Due to the necessity of starting over from scratch, V4 does not (yet) have a GUI, and the Web Interface is, so far, primordial. New features such as program catching, distributor integration, Twitter integration, support for multiple program streams, and vastly improved DJ assist mode have been implemented. System V IPC features are used to deal with resource contention and control. Remote control, submission, and collaboration features are very nice to have. Integrated flow and calendar-based scheduling have been implemented, and self-service web-based spot/PSA submission and scheduling is soon to be released. This release, as well as earlier releases, is incredibly stable and capable of running for very long periods of time, and with remote collaboration and submission possible, the product remains fresh even during long periods of unattended operation. No crashes have been logged since early 2011, and the longest run-time experienced has been around 4 months and counting.

In early 2011, Dr.Octo Version 4.0 was hatched, so to speak. An unusual case of an entire re-write from scratch (as the original code had been lost). In V4, the primary program source resides on hard disk, making it much easier and more efficient to work with than the CD carousels. The ability to insert and schedule streams as if they were static program sources was also added. This version is implemented on Ubuntu Linux, with some instances also running on Debian (and variants thereof). Due to the necessity of starting over from scratch, V4 does not (yet) have a GUI, and the Web Interface is, so far, primordial. New features such as program catching, distributor integration, Twitter integration, support for multiple program streams, and vastly improved DJ assist mode have been implemented. System V IPC features are used to deal with resource contention and control. Remote control, submission, and collaboration features are very nice to have. Integrated flow and calendar-based scheduling have been implemented, and self-service web-based spot/PSA submission and scheduling is soon to be released. This release, as well as earlier releases, is incredibly stable and capable of running for very long periods of time, and with remote collaboration and submission possible, the product remains fresh even during long periods of unattended operation. No crashes have been logged since early 2011, and the longest run-time experienced has been around 4 months and counting.