MKV blank screen on Apple TV app but plays fine on browser

[cloudwindhk 0]

Emby Server 3.6.0.75

Apple TV App 1.2.14

 

I deleted all the logs, started Emby server, then tried to play the file in question on Apple TV. Many (20) ffmpeg logs were created after an attempted playback time of around 5 seconds, all with the same error: "Error initializing output stream 0:1 -- Error while opening encoder for output stream #0:1 - maybe incorrect parameters such as bit_rate, rate, width or height".

 

Attached are one sample of the many Apple TV ffmpeg logs and the single ffmpeg log for successful playback on browser. Let me know if you need the server log too.

AppleTV-ffmpeg-transcode-1f29d937-0c8d-40c9-a539-af832f7c83f5_1.txt

browser-ffmpeg-transcode-70879298-d056-4acb-9d92-bfe9066ea889_1.txt

[ebr 15681]

@@softworkz

[softworkz 4574]

@@Luke (invalid audio stream specifiers)

[Luke 40154]

Please update to the latest beta server. Thanks.

[cloudwindhk 0]

I didn't have a chance to upgrade until now. 3.6.0.76 exhibits the same blank screen behavior.

[softworkz 4574]

@@Luke - The audio stream specifiers will be fixed in the next version (77) iirc?

[cloudwindhk 0]

Cool, I will test 77 when it becomes available and report back.

[Luke 40154]

No those are already fixed in .76.

[softworkz 4574]

@@cloudwindhk - OK sorry for misinformation. Could you please post a new log with .76

[cloudwindhk 0]

Please see attached for .76 logs. Same issue within ffpmeg "Error while opening encoder for output stream #0:1 - maybe incorrect parameters such as bit_rate, rate, width or height".

embyserver.txt

ffmpeg-transcode-7c29fd57-6c19-4b28-85bf-83c1da084cd8_1.txt

[Luke 40154]

Had you played this same file on apple tv prior to the last couple betas?

[cloudwindhk 0]

Unfortunately not, this file was ripped from a very recently purchased Blu-Ray, so I do not know of a version of Emby that plays this file correctly (on the Apple TV app). I could mux a snippet test file from the source for you when I have time, but it looks like a params specification issue specifically for the Apple TV client because it does play on web just fine.

Edited December 12, 2018 by cloudwindhk

[softworkz 4574]

@@Luke

 

Previously we had -ab:0 384000 (log in first post here)

and got:

Codec AVOption ab (set bitrate (in bits/s)) specified for output file #0 (/config/transcoding-temp/7b471f8c2fa49c37accf6c2bc34dc15b%d.ts) has not been used for any stream. The most likely reason is either wrong type (e.g. a video option with no video streams) or that it is a private option of some encoder which was not actually used for any stream.

Now we do: -ab:a:0 384000

 

The message above does not longer occur, but there's

[ac3 @ 0xde1bc0] invalid sample rate
Error initializing output stream 0:1 -- Error while opening encoder for output stream #0:1 - maybe incorrect parameters such as bit_rate, rate, width or height

[Luke 40154]

Right, I think we need to explicitly set a sample rate when encoding to ac3. I will look at this. Thanks.

[Luke 40154]

Please try again with the next beta server. Thanks.

[cloudwindhk 0]

Fixed in .77, thanks!

[Luke 40154]

Thanks for the feedback.

[andyjames 0]

I am experiencing this issue with several mv4 files on Apple TV. I have attached my log file and I am running 

Version 4.4.0.19 beta

All files play on other devices through Emby

ffmpeg-directstream-d4058ff0-550d-496d-acc8-deac0b8b4040_1.txt

Edited July 10, 2020 by andyjames

[Luke 40154]

On 7/10/2020 at 8:08 AM, andyjames said:

I am experiencing this issue with several mv4 files on Apple TV. I have attached my log file and I am running 

Version 4.4.0.19 beta

All files play on other devices through Emby

ffmpeg-directstream-d4058ff0-550d-496d-acc8-deac0b8b4040_1.txt 1.32 MB · 0 downloads

Why are you staying behind on an old beta? We're not going to be able to fully support that.

[andyjames 0]

I was not intentionally doing so. It says Emby is up to date in the dashboard.

I'll update and see if that resolves the issue. 

[vdatanet 1586]

Which player are you using, MPV or native player?

[Luke 40154]

@andyjames ?

[andyjames 0]

It appears the upgrade resolved the issue. Thanks.

[Luke 40154]

18 hours ago, andyjames said:

It appears the upgrade resolved the issue. Thanks.

To what version now?