Media Object Server: Difference between revisions

Revision as of 08:17, 3 July 2017

Revision as of 10:26, 3 July 2017

Line 1:

The '''Media Object Server''' ('''MOS''') protocol allows [[newsroom]] computer systems (NRCSNCS) to communicate using a standard protocol with [[video server]]s, [[sound server|audio servers]], [[Movie stills photographer|still stores]], and [[character generator]]s for [[Broadcasting|broadcast]] production.<ref>{{cite web|url=http://www.mosprotocol.com/ |title=MOS Project |publisher=Mosprotocol.com |date= |accessdate=2012-05-03}}</ref><ref>{{cite web|url=http://xml.coverpages.org/mos-x.html |title=Cover Pages: MOS-X (Media Object Server – XML) |publisher=Xml.coverpages.org |date= |accessdate=2012-05-03}}</ref>

The MOS protocol is based on [[XML]].<ref>{{cite web|last=Qureshi |first=Rizwan |url=http://www.codeproject.com/Articles/34527/MOS-Protocol-Fundamentals |title=MOS Protocol Fundamentals – CodeProject® |publisher=Codeproject.com |date=2009-04-01 |accessdate=2012-05-03}}</ref> It enables the exchange of the following types of messages:<ref>{{cite web|url=http://www.mosprotocol.com/mos_faq.htm#what_does_MOS_do |title=Mos Faq |publisher=Mosprotocol.com |date= |accessdate=2012-05-03}}</ref>

Line 7:

; Status Exchange. : The MOS can inform the NCS of the status of specific clips or the MOS system in general. The NCS can notify the MOS of the status of specific playlist items or running orders.

MOS was developed to reduce the need for theirthe development of [[Device driver|device specific drivers]]. By allowing developers to embed functionality and handle events, vendors were relieved of the burden of developing device drivers. It was left to the manufacturers to interface newsroom computer systems. This approach affords broadcasters flexibility to purchase equipment from multiple vendors.<ref>{{cite web|url=http://www.newsmaker.us/TheMOSStory.html |title=Newsmaker |publisher=Newsmaker.us |date= |accessdate=2012-05-03}}</ref> It also limits the need to have [[Computer operator|operators]] in multiple locations throughout the studio as, for example, multiple [[character generator]]s (CG) can be fired from a single control [[workstation]], without needing an operator at each CG console.<ref>{{cite web|url=http://www.enotes.com/topic/Media_Object_Server |title=Media Object Server – eNotes.com Reference |publisher=Enotes.com |date=2002-03-21 |accessdate=2012-05-03}}</ref>

MOS enables [[journalists]] to see, use, and control media devices inside [[Associated Press]]'s [[ENPS]] system so that individual pieces of newsroom [[Video production|production]] technology speak a common [[XML]]-based language.<ref name="autogenerated1">{{cite web|author=WGN-TV, Chicago, Illinois, USA |url=http://www.enps.com/pages/enps_integration/what_is_mos |title=ENPS and MOS |publisher=Enps.com |date= |accessdate=2012-05-03}}</ref>

Line 13:

== History of MOS ==

The first meeting of the MOS Protocolprotocol development group occurred at the [[Associated Press]] [[ENPS]] developer's conference in [[Orlando, Florida]] in 1998. The fundamental concepts of MOS were released to the public ___domain at that conference.<ref>{{cite web|url=http://www.mosprotocol.com/mos_faq.htm#MOS_group |title=Mos Faq |publisher=Mosprotocol.com |date= |accessdate=2012-05-03}}</ref>

As an [[open protocol]], the MOS Development Group encourages the participation of broadcast equipment vendors and their customers.<ref>{{cite web|url=http://www.mosprotocol.com/how_to_participate_in_mos.htm |title=How to Participate in MOS |publisher=Mosprotocol.com |date= |accessdate=2012-05-03}}</ref> More than 100 companies are said to work with AP on MOS-related projects. Compatible hardware and software includes [[video editing]], [[File server|storage]] and [[Content management system|management]]; [[Broadcast automation|automation]]; machine control; [[Teleprompter|prompters]]; character generators; [[Digital audio editor|audio editing]], store and management; [[web publishing]], [[Interactive television|interactive TV]], [[Electronic field production|field transmission]] and [[Motion graphics|graphics]].<ref name="autogenerated1" />

Line 19:

Current development is happening on two tracks: a [[Network socket|socket-based]] version, and a [[web service]] version. The current official versions of the MOS protocol, as of January 2011, are 2.8.4 (sockets) and 3.8.4 (web service).<ref>{{cite web|url=http://www.mosprotocol.com/MOS%20Files/2.8.4/MOS_Protocol_Version_2.8.4.htm |title=MOS Protocol 2.8.4 (Current) |publisher=Mosprotocol.com |date= |accessdate=2012-05-03}}</ref>

In 2016 proposals began to introduce IP Video support in the MOS Protocolprotocol. This proposal allows representations of live IP Video sources such as NDI ([[Network Device Interface]]) to be included as MOS objects alongside MOS objects representing files to be played off disk<ref>{{Cite web|url=http://www.sienna-tv.com/ndi/ndimonitor.html|title=NDIMonitor|website=www.sienna-tv.com|language=en-GB|access-date=2017-01-25}}</ref>

There is also a [[Java (programming language)|Java]] based implementation called jmos that is currently compatible with MOS specification 2.8.2.<ref>{{cite web|url=http://code.google.com/p/jmos/ |title=jmos – Open java implementation for Media Object Server Communications Protocol (MOS) – Google Project Hosting |publisher=Code.google.com |date= |accessdate=2012-05-03}}</ref>

In 2017 the National Academy of Television Arts and Sciences awarded an Emmy to the MOS Group for “Development"Development and Standardization of Media Object Server (MOS) Protocol."<ref>http://mosprotocol.com/forums/topic/mos-emmy-statues-nominations-and-voting/</ref>

== References ==