Jump to content
10479

Direct Streaming DTS 5.1 playback interrupts until hardware transcode takes over

Recommended Posts

10479

I was mentioning this in another topic, however, it appears my issue, while similar, is not the same as that one.

Currently on Emby Server Beta 4.5.13, but it doesn't matter if it's 4.4.2 or 4.4.3 either.

Clients are multiple Roku devices

When direct streaming a file encoded with DTS 5.1, playback will fail and buffer reliably after a few minutes. It will then resume playback and do the same thing shortly after. After this playback failure, Emby kicks to hardware transcoding at a very low bitrate and then plays through. Playing a similar bitrate file encoded with AC3 5.1 will direct stream perfectly fine. Both files are Direct Streamed for the same reason - Audio Codec Not Supported. If I disable transcode throttling, the DTS file will play through entirely without any issues.

I have attached all of the logs for the playback of two episodes. One in each format, including the server log with the relevant times logged. The log files are named according to the file type. There are multiple DTS files for the same episode because every time it buffers/restarts playback, it creates a new log file.

I can reproduce this 100% of the time, so if any additional info is needed, just let me know.

direct-stream-ac3-1.txt direct-stream-dts-1.txt direct-stream-dts-2.txt direct-stream-dts-3.txt direct-stream-dts-4.txt embyserver.txt

Share this post


Link to post
Share on other sites
mastrmind11

what device is your roku connected to?  Roku's don't support DTS so they will us passthrough.  If your device doesn't support DTS, Emby will remux to a supported format.

Share this post


Link to post
Share on other sites
ebr

Sounds like the Roku firmware 9.3 issue.  We are looking into it but maybe they'll fix it in an update before we can figure out what is going on :).

Share this post


Link to post
Share on other sites
10479
1 hour ago, mastrmind11 said:

what device is your roku connected to?  Roku's don't support DTS so they will us passthrough.  If your device doesn't support DTS, Emby will remux to a supported format.

Just a stereo TV and another TV with a sound bar that supports DTS. It does go to to AAC, however, it starts out strong and then just falls on its face from direct streaming (not direct playback) and interrupts playback quite often. It's a new development and has worked fine in the past.

45 minutes ago, ebr said:

Sounds like the Roku firmware 9.3 issue.  We are looking into it but maybe they'll fix it in an update before we can figure out what is going on :).

Okay. Hopefully it gets sorted one way or another. It looks like there's no options to roll back Roku firmware and lock it in. I've tried just about every arrangement of configurations to get it to work, but so far the only thing is to disable throttling, which implies some sort of compatibility. It's just less than ideal with some of my more indecisive viewers to fully transcode multiple files that never get watched.

Share this post


Link to post
Share on other sites
10479

Yeah, so it looks specific to roku. An Xbox will direct stream fine and when in force the roku to DTS on the stereo TV, it will direct play fine, albeit without sound. Not sure if this can be moved to the roku forum or not, but it isn't Linux related.

Share this post


Link to post
Share on other sites
speechles
Posted (edited)

The Emby app on Roku reads the supported codecs directly from the device. To disable DTS you just need to choose something other than AUTO in your HDMI/Audio settings on your Roku. The Emby app reads the main Roku audio/video settings to determine specific support for each and every codec(and for a few other things) for both audio and video. You can choose Dolby or Dolby+ but don't choose one with DTS included. This is easy to fix for users they just need to be educated that we do not have settings for this in the app. The main Roku settings are all you need.

It is unfortunate that Roku has some problems with either their engineers or their pool of Beta testers for their new firmwares is incredibly small, if not, microscopic. A drop in the ocean. Either way, there seems to be more problems inherited by Emby that were created by Roku that we wind up having to temporarily solve. This does slow down some features and cool things from being worked on because we have to chase our tails, so to speak. Known as "chasing rabbits" or "..in the rabbit hole". This is why we are HOPE and will CROSS OUR FINGERS that Roku understands their userbase is upset, does something about it, and pushes a new firmware update with bug fixes. Hope is the dream that things can get better when control of things are not within your grasp. We can only hope.

Edited by speechles

Share this post


Link to post
Share on other sites
10479

Just to make sure, I just went back and tried PCM, DD and DD+ and all of them experienced the same issue with playback failing and buffering throughout until finally ending up on hardware transcoding and playing through just fine.

I'm happy to take any specific steps and provide debug logging if needed. Everything works great if I disable throttling.

Share this post


Link to post
Share on other sites
ebr
18 hours ago, 10479 said:

Everything works great if I disable throttling

Something in the 9.3 Roku firmware update has somehow impacted our throttling and we are still trying to figure out what it is.

Thanks.

Share this post


Link to post
Share on other sites
10479

Okay, that definitely makes sense. I was pulling my hair out trying to figure out what had gone wrong as I had just also recently rebuilt the server. I sent you a fairly detailed description with a debug log from the Roku just a little bit ago. Going through all of these steps at least put my mind at ease for now. Thanks for you time.

Share this post


Link to post
Share on other sites
Luke

Are you still having an issue with this?

Share this post


Link to post
Share on other sites
10479

Yeah. I just turned throttling off and started testing both the stable emby for Roku and the current beta build 7 and it happened in both of them.

Share this post


Link to post
Share on other sites
Luke

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

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