Quantcast
Channel: Linux — Plex Forums
Viewing all 7311 articles
Browse latest View live

ubuntu repo busted

$
0
0

So, the ubuntu repo has been broken for me for months, finally getting around to asking about it. Anyone know what's going on?

I'm using the sources line:

deb https://downloads.plex.tv/repo/deb/ public main

but it's failing to read the repo, gets the following error:

W: Conflicting distribution: https://downloads.plex.tv/repo/deb public InRelease (expected public but got )

Create a profile for my specific Android Phone

$
0
0

Hi !

I find that the default Android.xml file is too generic so I wanted to override it with a custom profile.

I have Plex Media Server installed on my QNAP and the profiles are stored here:
/share/CACHEDEV1_DATA/.qpkg/PlexMediaServer/Resources/Profiles

I have created a Profile name SM-A520F.xml (it's a copy of Android.xml with a specific header to identify my phone).

<?xml version="1.0" encoding="utf-8"?>
<Client name="SM-A520F">
  <!-- Author: Plex Inc. -->
  <Identification>
    <!-- Indentify the Samsung A5 2017 -->
    <Header name="User-Agent" substring="SM-A520F" />
  </Identification>

  <TranscodeTargets>
    <VideoProfile protocol="hls" container="mpegts" codec="h264" audioCodec="aac" context="streaming" />
    <VideoProfile container="mp4" codec="h264" audioCodec="aac" context="static" />
    <MusicProfile container="mp3" codec="mp3" id="StereoMusicTranscodeProfile" />
    <PhotoProfile container="jpeg" />
  </TranscodeTargets>
  <DirectPlayProfiles>
    <VideoProfile container="mp4" codec="h264,mpeg4" audioCodec="aac,ac3" />
    <MusicProfile container="mp4" codec="aac" />
    <MusicProfile container="mp3" codec="mp3" />
    <MusicProfile container="flac" codec="flac" />
    <MusicProfile container="ogg" codec="vorbis" />
    <PhotoProfile container="jpeg,gif,bmp,png" />
  </DirectPlayProfiles>
  <ContainerProfiles>
    <VideoContainer name="mp4">
      <Limitations>
        <Match name="part.optimizedForStreaming" value="1" />
      </Limitations>
    </VideoContainer>
  </ContainerProfiles>
  <CodecProfiles>
    <VideoCodec name="*">
      <Limitations>
        <UpperBound name="video.width" value="1920" isRequired="true" />
        <UpperBound name="video.height" value="1080" isRequired="true" />
        <NotMatch name="video.anamorphic" value="1" />
      </Limitations>
    </VideoCodec>
    <VideoCodec name="h264">
      <Limitations>
        <Match name="video.profile" list="baseline|main|high" />
      </Limitations>
    </VideoCodec>
    <VideoAudioCodec name="aac">
      <Limitations>
        <UpperBound name="audio.channels" value="2" />
      </Limitations>
    </VideoAudioCodec>
  </CodecProfiles>
</Client>

How do I know that my device is mapped to SM-A520F.xml and not Android.xml anymore ?
Is there any extra step after creating the profile in the directory ?

Thanx !

Plex Media Server on Minimal Centos 6.5

$
0
0

Hi All,

Well I decided to try something new after running Plex Media Server on my Windows 7 Media Centre (WMC) PC for a couple of weeks. Plex runs very well with my W7MC but there are a few short comings for my setup that have prompted me to try a Linux build, particularly a minimal headless build.

While all information to build a minimal Linux server is available, I didn't find one location that had all of the information, so I thought I would share my current build steps on CentOS. In time I'm hoping to expand this to include the installation of PlexConnect as my main client is an Apple TV 3.

The target audience for this guide are those that are new to a minimal build, specifically a build that is performed on the command line interface. I have tested these steps on CentOS 6.5 and 6.6 minimal installation media. I have tested these instructions purely in a VMWare instance, there are a few things I'm trying to get working before I install I build on bare metal.

This guide assumes that you are installing on a x86 64 bit architecture, not a 32-bit architecture, but I imagine that the steps will be similar.

The scope will cover from downloading CentOS to basic application and server configuration to get Plex running. Please feel free to suggest better solutions or steps - I'm no expert.

Ok, enough talk, to the guide.


Obtain and Install Centos 6.x

First step is to download the Centos Minimal installation media. Go to https://www.centos.org/download/ and select the 'Older Versions' area, as CentOS 7 is the current version. The site will direct you to available mirrors. The ISO file you want to get is name something like "Cents-6.6-x86_64-minimal.iso". Remember to download the appropriate 32-bit or 64-bit iso, this guide assumes you are using the x86_64 architecture. Now burn a copy of the CD if you are installing via physical media if required.

Boot up the PC using the Minimal CD and perform the following steps: (this is verbose for completeness):

  • (Optional) Test the media, yes it will take a couple of minutes, but it will save hours if the media is corrupt.
  • Select the appropriate system language for the CentOS system
  • Select the appropriate keyboard layout, important for those that use a Dvorak Keyboard :P
  • Select 'Basic Storage Devices' (unless you know what you are doing)
  • Select 'Erase Whole Disk' - as the name implies it will wipe you entire drive (I will not be responsible for unintended data loss - if you are not sure STOP now! - this guide assumes you are installing to a fresh / formatted HDD)
  • Name the Host - it is up to you, I use 'pms.localdomain' for Plex Media Server (not for the other common meanings), as long as the name is unique on your network.
  • Important: select the 'Configure Network' option, this will open a Network Manager applet.
    • Important: ensure the 'Connect Automatically' flag is set so after every reboot it will bring up the network.
    • (Optional) Setup a static IP if you have planned out your network, this is recommended, but remember to set the correct IP, Gateway and DNS values - it is not the end of the world to use DHCP, but just more googling :)
  • Set the server's correct Location and Time.
    • Uncheck 'System Clock uses UTC' if your hardware has the correct time and date or leave it checked. If you don't know then uncheck it.
  • Set the root user password. Don't set this to something easily guessed.
  • Select 'Use All Space' as the installation option. Again this will erase your entire drive - make sure you are OK with this.
  • Select 'Write Changes to Disk’ to start the installation process and grab a coffee.


