I have just noticed as of one of the latest updates none of my plex clients direct play from the QNAP version of PLEX Server. I have a SHieldTV as well and the clients all direct play from that using the same media library files. The side by side test validates that something is no longer playing direct on plex for QNAP.
It USED to direct play all the time, now no matter what the file is it transcodes. Anyone else notice this? I am testing 100% on the local LAN as well with the clients and the ShieldTV
well that the deuce? Running the latest public code. Even in browser is transcoding…quality is junk. Started noticing it a about a week ago, but not sure i have access to previous versions to roll back until I see where it works again.
not sure. I know there has been some and they removed the ability to force, but the same FireTV client is direct play from other server just not QNAP. SO that would indicate something broken on the QNAP service vs the cloud and the SHield TV service.
I have literally tried the exact same files from the exact same client on
QNAP - Transcodes
ShieldTV - Direct
Plex Cloud - Direct
This really smells like a QNAP version update broke the ability to direct play the same exact files that the other 2 servers can direct play from the exact same test client. There is no other explanation.
Anyone here have some of the previous version before Dec 2017? Only way I can validate this theory is to get those but plex no longer allows access to previous version…which is garbage as well to troubleshoot stuff like this.
Please submit logs taken after restarting PMS and reproducing the problem, as stated in the previous link. There are many network errors in your logs and the startup sequence can help identify its cause.
Restarted, reproduced. Side by side of three servers, all the same files,
Cloud - Direct Play as expected
ShieldTV - Direct Stream as expected
QNAP - Transcoding (no reasonable explanation why it is thinking it needs to transcode)
Jan 15, 2018 10:55:15.068 [0x7fb72d4f0800] DEBUG - Network interfaces:
Jan 15, 2018 10:55:15.068 [0x7fb72d4f0800] DEBUG - * 1 lo (127.0.0.1) (loopback: 1)
Jan 15, 2018 10:55:15.068 [0x7fb72d4f0800] DEBUG - * 4 eth3 (192.168.201.4) (loopback: 0)
Jan 15, 2018 10:55:15.068 [0x7fb717959700] DEBUG - NetworkInterface: Watching for changes on the interfaces.
Jan 15, 2018 10:55:15.068 [0x7fb72d4f0800] DEBUG - * 5 eth2 (192.168.201.2) (loopback: 0)
Jan 15, 2018 10:55:15.068 [0x7fb72d4f0800] DEBUG - * 8 bond0 (192.168.100.2) (loopback: 0)
Jan 15, 2018 10:55:15.068 [0x7fb72d4f0800] DEBUG - * 11 qvs0 (169.254.100.100) (loopback: 0)
Jan 15, 2018 10:55:15.068 [0x7fb72d4f0800] DEBUG - * 12 docker0 (10.0.5.1) (loopback: 0)
Jan 15, 2018 10:55:15.068 [0x7fb72d4f0800] DEBUG - * 13 br0 (192.168.120.2) (loopback: 0)
Jan 15, 2018 10:55:15.068 [0x7fb72d4f0800] DEBUG - * 14 lxcbr0 (10.0.3.1) (loopback: 0)
In this situation PMS considers LAN 192.168.201.x local. Therefore, when you try to access from IP 192.168.100.144 this is considered a remote access, and may trigger transcoding (depending on the bitrate limits that you specify in PlexWeb). In your case transcoding is triggered:
Jan 15, 2018 10:55:35.716 [0x7fb716ab3700] DEBUG - Streaming Resource: Reducing playback quality for 7619kbps stream bitrate: video resolution to 1920x1080, audio channels to 2, quality to 8
Jan 15, 2018 10:55:35.716 [0x7fb716ab3700] DEBUG - MDE: analyzing media item 32025
Jan 15, 2018 10:55:35.716 [0x7fb716ab3700] DEBUG - MDE: E10 - The Informant: Direct Play is disabled
Jan 15, 2018 10:55:35.716 [0x7fb716ab3700] DEBUG - MDE: E10 - The Informant: media must be transcoded in order to use the dash protocol
Jan 15, 2018 10:55:35.716 [0x7fb716ab3700] DEBUG - MDE: E10 - The Informant: no direct play video profile exists for http/mkv/h264
Jan 15, 2018 10:55:35.716 [0x7fb716ab3700] DEBUG - MDE: E10 - The Informant: no direct play video profile exists for http/mkv/h264/eac3
Jan 15, 2018 10:55:35.716 [0x7fb716ab3700] DEBUG - The Informant - video.bitrate limitation applies: 8383 > 7393
Jan 15, 2018 10:55:35.716 [0x7fb716ab3700] DEBUG - The Informant - audio.channels limitation applies: 6 > 2
Please read Q21 in QNAP FAQ. It will help you parametrize the network interfaces in a “Plex friendly” way. Some add’l instructions:
Do not define any NIC in bridge mode (you have a br0)
Please assure that all docker, lxcbr, … interfaces are defined after the first eth (or bond) address
I have read the FAQ and challenge is I use the QNAP for some other Lab connectivity for stuff. Once you pointed out the 192.68.201.x was being considered local I added the .100.x network to the settings as “Local” and seemed to go back to direct stream.
I realize the FAQ states NOT to connecto more than one NIC, but I cannot do that in my case as since the QNAP does not support VLAN trunking I have to have different ports on different subnets. I also know there is some long standing requests to BIND plex to an interface which has never yet been implemented. It would actually solve this as I would bind it to one of the interfaces. I have noticed on restarts it has bound to the 201, also the 120 network, etc so it’s a bit random there. Once adding all subnets on the LAN as “Local” (most if not all clients are on the .100 net) I was able to get direct stream/ direct play.
@colotti said:
I realize the FAQ states NOT to connecto more than one NIC
Not exactly, you are free to connect more than one NIC. I agree that the instructions to do it are very simple and do not cover complex cases like your’s, but we’ve opted to leave complex cases to be answered in individual posts.
I have noticed on restarts it has bound to the 201, also the 120 network, etc so it’s a bit random there
We are chasing this situation with development in order to establish a criteria to always pick the same one. I hope to have it solved in the future (don’t know when) https://forums.plex.tv/discussion/45480/bind-to-specific-interface-only/p4
This feature request has not been considered by Plex Inc. yet. What I say ^^^ is a possible mitigation effort.
Once adding all subnets on the LAN as “Local” (most if not all clients are on the .100 net) I was able to get direct stream/ direct play.
This was the alternative I was about to suggest. I’m glad it worked in your case. Pls note however that you shall not use this in reverse proxy situations for security reasons.
