streaming video to Roku problem

Archived
1

I want to stream an online video to Roku’s play-on-Roku, using this url:
“http://” + host + String.format(“15985?t=v&u=%s&k=(null)&h=%s&videoName=%s&videoFormat=%s”,
encode(url),
encode(host),
encode(title),
encode(mediaFormat))

in which host is Roku’s ip address + “:8060”, like this: 192.168.1.137:8060,
url is the online video url, like “http://voyagerapps.com/ytb001.mp4” or “https://voyagerapps.com/ytb001.mp4”
title is the String that will show on the screen when play-on-Roku is retrieving video,
mediaFormat is the mediaFormat of the online video.

Here is my question, when the url starts with “http:”, it works fine. However, when loading “https:” url, it stops working. play-on-Roku just “crashes” and return to HOME screen.

Is there a way to fix it?

And one more question: when play-on-Roku is playing an online video, how to retrieve playing information like “video duration”, “playing status(pause or play)”, “video playing position(the current progress/postion of the video which is currently playing)”?

Thanks in advance.

2

I too seem to have an issue where https video streams are not working.

The following video plays fine…

http://wowzaec2demo.streamlock.net/vod/ … ylist.m3u8

But when made https, the video will no longer play.

https://wowzaec2demo.streamlock.net/vod … ylist.m3u8

Both videos play without issue in VLC Media Player.

3

“greubel” wrote:
Tried the URLs with my channel’s Remote Push and the https: failed.
Added this change to my video routine.

   if instr( 0, Lcase( url ), "https:" ) > 0
      vid.SetCertificatesFile("common:/certs/ca-bundle.crt")
      vid.InitClientCertificates()
   end if

And now it works.
So possibly Roku needs to add the same check on their PUSH !
Roku has always required you to set the certificates file for HTTPS requests, with all of their components.

4

“greubel” wrote:
But what happens on a PUSH request for Play-On-Roku ?
They must not check ! I wasn’t !
Oh, sorry. I see what you’re saying. I missed that the OP was asking about Play On Roku specifically.

5

“TheEndless” wrote:
Roku has always required you to set the certificates file for HTTPS requests, with all of their components.
How about this “radical” idea - make all ifHttpAgent components have a pre-set, default certificates path? Regardless if it is https even.

“Oh the horror” - but hear me out, that would be backwards compatible, since all code that already does SetCertificatesFile() will continue to work. And the influx of cries by developers that https does not work will stop. And this Play-on-Roku thing will also “magically” work with https.

6

“EnTerr” wrote:

“TheEndless” wrote:
Roku has always required you to set the certificates file for HTTPS requests, with all of their components.
How about this “radical” idea - make all ifHttpAgent components have a pre-set, default certificates path? Regardless if it is https even.

“Oh the horror” - but hear me out, that would be backwards compatible, since all code that already does SetCertificatesFile() will continue to work. And the influx of cries by developers that https does not work will stop. And this Play-on-Roku thing will also “magically” work with https.
Doesn’t seem that “radical”.. in fact, I would have expected it. Not sure why Roku chose not to include the certs, by default.

7

^ What he said.

-JT