Subtitles not displaying

[MTOakey]

Ok, tried that "test5.mkv" file and it did show the controls and Subtitles in the web player, and showed Subtitles on the TV... so that works.

My TV is a TCL 50Q651G 4K QLED Google AI TV, less than 6 months old.
I slimmed down the "Renderers" folder by over 150, so a custom/specific .conf for this model would be cool...

And strangely enough, I keep getting THIS error, like hundreds of times,

Code: Select all

13:52:56 WARN  Device descriptor retrieval failed: http://192.168.1.83:2869/upnphost/udhisapi.dll?content=uuid:ba541223-4de5-4b0b-b1ba-bae9981d60e0, 400 Bad Request

I get the same error for my Vizio SoundBar all the time, and My wife's computer when it's on.

192.168.1.83 is my computer where UMS is running and I just played that "test5.mkv" in a browser on.

The error came after that played just fine. This came just before playing it: "13:32:12 WARN Ignoring invalid audio/subtitle language configuration "eng"" - 7 times.

Also got this error both times playing that test5.mkv: "14:14:48 WARN Ignoring invalid audio/subtitle language configuration "eng""
And got this when playing on TV directly: 14:14:56 INFO Started playing test5.mkv (No transcoding) on your OakeyNet ViewPort TLC {my naming I input in TV}
and HUNDREDS more lines of errors for my computer as mentioned above...


What do you mean by:

"Are you able to upload that video with "CC1" message? It will help the devs fix it."

...

[mik_s]

Good, at least internal subtitles are working correctly.

When I looked at your logs I could not see your TV. I did see

Code: Select all

Matched media renderer "Windows Media Player" based on dlna details "OakeyNet ViewPort TLC 192.168.1.190 bf7d7fff-7d77-4d77-bfb8-b7fe7be3feff Microsoft Corporation Windows Media Player Media Renderer http://www.microsoft.com http://go.microsoft.com/fwlink/?LinkId=105926"

and assumed it was your computer as it was coming up as window media player which was confusing me. I think it is using a version of windows for its OS which includes Windows media player

Code: Select all

        <deviceType>urn:schemas-upnp-org:device:MediaRenderer:1</deviceType>
        <friendlyName>OakeyNet ViewPort TLC</friendlyName>
        <URLBase>http://192.168.1.190:16330</URLBase>
        <manufacturer>Microsoft Corporation</manufacturer>
        <manufacturerURL>http://www.microsoft.com</manufacturerURL>
        <modelDescription>Media Renderer</modelDescription>
        <modelName>Windows Media Player</modelName>
        <modelURL>http://go.microsoft.com/fwlink/?LinkId=105926</modelURL>
        <UDN>uuid:bf7d7fff-7d77-4d77-bfb8-b7fe7be3feff</UDN>
        <dlna:X_DLNADOC>DMR-1.50</dlna:X_DLNADOC>

but also shows up as

Code: Select all

    <deviceType>urn:dial-multiscreen-org:device:dial:1</deviceType>
    <friendlyName>OakeyNet ViewPort TLC</friendlyName>
    <manufacturer>TCL</manufacturer>
    <modelName>Smart TV</modelName>
    <UDN>uuid:d50968c2-c5ad-69de-8006-73f69a084345</UDN>

I know renaming a device can mess with how it identifies on the network as the model number is usually in the <friendlyName> tag, Samsung TVs do this so you have to match on other information.
There is not much to match on but hopefully "TCL" on its own will do.
I'll see if I can modify a conf from another make of TV as a base to hopefully get some of it working but you will have to tweak and test yourself it to get a fully working conf.


That warning message is nothing to worry about I think. It is just a service on a device that UMS can't handle, something like a second screen or remote device, so that was not programmed in and just ignored. Or there is some service on the TV which does not exist which UMS is querying.

Code: Select all

Service descriptor retrieval failed: http://192.168.1.190:8008/ssdp/notfound, 404 Not Found
Device service description failed: (RemoteDevice) Identity: (RemoteDeviceIdentity) UDN: uuid:d50968c2-c5ad-69de-8006-73f69a084345, Descriptor: http://192.168.1.190:8008/ssdp/device-desc.xml, Root: true
Ignoring remote device: dial (RemoteDevice) Identity: (RemoteDeviceIdentity) UDN: uuid:d50968c2-c5ad-69de-8006-73f69a084345, Descriptor: http://192.168.1.190:8008/ssdp/device-desc.xml, Root: true

