Changing the H.264 Level above the device’s recommended value could possibly result in severe playback stability issues or device instability.Selecting the “None” value may be safe based on you media. ![]() A H.264 level slightly higher than the recommended is usually safe.A H.264 level below that of the source video will force the video to transcode.Videos use the H.264 Level to define a maximum bitrate for the video as well as decoding parameters. Changing the Maximum H.264 Level global setting can allow many files to Direct Stream or Direct Play.Some devices can handle higher quality transcodes or remuxes. Most devices can handle streams with peak bitrates < 20Mbps. Setting a streaming quality value lower than the content’s bitrate will cause the video to be transcoded.Enabling multi-channel audio in the global settings menu adds support for the associated audio codec during Direct Play and transcoding.Higher streaming quality values have a better chance to allow the content to be Direct Streamed or Direct Played.Keep these tips in mind to help ensure the best experience. ![]() Tip!: Other audio formats such as FLAC or ALAC will be transcoded by your Plex Media Server to be compatible. The following audio formats are usually supported for music playback: Tip!: See below for specific model/manufacturer support. Transcoding 4K content is a very intensive process and will require a powerful computer running Plex Media Server. 4K/UHD content matching the following will Direct Play on supported devices:ĤK content not matching the above properties will be transcoded to 1080p. We’re working to bring 4K playback support to other devices, too. Some 4K (ultra high definition) devices are recognized by the Plex app. Related Page: Direct Play, Direct Stream, Transcoding 4K (UHD) Direct Play Video Support Unsupported audio formats in video will have the audio automatically transcoded to either AAC or AC3 (Dolby Digital) as appropriate by the Plex Media Server in order to preserve any surround sound audio channels. Enabling subtitles of any type will require them to be transcoded (burned) into the video stream. Other content will usually need to be either Direct Streamed or transcoded. Video Encoding: H.264 (level 4.0 or lower).Content matching the following can usually be Direct Played: See the Specific Model Differences later in the article for more information about cases that may vary from this. ![]() Content that is not natively supported will automatically be Direct Streamed or transcoded as needed by the Plex Media Server. Native video support is typically (but not always) limited to the MP4 container, H.264 video encoding, and AAC audio. Related Page: Which Smart TV models are supported? Direct Play Video Support In some cases, formats that can be played by DLNA or from a USB drive on a device may not be available for direct playback by Plex. Plex for Smart TVs uses playback systems provided by the TV manufacturer. Media compatibility and video quality limitations vary by device. It does not apply to the Plex app running on Android TV, Fire TV, Roku TV, or similar. This may have been due to exiting while the program was still scanning folders when the media library was still enabled, but it's stupid Java, so who knows.Tip!: This article is about our Smart TV app. ![]() One time so far the javaw.exe process stayed stuck in memory on exit, consuming over a GB of RAM. And it doesn't mention that the server has to be restarted to recognize this change. I had to disable transcoding of mp4 and others, because it was transcoding most files even though my WDTVLive device supports them directly just fine. I disabled and forego the media library to avoid this. Only caveats I've found: - The database size it creates for a modest media library it rather large, and takes forever to scan. But the program is nicely configurable, and does work rather well. Well, it's still a thing made with yucky Java, but at least now it includes its own runtime of it, so there's no ancient security risk, system polluting, full Java install required anymore! Of course, being Java, it's a RAM, CPU, and disk space hog.
0 Comments
Leave a Reply. |