At the end of the installation, CentOS will restart.

Configure Centos 6.x

In this section we will update the system, create and configure the ‘plex’ user that will be used to install and setup Plex Media Server and slightly secure the system. This will be done all within the Command Prompt… but don’t be scared.

To start we need to log in with the ‘root’ user after the PC has restarted. Use the login of ‘root’ without inverted comma’s and the password you gave root during the installation.

pms login: rootpassword: <root’s password>

Firstly we are best to update the system to get the latest Centos packages using the following command:

> yum update

Yum will automatically download and update any package that is currently installed. Yum will prompt you with a few questions, just reply with ‘y’ or ‘yes’ for all questions and you should be OK.

After we have updated all packages next we need to create a ‘plex’ user. This is the user that will install and generally run activities for the Plex Media Server. This will be a general user, but will be setup to run commands as the ‘root’ user if required.

To create the ‘plex’ user we use the following command:

> adduser -c "Plex Media Server User" -d /home/plex -s /bin/bash plex

This command will create a user ‘plex’ that has a home directory of ‘/home/plex/‘ and will be setup with the ‘bash’ shell. Don’t worry if that means nothing to you.

Next we have to give a password to the ‘plex’ user to activate (?) the user. We use the following command to prompt to set a password:

> passwd plex

You will be prompted to set a password and then prompted to confirm the password. This command is also used to change the password of a Linux user. Congratulations, you have created a new user from the command prompt.

Next we need to configure the ‘plex’ user to be allowed to run commands as ‘root’ using ‘sudo’. To do this we need to add ‘plex’ to the list of users that can use the ‘sudo’ command. use the following command to open the configuration file to do this:

> visudo

This will open the /etc/sudoers file in vi, an standard editor in Linux. Vi is not friendly to new users of linux. If you stumble with vi, you can use ’nano’ which is a more friendly editor. To use nano you will need first install with ‘yum install nano’. After yum has installed nano you can open the sudoers file with ‘nano /etc/sudoers’ command without inverted commas.

To add plex to the users you need to find the two lines in the sudoer’s file:

“## Allow root to run any commands anywhere
root ALL=(ALL) ALL”

then you need to add the following line after the line that mentions 'root':

“plex ALL=(ALL) ALL” so the 3 lines look like:

## Allow root to run any commands anywhere
root ALL=(ALL) ALL
plex ALL=(ALL)  ALL

Save the file. That is it, the ‘plex’ user will now be able to use the ‘sudo’ command and run commands as a superuser.

