Connecting to CUE Streaming Media Services

CUE Streaming Media Services system provides streaming media for various purposes, including links embedded in various web pages, SWIS displays, archival content, etc.

Clients and Compatability

To access streaming media at JLab, you must have a client program capable of connecting with compatible protocols, etc. There are loads of stremaming media clients for the various platforms. We've tested a few of the popular ones. The results are provided here. Please use the comments section to provide feedback, or additional infomation on other players and results of using them with CUE Streaming Media Services. We'll continue to add information to this page as it becomes available.


Device / Platform

Example URL


Available From?

Windows XP, Vista, 7, 8


Windows Media Player

builtin, default for Windows

CUE Linux systems (mount /apps) -- RHEL5/6



Available from /apps/mplayer

Standalone Linux -- Fedora, Others?



Added using local add software tools, or downloaded and installed.

Mac OsX 10.5 (Leopard), Intel and Power PC, 10.6 (Snow Leopard), and 10.7 (Lion)



Mac OsX (all versions), Windows



Does not work. Protocol discrepencies between Microsoft and Apple(?)




Apple's App Store or Google Play -- Android Apps (previously, the Android Market) 


Constructing URLs for CUE Streaming Media Services

The server actually supports numerous protocols and formats, negotiating the best available combination for the particular client and content involved. URLs consist of four parts, followed by optional parameters. In a typical URL like, The parts are:

  • Protocol -- "http"
  • Server Name -- ""
  • Path -- "div_dept/theory"
  • Filename (optional) -- "index.html"


When making connections to the server, the protocol portion of the URL (usually, you see this as "http") specifies the connection protocol desired. Windows clients, and some others use "mms". Many non-Windows clients require the use of "rtsp".

Server Name

CUE Streaming Media Services are provided by a group of servers, arranged into a single, load-balancing cluster. This allows several machines to be used to distribute a large load if needed, all accessible as though they were a single large machine. Clients connect to the cluster with the server name "".


On the server, content is arranged into "Publishing Points". These are basically just folders on the server that can be referred to in connecting URLs. These publishing points are used to construct the path portion of the URL.


Like with many web services, filenames are frequently not used. Instead, a default file within a particular path is used by the server.