Behind the Screen (Part 1 – Software)

Introduction

Hey guys, As promised here is a look behind the screen of Plex in particular to the software aspect of the server including the networking and NIC Teaming and the episode tracking/naming that keeps everything up to date.

Networking

Note the speed of the adapter being 5.0 GBps rather than the 1.0 GBps for typical gigabit ethernet interfaces. This is due to the NIC Teaming of the several Intel gigabit speed interfaces in my case.

These are the adapters used however they are named differently by the drivers to allow them to run on Windows 8.1 rather than Windows Server as they were initially intended to do. The type of Team I’m utilizing is the Static Link Aggregation which is described as such.

Static Link Aggregation

Static Link Aggregation (SLA) is a performance technology developed to increase throughput between switches or a server and switch. This is accomplished by bundling or channeling several ports together and showing them as a single link. This increases the total bandwidth for the link and provides fault- tolerance in the event of a switch port, cable, or adapter failure. Primary and Secondary adapters can be selected for this team, but are not required. If a Primary adapter is selected, the team will use that adapter’s MAC address. If a Primary adapter is added or changed, the team will reload, causing a momentary loss of connectivity. Configuration notes SLA supports two to eight adapter ports per team. All team members must be linked to the same switch. All team members must run at the same speed. All team members must be connected at full duplex. The switch must be configured for SLA before the team is created. To prevent packet loss, adapters should be added or removed from the team in a link-down stateThis team type is supported on Cisco switches with channeling mode set to “ON”, Intel switchescapable of Link Aggregation, and other switches capable of static 802.3ad. SLA balances all traffic. NOTE: The FEC (Fast EtherChannel) and GEC (Gigabit EtherChannel) team types have been renamed to Static Link Aggregation

Although this configuration only affects LAN traffic, this was the intention. The network is not only used by me and the Plex server but also two other people. As for my computer, its not really a dedicated server but really a gaming computer I use daily.

This enables me to efficently copy the terabytes of data housed and organized through Plex to my NAS for safe keeping and download new content as well as sometimes play a game online. This way, the work is divided between the NIC’s making for a smooth experience for me and the users.

Plex Media Server

Plex Media Server is a piece of software that organizes your media files and makes them viewable online or through your LAN via an easy on the eyes and simple to use interface that takes all those media files and puts a face or a poster to them that is easily recognized.

Another feature that I particularly enjoy is DLNA support which allows DLNA enabled devices to view the server and access it. For example my IPTV box which I use for TV however it is capable of playing media from networked devices that allow it making for a great viewing device on a full TV screen.

For the users, this is the frontend of the server and all they really see.

To download Plex or to find more information, visit https://plex.tv/

Episode Management

While Plex is fantastic for users to view catalogued information and media files, it only offers so much for myself to use to bring the content to you. In its place, for my use I employ a free application called SickBeard  which can be seen below.

Available at https://sickbeard.com/ this free software can rename files using a python script to keep all the media files organized however the impressive features become apparent when you add a show to the system.

Once added, SickBeard will go online and lookup shows that match the folder title and confirm which show it is that you are adding. Next SickBeard will lookup a list of episodes and download fanart, posters, season covers (like you’d see on the Bluray box). You can specify if you want .nfo files to be downloaded and thumbnails to be made for each episode as well.

A specifically useful feature for myself is the ability to allow sorting based on download quality. For example, I aim for HD only content when possible but allow initial downloads to be SD quality as most shows will not be uploaded quickly in HD (due to file size and regional airing limitations). This allows you to get the latest content as soon as its available but store a final version in HD.

Once every hour or whenever you set it to check, SickBeard will use the search provider information you supply to look for content that is available based on airing date and search provider feedback.

SABNZDB

Available for free here https://sabnzbd.org/, SABNZDB is an automated newsreader that uses python scripts for post-processing and server credentials to access your news site of choice and download the .nzb files including block repair, unpacking with password support and multiple notification methods supported including Growl to keep track of the action.

Through API support, SABNZDB communicates with SickBeard in real time and searches for content which then sends URLs of the .nzb files to SAB to finally fetch actual .nzb file and read its contents and download the parts.

A python or .cmd file directs the completed download content to SickBeard to be renamed as programmed  and finally catalogued as local content counting as an episode in the overall show episode count.

Final Words

I hope this quick look into the methods of the server offer insight into a effective method of data acquirement and organization. Contact me for any more details and visit the provided sites for downloads and support. Please donate to these free software developers as this wouldn’t be possible without them.