So lets confirm that the ‘plex’ user has been setup correctly. Logout using the following command:

> exit

This will return you to the login prompt, next enter ‘plex’ and the plex password to login in with the new user.

pms login: plexpassword: <plex’s password>

If all is fine you will have a command prompt. Next we need to check that the ‘plex’ user can run the ‘sudo’ command. Try the following:

> sudo pwd

You will be prompted for a password… you need to use the ‘plex’ user’s password. You should get a response of ‘/home/plex’, the home directory of the plex user that was setup with the 'adducer' command. If you got an error then repeat the steps to update the /etc/sudoers file.

At this time you can use a SSH client to access you Plex Media Server, something like the Mac OS X ‘Terminal’ application or Putty on windows is fine. I usually perform the rest of the setup via SSH but you can perform all the steps on the Plex Server locally.

While using SSH to remotely access the Plex Server is helpful it is also recommended to block the ‘root’ user to use SSH remotely. To do this use the following command to open the SSH config file:

> sudo vi /etc/ssh/sshd_config

Again you can use ‘sudo nano /etc/ssh/sshd_config’ if you don’t like vi.

Search for the ‘# PermitRootLogin yes’, delete the hash (‘#’) character and change ‘yes’ to ‘no’. The result should be:

PermitRootLogin no

Save the file. After the next restart root will not be able to remotely login over SSH, but will be able to log in locally.

That is the ‘plex’ user set up!


Downloading and Installing Plex Media Server

Because we are using just the command prompt and Plex Media Service isn’t out of the box linked to a Plex Repository we can’t use the ‘yum’ command. There are ways we can use this but from the forums it appears that the latest version of Plex Media Server is not always available via this route. So we are going to use commands to get the latest version.

Before we can get the Plex, we need to install some applications to allow Centos to download the Plex Media Server package. Run the following command to install the wget application. Note: going forward it is assumed that you are logged in under the ‘plex’ user and is why you will see 'sudo' infront of commands.

> sudo yum install wget

This will install the wget application that can download files using a URL. We also need to get the latest URL for the current version of Plex to download.

I got the download URL by using another PC, going to the Plex downloads section and copying the Link to the current version. Now that we have the URL for the latest version it is time to download. I recommending creating a download’s folder in the ‘plex’ users home directory, but this is optional. To do this use the following commands to create and then open the download directory:

> mkdir ~/Downloads> cd ~/Downloads

Next we want to download the Plex package using:

> wget <URL of the Plex Media Server RPM package>

i.e. (current as of 24th May): Important, please check the current URL, below is an example.

> wget https://downloads.plex.tv/plex-media-server/0.9.12.1.1079-b655370/plexmediaserver-0.9.12.1.1079-b655370.x86_64.rpm

This will download the Plex package.

After the download has completed it is time to install! As we have downloaded the package to our Plex Server we can use the ‘localinstall’ option in yum to install from the downloaded file.

To install plex from the download we use the following command:

> sudo yum localinstall <Plex Media Server RPM package>

Based on the filename from above this would be: (Again check the filename based on the current Plex package)

> sudo yum localinstall plexmediaserver-0.9.12.1.1079-b655370.x86_64.rpm

The installation will take a minute or two. That is it, Plex is installed…. but it is not running, and the Linux firewall will stop clients connecting - Doh! But first let’s check the install.

To start plex we need to start the service using the following command. We only have to do this once after we install, after we reboot the Plex Media Server should start automatically on your Plex Server.

> sudo service plexmediaserver start

That should be it… Plex is running. But what about the firewall? At this time the firewall will block Plex ports.

We will disable the firewall for a moment to check that things are OK. In the final section we will configure the firewall to allow Plex to work as desired.

To disable the firewall temporarily use the following command:

> sudo service iptables stop

Caution: this will disable the firewall, after we have confirmed things are OK we will bring it back up.

Next is to check that we can use a Web Browser on another PC (or tablet, etc) to access Plex. For the purpose of this guide lets assume that the Plex Media Server has an IP of 192.168.1.100. Please change 192.168.1.100 with the IP of your Plex Server

Open a supported Web Browser and enter the following address, for example of the Plex Server having an IP of 192.168.1.100.

http://192.168.1.100:32400/web/

If all is OK then Plex should start. WooHoo. If not, well check the steps above to make sure you haven't missed anything. I would double check that you have disabled the firewall.

