"renojim" wrote:
any idea why GetNowNextPrograms() doesn't seem to work?
I can see a great opportunity for Roku: utilize the OTA EPG with a "guide" channel, RMP, and a USB drive and you've got a DVR. Tell me a smart TV with basically a free DVR wouldn't be a hit among cord cutters.
"EnTerr" wrote:
(B) The minimum use case is for tvinput.dtv to just do that for /keypress/Lit_[0-9.]|Enter , w/o any UI element. Easy-peasy. And the beauty of it - again - is that nobody will need to update their remote app for this to work! Let's go with an example, a popular J/S remote: http://remoku.tv/ being able to "dial" channel# as-is, w/o any changes to the site.
"RokuKC" wrote:"EnTerr" wrote:
(B) The minimum use case is for tvinput.dtv to just do that for /keypress/Lit_[0-9.]|Enter , w/o any UI element. Easy-peasy. And the beauty of it - again - is that nobody will need to update their remote app for this to work! Let's go with an example, a popular J/S remote: http://remoku.tv/ being able to "dial" channel# as-is, w/o any changes to the site.
Given that Roku remotes don't have a numeric keypad, I don't see worthwhile value in this.
Smart remotes can use the ECP services to provide an intelligent TV channel selection UI, which is a much better user experience than the class dumb / 'trial and error' TV channel number entry.
"EnTerr" wrote:
Certainly a better TV channel UI is better - but who will re-do all existing apps?
"RokuKC" wrote:"EnTerr" wrote:
Certainly a better TV channel UI is better - but who will re-do all existing apps?
I'm not following your concern. I.e. I'm not aware of anything that would make these existing apps not work or have any different functionality than what the Roku remote provides. If an app wants to provide an enhanced user experience using the ECP APIs, that's up to them to do, or not, as the case might be.
"http wrote:The type="tvin" (and type="menu") did not have to be listed under ECP /query/apps - instead telling the app makers to re-write their apps to /keypress/InputHDMI1|InputHDMI2|InputHDMI3|InputTuner . But they do show now and that is a Good Thing - all apps that show list of channels suddenly got "upgraded" to being able to switch TV inputs. Same logic applies to dial-channel-by-number.
<apps>
<app id="tvinput.hdmi1" type="tvin" version="1.0.0">Satellite TV</app>
<app id="tvinput.hdmi2" type="tvin" version="1.0.0">Roku</app>
<app id="tvinput.hdmi3" type="tvin" version="1.0.0">Streaming box</app>
<app id="tvinput.dtv" type="tvin" version="1.0.0">Antenna TV</app>
<app id="12" type="appl" version="4.1.218">Netflix</app>
...
>>>To launch the TV input UI tuned to a particular TV channel, you can use launch/tvinput.dtv&ch=<CHANNEL_NUMBER>.
https://sdkdocs.roku.com/display/sdkdoc/External+Control+Guide#ExternalControlGuide-launch/tvinput.d...
Just in case others are interested in this: This launch requests works if you use “?” Instead of “&”, so tvinput.dtv?ch=xxx