Philips DLNA burned in subtitles
I own a Philips 65PUS7354/12.
Background:
Unfortunately, this Philips does not support .srt soft subtitles, so using my router's build-in DLNA server is no longer possible if I also want subtitles with my movies.
This is why I turned to serviio for the file formats that need .srt subtitles and don't have them built-in (like some .mkv files).
There would be 2 options:
1. mix-in the subtitles and then play the movies. This is very annoying to do as you need to pre-process the movies.
2. transcode the movie and burn in the subtitles on the go.
Unfortunately this is very CPU consuming, but it's easy to setup.
Pros:
- no prior setup to be done.
- subtitles can be downloaded automatically
Cons:
- the PC doing it will be using a lot of resources.
- Also, one more important thing I've noticed with this approach: skipping forward (fast-forward) no longer works properly. You can play and resume, but that's it.
The problem:
Trying to burn in the subtitles was pretty easy to setup, but it didn't work:
- used the "Philips 2010-" profile
- transcoding on
- build-in subtitles activated
- did all possible mixes of settings ith transcoding and subtitles.
Once the burn-in option is activated, the movie does not play at all, a spinner is blocked on the TV while it tries to start playing the movie.
ffmpeg is using 85% CPU power and there's a quite large .stf file being built in the background, but no movie.
The fix:
After digging around, I've seen the profile inherits most of the settings from the generic profile.
For transcoding and burning in the subtitles, it uses
This seems to be incompatible with Philips's DLNA implementation.
It works, however, with the targetContainer set to "mpegts".
So, overwriting the GenericTranscoding from the base profile did the trick:
Wanted to leave this here as I wasted a lot of time finding this.
If anyone has a fix for the fast-forward problem, it would be nice to get some insight on that.
Background:
Unfortunately, this Philips does not support .srt soft subtitles, so using my router's build-in DLNA server is no longer possible if I also want subtitles with my movies.
This is why I turned to serviio for the file formats that need .srt subtitles and don't have them built-in (like some .mkv files).
There would be 2 options:
1. mix-in the subtitles and then play the movies. This is very annoying to do as you need to pre-process the movies.
2. transcode the movie and burn in the subtitles on the go.
Unfortunately this is very CPU consuming, but it's easy to setup.
Pros:
- no prior setup to be done.
- subtitles can be downloaded automatically
Cons:
- the PC doing it will be using a lot of resources.
- Also, one more important thing I've noticed with this approach: skipping forward (fast-forward) no longer works properly. You can play and resume, but that's it.
The problem:
Trying to burn in the subtitles was pretty easy to setup, but it didn't work:
- used the "Philips 2010-" profile
- transcoding on
- build-in subtitles activated
- did all possible mixes of settings ith transcoding and subtitles.
Once the burn-in option is activated, the movie does not play at all, a spinner is blocked on the TV while it tries to start playing the movie.
ffmpeg is using 85% CPU power and there's a quite large .stf file being built in the background, but no movie.
The fix:
After digging around, I've seen the profile inherits most of the settings from the generic profile.
For transcoding and burning in the subtitles, it uses
This seems to be incompatible with Philips's DLNA implementation.
It works, however, with the targetContainer set to "mpegts".
So, overwriting the GenericTranscoding from the base profile did the trick:
Wanted to leave this here as I wasted a lot of time finding this.
If anyone has a fix for the fast-forward problem, it would be nice to get some insight on that.