Note: previously there has been an issue with Centos 6.x and Plex producing a 404 error. I have seen this before in a desktop Centos install, but not yet in a minimal install <touch wood>. I can’t help here if you see this (yet).

OK, lets reboot the server to ensure that Plex starts up automatically and that the firewall also turned back on. Use the following command to restart:

> sudo shutdown -r now

The command will immediately restart the server.

Once restarted, login with the ‘plex’ user. Now to configure the firewall.


Configuring the firewall to work with Plex

The last step is to configure the firewall so the Server doesn’t block Plex traffic. I found this to be tricky, but this was my first attempt too :)

NOTE: This is my first attempt with iptable (firewall) configuration, I’m assuming that people will have other recommendations and I will gladly update the following to ensure the best configuration.

Assuming that you are logged in with the ‘plex’ user, run the following commands (note that each command should be one line):

> sudo iptables -A INPUT -p tcp -m tcp --sport 513:65535 --dport 22 -m state --state NEW,ESTABLISHED -j ACCEPT
> sudo iptables -A INPUT -p tcp -m state --state NEW -m tcp --dport 32400 -j ACCEPT
> sudo iptables -A INPUT -p udp -m state --state NEW -m udp --dport 32400 -j ACCEPT
> sudo iptables -A INPUT -p udp -m state --state NEW -m udp --dport 32410 -j ACCEPT
> sudo iptables -A INPUT -p udp -m state --state NEW -m udp --dport 32412 -j ACCEPT
> sudo iptables -A INPUT -p udp -m state --state NEW -m udp --dport 32414 -j ACCEPT
> sudo iptables -A INPUT -p udp -m state --state NEW -m udp --dport 1900 -j ACCEPT
> sudo iptables -A INPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT
> sudo iptables -A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT
> sudo iptables -A INPUT -i eth0 -p udp -m udp --sport 53 -j ACCEPT
> sudo iptables -A INPUT -i eth0 -p tcp -m tcp --dport 443 -j ACCEPT
> sudo iptables -A INPUT -i eth0 -p tcp -m tcp --dport 80 -j ACCEPT
> sudo iptables -A OUTPUT -p tcp -m tcp -m state --state ESTABLISHED -j ACCEPT
> sudo iptables -A OUTPUT -o lo -j ACCEPT
> sudo iptables -A OUTPUT -p tcp -m tcp --sport 22 --dport 513:65535 -m state --state NEW,ESTABLISHED -j ACCEPT
> sudo iptables -A OUTPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT
> sudo iptables -A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT
> sudo iptables -A OUTPUT -o eth0 -p udp -m udp --dport 53 -j ACCEPT
> sudo iptables -A OUTPUT -o eth0 -p tcp -m tcp --dport 443 -j ACCEPT
> sudo iptables -A OUTPUT -o eth0 -p tcp -m tcp --dport 80 -j ACCEPT
> sudo service iptables save

This configuration will allow the Plex ports 32400, 32410, 32412, 32414 open. By default port 22 should be open from the base Centos installation. I have also opened DNS (53), HTTP (80) and HTTPS (443) in preparation of PlexConnect.

Again open a supported Web Browser on another PC and check you are able to connect to http://<IP address of Plex Server>:32400/web/ . If so - awesome.


Add you media to your server

Finally time to add your media to your server, and something I will leave up to you. Just remember that the plex user needs to have the right permissions to access your media if you are installing it locally as per the Plex Linux Guide in the FAQs.

I will also leave information about connecting to a SMB share or adding a local/external hard disk to Plex for other guides and posts in the forum. Once I get my Plex Server setup to successfully connect to a SMB mount on my NAS I might update this to cover the steps to install smb and firewall configuration if people will find it helpful.

Conclusion

I hope this guide is helpful for some people, at the very least this post will backup my steps if I need to reinstall :) . Please let me know if you have any other suggestions to improve this process too!

Cheers,
Isomorphic

22/2/15 - Updated RPM Link with current version

24/5/15 - Updated RPM Link with current version

Location of Installation on Ubuntu

$
0
0
Can anyone tell me where PMS is installed to on Ubuntu?

I want to install the Unofficial App store plugin into the Plugins folder and can't find where to put it!

sign in to plex from terminal?

$
0
0

I am having trouble seeing the web app and wondering if i signed in from a terminal would that help?

No MKV Support with Version 1.12.3.4973 ???

