Roku Developer Program

[SolveLLC]

"renojim" wrote:

"SolveLLC" wrote:
Here is an example of a HLS stream that played on the Roku1 2.9 and does not play on the Roku2 (hangs at 33% forever).

http://77.67.108.150/213.254.245.162/4e ... tream.m3u8

There should be commas at the end of your EXTINF lines if you don't have the optional title. MarkN and I had a discussion about this when 3.0 came out and I agreed with him that according to the spec the title is optional, but the comma is not. That m3u8 won't work on 3.0 either.

-JT

We don't control the feed. However, the above does work on Apple devices and it *did* work on Roku 2.9 (without supporting the mp3 audio).

[galexe]

"renojim" wrote:

"SolveLLC" wrote:
Here is an example of a HLS stream that played on the Roku1 2.9 and does not play on the Roku2 (hangs at 33% forever).

http://77.67.108.150/213.254.245.162/4e ... tream.m3u8

There should be commas at the end of your EXTINF lines if you don't have the optional title. MarkN and I had a discussion about this when 3.0 came out and I agreed with him that according to the spec the title is optional, but the comma is not. That m3u8 won't work on 3.0 either.

-JT

WOW thanks guys, this was a huge help! It would have taken awhile to find this.

[syan]

How do we fix thise issue in wowza?????? :oops:

[elan]

A bit of data here (from Plex). We send back this variant playlist and the Roku 2 immediately fails, it never requests any of the specific playlists.

Any ideas? We have a bunch of irate users 😞

#EXTM3U
#EXT-X-STREAM-INF:PROGRAM-ID=1,BANDWIDTH=720000
session/4488ade7ee98af05af2b3e1a5ee9c407daeb877e/4/index.m3u8
#EXT-X-STREAM-INF:PROGRAM-ID=1,BANDWIDTH=1500000
session/4488ade7ee98af05af2b3e1a5ee9c407daeb877e/5/index.m3u8
#EXT-X-STREAM-INF:PROGRAM-ID=1,BANDWIDTH=2000000
session/4488ade7ee98af05af2b3e1a5ee9c407daeb877e/6/index.m3u8
#EXT-X-STREAM-INF:PROGRAM-ID=1,BANDWIDTH=3000000
session/4488ade7ee98af05af2b3e1a5ee9c407daeb877e/7/index.m3u8
#EXT-X-STREAM-INF:PROGRAM-ID=1,BANDWIDTH=4000000
session/4488ade7ee98af05af2b3e1a5ee9c407daeb877e/8/index.m3u8

[dnelms]

"elan" wrote:
A bit of data here (from Plex). We send back this variant playlist and the Roku 2 immediately fails, it never requests any of the specific playlists.

Any ideas? We have a bunch of irate users 😞

#EXTM3U
#EXT-X-STREAM-INF:PROGRAM-ID=1,BANDWIDTH=720000
session/4488ade7ee98af05af2b3e1a5ee9c407daeb877e/4/index.m3u8
#EXT-X-STREAM-INF:PROGRAM-ID=1,BANDWIDTH=1500000
session/4488ade7ee98af05af2b3e1a5ee9c407daeb877e/5/index.m3u8
#EXT-X-STREAM-INF:PROGRAM-ID=1,BANDWIDTH=2000000
session/4488ade7ee98af05af2b3e1a5ee9c407daeb877e/6/index.m3u8
#EXT-X-STREAM-INF:PROGRAM-ID=1,BANDWIDTH=3000000
session/4488ade7ee98af05af2b3e1a5ee9c407daeb877e/7/index.m3u8
#EXT-X-STREAM-INF:PROGRAM-ID=1,BANDWIDTH=4000000
session/4488ade7ee98af05af2b3e1a5ee9c407daeb877e/8/index.m3u8

Elan... as a plex user I want as solution as well. I'm just shooting in the dark here, but the post a few above from renojim, states the following:
There should be commas at the end of your EXTINF lines if you don't have the optional title. MarkN and I had a discussion about this when 3.0 came out and I agreed with him that according to the spec the title is optional, but the comma is not. That m3u8 won't work on 3.0 either.

Should you have have a comma at the end of the #EXT lines? Keep in mind I speaking as someone who has a very small understanding of this type of code, so I may be very far off base.

[renojim]

Elan's problem is different than the one I mentioned above. It's only the #EXTINF lines in simple playlists that require a comma at the end. I suspect Elan's problem has something to do with the relative URIs in the variant playlist, but that's pretty much just a guess.

-JT

[elan]

Basically it appears that the variant playlist parser only accepts full URLs, e.g.

http://x.x.x.x/foo/bar/baz.m3u8

It does not accept the relative URLs that Apple recommends here: http://developer.apple.com/library/ios/ ... index.html

bar/baz.m3u8

Nor does it accept absolute URL paths

/foo/bar/baz.m3u8

Hope that helps others looking into this problem, and thanks to JT for the hint!

[renojim]

Glad to help!

-JT

[destruk]

I don't understand how Apple would be able to find anything simply based on a relative URL? How does Apple know what server to go to?
"When possible, use relative path names in Variant Playlists and in the individual .m3u8 Playlist files"

Amazing how that Apple thingie works eh? Right...think different. 🙂

[TheEndless]

"destruk" wrote:
I don't understand how Apple would be able to find anything simply based on a relative URL? How does Apple know what server to go to?
"When possible, use relative path names in Variant Playlists and in the individual .m3u8 Playlist files"

Amazing how that Apple thingie works eh? Right...think different. 🙂

Relative to the URL of the m3u8, not relative in general. The same as relative paths work in web pages. They're assumed relative to the page that contains them.