Top 10 Plex Myths Debunked

Top 10 Plex Myths Debunked (#6 Will Blow Your Mind!)

Taken from: https://www.reddit.com/r/PleX/comments/5miq8s/top_10_plex_myths_debunked_6_will_blow_your_mind/

Here are 10 of the most common misconceptions about Plex that I have seen posted on r/Plex, which mostly relate to Plex Pass, transcoding, and streaming issues. Hopefully this will help answer a lot of questions, especially for people new to Plex. If you have any other myths, please post them in the comments below and maybe I’ll include them in another post next time.

All of the myths below are FALSE as of January 06, 2017. I will try to remember to update this post if anything changes.


Myth #1: You need Plex Pass in order to share your server.Status: FALSE

You can share your server with anyone you want for free. You just need to go to your server Settings > Users > Friends > Invite Friend. You can invite someone by their Plex username, or by their email address. If they do not have a Plex.tv account, they will be asked to sign up through the email invite. You do not need to set up a Plex Home to share your server. All users will have their own watched/unwatched statuses.

Note: You can select which libraries to share with each user by clicking on the pencil icon beside their username, selecting your server on the left, and unchecking “All Libraries”.

Note: You can share your server with up to a maximum of 100 friends.

Related article: Create a New Share


Myth #2: You need Plex Pass in order to stream remotely.Status: FALSE

You can access your server remotely (outside your local network) for free. You just need to go to your server Settings > Server > Remote Access > Enable Remote Access. The most common reasons that it doesn’t work are:

  • You have not assigned a static IP address for the server machine.
  • You have not forwarded a port in your router and/or UPnP is disabled or failing.
  • You have not allowed Plex through your machine’s firewall.
  • You have not claimed your server by signing into your Plex.tv account.

Once remote access is enabled, you will be able to stream from your Plex server by signing into any of the Plex apps using your Plex.tv account.

Related article: Enabling Remote Access for a Server

Related article: What network ports do I need to allow through my firewall?

Related article: Troubleshooting Remote Access


Myth #3: You need Plex Pass in order to use the mobile apps.Status: FALSE

You can unlock the mobile apps (Android app, iOS app, Windows Phone app, and Windows app) using one of the two following methods:

  1. Pay for the one-time in-app purchase of $5 (per platform, per app store account)
  2. Sign up for a Plex Pass (all mobile apps will be unlocked for the duration of your Plex Pass).

Note: Paying the in-app-purchase does not give you Plex Pass benefits.

Note: Unlocking the app on one platform (Android/iOS/Windows) will unlock the app for all devices on the same platform as long as the devices use the same app store account (Google/Amazon/Apple/Microsoft).

Note: Friends of your server will need to unlock their own mobile apps. Users in a Plex Home will all have unlocked apps.

Related article: Plex: Free vs Paid

Related article: Unlocking or Activating Plex for Android

Related article: Unlocking or Activating Plex for iOS


Myth #4: Your friend needs Plex Pass in order to sync content from your server.Status: FALSE

Anyone can use mobile sync on your server as long as the server owner has Plex Pass and the server is claimed by that account. You can allow Friends or Plex Home users to sync from your server by going to your server Settings > Users > My Home or Friends > Click the pencil icon beside the username > Restrictions > Allow Sync. The thing that confuses people the most is that your friends need to unlock the mobile app in order to sync (see Myth #3).

Related article: Mobile Sync Overview

Related article: Mobile Sync for Shared Users


Myth #5: Plex only supports certain file formats.Status: FALSE

Plex can play nearly any media file you throw at it (except image formats), and will convert it on-the-fly if required. A media file typically consists of three parts: a video stream, an audio stream, and a container that holds it all together. The video and audio streams can be encoded using various codecs. Some examples include:

  • Containers: mp4, m4v, mkv, avi, etc.
  • Video Codecs: H.264/x264/AVC, H.265/x265/HEVC, DivX/Xvid, WMV, VC-1, mp4, etc.
  • Audio Codecs: AAC, AC3, DTS, DCA, mp3, vorbis, WMA, FLAC, etc.

The most important part is figuring out the codecs supported by your Plex client (the app/device you are using to watch your media). Of course there are many other factors to consider as well: resolution, bitrate, framerate, encoding level, network bandwidth, etc. Depending on these factors, your media will either direct play, direct stream, or transcode. (Note subtitles are not mentioned here, see the link for more details.)

  • Direct Play: The client supports the container, video stream, and audio stream natively. The Plex server just sends the media file as-is to the client. This uses very little CPU power.
  • Direct Stream: The client supports the video stream and audio stream, but not the container. The Plex server remuxes the file before sending it to the client (copies the video stream and audio stream into a compatible container). This uses very little CPU power.
  • Transcode: The client does not support the video stream and/or the audio stream. The Plex server re-encodes the video, audio, or both into a compatible format. Transcoding video uses a lot of CPU power, but transcoding audio uses little to moderate CPU power.

The Plex client determines if transcoding is required by the server, (unless you have enabled bandwidth limits on your server). If you have a weak CPU, then you may want to store your media in format that is compatible with your clients in order to reduce transcoding. The most widely supported format that will direct play on most clients is:

  • Container: mp4
  • Resolution: 1920×1080 or lower
  • Video Codec: H.264 (level 4.0 or lower)
  • Video Framerate: 30fps
  • Video Bit Depth: 8
  • Audio Codec: AAC
  • Audio Channels: 2
  • Bitrate: 20Mbps or lower

Related article: How are Direct Play, Direct Stream, and Transcoding different?

Related article: Streaming Media: Direct Play and Direct Stream

Related article: Why are ISO, VIDEO_TS, and other Disk Image Formats Not Supported?


Myth #6: Your stream will not stutter as long as your bandwidth is greater than or equal to the bitrate of the file.Status: FALSE

The bitrate that you see for most files is the average bitrate for the entire file. For variable bitrate (vbr) files, the actual bitrate can drop down very low for scenes with fewer details or no movement, but it can also spike up to several times the average for fast action scenes. These high bitrate scenes will cause your stream to stutter if you do not have sufficient bandwidth. You can read more about how Plex analyzes your media bitrates here. This also does not account for overhead for other things using the connection such as downloading, games, etc., or the ability for the client to buffer ahead to prevent stuttering.

Note: Media files can also be encoded using constant bitrate (cbr).

In addition, if you are streaming remotely, an online speedtest does not necessarily mean you are getting that speed between you and your Plex server. The best way to test the real-world speed between your remote client and server is to transfer a large file and monitor the transfer speed, or set up Speedtest Mini on your server.

Note: Stuttering can also occur if you do not have enough CPU power to transcode the file (see Myth #8).

Related article: Server Settings – Bandwidth and Transcoding Limits


Myth #7: Plex will not transcode if the streaming quality is set to “Original”.Status: FALSE

The streaming quality setting only determines the target resolution and bitrate the server should use for the stream. Therefore, selecting “Original” quality just tells the Plex server to use the file’s original resolution and bitrate. Compatibility of the file with your client will still cause it to direct play, direct stream, or transcode (see Myth #5). This applies when streaming on your local network and when streaming remotely.

Changing the streaming quality to a lower value will always result in transcoding. This can be used to reduce the bitrate of the stream due to limited available bandwidth (see Myth #6).

Note: Most Plex clients default to 720p 4Mbps for the remote quality setting.

Related article: How do I choose the right Streaming Quality in an app?


Myth #8: You do not need a powerful server because the Plex clients can transcode.Status: FALSE

Transcoding is always done by the server, and requires a decently powerful CPU. The general rule of thumb is a 2000 passmark score for each 1080p/10Mbps stream and 1500 passmark score for each 720p/4Mbps stream. You can find your CPU’s passmark score on cpubenchmark.netThe Plex client determines if transcoding is required by the server, (unless you have enabled bandwidth limits on your server). Plex clients do not need a very powerful CPU as they only need to receive the (transcoded) stream from the server.

Note: Transcoding H.265/HEVC and 4k content requires significantly more CPU power than the rule of thumb above.

Note: A powerful CPU on the server is not required if your clients can direct play/direct stream your media (see Myth #5).

This is why running using a Raspberry Pi as a Plex server can result in very poor performance, as the CPU is not powerful enough to do any transcoding. However, using the Raspberry Pi as a cheap, and very low power client with RasPlexOpenPHT, or Embedded PMP, will work great. These clients also support a wide range of file formats, so your server will do less transcoding (see Myth #5).

Related article: Transcoding Media

Related article: What kind of CPU do I need for my Server?


Myth #9: Your media must be stored on the Plex server.Status: FALSE

You can store your Plex media on any device you want, as long as the Plex server can access it. This includes on the server itself, on external USB hard drives, network attached storage (NAS) devices, and even remotely on a cloud service, or any combination of the above. You can have your media spread across different storage locations and add multiple folder to each library in Plex.

Note: You do not need to install Plex Media Server on the NAS if you are only using it as storage. If you do store your media on a device separate from the server, a wired connection is recommended for the best performance.

Note: Plex metadata will always be stored on the server.

Related article: Is Plex Media Server on a NAS Right for Me?


Myth #10: Streaming from your Plex server at home uses the internet to stream.Status: FALSE (-ish)

Streaming from within your local network does not require an internet connection. Local streaming does not go “out to the internet, and back in”, it will work offline, and will not count towards ISP data caps. You can test yourself this by disconnecting your internet modem or unplugging your internet cable. Of course if your network is not setup properly, then there may be a chance that your stream will use the internet.

Note: Some device/app do require an internet connection to stream function: Apple TV, Chromecast, Smart TVs, PlayStation, Xbox, and TiVo. Edit: To clarify, these clients require an internet connection for certain parts of the app to work. The media streaming is still local and does not use your internet connection.

Related article: Internet and Network Requirements


I feel that I need to add to this myth due to the massive amount of misinformation from the recent Plex.tv outage on New Years. There is a difference between streaming and authentication when Plex.tv is down.

  • Authentication (i.e. signing into your account) does require an internet connection and Plex.tv to be working. Most Plex clients will cache your login, so as long as you remain logged in, you will still be able to stream (locally and remotely) when Plex.tv is down.
  • Authentication on the server machine (i.e. 127.0.0.1 or localhost) is always disabled (except for Plex Home, see below). If your server is headless or on a different network, you can access your server as if it is local by using a SSH tunnel.
  • You may disable authentication on your local network if you wish, but this is not recommended as it exposes your server settings to everyone on your network. This can be used to temporarily bypass authentication when Plex.tv is down.

Related article: Installation

Related article: Network

Plex Home exception:

  • An internet connection and working Plex.tv is required if you are in a Plex Home with Fast User Switching enabled. However, if you have “Automatically Sign In” enabled for your app, you can continue to stream from the previously signed in user. If you try to switch to a different user in your Plex Home, you will get locked out until you can re-authenticate with Plex.tv.

Posted

in

by

Tags:

Comments

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.