Stuttering after pause

[pwhodges 2120]

4 hours ago, user84 said:

So I’m not seeing the clutter you described, and the 5.1 AAC track is what’s forcing the remux. You still think it's the container?

The order in which streams and metadata are combined within the MKV file can vary, and there are ways to optimise this ordering for streaming use (when the player can't see the whole file at once).  Remuxing in MKVToolNix picks the streams and metadata apart and recombines them following the rules for streaming - same data, but different file and compatibility.

Paul

[user84 54]

2 hours ago, ebr said:

Probably but perhaps only by coincidence.

Given your testing, the issue is related to the remux that is happening on the server - and only in the case of when you pause for a long time and then resume.  So, changing the audio will avoid the remux on the server and, thus, the problem.  What, exactly, is causing that problem is still a bit of a mystery in my view.

Before I move on from this, I just want to say that what you have said here has been my question all along. When I raised this a while back, and now it's coming up again, I do think that there is some problem that exists that could solve this issue that has yet to be identified. 

I finally found my old thread when I brought this up previously. A similar explanation was given, and I followed the steps provided to convert everything to MKV using MKVtoolnix. Both @ebrand @speechles were involved in that thread as well. This is a heck of a lot of work for me to do when I have to alter my library.

Now here I am years later making AC3 audio the number one track to solve the same problem.

If I'm being honest, the responses I've gotten to solve this problem have been extremely unsatisfactory. I'm happy to keep using Emby because it currently meets my needs.. But this is far from a solved issue. 

 

Here is the previous thread: 

 

[speechles 2125]

Back when you first had the issue the Roku was able to convert AAC 5.1 into AAC 2.0 on most of their devices. Roku was paying royalties to have that ability in their devices.

Rather than continue to incur that charge they removed the ability for Roku to play AAC 5.1 entirely. This change was done rather recently. The only reason Roku TV was missed in that change is because the TV hardware supports it and pays the charge. 

The fact you could convert the AAC 5.1 to AC3 with ffmpeg and make it play is exactly what Emby is supposed to be doing. But there are problems with it guessing the timestamps. Did you conversion with ffmpeg show the same issue? This isn't caused by the Roku app. This is something different in ffmpeg.

Edited October 9 by speechles

[user84 54]

1 hour ago, speechles said:

Back when you first had the issue the Roku was able to convert AAC 5.1 into AAC 2.0 on most of their devices. Roku was paying royalties to have that ability in their devices.

Rather than continue to incur that charge they removed the ability for Roku to play AAC 5.1 entirely. This change was done rather recently. The only reason Roku TV was missed in that change is because the TV hardware supports it and pays the charge. 

The fact you could convert the AAC 5.1 to AC3 with ffmpeg and make it play is exactly what Emby is supposed to be doing. But there are problems with it guessing the timestamps. Did you conversion with ffmpeg show the same issue? This isn't caused by the Roku app. This is something different in ffmpeg.

I don't know what you mean by your last question - "Did my conversion with ffmpeg show the same issue". Can you explain?

[ebr 16937]

16 hours ago, user84 said:

This is a heck of a lot of work for me to do when I have to alter my library.

Hi.  Remuxing this one file in MKVToolNix should be very simple and only take a few seconds.  It may or may not solve the issue but it would eliminate the MKV packaging as the issue if the problem still occurred after doing that.

Alternatively, you could provide us a link to a media item that exhibits the problem and we could try to reproduce locally.

Thanks.

[user84 54]

2 hours ago, ebr said:

Hi.  Remuxing this one file in MKVToolNix should be very simple and only take a few seconds.  It may or may not solve the issue but it would eliminate the MKV packaging as the issue if the problem still occurred after doing that.

Alternatively, you could provide us a link to a media item that exhibits the problem and we could try to reproduce locally.

Thanks.

I appreciate the willingness to help, truly. I decided to run my library through ffmpeg and make ac3 track one. It will solve this moving forward and stop the need for me to troubleshoot, which is frustrating. It was annoying, I don't think this fixes the issue for others that use Emby, but it fixed it for me for now.

Thanks again!