Video with ssa subtitles doesn't start playback with burn in selected

[knitowskimedia 9]

The Retrieving bar appears, loads about a third of the way and never goes any further. It occasionally jumps back and will then get to the third-filled position again, but it never goes past. The emby dashboard shows direct playing while this is happening. I have tried with hardware acceleration both enabled and disabled with the same result. The media starts playback normally when burn-in is disabled. Video works fine on android, in a web browser the file plays, but no subtitles appear.

[Luke 42077]

Hi there, let's look at an example. Please attach the information requested in how to report a media playback issue. thanks !

[speechles 2055]

@knitowskimedia Are you using "Hardware Acceleration"? What happens if you disable hardware acceleration?

[knitowskimedia 9]

@speechles I've tried with it on and off. It does the same thing.

@Luke I have attached the logs

I have also now noticed this behavior on a firetv.

ffmpeg-transcode-db139556-fa59-4a79-a5f9-84c848b2cbe9_1.txt embyserver(2).txt

[Luke 42077]

Try refreshing the metadata on the file and then see if that helps. Thanks.

[knitowskimedia 9]

Refreshing the metadata doesn't cause a change. Strangely, it does this on all movie-length files with ssa/ass subtitles selected, but on TV episode-length files it does start playing and stats for nerds shows that transcoding is happening for subtitles, however the subs do burn in with styling, but not with the correct fonts. They only show the default font, despite the mkv files having the correct fonts attached to them.

[Luke 42077]

Please try setting any server transcoding settings you may have customized back to default, for example: 

Quote

>>>>>  Non-Default Encoder Parameters
Warning EncoderParametersH264LibX.ConstantRateFactor: Original: 23 Actual: 20

See if that helps.

[knitowskimedia 9]

1 hour ago, Luke said:

Please try setting any server transcoding settings you may have customized back to default, for example: 

See if that helps.

No change. Trying with subtitle extraction on and off elicits no change either.

[Luke 42077]

What kind of drive is your d drive?

[knitowskimedia 9]

16 minutes ago, Luke said:

What kind of drive is your d drive?

It's a Windows Storage space made of 5 Seagate Ironwolf 4TB drives in parity (4 drives of storage, 1 redundant). The Storage Space in configured to have 12TB of storage, with 9TB used.

[Luke 42077]

Can you try the same video on the C drive and see how that compares? You'd just have to setup a small test library of that one video.

It's possible that the drive just isn't performing fast enough. This requires two simultaneous reads of the entire video file. One for the normal transcoding process, and then an additional read to fetch the subtitles to be burned in. The ffmpeg transcoder does not support doing both operations together on a single read of the file, which would help it perform considerably better. We are going to be adding this capability ourselves at some point, but it's not ready yet.

[knitowskimedia 9]

I should point out that this used to work, though I'm not sure when it stopped working.

[Luke 42077]

Can you try what I suggested? Thanks.

[knitowskimedia 9]

Just tried it, same result.

[knitowskimedia 9]

If it's a movie in a series the roku after 5-10 minutes shows a "too many errors moving on" dialogue box.

 

Also my C Drive is an ssd

[Luke 42077]

40 minutes ago, knitowskimedia said:

If it's a movie in a series the roku after 5-10 minutes shows a "too many errors moving on" dialogue box.

 

Also my C Drive is an ssd

Can you please provide the ffmpeg log file from that? Thanks.

[knitowskimedia 9]

I replicated that this morning, its the only thing emby has done today. Here are the logs from that time period.

embyserver.txt ffmpeg-transcode-2b95ea4d-a4bd-46f4-9872-3146437f4f4c_1.txt ffmpeg-transcode-e9960271-99cf-46ef-a895-77ca7996abd0_1.txt ffmpeg-transcode-9e4359fa-ac4c-40bf-be2a-5a1d24503697_1.txt ffmpeg-transcode-e867d5b5-dccd-4d5b-81cf-5eaed4babc99_1.txt ffmpeg-transcode-e6c44048-83aa-4e21-adb1-ad0b4c0f4591_1.txt ffmpeg-transcode-fa77e7fb-ff34-463d-9147-997546b282ce_1.txt

[ebr 16169]

Hi.  All of those transcode logs are playing an item from your "D:" drive...

[knitowskimedia 9]

5 minutes ago, ebr said:

Hi.  All of those transcode logs are playing an item from your "D:" drive...

I thought Luke was asking for the "too many errors" log

 

Here are the C Drive logs

embyserver.txt ffmpeg-transcode-49895c7e-9370-4078-bb99-4ecb13548a90_1.txt ffmpeg-transcode-6b3a456a-98c1-4e06-a05b-cd5c0160c730_1.txt ffmpeg-transcode-2de60fdf-c312-4da3-b6f9-c4ac91b16e66_1.txt ffmpeg-transcode-0db5cc04-091d-4ffc-931f-f96f9a0b21c3_1.txt ffmpeg-transcode-059ed52d-1002-4f93-bf76-4441d793b8ce_1.txt

[Luke 42077]

15 minutes ago, knitowskimedia said:

I thought Luke was asking for the "too many errors" log

 

Here are the C Drive logs

embyserver.txt 1.33 MB · 0 downloads ffmpeg-transcode-49895c7e-9370-4078-bb99-4ecb13548a90_1.txt 61.77 kB · 0 downloads ffmpeg-transcode-6b3a456a-98c1-4e06-a05b-cd5c0160c730_1.txt 12 kB · 0 downloads ffmpeg-transcode-2de60fdf-c312-4da3-b6f9-c4ac91b16e66_1.txt 12 kB · 0 downloads ffmpeg-transcode-0db5cc04-091d-4ffc-931f-f96f9a0b21c3_1.txt 12 kB · 0 downloads ffmpeg-transcode-059ed52d-1002-4f93-bf76-4441d793b8ce_1.txt 40 kB · 0 downloads

As a test can you also try not running as a windows service?

 

[knitowskimedia 9]

17 minutes ago, Luke said:

As a test can you also try not running as a windows service?

 

No change in behavior.

[Luke 42077]

Can we see a log example from that? Thanks.

[knitowskimedia 9]

Here they are

embyserver.txt ffmpeg-transcode-cad582d8-5f02-47c3-8890-22eafa48aeb5_1.txt ffmpeg-transcode-7fe353df-6d82-4f4e-bd69-2a76e8e37090_1.txt ffmpeg-transcode-56ab3cfb-1350-4c75-8d3d-7702ff1d19a3_1.txt ffmpeg-transcode-883e6493-7627-4276-bbdf-61785b057626_1.txt ffmpeg-transcode-2890ccc8-7623-4834-b75f-075cb1dcb07d_1.txt ffmpeg-transcode-2ba7e45d-74c1-4dcc-8562-426d66c60e5a_1.txt ffmpeg-transcode-ee0bb8ef-5934-4187-9796-c5dac82a8373_1.txt ffmpeg-transcode-bd3e6d8b-8cca-4b8c-8d93-73444baec616_1.txt hardware_detection-63768073951.txt

[knitowskimedia 9]

@Luke any ideas?

[softworkz 5066]

Thanks a lot for the logs!

This is a long-known issue with text subtitle burn-in. It surely wasn't better in any earlier Emby version.

The problem is that while transcoding the file, ffmpeg needs to open and read the file a second time simultaneously to extract all the text subtitles for burning in.
Your file is 28Mbps, that's why it causes such extreme slowdown ad the start.

The good news is that - after years - we are implementing a solution for this exactly right now. If all goes well, this will be fixed in the next beta version.

Thanks,
sw