Jump to content


Photo

Transcoding instead of direct streaming


  • Please log in to reply
8 replies to this topic

#1 Dan_Austin OFFLINE  

Dan_Austin

    Advanced Member

  • Members
  • 61 posts
  • Local time: 07:37 AM

Posted 19 October 2019 - 12:00 AM

I noticed this morning higher than normal FFMPEG cpu usage on my server

while watching live TV. I originally thought it was a server side change, but it wasn't.

 

Turns out that the Roku Emby client 175 will DirectStream the chosen channel and

188 transcodes it instead.  Luke mentioned in another thread that the channel was

being transcoded for a good reason and to ask here if I'd like to know why.

 

I'm guessing a new feature that depends on that change, since I haven't had any

issues with the DirectStream in the past, but I am generally curious.



#2 ebr ONLINE  

ebr

    Chief Bottle Washer

  • Administrators
  • 47694 posts
  • Local time: 10:37 AM

Posted 19 October 2019 - 10:16 AM

Hi.  What did the server dashboard say as the reason?

 

Also, the Stats for nerds in the app will tell you exactly what is going on.

 

Thanks.



#3 Dan_Austin OFFLINE  

Dan_Austin

    Advanced Member

  • Members
  • 61 posts
  • Local time: 07:37 AM

Posted 19 October 2019 - 12:03 PM

Testing with client versions 175 and 188.  For both 'Stats for Nerds' reports 'Container not Supported'.

Both result in a M3U8 container.  175 with an MPEG2VIDEO stream and 188 with an H264.  All other

stats (except bitrate obviously) are identical.  Audio is identified as AC3 on both.

 

With 188 the dashboard reports 'Container not Supported' and is transcoding MPEG2VIDEO to H264 (AVC)

 

With 175 the dashboard reports direct streaming, with compatible media in an unsupported container.

 

All tests are using the same Roku pointed at the same beta server and tuned to the exact same channel,

seconds apart.  Both apps have identical settings.  I suspect quality is the key one and it is set to auto

on both, and the Roku is using a wired connection. The source is an HD Homerun.

 

I am happy to provide any additional details or logs from each.


Edited by Dan_Austin, 19 October 2019 - 12:04 PM.


#4 ebr ONLINE  

ebr

    Chief Bottle Washer

  • Administrators
  • 47694 posts
  • Local time: 10:37 AM

Posted 19 October 2019 - 05:34 PM

Hi.  Yes, we have been getting a lot of reports of problems with mpeg2 on most Roku devices so we now will transcode to H264 in most instances.



#5 Dan_Austin OFFLINE  

Dan_Austin

    Advanced Member

  • Members
  • 61 posts
  • Local time: 07:37 AM

Posted 19 October 2019 - 10:14 PM

Well crud.  I've never had an issue with MPEG2 from the HDHR other than the

incompatibility with TS 'containers' forcing direct stream/remux.

 

Any chance this can be made an option and defaulting to on with the next 'release' update?

 

If not I guess I either need to figure out GPU hardware acceleration in a docker or

see if a shield or one of the better Android media boxes has a decent remote and

ability to avoid transcoding



#6 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 140579 posts
  • Local time: 10:37 AM

Posted 21 October 2019 - 05:28 PM

An options is possible, yes. I'm going to be reviewing all of the options in the app to see what makes sense. Thanks.



#7 ebr ONLINE  

ebr

    Chief Bottle Washer

  • Administrators
  • 47694 posts
  • Local time: 10:37 AM

Posted 11 November 2019 - 11:32 AM

Hi.  Can you test this with the latest beta of the Roku app and see if it is improved for you?



#8 Dan_Austin OFFLINE  

Dan_Austin

    Advanced Member

  • Members
  • 61 posts
  • Local time: 07:37 AM

Posted 11 November 2019 - 11:51 AM

Huge improvement.  The EmbyServer process is still using quite a bit of processor,

but I understand that was from timestamp analysis and correction, so well worth it.

 

FFMPEG went from 2.5~3 cores fully used to 3.4% of a single core.  The dashboard

confirms it is direct streaming again.

 

Thanks-



#9 ebr ONLINE  

ebr

    Chief Bottle Washer

  • Administrators
  • 47694 posts
  • Local time: 10:37 AM

Posted 11 November 2019 - 12:29 PM

Excellent.  Thanks for reporting back.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users