Jump to content


Photo

Some MKV files play fine on my Roku 3s but not on my Ultras


  • Please log in to reply
17 replies to this topic

#1 Gilgamesh_48 OFFLINE  

Gilgamesh_48

    Advanced Member

  • Members
  • 743 posts
  • Local time: 01:23 PM
  • LocationTennessee

Posted 09 October 2019 - 02:17 PM

The title pretty much says what is happening. The MKVs that do not play on my Ultra do play fine on my Roku 3s, Fire TVs, my Shield TVs and in my browser.

 

On my Ultras the files start to load and the blue bar moves about 1/3 of the way then it just hangs. The only way out is to exit the app.

 

I am attaching a server log and a transcoder log.

Attached File  ServerTxt.txt   1.48MB   1 downloads~

Attached File  Transcoder.txt   12.01KB   2 downloads

 


  • speechles likes this

#2 ebr OFFLINE  

ebr

    Chief Bottle Washer

  • Administrators
  • 47016 posts
  • Local time: 01:23 PM

Posted 09 October 2019 - 02:26 PM

And if you turn off HW Accel?



#3 Gilgamesh_48 OFFLINE  

Gilgamesh_48

    Advanced Member

  • Members
  • 743 posts
  • Local time: 01:23 PM
  • LocationTennessee

Posted 09 October 2019 - 02:48 PM

And if you turn off HW Accel?

 

I had not thought of that but if I do turn it off the playback works just fine.

 

I guess I have a work around BUT, since it plays fine on my Roku 3s with HW accel on I would think that there is something wrong in the configuration or the software on the Ultras and it should be fixable. At least I hope it is. I prefer using HW accel as in somewhat reduces load on my server but I am the only user so I guess I can run without it for a while.



#4 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 138220 posts
  • Local time: 01:23 PM

Posted 09 October 2019 - 02:51 PM

Right, you shouldn't have to turn that off. It was just a useful test to see if it would make a difference. Thanks.



#5 Gilgamesh_48 OFFLINE  

Gilgamesh_48

    Advanced Member

  • Members
  • 743 posts
  • Local time: 01:23 PM
  • LocationTennessee

Posted 09 October 2019 - 05:12 PM

One little addition:

I further tested and if I use the server on my Shield instead of my regular server and have hardware acceleration turned on on the shield the "problem" files play fine.

 

I do not know if that matters at all but I thought I would report it.



#6 speechles OFFLINE  

speechles

    Advanced Member

  • App Developer
  • 5480 posts
  • Local time: 10:23 AM

Posted 09 October 2019 - 09:15 PM

One little addition:

I further tested and if I use the server on my Shield instead of my regular server and have hardware acceleration turned on on the shield the "problem" files play fine.

 

I do not know if that matters at all but I thought I would report it.

 

Apologies. I think we identified an issue that could cause the player to hang. This was related to our fallback mechanics. This fix is in the hotfix queue and will make the next Beta for Roku. If this does not fix the issue and the next Beta still has a problem I will get with you personally via PM to resolve your issue. Stay tuned. :)

 

Thank you for reporting the issue. This show us the scale of the possible impact. Thanks again. 


Edited by speechles, 09 October 2019 - 09:17 PM.


#7 ebr OFFLINE  

ebr

    Chief Bottle Washer

  • Administrators
  • 47016 posts
  • Local time: 01:23 PM

Posted 10 October 2019 - 11:57 AM

I believe this particular issue may be addressed in the beta server.

 

I do not believe it is related to the app changes we just made.

 

Thanks.



#8 Gilgamesh_48 OFFLINE  

Gilgamesh_48

    Advanced Member

  • Members
  • 743 posts
  • Local time: 01:23 PM
  • LocationTennessee

Posted 10 October 2019 - 12:19 PM

I believe this particular issue may be addressed in the beta server.

 

I do not believe it is related to the app changes we just made.

 

Thanks.

 

I am running the beta server ver 4.3.0.13 which I "think" is the latest beta. It still has the problem in it.

 

Has the fix not yet made it into the beta server?



#9 ebr OFFLINE  

ebr

    Chief Bottle Washer

  • Administrators
  • 47016 posts
  • Local time: 01:23 PM

Posted 10 October 2019 - 12:28 PM

I am running the beta server ver 4.3.0.13 which I "think" is the latest beta. It still has the problem in it.

 

Has the fix not yet made it into the beta server?

 

Hmmm... that's unfortunate. @softworkz?



#10 Gilgamesh_48 OFFLINE  

Gilgamesh_48

    Advanced Member

  • Members
  • 743 posts
  • Local time: 01:23 PM
  • LocationTennessee

Posted 10 October 2019 - 12:45 PM

Hmmm... that's unfortunate. @softworkz?

 

Is there any additional info that I could provide that would help find the problem?

 

Again it is only my Ultras that have the problem. My Roku 3s, Fire TVs, Shield Tv and the web interface all work fine with hardware acceleration enabled.



#11 speechles OFFLINE  

speechles

    Advanced Member

  • App Developer
  • 5480 posts
  • Local time: 10:23 AM

Posted 10 October 2019 - 12:53 PM

Is there any additional info that I could provide that would help find the problem?

 

Again it is only my Ultras that have the problem. My Roku 3s, Fire TVs, Shield Tv and the web interface all work fine with hardware acceleration enabled.

 

What is special about those MKV files? Do they create an ffmpeg log when you play them? Can you kindly share it with us. :)

 

If it isn't creating an ffmpeg log it is trying to direct play but the device is actively refusing? O_o;;? hard to tell if it isn't creating an ffmpeg log other than maybe ffmpeg isn't starting when it should. Can you share your Emby server log with us so we can check that too? 

 

