cloudwindhk 0 #1 Posted December 9, 2018 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
softworkz 645 #3 Posted December 10, 2018 @@Luke (invalid audio stream specifiers) Share this post Link to post Share on other sites
Luke 24404 #4 Posted December 10, 2018 Please update to the latest beta server. Thanks. Share this post Link to post Share on other sites
cloudwindhk 0 #5 Posted December 12, 2018 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 645 #6 Posted December 12, 2018 @@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 0 #7 Posted December 12, 2018 Cool, I will test 77 when it becomes available and report back. Share this post Link to post Share on other sites
Luke 24404 #8 Posted December 12, 2018 No those are already fixed in .76. Share this post Link to post Share on other sites
softworkz 645 #9 Posted December 12, 2018 @@cloudwindhk - OK sorry for misinformation. Could you please post a new log with .76 Share this post Link to post Share on other sites
cloudwindhk 0 #10 Posted December 12, 2018 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 Share this post Link to post Share on other sites
Luke 24404 #11 Posted December 12, 2018 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 0 #12 Posted December 12, 2018 (edited) 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 Share this post Link to post Share on other sites
softworkz 645 #13 Posted December 12, 2018 @@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 24404 #14 Posted December 12, 2018 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 24404 #15 Posted December 13, 2018 Please try again with the next beta server. Thanks. Share this post Link to post Share on other sites
cloudwindhk 0 #16 Posted December 15, 2018 Fixed in .77, thanks! Share this post Link to post Share on other sites
Luke 24404 #17 Posted December 16, 2018 Thanks for the feedback. Share this post Link to post Share on other sites
andyjames 0 #18 Posted July 10 (edited) 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 by andyjames Share this post Link to post Share on other sites
Luke 24404 #19 Posted July 12 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 0 #20 Posted July 13 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 472 #21 Posted July 13 Which player are you using, MPV or native player? Share this post Link to post Share on other sites
andyjames 0 #23 Posted July 24 It appears the upgrade resolved the issue. Thanks. Share this post Link to post Share on other sites
Luke 24404 #24 Posted July 24 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
