My Panasonic VIERA TX-42ASM651 and DLNA weren’t 100% working with the Default profile that comes with Plex media server. The symptom was that the TV was unable to play MVK files and prompting the error : “Failed to read file”. Additionaly, the video format displayed by the TV when browsing was : “video” instead of “mkv“
By turning on the DLNA logs, I’ve found this :
|
1 2 |
mkv/h264/dca/srt is not a directplay profile |
When you check the shipped profile (this one) you see that dca is not part of the supported formats.
Find below a modified version that worked well for mkv files in my case, I had to slighty modify the following line:
|
1 2 |
<VideoProfile container="mkv" codec="h264,mpeg4" audioCodec="aac,ac3,mp3,pcm,dca,dts-hd" /> |
Make sure to place it under : <PLEX_HOME_FOLDER>/Profiles/Panasonic Viera 3D TV.xml and not modify the existing one
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 |
<?xml version="1.0" encoding="utf-8"?> <Client name="Panasonic Viera 3D TV"> <Identification> <DeviceDescription> <Manufacturer substring="Panasonic" /> <FriendlyName substring="VIERA" /> </DeviceDescription> </Identification> <Settings> <Setting name="TimelineBufferOffset" value="10" /> </Settings> <TranscodeTargets> <VideoProfile container="mpegts" codec="h264" audioCodec="ac3" /> <MusicProfile container="mp3" codec="mp3" /> <!-- Not 100% sure about this; other media servers use wav/lpcm --> <PhotoProfile container="jpeg" /> </TranscodeTargets> <DirectPlayProfiles> <VideoProfile container="mpeg" codec="mpeg2video,mpeg4" audioCodec="ac3,mp3" /> <VideoProfile container="mkv" codec="h264,mpeg4" audioCodec="aac,ac3,mp3,pcm,dca,dts-hd" /> <VideoProfile container="mpegts" codec="h264" audioCodec="ac3,mp3" /> <VideoProfile container="mp4" codec="h264" audioCodec="aac,ac3,mp3,pcm" /> <VideoProfile container="mov" codec="h264" audioCodec="aac,pcm" /> <VideoProfile container="avi" codec="mpeg4" audioCodec="pcm" /> <VideoProfile container="flv" codec="h264" audioCodec="aac" /> <MusicProfile container="mp3" codec="mp3" /> <MusicProfile container="mp4" codec="aac" /> <PhotoProfile container="jpeg" /> </DirectPlayProfiles> <CodecProfiles> <VideoCodec name="*"> <Limitations> <UpperBound name="video.width" value="1920" /> <UpperBound name="video.height" value="1080" /> <UpperBound name="video.bitDepth" value="8" isRequired="false" /> </Limitations> </VideoCodec> </CodecProfiles> <ContainerProfiles> <PhotoContainer name="*"> <Limitations> <UpperBound name="media.width" value="1920" /> <UpperBound name="media.height" value="1080" /> </Limitations> </PhotoContainer> </ContainerProfiles> </Client> |
if the file loads correctly, you should see :
|
1 2 3 |
DEBUG - Reading system DLNA client profiles DEBUG - Overriding Panasonic Viera 3D TV profile with user client profile |
16 January 2017 at 22 h 41 min
This worked for my Panasonic Viera TX-L50ET60Y, thanks =)
I also had to add vorbis to that same line for some files
20 January 2018 at 15 h 13 min
Hi!
Where do I find this path “/Profiles/Panasonic Viera 3D TV.xml “?
Plex is running on my synology disk.
Thx a lot!
Peter
13 February 2018 at 23 h 58 min
Check here
Where are profiles located?
Plex Media Server uses two different kinds of profile files:
System profiles
System profiles are provided and supported by Plex Inc. and are updated automatically when a new version of the server is installed. System profile files are stored in the Plex Media Server installation, under the Resources/Profiles directory. They should be assumed to be read-only from a user’s perspective, because any changes made will be lost when the server installation is updated.
User profiles
User profiles are authored by individual users and are never changed by the server. User profile files are located in the Plex Media Server user directory, in a directory called Profiles. If you have never authored a user profile before, this directory will not exist.
User profiles may provide support for devices not supported by system profiles, as well as override devices supported by system profiles. A system profile can be overridden by creating a client profile file with the same file name as the system profile file that is intended to be overridden.