Random closed captioning being burned in after last container update

Vaise Williams

About 10 days ago my docker container for tvheandnd updated and after than some channels and some programs are burning in the closed captioning.

I.E, in any client they are shown regardless if on or off.

I am recording the 'pass' stream from tvh as it is passed to Emby and hence it is emby doing the actual recording.

I tried changing the stream format to matroski but that was too jumpy.

I use very old HDHR dual's on the backend if that matters.

I have posted on the emby forums but they say there is nothing new on the emby side, no changes to the container or config - just updated.

Anyone have any ideas ?

edit - The container updated today - so fingers crossed the issue is gone......
Version showing - Build: 4.3-1950~g98a7c6cfd (2021-04-11T17:42:58+0200)

Flole

You didn't even state what Tvheadend version you are running. Anyways, Tvheadend does not alter the video by adding subtitles to it, so if thats what you are seeing it's a good idea to search elsewhere as it's not related to Tvheadend.

Vaise Williams

Just to close this out - It was NOT a TVHeadend issue.
The emby server has a conversion process post recording and their last betas introduced meant the conversion was burning in the closed captions.
I only randomly came across this situation. Was doing a chase play (watching while recording) and no closed captions, When I can to watch the end 2 hours later, the closed captions were there.
So Emby is at fault here, not tvheadend. To make matters worse, it may only be an Australian thing......