I think UMS is also querying something incorrectly on your or your wife's computer and soundbar.
The request is

Code: Select all

==================================== HTTPCLIENT REQUEST BEGIN ====================================
GET /upnphost/udhisapi.dll HTTP/1.1

HEADER:
  User-agent: UMS/14.9.0 UPnP/1.0 DLNADOC/1.50 (Windows_11)
==================================== HTTPCLIENT REQUEST END ======================================

but receives

Code: Select all

    <BODY><h2>Bad Request - Invalid Header</h2>
    <hr><p>HTTP Error 400. The request has an invalid header name.</p>

Looking at this there should be more information in /upnphost/udhisapi.dll

I don't know anything about these low level communications though, but as they are warnings they should not effect anything.


Looking again at your configuration and comparing it to my fresh install I think you have the subtitles and audio track settings the wrong way around. You have

Code: Select all

audio_subtitles_languages =eng
subtitles_languages = eng,on;*,eng;*,und 

where is should be

Code: Select all

# Audio/subtitle language priority
# --------------------------------
# Determine the string of audio language and subtitles language pairs ordered
# by priority for MEncoder to try to match. Audio language and subtitles
# language should be comma separated as a pair; individual pairs should be
# semicolon separated. "*" can be used to match any language. Subtitles
# language can be defined as "off" (e.g. "jpn,off;*,*").
# Default: a localized list (e.g. "eng,off;*,eng;*,und").
audio_subtitles_languages = eng,on;*,eng;*,und

# Subtitles language priority
# ---------------------------
# A comma-separated list of language codes that defines the priority for
# MEncoder when choosing subtitles languages, where "und" stands for
# "undefined". XXX Can be empty, which overrides the default value.
# Default: a localized list (e.g. "eng,fre,jpn,ger,und").
subtitles_languages =eng

This is probably why no subtitles have been working.
These sub and audio settings are not very intuitive and I think this is definitely something that can be improved for V15.



You mentioned there was a video that had a message about "CC1" in the logs.

BTW: what the hell is this in the Logs: { Unhandled exception while resolving New Whistleblowers Golf course: For input string: "CC1" }

Code: Select all

net.pms.store.StoreResource Unhandled exception while resolving New Whistleblowers Golf course: For input string: "CC1"

It is coming from "D:\Videos\zPersonalVids\New Whistleblowers Golf course.mp4"
This is a very uncommon format so I have not been able to find examples of it.
Apparently it is a format coming from some DVD rips where the subs were encoded in the the first lines of the picture like you would get with analogue over the air broadcasts.
If the Devs had an example of this they can fix this error.
You can use something like Mega.nz or google drive to host it and send the download link. Might be better to PM it though just in case.

[mik_s]

Try this. It is based on the Samsung-TV-2021-0.conf which should be new enough that the TCL has similar support.
I could not find a manual for it so got some basic information from here but not really enough information to make a good conf. Hopefully this is an improvement at least.
I just picked a random picture for the TV icon that appears to be similar.

[MTOakey]

WoW, Thanks, but I'm still stuck on ".mp4" being "a very uncommon format" ... I thought it was the most common out there !!! ALL my movies are .mp4, and my buddie's LG won't even play .mkv - has to be .mp4

Strange thing about the TV since it says "GoogleTV" on startup, and in the software OS.
The computer hosts the UMS and internal NVMe drives at 7TB.
All it said before was "TCL 50Q651G", and it is a 4K QLED Google AI TV.
The TV has it's own internal Media player, but it's interface is ugly and bulky, that's why I use the ROKU.
Wife's computer is not "On" all the time, only when she is working on it, and I don't think there is any "media player" setup on it.
The Vizio SoundBar is a media player, just for Audio, and I have not tried to play through that directly, I always use an interface on the TV, I use Musicbee.
I searched the computer and found at least 5 copies of "udhisapi.dll" - NONE in any directory of UMS ... did a "cmd regsvr32 udhisapi.dll" and it turned up this:

,on;*,eng;*,und

2025-02-19 13 24 35.jpg (35.16 KiB) Viewed 6649 times

