Jump to content


Photo

Transcoding via emby connect


  • Please log in to reply
45 replies to this topic

#41 speechles ONLINE  

speechles

    Advanced Member

  • App Developer
  • 4482 posts
  • Local time: 04:57 PM

Posted 30 January 2018 - 05:00 PM

In the log it said subtitle codec not supported. I'm pretty sure that was it said in the sever dashboard as well. The user uses a ROKU Ultra from 2016

Sent from my STV100-3 using Tapatalk

 

In that case, they cannot use the * button to change things and expect emby to remember. This is the internal roku options menu and things here are not passed back to emby. Roku is forcing all apps to adopt this menu as the defacto standard and not attempt intercepting or trapping it. Some devices still allow intercept/trap, the roku ultra both 2016/2017 do not allow intercept/trap. Future firmwares of all devices will disallow any intercept or trap of the * button. Except for applications written in native code using roku's internal NDK, such as netflix, amazon, hulu, etc...

 

https://sdkdocs.roku...?pageId=1608547

 

The behavior of the Roku Options overlay has been modified, such that the Options overlay now slides in whenever the image2017-7-13%208%3A40%3A18.png?version button is pressed, the Video node is in focus, and the app does not have its OnKeyEvent() handler fired. When the Video node is not in focus, the Options overlay does not slide in and the OnKeyEvent() handler is fired.

 

 

 

Instead, they need to use the OK button to change things. This is the emby OSD menu, here they can change the audio track or subtitles and emby will remember it for next time.

 

Confusing, I know.. but this is the cost of doing business on the roku nowadays. Hopefully you and they both understand now. :)

 

EDiT: Once there is a pre-play audio/subtitles chooser it will help to reduce this confusion. *crosses fingers*


Edited by speechles, 30 January 2018 - 05:12 PM.


#42 speechles ONLINE  

speechles

    Advanced Member

  • App Developer
  • 4482 posts
  • Local time: 04:57 PM

Posted 30 January 2018 - 05:25 PM

As for eac3 I'm seeing it transcode on premiere+. Maybe it's because it's going direct to TV? AAC 5.1 doesn't complain though.

 

Going back to this one just to follow up better. The roku knows what it is connected to and what audio formats and channels are supported. So if your TV/AVR does not support dolby digital+ (eac3) then the app is smart enough to disable it and transcode this to a format that can be played. If you TV/AVR doesn't support digital theater surround, then DTS (dta) is disabled. If your TV/AVR is stereo only then dolby (ac3) is disabled too.

 

The devices (roku ultra, premier+, rokuTV) which support AAC 5.1 are capable of downsample to AAC 2.0 on-the-fly on the device. So AAC 5.1 can play on a stereo TV directly. This is the only on-device transcoding taking place. The rest of the transcoding is provided by emby server, which you know already.. :)


Edited by speechles, 30 January 2018 - 05:28 PM.


#43 lorac OFFLINE  

lorac

    Advanced Member

  • Members
  • 375 posts
  • Local time: 04:57 PM
  • LocationVancouver, Canada

Posted 30 January 2018 - 05:32 PM

Going back to this one just to follow up better. The roku knows what it is connected to and what audio formats and channels are supported. So if your TV/AVR does not support dolby digital+ (eac3) then the app is smart enough to disable it and transcode this to a format that can be played. If you TV/AVR doesn't support digital theater surround, then DTS (dta) is disabled. If your TV/AVR is stereo only then dolby (ac3) is disabled too.

The devices (roku ultra, premier+, rokuTV) which support AAC 5.1 are capable of downsample to AAC 2.0 on-the-fly on the device. So AAC 5.1 can play on a stereo TV directly. This is the only on-device transcoding taking place. The rest of the transcoding is provided by emby server, which you know already.. :)

Well at least the Roku is smart enough to do something properly...

Sent from my STV100-3 using Tapatalk

#44 speechles ONLINE  

speechles

    Advanced Member

  • App Developer
  • 4482 posts
  • Local time: 04:57 PM

Posted 30 January 2018 - 06:03 PM

Well at least the Roku is smart enough to do something properly...

 

The audio capability reporting is properly detecting support. That part I can see no issues with. The problem is when the roku takes it upon itself to decimate AAC 5.1 to AAC 2.0 even when used on a system supporting surround codecs. The proper thing for roku to do, is allow the system to downsample AAC 5.1 to AAC 2.0 if the device only supports stereo. In that case, the device should report it supports AAC 5.1 even though it really isnt.

 

The problem is with systems that support surround sound, keeping that in surround is important. To have the system report it supports AAC 5.1 and have it downsample to AAC 2.0 rather than allow the emby server to preserve the 5.1 sound in either AC3 or EAC3 is just arrogant. So a setting is required to stop the roku from doing this when surround sound is present. I would rather have audio transcoded to keep surround, than direct play in simple stereo.

 

Others may not feel this way, and feel that the way roku does it on the device is fine if it allows direct play. These are two different mindsets and the option allows both to use the same app without compromise.

 

The roku is only as smart as the application running on it. The application is only as smart as those responsible for developing it. Those developing it are only as smart as their tinkering has allowed. My tinkering has allowed me several hundred hours to test all sorts of crazy options you can find in the blue neon app. It is this knowledge that was passed down that makes the new app work as well as it does. Sharing is caring. :P



#45 lorac OFFLINE  

lorac

    Advanced Member

  • Members
  • 375 posts
  • Local time: 04:57 PM
  • LocationVancouver, Canada

Posted 30 January 2018 - 06:24 PM

The audio capability reporting is properly detecting support. That part I can see no issues with. The problem is when the roku takes it upon itself to decimate AAC 5.1 to AAC 2.0 even when used on a system supporting surround codecs. The proper thing for roku to do, is allow the system to downsample AAC 5.1 to AAC 2.0 if the device only supports stereo. In that case, the device should report it supports AAC 5.1 even though it really isnt.

The problem is with systems that support surround sound, keeping that in surround is important. To have the system report it supports AAC 5.1 and have it downsample to AAC 2.0 rather than allow the emby server to preserve the 5.1 sound in either AC3 or EAC3 is just arrogant. So a setting is required to stop the roku from doing this when surround sound is present. I would rather have audio transcoded to keep surround, than direct play in simple stereo.

Others may not feel this way, and feel that the way roku does it on the device is fine if it allows direct play. These are two different mindsets and the option allows both to use the same app without compromise.

The roku is only as smart as the application running on it. The application is only as smart as those responsible for developing it. Those developing it are only as smart as their tinkering has allowed. My tinkering has allowed me several hundred hours to test all sorts of crazy options you can find in the blue neon app. It is this knowledge that was passed down that makes the new app work as well as it does. Sharing is caring. :P

So you're saying it would be nice and caring if emby Dev's were to open the Roku app back up...

Sent from my STV100-3 using Tapatalk

#46 ebr ONLINE  

ebr

    Chief Bottle Washer

  • Administrators
  • 44948 posts
  • Local time: 07:57 PM

Posted 30 January 2018 - 06:39 PM

So a setting is required to stop the roku from doing this when surround sound is present.

 

Just FYI this setting exists now in the beta of the official app.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users