Chromecast + Transcode/Remux = Seek issue

[schmuessla 2]

Hi folks,

it took me quite a while to analyze this but now I can reproduce it easily.

When casting from Emby Android App to Nvidia Shield (or Chromecast Ultra) I figured out three behaviours:

1. Transcoding (e.g. 4K -> 1080p): seeking or resuming a previously started Film not possible

2. Remuxing: seeking or resuming a previously started Film not possible

3. Direct playback (no output produced in transcoding temp directory): seeking or resuming works flawlessly

 

In case of 1) and 2) it can happen that an still frame of the sought position is shown and audio plays accordingly, but it is also possible that there is neither an image nor audio.

I usually run emby server (4.5.4.0) on arch linux within docker behind an apache reverse proxy. But when I directly connect to emby it behaves the same.

[Luke 42078]

Hi there, can we please look at an example? Please attach the information requested in how to report a media playback issue. thanks !

[schmuessla 2]

Hi that's an easy one.

Started to play test via android chromecast, plays fine.

Then set position to ~ 41 minutes. Playback stalls.

embyserver.txt ffmpeg-transcode-402342ac-5d04-4dd4-867f-c8ea1d857835_1.txt ffmpeg-transcode-db1f6b74-6f72-46bb-b4fb-8b7ccba3c8ce_1.txt

Edited March 14, 2021 by schmuessla

[Luke 42078]

Hi, we're looking into it. Thanks for reporting.

[osealion 0]

Having the exact same issue on a Chromecast Ultra. Playback from the beginning works fine, any seeking or remuxing of audio/CC settings fouls the playback.

Works fine on an old chromecast.

Running latest beta in a docker container on Linux. Tried with HW acceleration enabled and disabled. No change in behavior.

[Luke 42078]

On 3/24/2021 at 6:30 PM, osealion said:

Having the exact same issue on a Chromecast Ultra. Playback from the beginning works fine, any seeking or remuxing of audio/CC settings fouls the playback.

Works fine on an old chromecast.

Running latest beta in a docker container on Linux. Tried with HW acceleration enabled and disabled. No change in behavior.

Thanks for the info. We're looking into it.