Page 2 of 2

Re: Are soft-subtitle settings controlled by UMS or by the TV?

Posted: Tue May 01, 2018 9:18 pm
by nouse
Thank you guys. That was very helpful.
Also kudos to @Madoka for their smooth taste :)

The subtitles are now running smoothly, in a much better readable font (actually, its resembling srt now).

I am curious: If i remove ass-support from the renderer configuration, why does it recognize that subtitles are in the folder? How does it still know that ass is a subtitle?

Re: Are soft-subtitle settings controlled by UMS or by the TV?

Posted: Tue May 01, 2018 9:21 pm
by Nadahar
Removing the support simply means that UMS doesn't think the renderer can handle them. That means that UMS will transcode the video instead, burning the subtitles into the video stream. They are thus handled properly by the transcoding engine (FFmpeg, MEncoder etc).

Re: Are soft-subtitle settings controlled by UMS or by the TV?

Posted: Wed May 02, 2018 6:48 am
by nouse
Nadahar wrote: Tue May 01, 2018 9:21 pm Removing the support simply means that UMS doesn't think the renderer can handle them. That means that UMS will transcode the video instead, burning the subtitles into the video stream. They are thus handled properly by the transcoding engine (FFmpeg, MEncoder etc).
One last question.

I cannot fast forward the clips anymore for which UMS does the ass-rendering now instead of the tv. Is that normal?

Its not that crucial; its already a vast improvement from before, but i wonder if that is a design choice or inherited by the clip/subtitle combination.

Re: Are soft-subtitle settings controlled by UMS or by the TV?

Posted: Wed May 02, 2018 7:19 am
by Nadahar
When transcoding UMS is "generating" the video stream in real time. That makes seeking, fast forwarding etc complicated. It does normally work to some extent, but it's usually very delayed compared to when the file is streamed directly. On some renderers it doesn't work at all, which is usually caused by incompatibility between UMS and the renderer as far as I know. Some renderers use time codes and others use the number of bytes when requesting a new position, and there are some settings in the renderer configuration file for this. Testing different settings for this might make it work at least to some degree.