$
0
0

Hello team -

Just upgraded Plex to the new Version 1.12.3.4973 and now all my latest MKV files will NOT play.
Ideas?

Help. Plex Remote Access broken on latest version.

$
0
0

Remote access will not stay green for anything. I can see open ports with services running on my WAN interface. I only get an indirect or insecure connection when I am not on the LAN.

I have scoured the forum and tried everything, including deleting the cache and preference file with no lock.

I have a manually configured port forward. My PMS is running on a XenServer VM, Lubuntu 16.04LTS, DHCP reservation for the PMS.

I have a Untangle Appliance as my router, I have tried disabling all firewall settings and and can see no evidence in the Untangle logs that it is blocking traffic.

I use another XenServer VM with PiHole for my DNS Caching and Filtering. I do not see any blocking or failure to forward for any of the requests that my PMS is making. PiHole is forwarding to 8.8.8.8 and 8.8.4.4.

I have had this exact setup for about 4 months and it was working great until very recently. Prior to 4 months ago I was just using a Netgear Nighthawk router. That has been the only change other than system updates. That change happened about 4 months ago and as I mentioned above remote access worked just fine up until a week or so ago.

Any ideas would be great. I can provide logs for anything if needed. I spent a good few hours looking though the PMS logs last night and i wasn't able to find any corresponding helpful advice for any of the errors I was getting. I mostly am getting the "WARN - PubSub: Received notifyConnectivity event with incorrect async identifier" around the time that the remote access is turning red in the settings menu.

I am paying for Plex Pass and I am growing more and more discouraged with this product. I love it, but not having the ability to just stream remotely is a huge set back for me.

Subtitles will not work - tried almost everything

$
0
0

HI,
I want to seek the community's help because I after spending 3 days and googling everything I can find online, there is nothing I did that will allow me to get subtitles.

I've tried:
1. installed Subzero -- nothing
2. tried /Settings/Agents/OpenSubtitles.org -- nothing
3. manually download .srt files and rename the file to match the movie file with an .srt extension --> refresh metadata

Using Version: 1.12.2.4929 on Ubuntu Linux

What else should I try?

Best,

--Avanko


transcoder not playing certain hevc files

$
0
0

So yea i had a movie not work for me some time ago thats encoded in 4k with the hevc codec, recently i had an episode of the flash not play on me either last night. Direct play on my PC works fine from windows but not on the web or chromecast.

If any experts here have an opinion on this would be great, Specifically the episode of the flash s04E18

Removing or Hiding Recently Added

$
0
0

I recently added setup my phone to sync all of my photos and videos to my plex library. I love the idea of this, but seriously do not like that my home screen on all my devices now shows the recently added photos and vidoes. is there a way to hide this (setting or configuration file on the server itself?

Server unreacheable from outside

$
0
0

Hello guys,
I have a dedicated server running Plex on its default port.
SSL is also enabled and working (LetsEncrypt Certificate, green pad correctly showing).
I've been running it for some months so far without any glitch/issues.
After yesterday's update (or today's, depending on your timezone, v1.12.3.4973) I'm receiving the message in subject.
Weird thing is, although the dedicated server is up and running and surely can be accessed from outside, I can still access the web app by using the external IP of my server, so I really don't get it. Is it connected to the internet or not? Can it be seen by my invited friends or not?
I have already restarted my server and the plexmediaserver daemon.
Anyone else is experiencing the same issue after the update?

Thank you in advance.

Francesco

Plex Transcoding Priority of background tasks

$
0
0

Hello 

I notice a major flaw in Plex that degrades performance on any system..

I got like 3000 Movies 4000 Albums and 30 Shows, Plexmediascanner take forever on those machine 3.4GHz I5, plexmediascanner updates its database and this may take a very long time on this setup so i think its better to start those transcode tasks below with low priority. (some preview pictures i assume)

Transcoding Movies should be keept at -5 priority.

It doesn't make sense to run background tasks (preview pictures) at that high priority

Just add nice 10 as start parameter to extract previews the scanning script).

 

[Guide] Plex Media Server with Intel NUC and Ubuntu 16.04 LTS

$
0
0

HARDWARE

  • Intel NUC (BOXNUC7I5BNK, i5-7260U 2,20 GHz, Link)
  • 2 x 8GB DDR4 RAM (CT2K8G4SFD8213, Link)
  • 250GB M.2 PCIe NVMe SSD (Samsung 960 EVO MZ-V6E250BW, Link)