I swapped the "Audio/Subtitle languages" but I want Subtitles to show all the time - with a control to choose On-Off or a different subtitle from a directory. The "default" priority is "IF English Audio THEN Subtitles OFF ...."
I also moved "VLC decoder" to be above the "FFmpeg" - and FFmpeg still is the chosen decoder for the ROKU 4.
LoL, I just deleted that "Whistleblowers" vid file.
Copied that newly created TCL.conf to the "Renderers" directory.
Rebooted UMS after every change {QUIT not just Restarted}...

still no Subtitles through the ROKU on my TV, or on the TV directly.

...

[MTOakey]

and got distracted while on last test play of a video, and got this while the video is playing ... I heard many "glitches" but did not notice/see any video glitches nor buffering ...

Code: Select all

14:40:00 INFO  Stopped playing Fear Street~Part One-1994 (2021).mp4 on Roku 4 (NSP 6-7)
14:40:05 INFO  Started playing Fear Street~Part One-1994 (2021).mp4 (FFmpeg HLS Video) on your Roku 4 (NSP 6-7)
14:40:10 INFO  Stopped playing Fear Street~Part One-1994 (2021).mp4 on Roku 4 (NSP 6-7)
14:40:11 INFO  Started playing Fear Street~Part One-1994 (2021).mp4 (FFmpeg HLS Video) on your Roku 4 (NSP 6-7)
14:40:17 INFO  Stopped playing Fear Street~Part One-1994 (2021).mp4 on Roku 4 (NSP 6-7)
14:40:17 WARN  Device descriptor retrieval failed: http://192.168.1.83:2869/upnphost/udhisapi.dll?content=uuid:ba541223-4de5-4b0b-b1ba-bae9981d60e0, 400 Bad Request
14:40:17 WARN  Device descriptor retrieval failed: http://192.168.1.83:2869/upnphost/udhisapi.dll?content=uuid:ba541223-4de5-4b0b-b1ba-bae9981d60e0, 400 Bad Request
14:40:17 INFO  Started playing Fear Street~Part One-1994 (2021).mp4 (FFmpeg HLS Video) on your Roku 4 (NSP 6-7)
14:40:18 WARN  Device descriptor retrieval failed: http://192.168.1.83:2869/upnphost/udhisapi.dll?content=uuid:ba541223-4de5-4b0b-b1ba-bae9981d60e0, 400 Bad Request
14:40:18 WARN  Device descriptor retrieval failed: http://192.168.1.83:2869/upnphost/udhisapi.dll?content=uuid:ba541223-4de5-4b0b-b1ba-bae9981d60e0, 400 Bad Request
14:40:19 WARN  Device descriptor retrieval failed: http://192.168.1.83:2869/upnphost/udhisapi.dll?content=uuid:ba541223-4de5-4b0b-b1ba-bae9981d60e0, 400 Bad Request
14:40:20 WARN  Device descriptor retrieval failed: http://192.168.1.83:2869/upnphost/udhisapi.dll?content=uuid:ba541223-4de5-4b0b-b1ba-bae9981d60e0, 400 Bad Request
14:40:20 WARN  Device descriptor retrieval failed: http://192.168.1.83:2869/upnphost/udhisapi.dll?content=uuid:ba541223-4de5-4b0b-b1ba-bae9981d60e0, 400 Bad Request
14:40:20 WARN  Device descriptor retrieval failed: http://192.168.1.83:2869/upnphost/udhisapi.dll?content=uuid:ba541223-4de5-4b0b-b1ba-bae9981d60e0, 400 Bad Request
14:40:21 WARN  Device descriptor retrieval failed: http://192.168.1.83:2869/upnphost/udhisapi.dll?content=uuid:ba541223-4de5-4b0b-b1ba-bae9981d60e0, 400 Bad Request
14:40:21 WARN  Device descriptor retrieval failed: http://192.168.1.83:2869/upnphost/udhisapi.dll?content=uuid:ba541223-4de5-4b0b-b1ba-bae9981d60e0, 400 Bad Request
14:40:22 WARN  Device descriptor retrieval failed: http://192.168.1.83:2869/upnphost/udhisapi.dll?content=uuid:ba541223-4de5-4b0b-b1ba-bae9981d60e0, 400 Bad Request
14:40:23 INFO  Stopped playing Fear Street~Part One-1994 (2021).mp4 on Roku 4 (NSP 6-7)
14:40:23 WARN  Device descriptor retrieval failed: http://192.168.1.83:2869/upnphost/udhisapi.dll?content=uuid:ba541223-4de5-4b0b-b1ba-bae9981d60e0, 400 Bad Request
14:40:23 WARN  Device descriptor retrieval failed: http://192.168.1.83:2869/upnphost/udhisapi.dll?content=uuid:ba541223-4de5-4b0b-b1ba-bae9981d60e0, 400 Bad Request
14:40:23 WARN  Device descriptor retrieval failed: http://192.168.1.83:2869/upnphost/udhisapi.dll?content=uuid:ba541223-4de5-4b0b-b1ba-bae9981d60e0, 400 Bad Request
14:40:23 INFO  Started playing Fear Street~Part One-1994 (2021).mp4 (FFmpeg HLS Video) on your Roku 4 (NSP 6-7)
14:40:24 WARN  Device descriptor retrieval failed: http://192.168.1.83:2869/upnphost/udhisapi.dll?content=uuid:ba541223-4de5-4b0b-b1ba-bae9981d60e0, 400 Bad Request
14:40:24 WARN  Device descriptor retrieval failed: http://192.168.1.83:2869/upnphost/udhisapi.dll?content=uuid:ba541223-4de5-4b0b-b1ba-bae9981d60e0, 400 Bad Request
14:40:25 WARN  Device descriptor retrieval failed: http://192.168.1.83:2869/upnphost/udhisapi.dll?content=uuid:ba541223-4de5-4b0b-b1ba-bae9981d60e0, 400 Bad Request
14:40:26 WARN  Device descriptor retrieval failed: http://192.168.1.83:2869/upnphost/udhisapi.dll?content=uuid:ba541223-4de5-4b0b-b1ba-bae9981d60e0, 400 Bad Request
14:40:29 INFO  Stopped playing Fear Street~Part One-1994 (2021).mp4 on Roku 4 (NSP 6-7)
14:40:29 INFO  Started playing Fear Street~Part One-1994 (2021).mp4 (FFmpeg HLS Video) on your Roku 4 (NSP 6-7)
14:40:35 INFO  Stopped playing Fear Street~Part One-1994 (2021).mp4 on Roku 4 (NSP 6-7)
14:40:36 INFO  Started playing Fear Street~Part One-1994 (2021).mp4 (FFmpeg HLS Video) on your Roku 4 (NSP 6-7)
14:40:41 INFO  Stopped playing Fear Street~Part One-1994 (2021).mp4 on Roku 4 (NSP 6-7)
14:40:46 INFO  Started playing Fear Street~Part One-1994 (2021).mp4 (FFmpeg HLS Video) on your Roku 4 (NSP 6-7)
14:40:51 INFO  Stopped playing Fear Street~Part One-1994 (2021).mp4 on Roku 4 (NSP 6-7)
14:40:52 INFO  Started playing Fear Street~Part One-1994 (2021).mp4 (FFmpeg HLS Video) on your Roku 4 (NSP 6-7)
14:40:57 INFO  Stopped playing Fear Street~Part One-1994 (2021).mp4 on Roku 4 (NSP 6-7)
14:40:58 INFO  Started playing Fear Street~Part One-1994 (2021).mp4 (FFmpeg HLS Video) on your Roku 4 (NSP 6-7)
14:41:03 INFO  Stopped playing Fear Street~Part One-1994 (2021).mp4 on Roku 4 (NSP 6-7)
14:41:04 INFO  Started playing Fear Street~Part One-1994 (2021).mp4 (FFmpeg HLS Video) on your Roku 4 (NSP 6-7)
14:41:09 INFO  Stopped playing Fear Street~Part One-1994 (2021).mp4 on Roku 4 (NSP 6-7)
14:41:10 INFO  Started playing Fear Street~Part One-1994 (2021).mp4 (FFmpeg HLS Video) on your Roku 4 (NSP 6-7)
14:41:15 INFO  Stopped playing Fear Street~Part One-1994 (2021).mp4 on Roku 4 (NSP 6-7)
14:41:16 INFO  Started playing Fear Street~Part One-1994 (2021).mp4 (FFmpeg HLS Video) on your Roku 4 (NSP 6-7)
14:41:21 INFO  Stopped playing Fear Street~Part One-1994 (2021).mp4 on Roku 4 (NSP 6-7)
14:41:22 INFO  Started playing Fear Street~Part One-1994 (2021).mp4 (FFmpeg HLS Video) on your Roku 4 (NSP 6-7)
14:41:27 INFO  Stopped playing Fear Street~Part One-1994 (2021).mp4 on Roku 4 (NSP 6-7)
14:41:32 INFO  Started playing Fear Street~Part One-1994 (2021).mp4 (FFmpeg HLS Video) on your Roku 4 (NSP 6-7)
14:41:38 INFO  Started playing Fear Street~Part One-1994 (2021).mp4 (FFmpeg HLS Video) on your Roku 4 (NSP 6-7)
14:41:43 INFO  Stopped playing Fear Street~Part One-1994 (2021).mp4 on Roku 4 (NSP 6-7)
14:41:44 INFO  Started playing Fear Street~Part One-1994 (2021).mp4 (FFmpeg HLS Video) on your Roku 4 (NSP 6-7)
14:41:49 INFO  Stopped playing Fear Street~Part One-1994 (2021).mp4 on Roku 4 (NSP 6-7)
14:41:50 INFO  Started playing Fear Street~Part One-1994 (2021).mp4 (FFmpeg HLS Video) on your Roku 4 (NSP 6-7)
14:41:56 INFO  Stopped playing Fear Street~Part One-1994 (2021).mp4 on Roku 4 (NSP 6-7)
14:41:56 INFO  Started playing Fear Street~Part One-1994 (2021).mp4 (FFmpeg HLS Video) on your Roku 4 (NSP 6-7)
14:42:02 INFO  Stopped playing Fear Street~Part One-1994 (2021).mp4 on Roku 4 (NSP 6-7)
14:42:02 INFO  Started playing Fear Street~Part One-1994 (2021).mp4 (FFmpeg HLS Video) on your Roku 4 (NSP 6-7)
14:42:08 INFO  Stopped playing Fear Street~Part One-1994 (2021).mp4 on Roku 4 (NSP 6-7)
14:42:09 INFO  Started playing Fear Street~Part One-1994 (2021).mp4 (FFmpeg HLS Video) on your Roku 4 (NSP 6-7)
14:42:14 INFO  Stopped playing Fear Street~Part One-1994 (2021).mp4 on Roku 4 (NSP 6-7)
14:42:15 INFO  Started playing Fear Street~Part One-1994 (2021).mp4 (FFmpeg HLS Video) on your Roku 4 (NSP 6-7)
14:42:20 INFO  Stopped playing Fear Street~Part One-1994 (2021).mp4 on Roku 4 (NSP 6-7)
14:42:21 INFO  Started playing Fear Street~Part One-1994 (2021).mp4 (FFmpeg HLS Video) on your Roku 4 (NSP 6-7)
14:42:26 INFO  Stopped playing Fear Street~Part One-1994 (2021).mp4 on Roku 4 (NSP 6-7)
14:42:27 INFO  Started playing Fear Street~Part One-1994 (2021).mp4 (FFmpeg HLS Video) on your Roku 4 (NSP 6-7)
14:42:32 INFO  Stopped playing Fear Street~Part One-1994 (2021).mp4 on Roku 4 (NSP 6-7)
14:42:33 INFO  Started playing Fear Street~Part One-1994 (2021).mp4 (FFmpeg HLS Video) on your Roku 4 (NSP 6-7)
14:42:38 INFO  Stopped playing Fear Street~Part One-1994 (2021).mp4 on Roku 4 (NSP 6-7)
14:42:39 INFO  Started playing Fear Street~Part One-1994 (2021).mp4 (FFmpeg HLS Video) on your Roku 4 (NSP 6-7)
14:42:44 INFO  Stopped playing Fear Street~Part One-1994 (2021).mp4 on Roku 4 (NSP 6-7)
14:42:45 INFO  Started playing Fear Street~Part One-1994 (2021).mp4 (FFmpeg HLS Video) on your Roku 4 (NSP 6-7)
14:42:52 INFO  Stopped playing Fear Street~Part One-1994 (2021).mp4 on Roku 4 (NSP 6-7)
14:42:59 INFO  Started playing Fear Street~Part One-1994 (2021).mp4 (FFmpeg HLS Video) on your Roku 4 (NSP 6-7)
14:43:04 INFO  Stopped playing Fear Street~Part One-1994 (2021).mp4 on Roku 4 (NSP 6-7)
14:43:05 INFO  Started playing Fear Street~Part One-1994 (2021).mp4 (FFmpeg HLS Video) on your Roku 4 (NSP 6-7)
14:43:10 INFO  Stopped playing Fear Street~Part One-1994 (2021).mp4 on Roku 4 (NSP 6-7)
14:47:41 WARN  Device descriptor retrieval failed: http://192.168.1.83:2869/upnphost/udhisapi.dll?content=uuid:ba541223-4de5-4b0b-b1ba-bae9981d60e0, 400 Bad Request
14:47:41 WARN  Device descriptor retrieval failed: http://192.168.1.83:2869/upnphost/udhisapi.dll?content=uuid:ba541223-4de5-4b0b-b1ba-bae9981d60e0, 400 Bad Request
14:47:42 WARN  Device descriptor retrieval failed: http://192.168.1.83:2869/upnphost/udhisapi.dll?content=uuid:ba541223-4de5-4b0b-b1ba-bae9981d60e0, 400 Bad Request
14:47:42 WARN  Device descriptor retrieval failed: http://192.168.1.83:2869/upnphost/udhisapi.dll?content=uuid:ba541223-4de5-4b0b-b1ba-bae9981d60e0, 400 Bad Request
14:47:43 WARN  Device descriptor retrieval failed: http://192.168.1.83:2869/upnphost/udhisapi.dll?content=uuid:ba541223-4de5-4b0b-b1ba-bae9981d60e0, 400 Bad Request
14:47:44 WARN  Device descriptor retrieval failed: http://192.168.1.83:2869/upnphost/udhisapi.dll?content=uuid:ba541223-4de5-4b0b-b1ba-bae9981d60e0, 400 Bad Request
14:47:44 WARN  Device descriptor retrieval failed: http://192.168.1.83:2869/upnphost/udhisapi.dll?content=uuid:ba541223-4de5-4b0b-b1ba-bae9981d60e0, 400 Bad Request
14:47:44 WARN  Device descriptor retrieval failed: http://192.168.1.83:2869/upnphost/udhisapi.dll?content=uuid:ba541223-4de5-4b0b-b1ba-bae9981d60e0, 400 Bad Request
14:47:45 WARN  Device descriptor retrieval failed: http://192.168.1.83:2869/upnphost/udhisapi.dll?content=uuid:ba541223-4de5-4b0b-b1ba-bae9981d60e0, 400 Bad Request
14:47:45 WARN  Device descriptor retrieval failed: http://192.168.1.83:2869/upnphost/udhisapi.dll?content=uuid:ba541223-4de5-4b0b-b1ba-bae9981d60e0, 400 Bad Request
14:47:46 WARN  Device descriptor retrieval failed: http://192.168.1.83:2869/upnphost/udhisapi.dll?content=uuid:ba541223-4de5-4b0b-b1ba-bae9981d60e0, 400 Bad Request
14:47:47 WARN  Device descriptor retrieval failed: http://192.168.1.83:2869/upnphost/udhisapi.dll?content=uuid:ba541223-4de5-4b0b-b1ba-bae9981d60e0, 400 Bad Request
14:47:47 WARN  Device descriptor retrieval failed: http://192.168.1.83:2869/upnphost/udhisapi.dll?content=uuid:ba541223-4de5-4b0b-b1ba-bae9981d60e0, 400 Bad Request
14:47:47 WARN  Device descriptor retrieval failed: http://192.168.1.83:2869/upnphost/udhisapi.dll?content=uuid:ba541223-4de5-4b0b-b1ba-bae9981d60e0, 400 Bad Request
14:47:48 WARN  Device descriptor retrieval failed: http://192.168.1.83:2869/upnphost/udhisapi.dll?content=uuid:ba541223-4de5-4b0b-b1ba-bae9981d60e0, 400 Bad Request
14:47:48 WARN  Device descriptor retrieval failed: http://192.168.1.83:2869/upnphost/udhisapi.dll?content=uuid:ba541223-4de5-4b0b-b1ba-bae9981d60e0, 400 Bad Request
14:47:49 WARN  Device descriptor retrieval failed: http://192.168.1.83:2869/upnphost/udhisapi.dll?content=uuid:ba541223-4de5-4b0b-b1ba-bae9981d60e0, 400 Bad Request
14:47:50 WARN  Device descriptor retrieval failed: http://192.168.1.83:2869/upnphost/udhisapi.dll?content=uuid:ba541223-4de5-4b0b-b1ba-bae9981d60e0, 400 Bad Request

