Cannot play h.264 content on Samsung Q60 2020
Forum rules
Please make sure you follow the Problem Reporting Guidelines before posting if you want a reply
Please make sure you follow the Problem Reporting Guidelines before posting if you want a reply
Cannot play h.264 content on Samsung Q60 2020
I´m really getting frustrated and could use some help. I´ve been using UMS (and it´s predecessor PS3 Media Server) for many many years and never had any problems. But now I don´t seem to get out of trouble anymore.
I bought a new SamsungTV last weekend (QE50Q64TAU), and that´s where the problems started.
There is no DTS support anymore, so many of my videos won´t play. I searched the forums and used many instructions, to no avail. I always get the message that the audio codec is not supported. Maybe someone can check my config file? I used the Samsung QLED 4K 2019+ config and tweaked a little here and there, but it won´t play. I´d greatly appreciate it if I didn´t have to manually transcode half of my media collection.
My biggest problem currently is that my tv won´t play anything encoded in h.264. As you can see in the trace logs, every time I start a video with that video codec, I get an error message "An unexpected error ocurred". Never seen anything like that before.
To sum up, I´d be REALLY thankful if you could help me with a proper config file that:
I bought a new SamsungTV last weekend (QE50Q64TAU), and that´s where the problems started.
There is no DTS support anymore, so many of my videos won´t play. I searched the forums and used many instructions, to no avail. I always get the message that the audio codec is not supported. Maybe someone can check my config file? I used the Samsung QLED 4K 2019+ config and tweaked a little here and there, but it won´t play. I´d greatly appreciate it if I didn´t have to manually transcode half of my media collection.
My biggest problem currently is that my tv won´t play anything encoded in h.264. As you can see in the trace logs, every time I start a video with that video codec, I get an error message "An unexpected error ocurred". Never seen anything like that before.
To sum up, I´d be REALLY thankful if you could help me with a proper config file that:
- Supports all codec formats my tv supports
- Allows playback of UHD content (on my old tv I always had to use the "No Transcode" option to achieve this)
- Automatically transcode files with DTS to any other supported audio format
- Attachments
-
- ums_dbg.zip
- (322.41 KiB) Downloaded 610 times
Re: Cannot play h.264 content on Samsung Q60 2020
Samsung have dropped support for DTS and Divx so unfortunately those will have to be transcoded, the config doesn't show that they are supported so UMS will do that automatically.
Looks like it is streaming h264 correctly but I think the issue is the subtitle format, a lot of your files in your log use PGS for subtitles. I had never heard of that format before but looking it up it uses images instead of text to do the subs. Because the subs are defined in every supported format line in this config, UMS will transcode those files as PGS is not listed as supported.
When UMS is transcoding I did see this
which is probably causing problems for the TV causing it to throw up an error stopping UMS
Don't know why though, I don't know enough about it.
Possible fixes would be to use external sub files, disable subs or edit the config.
try removing this from every supported line
and adding to the bottom
Hopefully this will stop UMS rejecting those files because of the sub format but allow the use of other subs instead
Any file that fails to play, try the "No Transcode" option and see if your TV can play that file. if it does when UMS would normally transcode then the config will need updating.
Looks like it is streaming h264 correctly but I think the issue is the subtitle format, a lot of your files in your log use PGS for subtitles. I had never heard of that format before but looking it up it uses images instead of text to do the subs. Because the subs are defined in every supported format line in this config, UMS will transcode those files as PGS is not listed as supported.
When UMS is transcoding I did see this
Code: Select all
DEBUG 2020-06-09 10:13:15.780 [mencoder.exe-30-2] net.pms.io.OutputTextLogger [matroska,webm @ 013e0080]Could not find codec parameters for stream 4 (Subtitle: hdmv_pgs_subtitle): unspecified size
DEBUG 2020-06-09 10:13:15.780 [mencoder.exe-30-2] net.pms.io.OutputTextLogger Consider increasing the value for the 'analyzeduration' and 'probesize' optionsCode: Select all
DEBUG 2020-06-09 10:13:17.773 [HTTPv2 Request Worker 7] net.pms.network.RequestHandlerV2 Connection error: java.io.IOException: Eine vorhandene Verbindung wurde vom Remotehost geschlossen
DEBUG 2020-06-09 10:13:17.773 [HTTPv2 Request Worker 7] net.pms.network.RequestHandlerV2 Premature end, stopping...Possible fixes would be to use external sub files, disable subs or edit the config.
try removing this from every supported line
Code: Select all
se:ASS|MICRODVD|SAMI|SUBRIP|TEXT|TX3G si:ASS|SUBRIP|VOBSUBCode: Select all
SupportedExternalSubtitlesFormats = ASS|MICRODVD|SAMI|SUBRIP|TEXT|TX3G
SupportedInternalSubtitlesFormats = ASS|SUBRIP|VOBSUBAny file that fails to play, try the "No Transcode" option and see if your TV can play that file. if it does when UMS would normally transcode then the config will need updating.
Logs are important for us to help, Please follow This Link before asking for support. Just a forum cleaner, Will help if I can but no expert.
Re: Cannot play h.264 content on Samsung Q60 2020
Hey, thanks for your efforts. Unfortunately, your proposed solution didn´t work for me. I get the same error message when trying to start playback. When using the No Transcode option, playback starts without a problem.
Also, the automated DTS transcoding doesn´t work. For each DTS file I started I received the error message "audio format is not supported", then the video starts without sound. Is there anything I can change in the audio transcoding settings? I´ve already tried a few checkboxes, but nothing worked for me. Currently, only the "Keep AC-3 channel" is activated.
I attached another debug log, maybe there´s something else I could try?
Also, the automated DTS transcoding doesn´t work. For each DTS file I started I received the error message "audio format is not supported", then the video starts without sound. Is there anything I can change in the audio transcoding settings? I´ve already tried a few checkboxes, but nothing worked for me. Currently, only the "Keep AC-3 channel" is activated.
I attached another debug log, maybe there´s something else I could try?
- Attachments
-
- ums_dbg_02.zip
- (379.09 KiB) Downloaded 633 times
Re: Cannot play h.264 content on Samsung Q60 2020
It appears that UMS is detecting DTS tracks correctly and is transcoding them
The problem might actually be the settings for what it is getting transcoded to that is causing your TV to refuse to play and close the connection.
The actual transcoding side of things I know little of,@Nadahar would be better help, but have a play around with the options and try forcing a file that you know works to be transcoded using the #-TRANSCODE-# folder and make sure that it will still play. Try experimenting with these, see the DefaultRenderer.conf for options.
I did notice a couple of things that were interesting, a few files has "truehd" as a second audio track which is making UMS transcode even though the first track "AC3" is supported. My guess is that your TV would still play them without transcoding but would just ignore the 2nd audio track.
@Nadahar, just re-reading this before submitting I noticed something that might be wrong. Is the mime type correct for transcoded video? As the file is getting transcoded to MPEGTS-H264-AC, shouldn't the mime type be "video/mpeg" and not "video/x-matroska"?
Code: Select all
Wir waren Helden.mkv
Format: "Matroska" Duration: 2:18:32.972 Overall Bitrate: 16484759 Cover: No
FPS: 23.976
- Video track ID: 1
Format: "AVC" Profile: "[email protected]" CodecID: "V_MPEG4/ISO/AVC" Duration: 2:18:32.980
...
- Audio track ID: 2
Format: "DTS" CodecID: "A_DTS" Duration: 2:18:32.972 BitRate Mode: CBR
...
... Audio codec "dts" failed to match support line f:mkv v:h264 a:ac3|lpcm|adpcm|aac-lc|he-aac|wma|eac3|mp3 m:video/x-matroska w:4096 h:2160 b:600000000
... Final verdict: "Wir waren Helden.mkv" will be transcoded with player "FFmpeg Video" with mime type "video/x-matroska"
The actual transcoding side of things I know little of,@Nadahar would be better help, but have a play around with the options and try forcing a file that you know works to be transcoded using the #-TRANSCODE-# folder and make sure that it will still play. Try experimenting with these, see the DefaultRenderer.conf for options.
Code: Select all
TranscodeVideo = MPEGTS-H264-AC3
TranscodeFastStart = true
SeekByTime = trueI did notice a couple of things that were interesting, a few files has "truehd" as a second audio track which is making UMS transcode even though the first track "AC3" is supported. My guess is that your TV would still play them without transcoding but would just ignore the 2nd audio track.
Code: Select all
Star Trek X - Nemesis (2002).mkv
- Audio track ID: 2
Format: "AC-3" CodecID: "A_AC3" Duration: 1:56:30.656 BitRate Mode: CBR
...
- Audio track ID: 3
Format: "MLP FBA" CodecID: "A_TRUEHD" Duration: 1:56:30.656 BitRate Mode: VBR
...
... Matched support line f:mkv v:h264 a:ac3|lpcm|adpcm|aac-lc|he-aac|wma|eac3|mp3 m:video/x-matroska w:4096 h:2160 b:600000000
... Audio codec "truehd" failed to match support line f:mkv v:h264
... Final verdict: "Star Trek X - Nemesis (2002).mkv" will be transcoded with player "FFmpeg Video" with mime type "video/x-matroska"
@Nadahar, just re-reading this before submitting I noticed something that might be wrong. Is the mime type correct for transcoded video? As the file is getting transcoded to MPEGTS-H264-AC, shouldn't the mime type be "video/mpeg" and not "video/x-matroska"?
Logs are important for us to help, Please follow This Link before asking for support. Just a forum cleaner, Will help if I can but no expert.
Re: Cannot play h.264 content on Samsung Q60 2020
@mik_s Good observation. It's very unlikely that a renderer will accept a TS stream when announced as Matroska, yes. This might be caused by an error in the renderer configuration file, or by a "new" bug in UMS.
Edit: It looks to me like there's a bug here, I would start by trying an older version of UMS. The information extracted contradicts itself, as it states that it has "matched" the MKV line, which means that the file will NOT be transcoded, yet still it ends up being transcoded. My guess is that this confusion leads to the configurared MIME-type for the "matched supported line" is used despite this being overruled and the file being transcoded.
Edit: It looks to me like there's a bug here, I would start by trying an older version of UMS. The information extracted contradicts itself, as it states that it has "matched" the MKV line, which means that the file will NOT be transcoded, yet still it ends up being transcoded. My guess is that this confusion leads to the configurared MIME-type for the "matched supported line" is used despite this being overruled and the file being transcoded.
Re: Cannot play h.264 content on Samsung Q60 2020
Yeah I definitely think it is a bug, checked my logs to see what the mime is when I am transcoding and it is "video/x-matroska" whenever the source file is a mkv. I guess some renderers are tolerant to that so it still works but might confuse others when receiving a container that is different than expected.
I'm not on the latest version though, haven't got round to doing the update.
I'm not on the latest version though, haven't got round to doing the update.
Logs are important for us to help, Please follow This Link before asking for support. Just a forum cleaner, Will help if I can but no expert.
Re: Cannot play h.264 content on Samsung Q60 2020
If the bug is caused by what I suspect, it's been around since 9.1 or so, so you would need to test something older than that.
Re: Cannot play h.264 content on Samsung Q60 2020
If you point me to your suspicion I can check and probably fix it
Re: Cannot play h.264 content on Samsung Q60 2020
I looked at the logs just now and the MIME type is actually video/mpeg:
<res xmlns:dlna="urn:schemas-dlna-org:metadata-1-0/" bitrate="2060594" colorDepth="8" duration="2:18:32.972" nrAudioChannels="6" protocolInfo="http-get:*:video/mpeg:DLNA.ORG_PN=AVC_TS_HD_24_AC3_ISO;DLNA.ORG_OP=11" resolution="1920x816" sampleFrequency="48000">http://192.168.0.73:5001/get/688/Wir+wa ... to.ts</res>
That's not the right MIME type for .ts though. It should be video/vnd.dlna.mpeg-tts
I have modified the renderer config to hopefully use that MIME type, please try it and provide new logs if it doesn't work:
<res xmlns:dlna="urn:schemas-dlna-org:metadata-1-0/" bitrate="2060594" colorDepth="8" duration="2:18:32.972" nrAudioChannels="6" protocolInfo="http-get:*:video/mpeg:DLNA.ORG_PN=AVC_TS_HD_24_AC3_ISO;DLNA.ORG_OP=11" resolution="1920x816" sampleFrequency="48000">http://192.168.0.73:5001/get/688/Wir+wa ... to.ts</res>
That's not the right MIME type for .ts though. It should be video/vnd.dlna.mpeg-tts
I have modified the renderer config to hopefully use that MIME type, please try it and provide new logs if it doesn't work:
Code: Select all
#----------------------------------------------------------------------------
# Profile for Samsung QLED 4K TVs from 2019+.
# See DefaultRenderer.conf for descriptions of all the available options.
#
# This is based on Samsung-UHD.conf but removes dts and divx support, which
# was removed from all Samsung TVs in 2019, and has more specific subtitles
# support.
#
RendererName = Samsung QLED 4K 2019+
RendererIcon = samsung-tv.png
# ============================================================================
# We have not confirmed the identifying strings for this renderer yet, and are
# assuming based on previous years it will be like:
# modelName=QN49Q70RAFXZA
# modelName=QN75Q90RAFXZA
# modelName=UE43RU7179UXZG
# etc.
#
# Example manuals:
# http://downloadcenter.samsung.com/content/UM/201909/20190919132100565/MUSATSCR-4.0.0_EM_MUSE_USA_ENG-US_190731.0.pdf
# http://downloadcenter.samsung.com/content/UM/201910/20191024133448825/MUSDVBEUR-3.0.0_EM_MUSE_EU_ENG_190820.0.pdf
# ============================================================================
#
# as friendlyName and USER-AGENT can be changed in the TV menu, we can't rely on it
# we will rely on modelName and modelDescription
#
UserAgentSearch = (QN|UE)\d{2}(Q|RU)[5-9]\d
UpnpDetailsSearch = (QN|UE)\d{2}(Q|RU)[5-9]\d
LoadingPriority = 2
TranscodeVideo = MPEGTS-H264-AC3
TranscodeFastStart = true
SeekByTime = true
UseClosedCaption = true
SubtitleHttpHeader = CaptionInfo.sec
MediaInfo = true
MaxVideoWidth = 4096
MaxVideoHeight = 2160
# Samsung TV allow up to H264 5.1
H264Level41Limited = false
# some Samsung UHD display are 8 bits, but all are 12 bits capable (dithering)
SupportedVideoBitDepths = 8,10,12
#HEVC codec is only available in MKV/MP4/TS containers.
#VC1 AP L4 is not supported
# Supported video formats:
Supported = f:avi v:h264 a:ac3|lpcm|adpcm|aac-lc|he-aac|wma|eac3|mp3 m:video/avi w:4096 h:2160 b:600000000
Supported = f:avi v:mjpeg a:ac3|lpcm|adpcm|aac-lc|he-aac|wma|eac3|mp3 m:video/avi w:3840 h:2160 b:800000000
Supported = f:avi v:mp4|mpeg1|mpeg2|vc1|wmv|h263|vp6 a:ac3|lpcm|adpcm|aac-lc|he-aac|wma|eac3|mp3 m:video/avi w:1920 h:1080 b:200000000
Supported = f:mkv v:h264 a:ac3|lpcm|adpcm|aac-lc|he-aac|wma|eac3|mp3 m:video/x-matroska w:4096 h:2160 b:600000000
Supported = f:mkv v:h265 a:ac3|lpcm|adpcm|aac-lc|he-aac|wma|eac3|mp3 m:video/x-matroska w:4096 h:2160 b:1000000000
Supported = f:mkv v:mjpeg a:ac3|lpcm|adpcm|aac-lc|he-aac|wma|eac3|mp3 m:video/x-matroska w:3840 h:2160 b:800000000
Supported = f:mkv v:mp4|mpeg1|mpeg2|vc1|wmv|h263|vp6 a:ac3|lpcm|adpcm|aac-lc|he-aac|wma|eac3|mp3 m:video/x-matroska w:1920 h:1080 b:200000000
Supported = f:mp4 v:h264 a:ac3|lpcm|adpcm|aac-lc|he-aac|wma|eac3|mp3 m:video/mp4 w:4096 h:2160 b:600000000
Supported = f:mp4 v:h265 a:ac3|lpcm|adpcm|aac-lc|he-aac|wma|eac3|mp3 m:video/mp4 w:4096 h:2160 b:1000000000
Supported = f:mp4 v:mjpeg a:ac3|lpcm|adpcm|aac-lc|he-aac|wma|eac3|mp3 m:video/mp4 w:3840 h:2160 b:800000000
Supported = f:mp4 v:mp4|mpeg1|mpeg2|vc1|wmv|h263|vp6 a:ac3|lpcm|adpcm|aac-lc|he-aac|wma|eac3|mp3 m:video/mp4 w:1920 h:1080 b:200000000
Supported = f:3gp v:h264 a:ac3|lpcm|adpcm|aac-lc|he-aac|wma|eac3|mp3 m:video/3gpp w:4096 h:2160 b:600000000
Supported = f:3gp v:mjpeg a:ac3|lpcm|adpcm|aac-lc|he-aac|wma|eac3|mp3 m:video/3gpp w:3840 h:2160 b:800000000
Supported = f:3gp v:mp4|mpeg1|mpeg2|vc1|wmv|h263|vp6 a:ac3|lpcm|adpcm|aac-lc|he-aac|wma|eac3|mp3 m:video/3gpp w:1920 h:1080 b:200000000
Supported = f:mov v:h264 a:ac3|lpcm|adpcm|aac-lc|he-aac|wma|eac3|mp3 m:video/quicktime w:4096 h:2160 b:600000000
Supported = f:mov v:mjpeg a:ac3|lpcm|adpcm|aac-lc|he-aac|wma|eac3|mp3 m:video/quicktime w:3840 h:2160 b:800000000
Supported = f:mov v:mp4|mpeg1|mpeg2|vc1|wmv|h263|vp6 a:ac3|lpcm|adpcm|aac-lc|he-aac|wma|eac3|mp3 m:video/quicktime w:1920 h:1080 b:200000000
Supported = f:flv v:h264 a:ac3|lpcm|adpcm|aac-lc|he-aac|wma|eac3|mp3 m:video/x-flv w:4096 h:2160 b:600000000
Supported = f:flv v:mjpeg a:ac3|lpcm|adpcm|aac-lc|he-aac|wma|eac3|mp3 m:video/x-flv w:3840 h:2160 b:800000000
Supported = f:flv v:mp4|mpeg1|mpeg2|vc1|wmv|h263|vp6 a:ac3|lpcm|adpcm|aac-lc|he-aac|wma|eac3|mp3 m:video/x-flv w:1920 h:1080 b:200000000
Supported = f:mpegps v:h264 a:ac3|lpcm|adpcm|aac-lc|he-aac|wma|eac3|mp3 m:video/mpeg w:4096 h:2160 b:600000000
Supported = f:mpegps v:mjpeg a:ac3|lpcm|adpcm|aac-lc|he-aac|wma|eac3|mp3 m:video/mpeg w:3840 h:2160 b:800000000
Supported = f:mpegps v:mp4|mpeg1|mpeg2|vc1|wmv|h263|vp6 a:ac3|lpcm|adpcm|aac-lc|he-aac|wma|eac3|mp3 m:video/mpeg w:1920 h:1080 b:200000000
Supported = f:mpegts v:h264 a:ac3|lpcm|adpcm|aac-lc|he-aac|wma|eac3|mp3 m:video/vnd.dlna.mpeg-tts w:4096 h:2160 b:600000000
Supported = f:mpegts v:mjpeg a:ac3|lpcm|adpcm|aac-lc|he-aac|wma|eac3|mp3 m:video/vnd.dlna.mpeg-tts w:3840 h:2160 b:800000000
Supported = f:mpegts v:mp4|mpeg1|mpeg2|vc1|wmv|h263|vp6 a:ac3|lpcm|adpcm|aac-lc|he-aac|wma|eac3|mp3 m:video/vnd.dlna.mpeg-tts w:1920 h:1080 b:200000000
Supported = f:mpegts v:h265 a:ac3|lpcm|adpcm|aac-lc|he-aac|wma|eac3|mp3 m:video/vnd.dlna.mpeg-tts w:4096 h:2160 b:1000000000
Supported = f:wmv v:h264 a:ac3|lpcm|adpcm|aac-lc|he-aac|wma|eac3|mp3 m:video/x-ms-wmv w:4096 h:2160 b:600000000
Supported = f:wmv v:mjpeg a:ac3|lpcm|adpcm|aac-lc|he-aac|wma|eac3|mp3 m:video/x-ms-wmv w:3840 h:2160 b:800000000
Supported = f:wmv v:mp4|mpeg1|mpeg2|vc1|wmv|h263|vp6 a:ac3|lpcm|adpcm|aac-lc|he-aac|wma|eac3|mp3 m:video/x-ms-wmv w:1920 h:1080 b:200000000
Supported = f:asf v:h264 a:ac3|lpcm|adpcm|aac-lc|he-aac|wma|eac3|mp3 m:video/x-ms-asf w:4096 h:2160 b:600000000
Supported = f:asf v:mjpeg a:ac3|lpcm|adpcm|aac-lc|he-aac|wma|eac3|mp3 m:video/x-ms-asf w:3840 h:2160 b:800000000
Supported = f:asf v:mp4|mpeg1|mpeg2|vc1|wmv|h263|vp6 a:ac3|lpcm|adpcm|aac-lc|he-aac|wma|eac3|mp3 m:video/x-ms-asf w:1920 h:1080 b:200000000
Supported = f:webm v:vp8 a:vorbis m:video/webm w:1920 h:1080 b:200000000
Supported = f:webm v:vp9 a:vorbis m:video/webm w:3840 h:2160 b:800000000
# Supported audio formats:
Supported = f:aac m:audio/x-m4a
Supported = f:aiff m:audio/L16
Supported = f:alac m:audio/m4a
Supported = f:ape m:audio/ape
Supported = f:mp3 m:audio/mpeg
Supported = f:flac m:audio/x-flac n:2
Supported = f:vorbis m:audio/vorbis n:2
Supported = f:wav m:audio/wav
Supported = f:wma m:audio/x-ms-wma
# Supported image formats:
Supported = f:bmp m:image/bmp w:4096 h:4096
Supported = f:jpg m:image/jpeg w:15360 h:8640
Supported = f:mpo m:image/mpo w:15360 h:8640
Supported = f:png m:image/png w:4096 h:4096
SupportedExternalSubtitlesFormats = ASS|MICRODVD|SAMI|SUBRIP|TEXT|TX3G
SupportedInternalSubtitlesFormats = ASS|SUBRIP|VOBSUB
Re: Cannot play h.264 content on Samsung Q60 2020
Hi everyone,
first of all let me tell you that I greatly appreciate the effort everyone is putting into this.
I tried SubJunk's config with the current build 9.5.0, behaviour of my renderer didn´t change. Playback of most videos was still impossible, see attached ums_dbg_03 for results.
After that, I uninstalled UMS and installed build 9.0.0 since Nadahar mentioned the bug ocurred with 9.1.0. With the same config file, I could reproduce the exact same problems - see ums_dbg_04 for results.
Should I try an UMS build 8.x or lower?
first of all let me tell you that I greatly appreciate the effort everyone is putting into this.
I tried SubJunk's config with the current build 9.5.0, behaviour of my renderer didn´t change. Playback of most videos was still impossible, see attached ums_dbg_03 for results.
After that, I uninstalled UMS and installed build 9.0.0 since Nadahar mentioned the bug ocurred with 9.1.0. With the same config file, I could reproduce the exact same problems - see ums_dbg_04 for results.
Should I try an UMS build 8.x or lower?
- Attachments
-
- ums_dbg_04.zip
- (266.72 KiB) Downloaded 771 times
-
- ums_dbg_03.zip
- (273.2 KiB) Downloaded 548 times