This hardware setup is meant to be an allrounder. Fast enough to transcode multiple movies at the same time, almost completely silent in order to run it in the living room and power efficient in order to run it 24/7. It is able to hardware transcode three H.264 1080p movies at the same time with ~30-35% CPU load. Transcoding a single H.265 4K HDR movie has ~35-40% CPU load.
If you are looking for a single user setup this NUC might be overkill, the NUC i3 with 2 x 4GB RAM should be fine then.


Step 1: Install Ubuntu

  • Update BIOS with latest from Intel's website
  • Install Ubuntu 16.04 LTS 64bit server version
  • Use the following partition scheme (ESP size was suggested by Ubuntu, swap size is much bigger than usual because of RAM transcoding):

    #1: 536MB, ESP, bootable
    #2: 64GB, swap
    #3: 185,5GB, ext4

  • Setup user named plex


Step 2: Install Plex Media Server

  • Add plex repository as source

    • echo deb https://downloads.plex.tv/repo/deb/ public main | sudo tee /etc/apt/sources.list.d/plexmediaserver.list
    • curl https://downloads.plex.tv/plex-keys/PlexSign.key | sudo apt-key add -
  • Install Plex Media Server + dependencies

    • sudo apt-get update && sudo apt-get install avahi-daemon avahi-utils plexmediaserver
    • During installation you will be asked if you want to override the plex repository source with the one from the package. Select yes.
  • Re-enable plex repository source

    • By default the plex repository source from the package is disabled (commented out), enable it in /etc/apt/sources.list.d/plexmediaserver.list


Step 3: Setup NFS and Autofs

  • Install dependencies

    • sudo apt-get install autofs nfs-common
  • Create mount directory and configure Autofs

    • sudo mkdir /data
    • sudo nano /etc/auto.master
    • Append the following line at the end of the file:
/data      /etc/auto.data
  • Create Autofs configuration file for data directory
    • sudo cp /etc/auto.misc /etc/auto.data
    • Append all your mount points at the end of the file, for example:
movies    -fstype=nfs4    <ip-of-your-nas>:/volume1/Movies
music     -fstype=nfs4    <ip-of-your-nas>:/volume1/Music
  • Restart Autofs

    • sudo systemctl restart autofs
  • All your mount points are now available at /data/...

  • Autofs will automatically unmount all mount points if there is no access within 5 minutes and remount if you try to access the mount point. You can keep ghost references to the mount points by adding --ghost in auto.master at the end of the appended line


Step 4: Configure Plex Media Server

  • Open http://<ip-of-your-server>:32400/web in your browser and configure your server


Step 5: Setup RAM transcoding

  • Create transcoding directory

    • sudo mkdir /tmp/transcoding
  • Setup the system to mount the RAM disk on every boot

    • sudo nano /etc/fstab
    • Append the following line:
tmpfs    /tmp    tmpfs    defaults,noatime,nosuid,nodev,noexec,size=64G,mode=1777    0    0
  • Grant writing permissions for the transcoding directory

    • sudo chown -R plex:plex /tmp/transcoding
  • Use /tmp/transcoding in Plex Media Server > Settings > Server > Transcoder > Temporary directory


Additional notes / tips

  • In order to update plex media server it is enough to run the system update: sudo apt-get update && sudo apt-get upgrade
  • If you setup a DDNS service for your server consider to configure the Ubuntu firewall. In that case please check out the Plex reference for which ports you need to allow

Transcoding priority of background tasks - Athlon X4

HW Transcoding Performance Comparisons

$
0
0

Curious about HW Transcoding Performance of different video cards. Figured this might be a good place to start.

For comparison sake, we would need to specify:
CPU or GPU used: (cuvid for nvidia cards, qsv for intel hd integrated gpu on cpu, etc)
FFMPEG command line used.
Probably good to expose some random test video everyone can get access to to benchmark against? But then we'd need multiple video files if we wanted to test different scenarios, ie h264, h265 encodings, etc.

And what exactly do we use for the benchmark comparison numbers. What I've found as the easiest way to compare personally and maybe I'm completely misreading this, is the multiple it transcodes at. Ie, when I transcode using "ffmpeg -hwaccel cuvid -i test.mkv -c:v h264_nvenc -c:a copy -preset slow out.mkv" I end up with speed=8.57x on my quadro k2200, and speed=2.22x on my gtx 660 ti.

