Page 2 of 2
Re: Problems with tsMuxeR on Mac, incl. audio delay
Posted: Tue Nov 11, 2025 10:14 am
by Shangri La
I don't have WebOS 25, it's not out yet for my model/region. I guess they're still fixing bugs. I will try it out when it's released, hopefully in the next couple of months. In the meantime, UMS 15.1 is working ok after I replaced its tsmuxer binary, except for the couple of small issues I mentioned above, or when there are forced subs (or I want subs). In those cases, I will do a manual transcode to MP4 first, but it will be nice if I don't have to bother with that in the future with WebOS 25.
Re: Problems with tsMuxeR on Mac, incl. audio delay
Posted: Mon Dec 01, 2025 1:04 pm
by Shangri La
Fyi, I just got WebOS 25, with firmware 33.22.52. I can confirm that Dolby Vision Profile 8 plays now directly from MKV files. I don't have the problems I mentioned with tsMuxer, with weird colors and audio delays in certain files. Subtitles are working too. So far, I haven't had any problems that suggest a memory leak. I don't have files to test for the other Dolby Vision profiles. I've turned off transcoding altogether now, so that the MKVs won't get remuxed.
Re: Problems with tsMuxeR on Mac, incl. audio delay
Posted: Mon Dec 01, 2025 3:27 pm
by mik_s
Glad it seems to not have those problems others have mentioned with WebOS25. I wonder if they have fixed it or only happened on some models.
You will probably need to modify your conf to add in DV as supported in MKV now to stop the remuxing but still allows transcoding of other unsupported videos.
I suggest copying the conf that is being used and put it in C:\ProgramData\UMS\renderers and modify that so it will not be overwritten when you next update UMS.
You may need to increase the LoadingPriority and should change the RendererName slightly so you can see if UMS is actually using this one in the UI and not the default one.
It will be helpful if you post your logs as there is a chance the headers are slightly different for WebOS25 and if so I can make a conf that will automatically be used for this version, otherwise it will have to be something that has to be done by the user.
Re: Problems with tsMuxeR on Mac, incl. audio delay
Posted: Mon Dec 01, 2025 9:30 pm
by Shangri La
Thanks. I don't think I have any unsupported videos that need transcoding, it was only the remuxing for DV MKV. So I've just turned off transcoding, and that seems to work. It's easier than trying to modify the configuration file. Sorry, I'd rather not post logs, it seems like they have a lot of personal information, and it would take me some time to strip it out. I just wanted to let you know that the problems I mentioned with audio delay and weird color patches on some files are indeed related to tsmuxer - without it, they play properly.
I can't say for sure that I don't have any problems with WebOS 25. The memory leak problem seems to have been fixed, but I've only had it one day. I saw that someone said it won't play Profile 7 MKV files at all anymore. I found one test file, and it does play, but not with DV, only as HDR. Maybe it depends on the file. Not sure if it will be ok for you to completely turn off remuxing DV MKV for WebOS 25, or only for profile 8, or not at all, or if that's even possible. Anyway, it's working well enough for me at the moment.
Re: Problems with tsMuxeR on Mac, incl. audio delay
Posted: Wed Sep 02, 2026 12:02 pm
by Shangri La
By the way, you're still shipping a completely wrong and non-functional tsMuxeR with the Mac version of UMS. It's a Linux binary:
% file '/Applications/Universal Media Server.app/Contents/Resources/osx/tsMuxeR'
/Applications/Universal Media Server.app/Contents/Resources/osx/tsMuxeR: ELF 64-bit LSB executable, x86-64, version 1 (GNU/Linux), statically linked, BuildID[sha1]=56c7bf03a7cbd46c1f7fc3ce82bf651f023e9f7c, for GNU/Linux 3.2.0, with debug_info, not stripped
Re: Problems with tsMuxeR on Mac, incl. audio delay
Posted: Wed Sep 02, 2026 9:24 pm
by mik_s
I've added more info to the issue on Github as it is probably a mis-configuration during build.
I think what happened was there was a new version of tsMuxer so when the build script was updated for the MacOS versions the wrong filename was used.