192.168.1.83 is the computer with UMS playing/serving the file.
This is really crazy, prior to v12.x.x everything was fine - no errors, no problems, no issues ...

...

[mik_s]

I meant the subtitle format "CC1" is uncommon inside the MP4 and the related "CC2, CC3, and CC4". I think 2 and 4 are for Spanish subs so more common in parts of the US.
1 and 2 are subs, and 3 and 4 are closed captions from what I remember when I last looked into these.

That dll file will be running on the device UMS is talking to as part of the OS, not the computer running UMS. That link I posted is more than I know about it.
This is nothing to worry about as UMS is ignoring it and does not harm how it works.

The subs should be on all the time with those options, just the entries were in the wrong setting so it was causing an error.
These 2 settings are similarly named so I can see how it got mixed up. I am also not sure it understands "on" as an option here, instead try "eng,eng;*,eng;*,und"
This is mostly for when transcoding so UMS knows what subtitle to burn into the video, but may have had an influence which sub to offer to the TV when a video is streaming.

Try setting these like I said and this should fix subtitles on most of the TVs and maybe the Roku app too if you remove the HLS transcoding.
I have not seen an answer to my question on Github about HLS and external subtitles yet.

Is the Roku that shows in the logs the app? or a physical device?
That conf may also work for the Roku app if you change the UserAgentSearch to "Roku/4400X|Roku/4640X" and delete "UpnpDetailsSearch = TCL"