I also know by doing multiple transcodes a the same time, the speed generally halves. So only real point in doing multiple transcodes is doing 3 to test if your video card is limited to 2 transcodes as most gtx and quadro < k2000 are. Ie, my k2200 can transcode 8 streams at around x1, my gtx 660 ti is limited to 2 streams at 1x, 3rd stream throws an error because its limited to 2.

So in the interest of helping others with creating hw transcode threads, would it be beneficial to setup some standard benchmark and result thread here to get results from different video cards or does this already exist perhaps else where (even better!)?


Plex no longer showing activity via plex web when scanning or user watching...

$
0
0

In a nutshell if a user is streaming something it does not list active users in the Status > Now Playing area (no lit icon with number of users in top right either). If I run a Library scan the little refresh icon spins for a sec then goes away...even though the library scan did fire off and is running.

This is kind if annoying and would be unbearable if I wasn't using plexpy/tatulli as those correctly show streams etc.

Any ideas why this happened and how to fix it?

I am on newest PMS release (Version 1.12.3.4973 ).

Thanks!

[Ubuntu 17.10] Repo not available

$
0
0

After upgrading my server to Artful, the repo stopped working. I guess I should have waited a bit more and someone is already working on it, but just in case:

$ echo deb https://downloads.plex.tv/repo/deb ./public main | sudo tee /etc/apt/sources.list.d/plexmediaserver.list
deb https://downloads.plex.tv/repo/deb ./public main
$ curl https://downloads.plex.tv/plex-keys/PlexSign.key | sudo apt-key add -
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 3072 100 3072 0 0 3072 0 0:00:01 --:--:-- 0:00:01 10893
OK

$ sudo apt-get update
Hit:1 http://se.archive.ubuntu.com/ubuntu artful InRelease
Hit:2 http://se.archive.ubuntu.com/ubuntu artful-updates InRelease
Hit:3 http://se.archive.ubuntu.com/ubuntu artful-backports InRelease
Hit:4 http://security.ubuntu.com/ubuntu artful-security InRelease
Ign:5 https://downloads.plex.tv/repo/deb ./public InRelease
Hit:6 https://apt.syncthing.net syncthing InRelease
Err:7 https://downloads.plex.tv/repo/deb ./public Release
404 Not Found [IP: 104.20.7.9 443]
Reading package lists... Done
E: The repository 'https://downloads.plex.tv/repo/deb ./public Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

PMS kernel requirements

$
0
0

I'm currently running plexmediaserver-1.12.2.4929 Centos 6.9 and am planning to upgrade to CentOS 7.
I keep on seeing comments about the kernel being too old which confuses me as my current configuration works just fine, and the C6.9 kernel is even older than the C7 kernel
So tell me what is too old and why?

What am I missing for HW Acceleration?

$
0
0

I have a Fedora 27 system with dual Xeon E5-2670 which were not capable of Intel QSV so I went with a GeForce 1030 to try out HW acceleration. So far, no luck and I was hoping you all could help.

lspci

[root@stream01 Logs]# lspci | grep -i nvidia 81:00.0 VGA compatible controller: NVIDIA Corporation GP108 [GeForce GT 1030] (rev a1) 81:00.1 Audio device: NVIDIA Corporation GP108 High Definition Audio Controller (rev a1)

dmesg

[root@stream01 Logs]# lspci | grep -i nvidia 81:00.0 VGA compatible controller: NVIDIA Corporation GP108 [GeForce GT 1030] (rev a1) 81:00.1 Audio device: NVIDIA Corporation GP108 High Definition Audio Controller (rev a1) [root@carniflix-stream01 Logs]# dmesg | grep -i nvidia [ 3.812105] nvidia: module license 'NVIDIA' taints kernel. [ 3.827444] nvidia-nvlink: Nvlink Core is being initialized, major device number 238 [ 3.827974] nvidia 0000:81:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=io+mem [ 3.828198] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 384.111 Tue Dec 19 23:51:45 PST 2017 (using threaded interrupts) [ 3.848085] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms 384.111 Tue Dec 19 22:56:18 PST 2017 [ 3.860962] [drm] [nvidia-drm] [GPU ID 0x00008100] Loading driver [ 3.860965] [drm] Initialized nvidia-drm 0.0.0 20160202 for 0000:81:00.0 on minor 0 [ 4.042521] input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:80/0000:80:03.0/0000:81:00.1/sound/card0/input4 [ 4.042568] input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:80/0000:80:03.0/0000:81:00.1/sound/card0/input5 [26014.028896] nvidia-uvm: Loaded the UVM driver in 8 mode, major device number 237 [26014.486327] caller os_map_kernel_space.part.2+0x6d/0x80 [nvidia] mapping multiple BARs

