Main article: Cross-platform., a multi-faceted media player/organizer with a DLNA/UPnP server, controller, and renderer, including conversion. Runs on Microsoft Windows. Supports most all HTML5 devices as remote controls. Asset UPnP (DLNA compatible) from Illustrate. An audio specific UPnP/DLNA server for Windows, QNAP, macOS and Linux. Features audio WAVE/LPCM transcoding from a range of audio codecs, and playlists., very simple server, historically used to stream to the STB Freebox, based on.net/mono., a multi-faceted media player/organizer with a DLNA/UPnP server, controller, and renderer, including conversion. Supports Microsoft Windows, macOS and Linux.
(previously XBMC), a cross platform open source software / for Android, Apple TV, Linux, macOS and Windows., a free cross platform home- and UPnP/DLNA mediaserver with android app and transcoding for browser playback (build with java and )., a Java-based highly configurable uPnP/DNLA music server with additional consideration given to Classical Music, supports transcoding with MinimStreamer, supports Microsoft Windows, macOS, Linux, and various NAS devices., acts as a cross platform UPnP/DLNA Media Renderer server available for, & platforms. Supports gapless playback and has possibility to output rendered audio further to the high-resolution internal DAC or external USB DAC or another UPnP/DLNA Media Renderer with all supported DSP effects applied., a cross-platform and closed source software media player and entertainment hub for digital media, available for macOS, Microsoft Windows, Linux, as well as mobile clients for iOS (including Apple TV (2nd generation) onwards), Android, Windows Phone, and many devices such as. Supports on-the-fly transcoding of video and music. Based on the JRiver Media Center software, includes similar features along with a store for purchasing HD audio tracks., a free cross platform Java based UPnP especially good for AVC and other current HD media codecs with on-the-fly transcoding., is available with a free and a pro license. It can stream media files (music, video or images) to renderer devices (e.g.
A TV set, Blu-ray player, games console or mobile phone) on a local area network., a cross platform, high performance UPnP/DLNA Media Server for Windows, macOS and Linux., a cross-platform multimedia server and entertainment hub for digital media, available for Android, Apple TV, iOS, Linux, macOS, Microsoft Windows, Windows Phone, and Xbox 360., a free (open source) DLNA-compliant UPnP Media Server for Windows, macOS and Linux (originally based on the PS3 Media Server). It is able to stream videos, audio and images to any DLNA-capable device. It contains more features than most paid UPnP/DLNA Media Servers.
It streams to many devices including TVs (Samsung, Sony, Panasonic, LG, Philips and more.), PS3, Xbox(One/360), smartphones, Blu-ray players and more., a simple, cross platform (Chrome App) DLNA server and controller for single, local video files., an open-source Java-based BitTorrent client which contains MediaServer plugin. Android. Android UPNP/DLNA Server, Controller and Renderer., Android UPNP/DLNA Media Server. Supports all popular Video and Audio files. It also support external subtitle file (SRT).
is an Android UPNP Client App that can play videos and audio. Android UPNP/DLNA Server, Controller and Renderer., Android App that can play videos embedded in websites on DLNA Renderers., Android UPNP Client App that can play videos/Audio. is a DLNA Server that allows individual file selections for sharing. A minimal and intuitive open-source Android UPNP client app that can play video/audio. (It is not DMS) Complete Systems., a free NAS.
Based on and works on -based computers. (FreeNAS UPnP server code is from the Portable Universal Plug and Play (UPnP) SDK project) Linux., an open source lightweight for Linux that supports DLNA through (uShare development is currently discontinued)., an open source DLNA server for Linux., a simple, lightweight alternative to mediatomb, but has fewer features.
It does not have a web interface for administration and must be configured by editing a text file., a music-centric DLNA server for Linux running on Raspberry Pi., an open-source and software for Linux, with a built-in UPnP AV MediaServer. (formerly known as MiniDLNA) is a simple media server software, with the aim of being fully compliant with DLNA/UPnP-AV clients. It is developed by a NETGEAR employee for the ReadyNAS product line. Rygel, an open-source media server, part of the Live! Project. a native Linux TV Server providing DVB, ATSC and ISDB-T via UPnP/DLNA, it also supports streaming media files (it only supports TV devices from Sundtek).
is a free, open source (GPL v3), quick-install ISO that turns your unused computer into an easy-to-use music server/jukebox Microsoft Windows. a native Windows TV Server providing DVB, ATSC and ISDB-T via UPnP/DLNA, it also supports streaming media files (it only supports TV devices from Sundtek)., a Windows application that streams the sound of your computer (i.e.: “what you hear”) to UPnP/DLNA device such as TVs, amps, network receivers, game consoles, etc., a Windows application that streams multimedia content from a personal computer to UPnP, DLNA and mobile devices (Chromecast is also supported). It was the first media server to offer real-time transcoding (back in 2005)., a Windows application that mirrors the screen of a personal computer to UPnP, DLNA and mobile devices., a Windows application, mainly for TV/Radio recording/playback, but with the ability to stream live TV/radio as well as multimedia files via UPNP/DLNA., a Windows application, mainly for video encoding into DivX format, but has the ability to stream multimedia files via DLNA., a freeware audio player for Windows. Highly customizable, audio only. Download of dlna-extension from the developers's webpage necessary., a free and open source media server compatible with DLNA. Includes web interface for streaming content to web browser (Android, iOS, ), subtitles integration and Windows desktop streaming.
This server is easy to use., a commercial DLNA media server and organizer for Windows. Includes on-the-fly transcoding, per-file and per-folder parental controls, powerful organizing features with dynamic playlists, Internet radio streaming, 'Play To' functionality and remote device control, burned-in and external subtitles, extensive format support including RAW photo formats. Streams all files to all devices., a free media player/tagger/editor with an UPnP/DLNA client and server for., a commercial software package. Mezzmo streams music, movies, photos and subtitles to the UPnP and DLNA-enabled devices.
It automatically finds and organizes music, movies and photos, imports multimedia files from iPad, iPhone, iPod, Audio CDs, iTunes, Windows Media Player and WinAmp. DLNA server supports all popular media file formats with real time transcoding to meet the device specifications., a commercial UPnP/DLNA media server for Windows, includes a transcoder for streaming web video., a cloud connected (Rotten tomatoes/TMDB etc.), Torrent streaming, DLNA enabled media server.
Allows single file or playlist downloads. Wild Media Server, a media server for Windows, Linux, macOS, individual device settings, transcoding, external and internal subtitles, restricted device access to folders, uploading files, Internet-Radio, Internet-Television, Digital Video Broadcasting (DVB), DMR-control and 'Play To', Music (Visualization), Photo (Slideshow), support for 3D-subtitles, support for music fingerprints, support for files, Web-navigation with HTML5 player. from, a free UPnP AV MediaServer and control point (server and client) for. WMC version 2.0 can be installed for usage with for. WMC version 3.0 can be installed for usage with for.
WMC version 4.0 comes pre-installed on with its. WMC can also refer to Windows Media Center. From the Windows Media Center entry in Wikipedia: In May 2015, Microsoft announced that Windows Media Center would be discontinued on Windows 10, and that it would be uninstalled when upgrading; but stated that those upgrading from a version of Windows that included the Media Center application would receive the paid Windows DVD Player app to maintain DVD playback functionality, the main purpose for Media Center's use. This is stated on a Windows 10 FAQ page. MacOS. a native macOS TV Server providing DVB, ATSC and ISDB-T via UPnP/DLNA, it also supports streaming media files (it only supports TV devices from Sundtek). by Cyaneous, Inc., a commercial UPnP/DLNA media server for macOS with advanced transcoding capabilities, per-device profiles and native Mac media organization.
ArkMS by, a full-featured UPnP/DLNA media server for macOS to stream video, music and pictures to UPnP/DLNA/Samsung Link compatible devices from Mac. Hardware. DSL-N55U ADSL Modem Router, supports USB drive media sharing. (Dual Band WIFI, 10/100/1000 Mbit/s)., the newer revisions of these residential gateway devices come with a UPnP/DLNA compliant media server. 7800xxx series modem-routers come with a built in uPnP/DLNA compliant media server. WBMR-HP-G300H ADSL2+ Modem Router, supports USB drive media sharing, possible to install Open-/DD-WRT.
Fast NAS sharing too. (Dual Band WIFI, 10/100/1000 Mbit's). DNS-323 2-Bay Network Attached Storage Enclosure. DNS-325 Share Centre2-Bay Network Attached Storage Enclosure.
WRT610N gigabit Wifi-N router supports UPnP with a USB hard drive, as a Storage feature. N1 UPnP ripping server. HDX ripping UPnP server and player. UnitiServe ripping UPnP server. ReadyNAS Includes ReadyDLNA (branded version of miniDLNA) on all ReadyNAS products and some routers as the ReadyShare USB feature.
Alix and APU UPnP Media server based on ReadyMedia with. 2 and 3 UPnP Media server based on ReadyMedia with. NeufBox 5 (Gigabit LAN) and NeufBox 4 (10/100 Mbit/s with firmware 2.0.8) and USB drive key. All DSL/GPON Gateways from the TG712 upwards have an embedded DLNA certified Server (sharing content of a USB attached HDD). All Synology NAS are DLNA mediaserver and contain a webbased DLNA player which is also available as App for Android or iOS. See also – there are many uncatalogued NAS devices with UPNP.
UPnP AV clients See also. A UPnP client, also called a control point, functions as a digital audio/video remote control. Control points automatically detect UPnP servers on the network to browse content directories and request the transfer or streaming of media. A UPnP media renderer performs the actual audio or video rendering. Control points and media renderers most commonly run on separate devices, the control point being for example a tablet, and the renderer a television or a networked audio computer connected to an audio receiver. Some control points integrate a media renderer and may function as a complete music playing application. UPnP control points and player software Cross-platform., an open source (MIT) media player with UPnP-client support since version 2.4.
Kinsky is an open source UPnP control point for iPod/iPhone, iPad, Windows, macOS, Linux, Android and PocketPC. (previously XBMC), a cross platform open source software / for Apple TV, Linux, macOS, Windows, Android and the custom., a cross platform UPnP/DLNA client which is able to read music files from UPnP/DLNA Media Server or send processed audio to UPnP/DLNA Media Renderer as an endless stream. Available for, & platforms., a desktop UPnP audio Control Point for Linux/Unix and MS Windows, is a light QT-based Control interface. It is free, open-source, and licensed under the GPL., a cross-platform and open source (GPL) software media player and a closed source media server and entertainment hub, available for macOS, Microsoft Windows, Linux, as well as mobile clients for iOS (including Apple TV (2nd generation) onwards), Android, and Windows Phone. The desktop version of the media player is free while the mobile version is chargeable. is a cross-platform UPnP client, Media Renderer, Media Server and control point available for iPod/iPhone, iPad, Android, Google TV and macOS. In addition to UPnP servers, PlugPlayer can also utilize some cloud-based media services such as MP3tunes and CloudUPnP., a free, open-source and cross-platform media player that has a built-in UPnP-client that lets the user access the contents listed from an UPnP Media server.
Though a very complete media player in itself, it does not provide any UPnP Control Point capabilities, nor can the player be controlled as a UPnP compliant Media Renderer. (For Windows, macOS, Linux, iOS & Android.)., a free software to play content fom a media server on a client, has a built-in UPnP-client for music.
(For Windows & Linux) Android. is a DLNA Server, Controller and Renderer.
is a free UPnP renderer/player. (formerly iMediaShare) is a free DLNA compliant Digital Media Controller, Server and Renderer.
is a free UPnP AV Control Point and Renderer. is a free UPnP control point for Android tablets with included UPnP renderer and server functionality.
is a UPNP/DLNA server, renderer and controller. There is a free trial version and a paid licensed version.
Android UPNP/DLNA controller. is a free DLNA Controller. is a free UPnP renderer/player/server/controller.
is a free DLNA compliant Digital Media Server on Android platform. Has external subtitles support. is a free DLNA compliant Digital Media Controller on Android platform to control DLNA certified/compliant Digital Media Server, Digital Media Render and Digital Media Printer on Android.
Can browse contents from the Media Server and playback media at a DLNA certified TV or renderer devices, and print at DLNA certified Printer. (discontinued) - a DLNA Certified software app. Android UPNP/DLNA Server, Controller and Renderer. is a free UPnP control point and renderer. is a free UPnP renderer/player.
is a multi-room control point and DLNA media server which offers the opportunity to stream media from a smartphone or a network hard drive to a media player. is a free DLNA compliant Digital Media Controller, Server and Renderer.
is an open source UPNP/DLNA server, renderer and controller. is a free DLNA compliant Digital Media Controller, Server and Renderer. Archos Video Player has DLNA rendering/player capabilities. DroidUPnP is an open source DLNA controller.
for Android is a UPnP Renderer and Controller. is a UPnP/DLNA Controller with free and paid version. BlackBerry All devices running the operating system include native UPnP Media Server capabilities.
is a free UPnP media server. IOS. DLNA/UPnP Media Server for iOS with features to push and control media using iOS. Infuse DLNA/UPnP streaming client for iPhone and iPad. nPlayer DLNA/UPnP Client for iPhone/iPad. DLNA/UPnP Client for iPhone/iPad.
DLNA/UPnP Client for iPhone/iPad. DLNA server, controller and renderer. is a media playback and organizing solution. & Lite., formerly & iMediaShare Lite. DLNA/UPnP Client for iPhone/iPad. player with downloading & background play features. UPnP control point app and client supporting both audio and video from a variety of sources.
is a UPnP/DLNA Controller with free and paid version. supports UPnP, OpenHome & Chromecast audio devices. Linux. BRisa UPnP Framework, a free and open-source UPnP framework that allows the development of UPnP devices, as well as provides three implementation reference of UPnP applications: the BRisa Media server, the BRisa Media Renderer and the BRisa Control Point.
djmount, free software to mount as a Linux filesystem the media content of compatible UPnP AV devices., a free and open-source Media Player part of the desktop, via the grilo plugin. upmpdcli, a free and open-source UPnP media renderer front end to MPD, the. upplay, a free and open-source basic UPnP audio control point for the Unix Desktop, based on Qt. GUpnp-tools supplies a free and open-source GUI control point for AV devices, gupnp-av-cp.
GMediaRender, a UPnP™ media renderer for POSIX®-compliant systems, such as GNU/Linux® or UNIX®. It implements the server component that provides UPnP controllers a means to render media content (audio, video and images) from a UPnP media server. GMRender-Resurrect, resource efficient UPnP/DLNA renderer, optimal for Raspberry Pi, CuBox or a general MediaServer. Fork of GMediaRenderer. is an audio player with built-in UPnP/DLNA support, and can act as a UPnP client. Microsoft Windows., an audio player, supports UPnP via a plugin., is a commercial and video-files playback software for Windows., a commercial software package containing both a UPnP client and server supporting music and video playback., free media player/tagger/editor with an UPnP/DLNA client and server., a media player/organizer with a DLNA/UPnP server, controller, and renderer, including conversion., a media player/server with DLNA/UPnP capabilities.
MacOS., UPnP Audio/Video Player & Control Point., UPnP Control Point., media player that has a built-in UPnP-client., a media player/organizer with a DLNA/UPnP server, controller, and renderer, including conversion., a company who builds screen mirroring apps for Samsung, LG, Panasonic, Sony and Philips TVs based on the UPnP renderer in the TV, the Mac acts as the UPnP server as well as the UPnP control point. Symbian. has client and server. has client and server, both DLNA certified. has client and server, only the server is DLNA certified. has client and server, both DLNA certified., the first Nokia E-Series device having client and server, both DLNA certified. has client and server, both DLNA certified.
has client and server. has server and is DLNA certified. has server and is DLNA certified. has server and is DLNA certified.
Windows Phone. Linada. Other., an open-source lightweight, no installation required.
and its native MediaStreamer application.
VMware ESX software has been tested and deployed in a variety of storage network environments. This guide describes the storage devices currently tested by VMware and its storage partners. ESX, ESXi Embedded and ESXi Installable are equivalent products from a storage compatibility perspective.
In this guide we only explicitly list ESX compatibility information. If a product is listed as supported for ESX, the product is also supported for ESXi Embedded and ESXi Installable corresponding versions. Note: Boot from SAN (Fibre Channel, Fibre Channel over Ethernet, SAS, or iSCSI) is not supported with ESXi version 4.0 and earlier.
If you are having a technical issue with 3rd party HW/SW and it is not found on this list, please refer to our 3rd Party HW/SW support policy. VMware works closely with each of its OEMs to drive towards mutual support of ESX at the time of announcement.
Due to different product release cycles, levels of testing, and OEM agreements, not all OEM devices will be supported at the general availability date of a new version of ESX. We recommend contacting the OEM vendor for the best information on when their device is planned to be certified with Virtual Infrastructure. For further details about array firmware, storage product configurations and best practices, please contact the storage vendor.
NOTE: The use of an external enclosure, or JBOD connected to a supported SAS/SCSI controller in a supported server is supported, as long as there is no disk sharing among multiple servers or SAS/SCSI cards. This SAN HCL lists storage devices starting with ESX 3.0.x onwards. It does not include older ESX 2.5.x or earlier versions listed in. Please contact your storage vendors if you do not find devices certified in the SAN HCL list. Microsoft Windows Failover Cluster with ESX Windows Clustering refers Cluster Services in Windows operating systems in a shared disk configuration between two virtual machines or a virtual machine and a physical system. Such clustering is certified only with a subset of arrays listed in this guide.
Previously Failover Clustering was called MSCS. Before installing VMware ESX software with your storage array, please examine the lists on the following pages to find out whether your array and configuration are supported. Please refer to your storage vendor for more information and configuration details.
Windows Failover Cluster support with ESX 3.0.x Below table shows the supported list of Windows OS, FC HBA speed and drivers. Windows Failover Cluster support with ESX 3.5.x MSCS/Failover cluster is supported with ESX 3.5 with both 32 bit and 64 bit VMs running - Windows 2000 SP4 and - Windows 2003 (x86 and x64) up to and including SP2 Only 4Gb Emulex and Qlogic FC HBAs are supported. Windows Failover Cluster support with ESX 4.0 With native multipathing (NMP), clustering is not supported when the path policy is set to round robin. Please see 'Setup for Failover Clustering and Microsoft Cluster Services' for limitations on MSCS support with PSA. Virtual SCSI adapter and Windows OS supported - LSI Logic Parallel for Windows Server 2000 SP4 - LSI Logic Parallel for Windows Server 2003 RTM (x86 and x64) up to and including SP2 - LSI Logic SAS for Windows Server 2008 (x86 and x64) up to SP1 2. Only 4Gb Qlogic and Emulex Fibre Channel HBAs are supported. The driver versions supported are as follows: qla2xxx-400.821.kl.38vmw qla4xxx-400.5.01.00.vml lpfc820-400.2.0.30.49vmw PSA Plug-ins with ESX 4.x and ESX 5.x Array operating modes and path selection behavior are supported through the Pluggable Storage Architecture (PSA) framework.
Storage partners may (1) provide their own Multi-Pathing Plug-ins (MPP), (2) use Storage Array Type Plug-ins (SATP) and Path Selection Plug-ins (PSP) offered by VMware 's Native Multi-pathing (NMP) or (3) provide their own SATP and PSP. The plug-ins supported with a storage array are noted in the 'Mode' and 'Path Policy' columns of the 'Model/Release Details' page. The path policy of VMWPSPRR may also be supported but not be necessarily listed in the 'Mode' and 'Path Policy' columns of the 'Model/Release Details' page. Storage partner may recommend VMWPSPRR for path failover policy for certain storage array models. If desired, contact the storage array manufacture for recommendation and instruction to set VMWPSPRR appropriately.
With native multipathing (NMP), clustering is not supported when the path policy is set to round robin. Please see 'Setup for Failover Clustering and Microsoft Cluster Services' for limitations on MSCS support with PSA. Note that VMware does not currently support unloading of third-party PSA plug-ins on a running ESX/ESXi host. Installation, upgrade or removal of third-party PSA plug-ins may require a reboot of the ESX/ESXi host. Please refer to the third party product's documentation for details on right procedures for installation, upgrade or removal. Fibre Channel SANs For Fibre Channel SANs, if listed, VMware supports the following configuration, unless footnoted otherwise:.
Basic Connectivity - The ability of ESX hosts to recognize and interoperate with the storage array. This configuration does not allow for multipathing or any type of failover. Multipathing - The ability of ESX hosts to handle multiple paths to the same storage device. HBA Failover - In this configuration, the ESX host is equipped with multiple HBAs connecting to one or more SAN switches.
The server is robust to HBA and switch failure only. Storage Port Failover - In this configuration, the ESX host is attached to multiple storage ports and is robust to storage port failures.
Boot from SAN - In this configuration, the ESX host boots from a LUN stored on the SAN rather than a local disk. Direct Connect - In this configuration, the ESX host is directly connected to the array. There is no switch between HBA and the array and each HBA port must be connect directly to a storage port on the array.
Multiple storage ports also known as FC target port on single Fiber Channel-Arbitrated Loop are not supported; therefore, daisy-chaining of storage ports within a storage controller, across storage controller, or across multiple arrays is not supported. Windows Failover Clustering is not supported in this configuration. NOTE: Windows Failover Clustering (MSCS) support applies to Windows 2000 SP4, Windows 2003 RTM, SP 1, R2 and SP 2. For ESX version requirements for these operating systems in cluster environment, please refer to.
Windows Failover Clustering is supported only with a limited set of HBAs; please refer to the I/O Compatibility Guide for the list of HBAs not supported with Windows Failover Clustering. NOTE: MSCS is not supported, unless footnoted. NOTE: MSCS is not supported for Direct Connect. NOTE: Only footnoted storage arrays are supported with Brocade 415 and 425 HBAs.
NOTE: Unless otherwise footnoted, all fibre channel arrays are supported with both 2Gb and 4Gb FC HBAs on ESX NOTE: For ESX 3.5 U2 onwards unless otherwise footnoted, all fibre channel arrays are supported with 2Gb, 4Gb and 8Gb FC HBAs on ESX. NOTE: For devices with external SAN storage support, please refer to Storage Virtualization Device (SVD). NOTE: Unless otherwise noted, all fibre channel storage products are supported in a boot from SAN configuration. NOTE: End-to-end connectivity at 8Gbps FC speed is supported with 8G FC arrays only if the product details has prefix of '8G FC' or is footnoted. Otherwise support for 8G FC arrays is limited to up to 4Gbps speed only. Storage Virtualization Device (SVD) VMware supports Storage Virtualization Devices (SVD) with ESX 3.0.2 or later, ESX/ESXi 4.x and ESXi 5. Gateways are included as part of SVDs.
Backend storage arrays must be listed on both the ESX Storage/SAN Compatibility Guide and the SVD Vendor supported list. Back-end array and the SVD are both required to be certified with the same ESX release. Do not share the same LUN of the backend storage array between SVD and any other host. Only devices that are listed with Array Type SVD are allowed to connect to external Fibre Channel SAN storages. Storage Arrays supported with FCoE CNAs VMware supports Fibre Channel (FC) Arrays connected to Fibre Channel Over Ethernet (FCoE) Converged Network Adapters (CNAs) with ESX 3.5 U4 and newer releases. Native FCoE arrays connected to FCoE CNAs are also supported with ESX 4.0 and newer releases.
Network Attached Storage The following Linux distributions are supported network attached storages ESX 3.x. Red Hat Enterprise Linux 5 NFS Server (Update 2). Red Hat Enterprise Linux 3 NFS Server (Update 5). Fedora Core 4 NFS Server (2.6.12-1.1456FC4.9550smp). Fedora Core 6 NFS Server (2.6.18-1.2798.fc6 #1 SMP) for ESX 3.5 only. ESX 4.0 Fedora Core 8 NFS Server NOTE: Windows Clustering (MSCS) is not supported with NAS. ISCSI VMware supports connections to iSCSI arrays using the following iSCSI initiators: Software iSCSI Adapter A software iSCSI adapter is a VMware code built into the VMkernel.
It allows the host to connect to the iSCSI storage device through standard network adapters. The software iSCSI adapter handles iSCSI processing while communicating with the network adapter. With the software iSCSI adapter, you can use iSCSI technology without purchasing specialized hardware. Hardware iSCSI Adapter A hardware iSCSI adapter is a third-party adapter that offloads iSCSI and network processing from your host. Hardware iSCSI adapters are divided into categories.
Dependent Hardware iSCSI Adapter: Depends on VMware networking, and iSCSI configuration and management interfaces provided by VMware. This type of adapter can be a card that presents a standard network adapter and iSCSI offload functionality for the same port.
The iSCSI offload functionality depends on the host's network configuration to obtain the IP, MAC, and other parameters used for iSCSI sessions. An example of a dependent adapter is the iSCSI licensed Broadcom 5709 NIC. Independent Hardware iSCSI Adapter: Implements its own networking and iSCSI configuration and management interfaces.
An example of an independent hardware iSCSI adapter is a card that either presents only iSCSI offload functionality or iSCSI offload functionality and standard NIC functionality. The iSCSI offload functionality has independent configuration management that assigns the IP, MAC, and other parameters used for the iSCSI sessions. An example of a independent adapter is the QLogic QLA4052 adapter. Hardware iSCSI adapters might need to be licensed. Otherwise, they will not appear in the vSphere Client or vSphere CLI. Contact the adapter's vendor for licensing information. Please refer to the I/O Compatibility Guide for a list of hardware iSCSI adapters and NIC that can be used with ESX.
For iSCSI storage with the Software and Dependent Hardware iSCSI Adapter, if listed, VMware supports the following configuration, unless footnoted otherwise:. iSCSI Base Connectivity - The ability of an ESX host to recognize the target and interoperate with it. SP failover - In this configuration the ESX host is attached to multiple ports and is robust to storage port failover. Boot from iSCSI - In this configuration, ESX hosts boot from the target iSCSI array rather than from a local disk. This is only supported on ESXi starting with ESXi 4.1 and requires the NIC to support iSCSI Boot Firmware Table (iBFT). NIC failover for software initiator - If the Ethernet adapters are teamed and one fails, the other one takes over. Both adapters must be connected to the same physical switch and be on the same subnet (both NICs and iSCSI storage ports).
iSCSI initiator failover - The ESX host is equipped with multiple software and/or dependent hardware iSCSI adapters and is robust to iSCSI adapter failover. This is supported is starting with ESX 4.0 and later versions. For iSCSI storage with the Independent Hardware iSCSI Adapter, if listed, VMware supports the following configuration, unless footnoted otherwise:. iSCSI Base Connectivity - The ability of an ESX host to recognize the target over an iSCSI HBA and interoperate with it.
SP failover - In this configuration, ESX host is attached to multiple ports over an Hardware iSCSI HBA and is robust to storage port failover. Boot from iSCSI - In this configuration, ESX hosts boot from the target iSCSI array rather than from a local disk. iSCSI initiator failover - The ESX host is equipped with multiple independent hardware iSCSI adapters and is robust to iSCSI adapter failover. NOTE: Windows Clustering is not supported with iSCSI. NOTE: Software initiated iSCSI is supported fully in ESX 3.0 and later releases.
Hardware initiated iSCSI is supported in experimental mode only in ESX 3.0. It is supported fully in ESX 3.0.1 and later with iSCSI arrays that have been qualified/certified for use with the hardware initiators. NOTE: Dependent Hardware iSCSI adapters are supported starting with ESX 4.1 and later versions. SAS Arrays For SAS Arrays, if listed, VMware supports the following configuration, unless footnoted otherwise:. Basic Connectivity - The ability of ESX hosts to recognize and interoperate with the storage array.
This configuration does not allow for multipathing, any type of failover, or sharing of LUNs between multiple hosts. Direct Connect - In this configuration, the ESX host is directly connected to the array (that is, no switch between HBA and the array). Windows Clustering is not supported in this configuration.
LUN sharing - The ability of multiple ESX hosts to share the same LUN. Multipathing - The ability of ESX hosts to handle multiple paths to the same storage device.
HBA Failover - In this configuration, the ESX host is equipped with multiple HBAs connecting directly to the array. The server is robust to HBA failure only. Storage Port Failover - In this configuration, the ESX host is attached to multiple storage ports on the same array and is robust to storage port failures. Boot from SAS - SAS boot is supported unless explicitly stated in a footnote for a specific array.
Storage IO Control (SIOC) feature in vSphere 4.1, 5,0, and 5.1: SIOC feature is available with VMware vSphere 4.1T GA. SIOC is a QoS feature that is disabled by default.
When enabled, this feature monitors ESX-array latency to determine when a datastore is congested. When congestion is detected (latency above a threshold), SIOC allocates the limited I/O resources to virtual machines in accordance to their relative importance (user-specified). All the storage devices listed on vSphere 4.1 Storage HCL are supported for use with SIOC. There is no special certification requirements for the SIOC support. VSphere Metro Cluster Storage (vMSC)in vSphere 5.0 VMware supports Metro Cluster Storage with vSphere 5.0 where the storage systems present internally synchronously replicated storage by storage controllers and present such storage as a single LUN from different geographically distributed sites.
Only array-based a synchronous replication is supported and asynchronous replication is not supported. Storage Array types FC, iSCSI, SVD, and FCoE are supported. NAS devices are not supported with vMSC configuration.
Host Access configuration The following terms describe the accessibility from ESXi to storage device with appropriate vSphere Native Multi Pathing. Uniform host access configuration - When ESXi hosts from various sites are all connected to a storage node in the storage cluster across all sites. Paths presented to ESXi hosts are stretched across distance. Non-Uniform host access configuration - ESXi hosts in each site are connected only to storage node(s) in the same site.
Paths presented to ESXi hosts from storage nodes are limited to local site. Inter-site links The stretch cluster configuration has two intersite links; a link between ESXi hosts at different sites, and a link between storage controllers at different sites. The latency requirements for these links are as follows: - The supported latency between the ESXi ethernet networks sites must be less than 10 milliseconds RTT.
The supported latency for synchronous storage replication must be less than 5 milliseconds RTT In the event of Inter-site link failure between storage controllers, the I/O continues at the biased side of storage device access. On the unbiased side the I/O fails. Although unlikely, if a running virtual machine is on the unbiased side, it is restarted on the biased side. The site bias is set by vendor specific interface. ESXi does not set the site bias. VAAI Block Thin Provisioning Space Reclamation Schedule Changes in vSphere 5.0: Space Reclamation part of the VAAI Block Thin Provisioning has been delayed.
For details please refer to the Knowledge Base article 2007427 on how to disable the UNMAP command used for the Space Reclamation. Windows Failover Cluster support with ESX 5.0 is 1. Virtual SCSI adapter and Windows OS supported - LSI Logic Parallel for Windows Server 2000 SP4 - LSI Logic Parallel for Windows Server 2003 RTM (x86 and x64) up to and including SP2 - LSI Logic SAS for Windows Server 2008 (x86 and x64) up to SP2 - LSI Logic SAS for Windows Server 2008 R2 (x86 and x64) SP1 2. Only 4Gb Qlogic and Emulex Fibre Channel HBAs are supported. The driver versions supported are as follows: qla2xxx-911.k1.1-19vmw lpfc820-8.2.2.105.36vmw Storage Array Device and Model Information. ESX, ESXi Embedded and ESXi Installable are equivalent products from a storage compatibility perspective. In this guide we only explicitly list ESX compatibility information.
If a product is listed as supported for ESX, the product is also supported for ESXi Embedded and ESXi Installable corresponding versions. The detailed lists show actual vendor devices that are either physically tested or are similar to the devices tested by VMware or VMware partners. VMware provides support only for the devices that are listed in this document. THIS CONTENT IS PROVIDED AS IS, AND TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, VMWARE DISCLAIMS ALL OTHER REPRESENTATIONS AND WARRANTIES, EXPRESS OR IMPLIED, REGARDING THIS CONTENT, INCLUDING THEIR FITNESS FOR A PARTICULAR PURPOSE, THEIR MERCHANTABILITY, OR THEIR NONINFRINGEMENT. VMWARE SHALL NOT BE LIABLE FOR ANY DAMAGES ARISING OUT OF OR IN CONNECTION WITH THE USE OF THIS CONTENT, INCLUDING DIRECT, INDIRECT, CONSEQUENTIAL DAMAGES, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF VMWARE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. THE VMWARE COMPATIBILITY GUIDE IS UPDATED FROM TIME TO TIME WITHOUT NOTICE.
FOR THE LATEST VMWARE COMPATIBILITY GUIDE, PLEASE GO TO THE FOLLOWING LINK.
. Software (Firmware) ReadyNAS OS is the software that drives the ReadyNAS devices. You can elect to perform a remote update from your ReadyNAS management interface or you can download the relevant image below and perform a local update.
Note: Image downloads are zipped and must be unzipped before being uploaded into your ReadyNAS. Last Updated: Article ID: 20684 Was this article helpful?
This article applies to:. GearHead Support for Home Users GearHead Support is a technical support service for NETGEAR devices and all other connected devices in your home. Advanced remote support tools are used to fix issues on any of your devices. The service includes support for the following:.
Desktop and Notebook PCs, Wired and Wireless Routers, Modems, Printers, Scanners, Fax Machines, USB devices and Sound Cards. Windows Operating Systems (2000, XP or Vista), MS Word, Excel, PowerPoint, Outlook and Adobe Acrobat.
Anti-virus and Anti-Spyware: McAfee, Norton, AVG, eTrust and BitDefender.
Well WhoCares? Did it, so it is possible and he would know how easy/difficult it is.
For the source code take a look at Add-ons ('.bin' files are developed using ) To install PHP manually you wouldn't need to use that. You could do an # apt-get update && apt-get install build-essential Then download PHP source, extract the contents, read the README (or similar) document and attempt to compile it. If it doesn't work then there'll be an issue e.g. With a dependency.
You'll either need to backport the code to work with the version installed on the ReadyNAS or update the version on the ReadyNAS (note this may break things).
. Server:. Player:, rank 1,159 (September 2017 ) Website Plex is a system and software suite comprising two main components. The Plex Media Server desktop application runs on, and -compatibles including some types of devices. The 'server' desktop application organizes video, audio and photos from your collections and from online services, enabling the players to access and stream the contents.
The media players. There are official clients available for, and, a and Plex Home Theater (no longer maintained), as well as many third-party alternatives.
Additional functionality can be added through an and Plex Inc sells a premium service Plex Pass with features like with mobile devices, integration, and matchings for music, Live TV and DVR, trailers and extras and offers. This section contains content that is written like. Please help by removing and inappropriate, and by adding encyclopedic content written from a. (July 2017) Birth Plex began as a in December 2007 when developer Elan Feingold wanted a media centre application for his, but none of the existing players met his needs. He decided to the media player (now known as Kodi) to as a challenge. Around the same time, Cayce Ullman and Scott Olechowski - software executives who had recently sold their previous company to, were also looking to port XBMC to OSX, and noticing Feingold's progress via XBMC they contacted him and offered support and help with funding so that he could dedicate more hours to the project. Feingold, Olechowksi and Ullman formed as a team by January 2008, and founded Plex, Inc.
In December 2009. Feingold was subsequently contacted by the XBMC team, and he, Olechowski and Ullman were brought rapidly on their team. Over the next few months, they made some early releases of the port, which they called “OSXBMC”. Their purposes were to bring to the project a complete integration to the Mac. That integration comes from DVD playing, to energy saving features without hesitating to cut features out to benefit stability. Given that the three of them came from professional and enterprise software background they were not satisfied with many of XMBC's engineering practices.
They thought as a maturing project, XBMC had to improve its engineering practices, embrace software regression tests and provide end-user support with an improvement of. Fork The developers worked under the auspices of the XBMC project until May 21, 2008. Due to different goals and vision from the XBMC team, they shortly forked the code to become Plex, and published it on.
The code was kept roughly in sync with the Linux code. The new name was announced on July 8, 2008. While the team received many suggestions from users (Meteor Center, Media Hugger, etc.), Ullman came up with the name Plex² or Plex Square, due to the unavailability of plex.com, and the availability of plex2.com. Feingold suggested Plex² was too unwieldy and the single word, Plex, was ultimately chosen because the 'plex' suffix evokes “comprising a number of parts”.
Then, the team began to work on a media centre component to aggregate not only local content but also to bring together web-based multimedia services. The new library system was redeveloped from scratch. Work for new remote control was also on the todo list.
The CenterStage UI group, a team aiming at improving the UI interface, often considered as 'The interface that the AppleTV forgot', teamed with Plex to develop the idea further. CenterStage was looking for developers and Plex was looking for designers, a perfect match. As that hobby was costing money for the required infrastructure (for example), the project used donations and was selling mugs in order to lessen the burden of self funding.
Relations with content companies Like, Plex had applications for services such as. Even if Boxee and Plex extensions were both written in Python, Feingold advertised Plex extensions were easier to write thanks to a new in-house framework developed by James Clarke, one of the main Plex developers. At that point, Plex had 120 plug-ins (also called applications). Plex has been listed as an officially approved app. With the situation was different. Hulu deployed 'counter-measures' by creating changes deliberately to prevent Plex from parsing their HTML. Netflix and Hulu services are no longer officially available with Plex anymore (see for more info).
The relationships with content companies were not completely adversarial. Some companies contacted Feingold to add their content to Plex, including music streaming service. Future In order to develop his software and make the project viable at some point in the future, the team's purpose was to bring the Plex experience to other devices, without the need for users to buy yet another computer or dedicate one as a. They also recognized a Mac Mini was a barrier to entry and the Apple TV of that generation with its limitations and closed hardware decoder was an underpowered and too closed device. They thought the evolution of video media consumption is to be able to watch whatever content we want, whenever we want ( and download) with instant access to all pieces of media server ever created.
Therefore, implementing features into Plex has, according to them, no interest as requiring cable or IPTV subscriptions would be like 'returning to Neolithic'. In December 2009, the project evolved into a owned and developed by a single for-profit, Plex, Inc., a U.S.-based firm that is responsible for the development of the Plex Media Server and media player app, its, all accompanying software under the Plex brand name, as well as the exclusive, parts, whether distributed on its own or as a in products manufactured via a. Elan Feingold, Scott Olechowsi and Cayce Ullman were the three founders, with Ullman and Feingold taking on full-time roles as the CEO and CTO, respectively. A Christmas post indicated two new project contributors have been hired to Plex, Feingold specifying they are hiring, looking to grow the company in 2011. Windows engineers were hired to bring Windows support.
Plex had at that time 130 apps whose most popular ones were Apple Movies Trailers, Hulu, and. In an interview for, Feingold declared Plex apps have been downloaded about 1 million times. Elan Feingold is the CTO. Cayce Ullman remained CEO and co-founder until 2011 when he left the company. Keith Valory is the new CEO since February 2013.
In 2014, Plex raised $10 million from the. In an interview at 2014, Scott Olechowski, Plex Chief Product Officer, added that Plex is considering eventually adding paid music downloads, or teaming up with a music subscription service, to give users a chance to grow their music library.
These partnerships, like the one with VEVO (see below), are costly for Plex, which lead to fundraising from Kleiner Perkins. As of July 2016, Plex has 65 employees. Plex Media Server Plex Media Server (sometimes called PMS or PMS Software ) is the back-end media server component of Plex. It organizes audio (music) and visual (photos and videos) content from personal media libraries and streams it to their player counterparts, either on the same machine, the same, or over the.
It can run on, a plethora of devices or on. Introduced in 2009, Plex Media Server was originally called Plex Media Center and was based on formerly known as XBMC. Plex Media Center's was initially from XBMC on May 21, 2008. This fork continued to be used as a front-end media player on Linux for Plex's media server back-end until Plex fully replaced it with a version in October 2015. Indexing Import Plex Media Server can be configured to index content in any directory on the machine it is run on, as well as to automatically acquire content from such sources as iTunes, iPhoto and Aperture.
Support for importation of iTunes playlists has been announced long after, on July 31, 2014, along a true play list system. While an import support for was initially announced to be available shortly after Aperture support, as of July 2016, that feature has not been implemented yet.
New framework On March 14, 2010, the plugin framework and the new library system called Alexandria were announced. Both were completely rewritten as a distributed architecture with a REST HTTP/XML API opposed to the old monolithic one, less customizable. These were released with a new Plex version called Plex/Nine on August 30, 2010.
The advantages of the new library is the ability to scan and sort the media even if the websites adding additional metadata and content are down. If the user had a custom filename layout organization, he can write his own parser. Parsers work exactly like Plex plugins using the new plugin framework with parsing and support. The old Plex/Eight used the old XBMC scrapers which used encoded in XML which is considered much harder to program. Video library The video library is one of the Plex metadata and is, therefore, a key feature of Plex. It allows for the automatic organization of video content by information associated with the video files (movies and recorded ) themselves.
The Library Mode view in Plex allows the user to browse video content by categories such as, title, year, actors, and directors. Music library The music library is another of the Plex metadata databases. The music library feature received a major overhaul with a new release announced on April 30, 2015. That version allows for the automatic organization of a music collection by information stored in the or tags, such as title, artist, album, genre, year, and popularity. If the metadata are not stored in the files themselves, the naming and organization of the music files are important. If the user has a Plex Pass account, the file naming and organization is not as critical as the music will be matched via sonic fingerprinting. The music library feature brought instant metadata and poster downloads instead of waiting the end of the media scan.
Metadata can be edited, multi-discs, multi-selection to remove a whole album content or to move or copy tracks between albums and/or artists has been added are supported. Music videos can be associated to the music library and lyrics or even interviews can be downloaded. The new library allows to rediscover the user's music with suggestions based on the most played media or the least played, but also with similar artists or genres. The library also displays when and where artists are on tour. If the user has a Plex Pass account, the whole music video catalog from can be accessed and an extra feature called is available.
Extra library content Plex recognizes extra content to a video or music file. In that regard the extra content must have the same filename as the media it complements, but have the suffixed with the kind of content it represents. Depending of whether the file is linked to music or a video, the following suffixes are supported: -behindthescenes, -concert, -interview, -live, -lyrics, -video, -deleted, -featurette, -scene, -short and -trailer. Plex recognizes lyrics as the file formats or as simple text file. Tagging Thanks to Agents, Plex can automatically gather information and artwork for media stored in the Plex library.
These metadata are fetched from the following sites using: (TMDb) for synopses and for movies and TV shows, just for metadata and thumbnails, Fanart.tv, CineMaterial, Music Videos for clips (only available with ), and for lyrics and OpenSubtitles.org for subtitles. Plex previously had access, but that access was removed when the Plex app for iPhone was released.
The mobile app usage was so widely used that the IMDb servers crashed. Plex received a letter from IMDb parent company 's lawyers who made it clear that that access was a commercial use and therefore Plex had to license it if they still wanted to use it. Also, PlexPro accounts would have been required, as Plex has now a paid version and would, therefore, violate IMDb terms of use. Access to that database is not officially supported by Plex anymore, but community members have expressed the need to have it since decided to close its Freebase's service. Previously, there was access to Online TV Database. Plex supports rich text in subtitles, and up to two subtitles channels are supported at the same time.
Specifying subtitle preferences on an app will be reflected on the other. Plex supports SSA, SRT and SMI subtitle formats.
Multi sources As a media player software, Plex can play media from many sources: local files from libraries (from local ), but also from network shares using the protocol either located at home or on the internet, media devices using the interoperability guidelines, and. While DVD playback initially had support, it required helper applications like. DVD playback is no longer supported. While Plex can access media recorded via digital video recorders (DVR), it does not support recording the content itself.
DVRs are only in charge of recording live TV content from for cable companies and/or for companies. Depending on the services provided by the DVRs, Plex could access the content.
Still depending on the offered features, DVRs can also stream content without recording it on a hard disk drive. Are reported to work fine with Plex, because two tablo users, developed a Plex Channel (see below) to watch content recorded by Tablo DVRs and even watch the TV, as Tablo does support Live TV streaming. Thanks to that combination of Plex and Tablo, it is now possible to watch over-the-air (OTA streaming). Media formats Plex media player software is able to decode up to, as well as sources. With the appropriate hardware, Plex also supports hardware decoding of H.264 video. Like other XBMC-derived media players, Plex uses and other open source libraries to handle all common formats.
It can decode these in software, using hardware video decoding where available and optionally passing-through or audio directly to an external audio-/ via. Plex video-playback uses a video-player 'core' which was originally developed in-house by the XBMC developers as a for contents, including the support of. This video-player 'core' supports all the FFmpeg codecs, and in addition the, and the DTS and AC3. PAPlayer handles a very large variety of audio file-formats. Plex handles all common with the options of panning, zooming and slideshow with ', with the use of CxImage open source code. Transcoding Content may be by the server before it is streamed, in order to reduce bandwidth requirements or for compatibility with the device being streamed to. This way, transcoding allows media to be available on the widest range of clients possible over any connection, while without transcoding clients would not be able to read the format because lacking the proper codec or because of performances restrictions.
During the media analysis phase, the Plex Media Server looks at certain attributes of the media (resolution, bitrate, etc.). When a client requests a piece of media, the server looks at the client’s capabilities, compares them to the media parameters, and makes a determination as to whether or not the file can be directly played on the device. This feature is called Direct Play. Another feature called Direct Streaming allows to change only the container without reencoding the video and music tracks if these are encoded in a codec the destination device can read. Mobile apps have the ability to define the maximum the mobile connection is limited to, in order to force the server to reencode the piece of media, reducing filesize and avoiding lags when the piece media is being streamed.
The transcoding feature is reported to not have a good of sources to 2.1. Remote access Plex Media Server can be remote controlled via a web interface. As Plex does support and protocols, the connection should be automatically configured. While a Plex account is reported necessary to help redirecting port and improve availability, configuring the ports manually does work, but when the users accesses the remote web interface, login and password to a PLex account are required.
SSL Plex Media Server via its supports. The SSL connection was previously only reachable via the dedicated port 32443, which provided secure authentication but lacked support for encrypting streams. Now, simply prefixing https on port 32400 (e.g. Is enough only if a proper certificate and key have been installed in the Network section of the server. Also, SSL is supported for both streaming and authentication, except in a few rare cases when a mobile server has been enabled on mobile applications.
However, this SSL configuration is only valid for users who know how to generate a certificate self-signed or signed by a and configure a domain name. On June 4, 2015, Plex announced all connections to Plex will be encrypted as soon the user has upgraded to at least 0.9.12.3 and has connected its web server to a Plex account ( not needed).
Plex also announced the user interface for the user's Plex Media Server will also be available via While the system looks trivial this is technically not the case. When the user connects to authenticating to its Plex account, the Plex website enumerates a list of the user's servers and then connect to each of them via an (XHR) to Since the Plex website uses an SSL connection, the XHR connections would be blocked because the users might not have installed a SSL certificate on his/her own Plex Media Server (XHRs are blocked when they load an link from an one). Since Plex could not ask users to acquire a domain name and a certificate just to watch movies over TLS, they had to provide the solution by themselves. Since Plex Media Servers do not all have a domain name or a stable IP address (a dynamic public IP address or even a local one), the solution had to provide a dynamic DNS for each user. Each Plex user is thus provided with a DNS domain.plex.direct where the hash part is probably a hash of the user or the server name ID. Each user domain name is prefixed by an IP address.
Each user can have several DNS records each representing the IP addresses the user's Plex Media Servers are reachable. Here is an example with the command: $ dig 1-2-3-4.625d406a00ac415b978ddb368c0d1289.plex.direct +short 1.2.3.4 $ dig 10-10-10-10.aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa.plex.direct +short 10.10.10.10 where 1.2.3.4 represents a public IP address and 10.10.10.10 a private IP address. The next step for Plex was to provide each user a certificate.
Since each user can have several IPs and thus several Plex subdomains as mentioned above, a valid wildcard certificate was needed. Choosing only a wildcard certificate for.plex.direct would imply that each user would be using the same certificate and thus the same, allowing a Plex user to decode the content of another Plex user. Also using only a certificate would not provide the ability to a certificate if the user had his certificate compromised or if he/she wants to unsubscribe from Plex. As this would have been too expensive for Plex to register directly to a a certificate each time a Plex user subscribes to a Plex account, Plex had to become a registration authority (RA) (also called ). They choose to partner with. This kind of offer is often called a private PKI.
In DigiCert terms, this is called Managed PKI. In this way of configuration, each user domain name will have a wildcard certificate as.plex.direct. Each user's certificate is thus not signed directly by the sub CA of DigiCert (currently DigiCert SHA2 Secure Server CA) anymore, but by Plex directly (Plex Devices High Assurance CA2) which itself is signed by DigiCert root certificates. Plugins Plex Media Server can be extended using plugins, sometimes called 'apps'. These can be installed via a kind of 'app store', a built-in library of free third-party plugins that allow Plex to download content from websites like, and. As of July 2016, there are 131 channels available. This 'app store' is accessible either via a dedicated Plex Media Server section called Channels (previously called Plex Online) or via Plex Home Theater, the old Plex Media Player.
While Plex channels are maintained and supported by community volunteers, only those in the Channels Directory are considered as stable. Even if Plex came from Kodi, these Plex plugins now use a proprietary plugin architecture. They are written in and XML. Many plug-ins for Plex Media Server leverage to display videos from online sources using the same and players that the sources provide for web browsers. This basically means that the server needs to render the streaming video on an offscreen WebKit canvas before capturing it, transcoding it and streaming it to the server.
This software chain sometimes causes issues depending on the server configuration, and on the version of the app in the software chain. Since January 2014, Plex removed support for WebKit based plugins (like Netflix and Hulu) as they couldn't provide a cohesive experience across all platforms with their new client/server infrastructure. API Plex Media Server via its web-based structure has a API returning either XML or responses. This API provides a way for clients to browse and manage media libraries, as well as rich transcode functionality for video, images, and audio and synchronization.
Multiplatform While Plex was initially a Mac OS X-only application, Plex Media Server became available for Windows and Linux too. On May 14, 2011, Plex announced support for Linux.
Three Linux flavors were initially supported: 10.01, 13.1 used in devices, and (NAS from using CPUs). It should also work for other GNU Linux distribution or versions, as the C code is highly portable and the only hard dependency is for -based network discovery. The Linux version of Plex Media Server is reported to work on CPUs of any speed (except if the user wants transcoding) and the resident daemon only uses 16 MB of RAM. Support for Windows has been added with the Laika release on October 28, 2011. Multilanguage On October 5, 2014, Plex added support for translating the media server interface to languages others than English. The localization is hosted at Get Localization and anyone applying either as a volunteer or professional translator can begin to translate the app.
This section may require to meet Wikipedia's. The specific problem is: Contains badly written/out-of-date/unsourced information Please help if you can. (February 2017) Unlike the initial front-end that was based on XBMC open source software, Plex Media Server is now a combination of 10% software and 90% code. The open source parts of the code are mostly used for support of most popular video and audio codecs brought through libraries, such as, (for ), and (from the FFmpeg project). Plex uses the metadata from several free open-source online libraries to automatically find all artwork, media descriptions, and theme music for the entire library.
As of July 2016, Plex uses the following libraries and open source code: cpp-netlib, vo-aac, libfribidi, soci, cjson, simplejson, pyOpenSSL, lxml, expat, libxslt, and some FreeBSD network interface code for real time sockets. Player apps Player apps are Plex's allowing the user to manage and play music, photos, videos and online content from a local or remote computer running Plex Media Server. Plex Web App. Plex Web App: Users can manage their libraries, server settings, and watch content from this browser-based interface The web app client has foundation based on the, but was rewritten using. Before the rewrite, it was only possible to configure the Plex Media Server with it, but support to view and organize collections have been added.
The web UI became a Plex App Client viewer too. The new web app was written by Eric Matthys and Schuyler Ullman, both Plex employees. The new version was aiming at replacing the old manager for Mac OS X written using the Mac OS X and because Windows and Linux versions of Plex didn't have an while the one for Mac OS X was outdated. The web UI was released for all Plex users (not only Plex Pass members) on November 16, 2012. Plex Media Player The Plex Media Player (sometimes called PMP), announced on October 20, 2015, uses hardware acceleration for a consistent user interface across all devices. This player uses as media playback engine, for the media browsing experience and Qt for the multi-platform glue between the media engine and the Chromium web-based interface. Plex's media player is open source.
Plex have helped FOSS projects on which Plex relies on. Plex contributed to MMAL hardware decoder for the and brought improvements to Qt. While Plex Media Player is reported to be open source and its code available on as, not the whole software is actually open source. Only the host parts of the application (mpv, chromium, Qt and the glue between them) can be contributed.
The UI cannot be modified nor corrected by the communities if there are issues. That UI is downloaded as a binary bundle from Plex servers when Plex Media Player is being compiled.
Plex Media Player is developed nearly exclusively by the German, Vincent Lang (@wm4), the primary contributor to the mpv project. Plex Media Player is as of July 2016 in early preview and requires a Plex Pass subscription to access pre-versions of the software. It is compatible with and upwards, and upwards, embedded platforms like the 2 (the Raspberry Pi 1 is not supported due to both performance and resource limitations) and. While Linux is not clearly cited, since Raspberry Pi and NUC uses Linux-based distributions, Linux is compatible. Plex Home Theater (discontinued). An example of the TV Episode interface on Plex.
Includes fan-art background Previously known as Plex Media Center, Plex Home Theater is the software component used for a long time as the front-end media player for Plex's back-end server component Plex Media Server. This component came from the fork from the completely open-source software on May 21, 2008. It is now discontinued in favour of the new. Since Plex Home Theater is based on Kodi, it has a. The old and now obsolete Plex Home Theater is still distributed as open source under the (GPL), with source code on. This client media player was primarily programmed in, and made use of the (SDL) framework with an renderer. Some of the third-party libraries that Plex Home Theater depended on was written in, but are used with a C wrapper and loaded as when used inside Plex.
Since Plex Home Theater was based on XBMC Media Center it shared its flexible and robust. With themes based on a standard base, and personal customization which was very accessible.
Users could create their own skin (or simply modify an existing skin) and share it with others via third-party public websites for XBMC skin trading. On October 28, 2011, support for Windows was announced for Plex Home Theater. That release named Laika had its code rebranched with the latest stable version of XBMC, brought integration with, corrections, support for optical media, for 10-bit video (Hi10P), HTTP Live Streaming and huge changes with regard to episode management of TV series, reducing the time to access content and offering media depending on the context and on the episodes watched. The Laika release came with a new skin. Plex Home Theater was originally using a modified version of the 'MediaStream' skin as its default skin, a skin that was originally designed by Team Razorfish for XBMC.
Sebastian Pitkanen, the author of the Retroplex skin, one of the most popular third party skins, updated the Plex default theme for the Plex release codenamed Laika. Pitkanen is now a Plex employee. Amazon Fire TV Plex announced an application for the, the same day it launched on April 2, 2014.
Android On February 16, 2011, six months after the iOS app release, Plex announced its Android application, but without the same restrictions for free users as the iOS counterpart. On February 11, 2013, a complete Android app rewrite was announced, targeting Android 3.2 and newer with its new Android Design Guidelines, and using new platform feature like Google Cloud Messaging, lock-screen music controls, global search integration. The new app integrated features like Mobile Sync, still called PlexSync at that time. On June 25, 2014, support for the platform has been announced, just on time for the launch of the Android TV platform, announced the day after at the Google I/O. The Android features specific to the TV have been integrated like a redesigned home stream and voice control support. The app received basic trailers and playlists support on July 31, 2014.
The Android TV application can run on the. As of March 20, 2017, free users' playback on Android devices is limited to one minute for music and video, watermark on photos, until the app is unlocked (similar to iOS app), when playing media from a Plex Media Server, as the app cannot play content not created on the device itself without it. Apple TV With the, third-party developers could write their own applications, removing the main limitations of previous models (see above).
This application was built in just 5 weeks, from the moment Apple released the new and API documentation. Apple TV applications can be developed using TVML for the UI or native code. As using native code would have required too much time to develop for the UI, Plex combined advantages of both worlds making a bridge between TVML and native code. XML is sent from the Plex Media Server, and converted to TVML using.
The app received text based subtitles support on December 23, 2015. Chromecast On March 13, 2014, Plex announced free support of Chromecast in its iOS and Android applications. IOS An application was released on August 30, 2010 and provided a way to use iOS devices to remote control a Plex Media Server and view media on the iOS device. In March 2011, the iOS platform received a massive UI refresh. New features included grid views, improved UI around channels, removing second level menu and replaced by filter list. The iPad version got rich new views and tweaked typography.
Support for TV Out, multi-part media, image caching, subtitles and audio stream selection have been added to the app. Setting a subtitle in iOS will be reflected on other Plex app players. A search-as-you-type feature has been implemented. Results from the Plex Media Server appear nearly instantly.
Integration of search results from YouTube and Vimeo have been integrated thanks to a partnership with Videosurf. As that company has been bought by Microsoft, Videosurf's features are not available anymore. On November 19, 2012, the Plex Pass feature Mobile Sync was implemented on iOS. On August 10, 2015, Plex announced a complete rewrite of the app supporting the new features of Plex Pass like Mobile Sync, Cloud Sync, Plex Home, Plex Mix and music and video extras. Despite the rumors that the app was to be completely written using, it is still entirely written in.
This new version requires 8.1 and upwards. The app received basic trailers and playlists support on July 31, 2014. And an update to support text based subtitles on December 23, 2015 LG On September 2, 2010, Plex announced a partnership with to integrate the software component into LG 2011 NetCast™ enabled HDTVs and devices.
Now, only NeCast models from 2013 and models running are supported. Opera TV Opera TV is a browser for set-top boxes and smart TVs. It comes with an extension app store (containing HTML5 web apps) called Opera TV Store. Plex is the first personal media organizer to join the Opera TV Store. The app was announced on December 12, 2014. PlayStation Plex announced their apps for and on December 17, 2014 and were available the same day for Europe and most of Asia. With regard to the formats supported, the app on the PlayStation 4 supports a maximum 1080p resolution.
The PlayStation 3 is limited to 720p when Plex is installed through a SCEE (Sony Europe) PlayStation store. The app supports MP4 as container, H.264 (level 4 or lower) for the video decoding, AAC (m4a) for the sound decoding, all with a maximum bitrate of 20Mbit/s (do not overtake 8Mbit/s is recommended). And are not supported. Roku On May 3, 2011, Plex announced a client app on the Roku, available by installing the Plex private channel.
The app was written by developer Jonny Wray. Only video was supported at first, with support for music and photos part of a later release. A new version of the app supporting new Roku devices (Roku 1/2/3, Roku Stick, and Roku TV) was unveiled on February 24, 2015.
Samsung On August 3, 2012, Plex announced support for Samsung TV and Blu-ray players. The app includes native support for external SRT subtitles without transcoding, and 3D support. Samsung Smart TV / and Blu-ray players (C-Series / D-Series / E(S)-Series / F-Series / H-Series) are supported. Sonos On July 20, 2016, Plex announced product support for devices. Users have the ability to stream their entire Plex Music collection on their own Sonos devices.
The app, called 'Plex for Sonos,' is available as a beta. Users need to register to the Sonos Public Beta Program first and then add the 'music service' to their Sonos Controller either via the Sonos webapp or their mobile apps. Needs to be enabled for using Plex for Sonos.
TiVo DVRs have a Plex app from software version 20.4.7a or higher. VIZIO On October 15, 2014, Plex announced a partnership with in order to have rights to release a Plex application on their devices. The Plex app is available on Vizio TVs from 2013 E/M series with Vizio Internet Apps Plus, or 2014 E/M/P series, or future 4K ones and onwards. Windows On March 30, 2012, Plex announced the availability of Plex for. The app was developed partially by Elan Feingold and another coworker. On December 4, 2012, Plex announced a client application for using the new.
Xbox On October 5, 2014, applications for and were announced, supporting voice and gesture control of the devices. The apps integrate a new home screen suiting the Xbox user interface, and a new movies library based upon viewing habits and user taste. Plex Account Initially unveiled as myPlex on October 28, 2011, the Plex account aims at 3 main purposes, in addition to providing access to Plex forums. Facilitating the connection between a Plex Player App and a Plex Media Server without the hassle need to play with NAT, port redirection, etc.
The user simply needs to sign in on his/her Plex Media Server with his/her Plex Account, and do the same on the Plex client apps (e.g. IOS, Android.), and the connection is done.
This is even working with multiple Plex Media Servers in multiple locations. Providing a watch queue. The user can bookmark a video (local or on the web via supported websites) to watch it later. The queue is available on all clients connected to the user's Plex account.
The following features are supported: saving the progression in TV series, stopping a media on one client and resuming it later on another. Sharing personal media with friends. This feature is offered by specifying an email address or a Plex account username. Zero additional configuration is needed. Any client connected to the users's Plex account can browse and play the shared media. Plex Pass Plex announced on August 28, 2011, a premium version of the service, called Plex Pass, which offers the following advanced features.
Due to increasing premium features and content, the cost of Plex Pass increased to $4.99 / month. The annual and lifetime subscriptions increased too. Mobile Sync Previously known as PlexSync, Mobile Sync is a feature offering synchronization of movies, music and photos with mobile devices either on the local network or via internet. The speed depends on the upload rate of the bandwidth connection. The feature is especially useful when travelling offline or without a broadband connection. The user can sync partially its movies, music or photos collection to their device, in a format readable by the latter (see ). View progression of episodes are synced back to the Plex Media Server when a connection is available again.
The reverse side is also supported with the feature allowing to sync videos, photos and music from a mobile device to the Plex Media Server. The synchronization does support filters. The user can sync everything, limit based on duration on movies already watched or media that has just been added. The synchronization is quite smart with the server already transcoding files when similar content has been watched or already synced. Cloud Sync Cloud Sync is a feature to access cloud storage providers announced on October 14, 2013., and are currently supported.
Support for has been added afterwards and announced on December 13, 2013. Accesses to these cloud providers are defined, revoked and organized in the Plex account on the Plex website. The order of appearance of these accounts are important because items will be uploaded to the cloud storage providers in the order in which they are listed. The feature offers the ability to specify multiple storage providers at once, but Plex currently only supports linking to a single account from each cloud storage provider. This means the user can only connect to only one Google Drive account for example.
Individual limits can be defined for each account. These limits can be storage limits like 'leave 25% of free storage on the account' or be more advanced like 'only sync the newest 20 movies I added to my library'. This synchronization feature allows the Plex Media Server to be shut down completely when the synchronization has finished. The client's apps will be automatically aware of that and stream content from these online accounts instead when the file is available and stored there. When the media server is online again, the progression in episode views will be synced back to the server from the viewer apps.
The Cloud Sync feature is not intended at streaming content directly from these external storage places without having the content locally on the Plex server first. It is not intended at uploading entire Libraries or even large sync selections, but more specific content instead. Plex Mix Plex Mix is a feature allowing music mixes based on moods and lyrics. The music files are automatically fingerprinted and matched against online database to grab up to date high quality metadata like the cover art, artist biography, mood and genres tagging and album extras. Lyrics are synced across devices. Plex Home Plex Home is a feature allowing to have advanced and fast switching between users.
Php 5 3 8 For Readynas X86 Servers
This feature is accessible from the Plex Web App. The first user of Plex is considered as the admin and can create, modify and remove other users. A maximum of 15 additional users can be created. If Plex Home is enabled, each app, device or tool communicating with the concerned Plex Media Server will need to be signed in a Plex Account and the server will have DLNA disabled. Each user can be customized, and managed with fine-grained access controls. A PIN code can be used to switch faster between accounts.
Each users inherits the Plex Pass benefits from the admin. This feature is particularly convenient in a family when a member wants to watch a movie while another wants to watch another TV series episode for example. Parental controls to restrict content to underage users are available.
High quality content Access to high quality movie trailers, cast interviews, and other extras for movies in the library is a feature added on July 31, 2014. The feature also allows to select the number and the kind of trailers to read (the DVD version or the Blu-Ray disk for example).
This was the most requested feature among Plex Pass subscribers. At launch, this feature was fully supported on the Plex Web App and in Plex Home Theater, with basic support for Android and iOS applications.
Full support to these platforms and others came in later releases. This feature release marked the first time Plex Pass subscribers received licensed content.
In that regard, Plex reserved the right to impose viewing limits in the future. Camera Upload Camera Upload is a feature allowing to wireless sync photos only from phones or tablets to Plex Media Server in order to access them from other devices. Privacy On July 2, 2015, Plex revealed the machine hosting their blog and forums had been compromised. Personal information like IP addresses, forum private messages, email addresses and hashed and salted passwords had been accessed.
This access was gained via a vulnerability in their forums software. Following this intrusion, Plex decided to migrate their whole forums to, reducing the maintenance and security burden self-hosting their forums represented. On September 20, 2017, Plex was going to implement a new privacy policy in which it was no longer possible for users of Plex to prevent their user data from being collected. However, in a later privacy policy update, the CEO of Plex, Keith Valory, has stated that they will generalize the playback data and offer users the ability to opt out of sending more specific playback information. See also. (ex XBMC Media Center), the cross-platform open source media player software that Plex is based on., an open source alternative to Plex. porting of Plex for on for.
References. Retrieved 2 July 2016. Retrieved September 11, 2017. April 29, 2008. Retrieved July 10, 2016.
January 15, 2010. Retrieved July 6, 2016.
May 23, 2008. Retrieved March 13, 2009. July 5, 2008. Retrieved July 10, 2016. July 9, 2008. Retrieved July 10, 2016.
July 14, 2008. Archived from the original on July 14, 2008. Retrieved July 10, 2016.
CS1 maint: BOT: original-url status unknown. July 13, 2008. Retrieved July 10, 2016. September 2, 2010.
December 24, 2010. Retrieved July 10, 2016. October 28, 2011. Retrieved July 8, 2016. Anderson, Kevin (2009-10-07).
September 3, 2010. Retrieved July 8, 2016. Retrieved July 26, 2016.
Tobias Hieta @tobiashiet (July 26, 2016). Retrieved July 26, 2016 – via. Retrieved July 26, 2016. January 1, 2015. Retrieved July 26, 2016.
Retrieved July 8, 2016. Retrieved July 7, 2016. November 11, 2008. Retrieved July 8, 2016. November 25, 2008. Retrieved July 8, 2016. July 31, 2014.
Retrieved July 26, 2016. Retrieved July 8, 2016. Retrieved July 8, 2016. March 24, 2010. Retrieved July 10, 2016. August 27, 2010. Retrieved July 10, 2016.
August 30, 2014. Retrieved July 10, 2016. Retrieved July 8, 2016.
August 25, 2015. Retrieved July 8, 2016. Retrieved July 8, 2016. April 30, 2015. Retrieved July 26, 2016. Retrieved July 8, 2016.
Retrieved October 7, 2016. Retrieved July 8, 2016. December 23, 2015. Retrieved July 26, 2016. Retrieved July 7, 2016. January 25, 2015.
Retrieved July 7, 2016. Retrieved July 7, 2016. Retrieved July 7, 2016. June 29, 2009. Retrieved July 6, 2016. March 13, 2011. Retrieved July 10, 2016.
November 10, 2008. Retrieved July 8, 2016. December 23, 2011. Retrieved July 8, 2016. March 12, 2014. Retrieved July 8, 2016.
March 4, 2015. Retrieved July 8, 2016.
April 29, 2015. Retrieved July 8, 2016. May 22, 2014.
Retrieved July 8, 2016. July 22, 2014. Retrieved July 8, 2016. Retrieved July 8, 2016. December 25, 2012. Retrieved July 8, 2016.
April 27, 2010. Retrieved July 8, 2016. March 29, 2015. Retrieved July 8, 2016. March 14, 2011.
Retrieved July 11, 2016. March 16, 2011. Retrieved July 11, 2016.
Retrieved July 8, 2016. January 29, 2014. Retrieved July 9, 2016. August 19, 2014. Retrieved July 9, 2016. Retrieved July 9, 2016.
June 4, 2015. Retrieved July 9, 2016. Elan Feingold @leafmuncher (July 11, 2016). Retrieved July 11, 2016 – via. June 6, 2015. Retrieved July 10, 2016. Retrieved August 15, 2016.
Retrieved July 7, 2016. Retrieved July 7, 2016.
July 15, 2014. Retrieved August 15, 2016. Retrieved July 7, 2016. November 19, 2012.
Retrieved July 11, 2016. May 14, 2011.
Retrieved July 11, 2016. September 20, 2013. Retrieved December 24, 2015. ^ See LICENSE file from Plex Media Server 1.0.0.2261. August 28, 2012. Retrieved July 11, 2016.
November 16, 2012. Retrieved July 11, 2016. Retrieved July 7, 2016. October 20, 2015. Retrieved July 7, 2016. July 13, 2015. Retrieved July 8, 2016.
Retrieved July 7, 2016. Retrieved July 8, 2016. Retrieved July 8, 2016. Retrieved July 8, 2016. October 24, 2015.
Retrieved July 8, 2016. December 24, 2012. Retrieved July 8, 2016.
September 1, 2008. Retrieved July 8, 2016. March 10, 2012. Retrieved July 8, 2016. November 23, 2013. Retrieved July 8, 2016.
April 2, 2014. Retrieved July 26, 2016. September 22, 2016.
Retrieved July 26, 2016. February 11, 2013. Retrieved July 11, 2016. June 25, 2014. Retrieved July 26, 2016.
October 15, 2014. Retrieved July 26, 2016. March 13, 2014. Retrieved July 10, 2016. August 30, 2010. Retrieved July 8, 2016.
March 12, 2011. Retrieved July 1, 2016. March 15, 2011. Retrieved July 11, 2016. August 10, 2015. Retrieved July 9, 2016. September 3, 2010.
Retrieved July 8, 2016. Retrieved July 11, 2016. December 12, 2014. Retrieved July 26, 2016. Retrieved July 26, 2016. Retrieved July 11, 2016. August 3, 2012.
Retrieved July 11, 2016. Retrieved July 11, 2016. July 20, 2016.
Retrieved August 10, 2016. Retrieved August 10, 2016. July 6, 2016. Retrieved August 10, 2016. June 8, 2015. Retrieved July 26, 2016. October 15, 2014.
Retrieved July 26, 2016. March 30, 2012. Retrieved July 11, 2016. October 28, 2011. Retrieved July 1, 2016. February 11, 2016. Retrieved July 6, 2016.
August 28, 2011. Retrieved July 11, 2016. Retrieved 2016-12-04.
December 13, 2013. Retrieved July 26, 2016. Retrieved July 2, 2016. Retrieved July 2, 2016. October 24, 2013. Retrieved July 6, 2016.
Retrieved July 26, 2016. Retrieved July 8, 2016. November 20, 2014. Retrieved July 6, 2016. Retrieved July 6, 2016. July 2, 2015. Retrieved July 26, 2016.
July 11, 2015. Retrieved July 26, 2016. August 19, 2017. Retrieved August 19, 2017. Retrieved September 11, 2017. External links. – official site.