If you make new logs with that conf I will be able to see if UMS is using it or if something else is taking priority. It also might not be matching at all and I need to tweak it.

[MTOakey]

I did try to remove that reference to "HLS" and it didn't change anything.

I changed the "on" option to eng {on is the logical opposition option for a switch - on, or off, not off - eng"

Log file too large ... 5mb is limit, file zipped is over 8mb.

2025-02-19 17 55 24.jpg (13.44 KiB) Viewed 6575 times

Which do you really need or not need ... ?

2025-02-19 17 58 46.jpg (72.55 KiB) Viewed 6575 times

[mik_s]

You can uncheck the prev logs as I am only interested in the current session.
Make sure you also include the debug.log.zip if it is there as the logs get spit up and zipped at a certain size, however stating UMS in trace mode will reset the logs anyway so this should be fairly small. Seeing as it is not including the TCL.conf would mean it is not using it so I definitely need to tweak it.

Someone else just posted about the same warnings in the logs and this reminded me that Subjunk did mention this on Github recently and if these should be filtered from the logs as not important. These will be coming from the JUPnP library UMS switched to using not long ago.

[MTOakey]

I tried adding that "debug.log.zip", got an error window stating that it did not exist.

ums_dbg_2025-02-19-21-32.zip

(895.59 KiB) Downloaded 644 times

Thanks again !!

[mik_s]

Sorry I missed your last post as it went on the next page.

Its alright if the "debug.log.zip" did not exist, this is expected when restarting UMS as the logs should not be large. If it did then there could be something seriously wrong.

I made a few confs for you to test one at a time. First with the TV's media player with and without HLS, then ones for the Roku app again with and without HLS.
Hopefully one of these should work a lot better.

UMS should be able to find a match now as it will only look for TCL, I was trying to make it less generic before.
One thing that may help is if you rename your TV from "OakeyNet ViewPort TLC" to "OakeyNet ViewPort TCL" just to give something else that UMS can match, as I think this might have been a mistake anyway.

I also made some changes to your UMS.conf that may fix the external subtitles. I reset some options to default (I kept the old settings but commented them out).
Just copy to C:\ProgramData\UMS when UMS is not running.
If this fixes external subtitles then you can start to change them back one at a time to see which one will break it.
One option will change the filename if subs are available so you can see if it is working at a glace.

Also try playing from the #--TRANSCODE--# folder where you will be able to select the subs here to burn in to the video, but hopefully you won't need to transcode anything if they can be streamed.


BTW I was able to get a video with that embedded "CC1" format and it turns out this was breaking things.
It has just been fixed but awaiting review before merging with the main code.
Since you deleted this video it will not effect you anymore.