modinfo nvidia

[root@stream01 Logs]# modinfo nvidia filename: /lib/modules/4.14.13-300.fc27.x86_64/kernel/drivers/video/nvidia.ko alias: char-major-195-* version: 384.111 supported: external license: NVIDIA srcversion: EB07FB20BD3656BF1198872 alias: pci:v000010DEd00000E00sv*sd*bc04sc80i00* alias: pci:v000010DEd*sv*sd*bc03sc02i00* alias: pci:v000010DEd*sv*sd*bc03sc00i00* depends: name: nvidia vermagic: 4.14.13-300.fc27.x86_64 SMP mod_unload parm: NVreg_Mobile:int parm: NVreg_ResmanDebugLevel:int parm: NVreg_RmLogonRC:int parm: NVreg_ModifyDeviceFiles:int parm: NVreg_DeviceFileUID:int parm: NVreg_DeviceFileGID:int parm: NVreg_DeviceFileMode:int parm: NVreg_UpdateMemoryTypes:int parm: NVreg_InitializeSystemMemoryAllocations:int parm: NVreg_UsePageAttributeTable:int parm: NVreg_MapRegistersEarly:int parm: NVreg_RegisterForACPIEvents:int parm: NVreg_CheckPCIConfigSpace:int parm: NVreg_EnablePCIeGen3:int parm: NVreg_EnableMSI:int parm: NVreg_TCEBypassMode:int parm: NVreg_UseThreadedInterrupts:int parm: NVreg_EnableStreamMemOPs:int parm: NVreg_MemoryPoolSize:int parm: NVreg_RegistryDwords:charp parm: NVreg_RegistryDwordsPerDevice:charp parm: NVreg_RmMsg:charp parm: NVreg_AssignGpus:charp

HW Acceleration Errors

Jan 26, 2018 11:29:30.955 [0x7f0b93bff700] ERROR - [FFMPEG] - OpenEncodeSessionEx failed: unsupported device (2) Jan 26, 2018 11:29:31.130 [0x7f0b93bff700] ERROR - [FFMPEG] - No NVENC capable devices found Jan 26, 2018 11:29:31.130 [0x7f0b93bff700] ERROR - [FFMPEG] - Failed to initialise VAAPI connection: -1 (unknown libva error). Jan 26, 2018 11:29:31.130 [0x7f0b93bff700] DEBUG - Codecs: hardware transcoding: opening hw device failed - probably not supported by this system, error: Input/output error


As I try to show above, I have installed the latest nvidia linux drivers. A repo search for vaapi led me to gstreamer1-vaapi-1.12.4-1.fc27.x86_64 which is installed but no idea if it's correct. libva is version libva-1.8.3-3.fc27.x86_64 which leads me to this: https://forums.plex.tv/discussion/281177/intel-updates-vaapi-driver-for-linux
Does this mean I should be waiting until libva 2.1 before proceeding to bang my head against this further?

Thanks for any help!

EasyAudioEncode on linux ubuntu x86_64 not being utilized

$
0
0

When trying to play a video with EAC3 audio from a Ubuntu 16.04 PMS server it just waits..
Can see the Plex Transcoder process but no EasyAudioEncoder process

This is with Ubuntu 16.04 trying the following PMS verisions
plexmediaserver_1.11.3.4803-c40bba82e_amd64.deb
plexmediaserver_1.12.0.4829-6de959918_amd64.deb
plexmediaserver_1.12.1.4885-1046ba85f_amd64.deb
plexmediaserver_1.12.2.4929-29f6d1796_amd64.deb

note: that plexmediaserver_1.12.1.4929 running on windows 7 works correctly with my clients
I have not tried anything other then look at settings etc.. since its the only correctly working version I have.

It seems to be a Ubuntu / PMS issue with Easy Audio Encoder..

How do we fix this?

Viewing all 7311 articles
Browse latest View live


Latest Images

<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>