Jump to content
cloudwindhk

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

Recommended Posts

cloudwindhk

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

Share this post


Link to post
Share on other sites
Luke

Please update to the latest beta server. Thanks.

Share this post


Link to post
Share on other sites
cloudwindhk

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

Share this post


Link to post
Share on other sites
softworkz

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

Share this post


Link to post
Share on other sites
cloudwindhk

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

Share this post


Link to post
Share on other sites
Luke

No those are already fixed in .76.

Share this post


Link to post
Share on other sites
softworkz

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

Share this post


Link to post
Share on other sites
Luke

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

Share this post


Link to post
Share on other sites
cloudwindhk

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 by cloudwindhk

Share this post


Link to post
Share on other sites
softworkz

@@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

Share this post


Link to post
Share on other sites
Luke

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

Share this post


Link to post
Share on other sites
Luke

Please try again with the next beta server. Thanks.

Share this post


Link to post
Share on other sites
Luke

Thanks for the feedback.

Share this post


Link to post
Share on other sites
Luke
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.

Share this post


Link to post
Share on other sites
andyjames

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. 

Share this post


Link to post
Share on other sites
vdatanet

Which player are you using, MPV or native player?

Share this post


Link to post
Share on other sites
andyjames

It appears the upgrade resolved the issue. Thanks.

Share this post


Link to post
Share on other sites
Luke
18 hours ago, andyjames said:

It appears the upgrade resolved the issue. Thanks.

To what version now?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...