|
Deprecated
|
MediaArchitecture
Table Of Contents
PiBox Media Systems
PiBox Media Systems provide media services to a network of Raspberry-Pi based devices. The intent is to allow playback of media services to one or more devices using a central server and zero or more distributed players. The network can be connected to an external router for connection to the Internet or the server can be configured as a wireless access point to provide a closed network of PiBox devices. PiBox Media Systems are intended for use with wireless networks though they can be used with wired networks as well. Common hardware and software services
All PiBox Media systems provide both a console UI and a web UI. The console UI provides a collection of PiBox Apps. Each app provides a specific service such as network configuration, date and time, webcams, music and video players, a terminal and even an XM/Sirius player. The web UI provides network configuration support along with managing users. The webcam can be accessed from the console or through the web UI. Remote control services for console apps flow also through the web interface using RESTful APIs. Operating system support is common to PiBox devices. While a small set of wireless chip support is included, only the RTL5370 is fully endorsed due to its stable nature and speed. Extensive research was performed on various Linux kernels with a variety of wifi chips and only the RTL5370 provided reliable for distributed video file access over SMB. The Raspberry Pi 3 builtin WiFi support works adequately as well. PiBox Media Systems are configured, using the Raspberry Pi config.txt firmware configuration file, to only use HDMI and the onboard analog audio output. The intent is to guarantee audio support even if the HDMI device does not support it while targeting newer HDMI display devices. While any wireless keyboard/mouse combination should work, PiBox Media Systems provide specific support for the Favi mini-keyboard. This keyboard is the size of a standard IR remote, integrates both a keyboard and mouse and provides the requisite navigation keys (re: arrow keys) for use of the console UI without a mouse. Authentication
The web UI provides authentication and services for remote access to a PiBox Media System. This includes applications running on 3rd party devices. There is no authentication required on the console. Consumer UI
The console UI is designed to be consumer oriented. This means the interface has large icons for accessing services and does not require the use of a mouse. Navigation is done with the arrow keys of the keyboard. Android Support
Media System devices can be controlled using a mini wireless keyboard/mouse or via an Android application for PiBox application navigation. An Android device can also be used for video playback if a supporting application is installed on the Android device. Only the Android application used for PiBox application navigation is part of the PiBox software suite. Video playback on the Android device must be provided through the use of an SMB-mount application such as ES File Explorer and a video playback application that supports MP4, AVI and potentially other video formats. A web browser Android application can also be used to connect to a PiBox Media Server to access the server's webcam. Apple iOS devices can be used for video playback and access to the webcam if they have supporting applications. However, iOS is not currently tested for use with PiBox. Android apps can interface with PiBox Media Systems using RESTful APIs. The APIs are still will be published and will require authentication through the web UI. Power Considerations
PiBox Media Systems utilizes an external powered 7 port USB hub. The system's USB hub must be powered and provides power to the Raspberry Pi. The hub connects the following devices:
The Raspberry Pi Model B provides enough compute power to support these devices, including hardware accelerated video playback on an HDMI-connected display on the server. However, it lacks sufficient USB ports for these external devices when using more than 1 media stick at a time. Since the additional USB ports will require additional power an external hub is used that will also power the Raspberry Pi. The external hub must include a 5V 3A or greater power supply. This will provide enough input power for the 7 connected devices, including providing power from a single USB port to the USB OTG port on the Raspberry Pi. HDMI output
Media systems provide video output over the HDMI port only. The RCA video port is not supported. Audio output
The analog audio port is used for most audio output, although the HDMI port can also support audio out. Support for Bluetooth audio is a long term design goal. Software services
A Media System exports video files found on media sticks over SMB. Networked players (ie other PiBox Media Systems) mount these automatically if found on the local network. The video formats supported are dictated by the formats supported by the Raspberry Pi's omxplayer application. Video Playback
A Media System utilizes media sticks connected to the USB ports on the Raspberry Pi. However, The Pi's ports are arranged too close for more than one stick to be inserted at a time. This is another reason for use with an external USB humb. Any media sticks inserted into the hub are also exported to all other PiBox Media Systems and will show up immediately under the video player on those devices. |
