UPnP Discussion (Talk:UPnP)
UPnP standard protocols has the potential of replacing all communication (including data control and /audio/video streaming) between MythTV back-end (server-side) and front-end (client-side). UPnP even has a 'extendable' feature where the application developer could add extra UPnP commands which are not in the standard UPnP specifcitions, thus covering every existing and future connectivity and communication needs between the MythTV back-end and the MythTV front-end.
Other info needed?
This article is a great overview of UPnP, but I think some more information in the context of how MythTV interacts in UPnP mode would be very useful. I think many people looking here for information will be MythTV users who are considering adding a UPnP media extender. Some relevant topics would be: What is the user interface like (ideally with screenshots of the menus, filenames and general usage experience)? What do you lose (gain?) when using a UPnP frontend?
Update May 5, 2007
Individual pages are being created for hardware UPnP players here: UPnPClientInfo
All UPnP AV (UPnP = Universal Plug and Play Protocol, and AV = Audio/Video) connectivity and communication protocols could also make MythTV be fully UPnP compliant on both the back-end (server) side and the front-end (client) side. So that both MythTV's back-end and front-end would be intercooperative with other UPnP servers and clients, (then especially other HTPC applications, both open sourced ones and closed source commersial ones, thus the end-user can choose the best 'back-end' and the best 'front-end' which suits their needs, like a MediaPortal back-end, or a XBMC front-end together with MythTV). For more information see MythTV developers notes on UPnP.
- Note! UPnP could be implemented one or more native feature(s) or one or more plugin(s):
- UPnP AV MediaServer - which is the UPnP-server (a 'slave' device) that share/stream media-data (like audio/video/picture/files) to UPnP-clients on the network). Now a UPnP AV MediaServer has already been implemented into MythTV back-end but the code classes could be updated according to the v2.0 specifications to be UPnP v2 compliant.
- UPnP SSDP Discovery Service in both MythTV back-end and front-end to make the MythTV and MythTV auto-discover each other. If not into to both then at least into the MythTV front-end to let it (and other UPnP-clients) auto-detect the MythTV back-end over a local-network.
- UPnP Remote User Interface (RUI) server/client (in MythTV back-end and front-end respectivly) - which recieves/sends control-commands beween the UPnP-server and UPnP-client over network, (like record, schedule, play, pause, stop, etc.). With UPnP RUI in both MythTV back-end and front-end, the front-end can control/command the back-end via UPnP, and since UPnP is a standard other 'front-ends' which also feature UPnP RUI can also control/command the MythTV back-end, and the MythTV front-end can control/command other 'back-ends' if they feature UPnP RUI.
- UPnP MediaServer ControlPoint - which is the UPnP-client (a 'master' device) that can auto-detect UPnP-servers on the network to browse and stream media/data-files from them. Should be implemented into
- UPnP MediaRenderer DCP - which is a 'slave' device that can render content.
- UPnP RenderingControl DCP - control MediaRenderer settings; volume, brightness, RGB, sharpness...).
This page has a lot of good info but it could use some reorganization. I think the intent of the page is to be an overview of UPnP but has ended up with more detailed information. For example, information specific to particular UPnP clients should be on the page for the specific device. If there are no objections, I'd like to work on this page and improve its layout, etc. MythMike 00:04, 20 February 2010 (UTC)