Thanks. :)



#12 Gilgamesh_48 OFFLINE  

Gilgamesh_48

    Advanced Member

  • Members
  • 743 posts
  • Local time: 01:23 PM
  • LocationTennessee

Posted 10 October 2019 - 01:45 PM

What is special about those MKV files? Do they create an ffmpeg log when you play them? Can you kindly share it with us. :)

 

If it isn't creating an ffmpeg log it is trying to direct play but the device is actively refusing? O_o;;? hard to tell if it isn't creating an ffmpeg log other than maybe ffmpeg isn't starting when it should. Can you share your Emby server log with us so we can check that too? 

 

Thanks. :)

 

I attached a log to my first post but here are others that were just created:

 

These were generated while the froze bar was on the screen:

Attached File  E-Server-10-10-before forced exit.txt   293.73KB   2 downloads

Attached File  E-fmpegLog-10-10-before forced exit.txt   1.46MB   4 downloads

 

These were captured after I exited the app on my Ultra:

 

Attached File  E-Server-10-10-after forced exit.txt   616.13KB   2 downloads

Attached File  E-fmpeg-10-10-after forced exit.txt   1.59MB   3 downloads

 

I hope those are of some help. Again note that if I turn off HW Accl then the files play fine and they also play fine if I use my Server on my Shield.

 

Good luck. I understood almost nothing in the logs but I have never learned to speak and read Emby-a-Log. It is a more difficult language than Dutch or Japanese.



#13 ebr OFFLINE  

ebr

    Chief Bottle Washer

  • Administrators
  • 47016 posts
  • Local time: 01:23 PM

Posted 10 October 2019 - 01:53 PM

Let's see what Softworkz has to say.

 

Thanks.



#14 speechles OFFLINE  

speechles

    Advanced Member

  • App Developer
  • 5480 posts
  • Local time: 10:23 AM

Posted 10 October 2019 - 01:55 PM

It looks like it might be using level 5.2 when transcoding some of those. That would be a problem when it needs to be 5.1. We send the max level supported as 5.1 too. Something might be haywire ATM. This needs to be sent to the fellows upstairs. @Luke



#15 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 138220 posts
  • Local time: 01:23 PM

Posted 10 October 2019 - 03:45 PM

It looks like it might be using level 5.2 when transcoding some of those. That would be a problem when it needs to be 5.1. We send the max level supported as 5.1 too. Something might be haywire ATM. This needs to be sent to the fellows upstairs. @Luke

 

Anytime we transcode to h264, it is always level 4.1.



#16 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 138220 posts
  • Local time: 01:23 PM

Posted 10 October 2019 - 03:45 PM

I attached a log to my first post but here are others that were just created:

 

These were generated while the froze bar was on the screen:

attachicon.gifE-Server-10-10-before forced exit.txt

attachicon.gifE-fmpegLog-10-10-before forced exit.txt

 

These were captured after I exited the app on my Ultra:

 

attachicon.gifE-Server-10-10-after forced exit.txt

attachicon.gifE-fmpeg-10-10-after forced exit.txt

 

I hope those are of some help. Again note that if I turn off HW Accl then the files play fine and they also play fine if I use my Server on my Shield.

 

Good luck. I understood almost nothing in the logs but I have never learned to speak and read Emby-a-Log. It is a more difficult language than Dutch or Japanese.

 

Please make sure to attach using the original log file names so that we can see certain information from a glance. Thanks.



#17 softworkz OFFLINE  

softworkz

    Advanced Member

  • Developers
  • 1795 posts
  • Local time: 07:23 PM

Posted 12 October 2019 - 04:25 AM

It looks like it might be using level 5.2 when transcoding some of those. That would be a problem when it needs to be 5.1. We send the max level supported as 5.1 too. Something might be haywire ATM. This needs to be sent to the fellows upstairs. @Luke

 

 

Anytime we transcode to h264, it is always level 4.1.

 

Codec levels are not a concern of compatibility!

 

Those do not have any effects like that a video which has been encoded with a level too high for the decoder on the other side could not be played back by the decoder because it cannot handle the full set of special techniques that the encoder has used.

=> That is indicated by the "codec profile"

 

The level instead provides an indication of the encoder's or decoder's maximum throughput for realtime video de-/encoding.

That means that a decoder indicating "level 3.0" for example will also be able to decode a "level 6.0" video - just not in realtime.



#18 softworkz OFFLINE  

softworkz

    Advanced Member

  • Developers
  • 1795 posts
  • Local time: 07:23 PM

Posted 12 October 2019 - 04:29 AM

I attached a log to my first post but here are others that were just created:

 

These were generated while the froze bar was on the screen:

attachicon.gifE-Server-10-10-before forced exit.txt

attachicon.gifE-fmpegLog-10-10-before forced exit.txt

 

These were captured after I exited the app on my Ultra:

 

attachicon.gifE-Server-10-10-after forced exit.txt

attachicon.gifE-fmpeg-10-10-after forced exit.txt

 

I hope those are of some help. Again note that if I turn off HW Accl then the files play fine and they also play fine if I use my Server on my Shield.

 

Good luck. I understood almost nothing in the logs but I have never learned to speak and read Emby-a-Log. It is a more difficult language than Dutch or Japanese.

 

Could you please post a log of a file where it's working (with hw acceleration)?

Also include a hw detection log.

 

 

Further:

 

Does QuickSync work when you connect a monitor?

In this case you should see the QuickSync codecs doubled - each with and without D3D11 in its name.

Could you try both variants with a monitor connected?






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users