Name is required.
Email address is required.
Invalid email address
Answer is required.
Exceeding max length of 5KB

HLS streaming for desktop browsers (Flash), .m3u8 cross-domain error


We just purchased a Premium license and I'm in the process of migrating all of our streaming pages to the JW Player. The topic page states that "the Premium and Enterprise editions support HLS playback for desktop browsers (using Flash)." I would like to set up pages to adaptively stream our videos (1000+ streams) which were Flash only, single bit rate streams on our previous pages. If I can get this to work this would make a huge difference in terms of efficiency and storage space (3000+ video files vs. 6000+ files).

I want HLS streaming for both Flash and iOS devices in order to avoid having 6 files for each video stream (high, mid, low bandwidth for rtmp, same for Apache http streaming). Would this be possible using an .m3u8 manifest file loaded via an RSS feed? I have a test page that works with six files contained both a .smil manifest file (3 different bandwidths for Flash) and an .m3u8 file (same for HLS), but when I try it with only .m3u8 manifests on the Desktop I'm getting a cross-doman error (cannot load .m3u8: cross domain access denied).

First Question: Can this be done, and if so, what is the proper way to do this?
This is the page: http://www.librarymedia.net/Videogallery/Recent-test.html

This is what part of the rss file looks like (first three videos do not have the .smil manifests in the RSS):
<rss version="2.0" xmlns:jwplayer="http://rss.jwpcdn.com/">
<channel>
<title>THS Streaming</title>
<item>
<title>Board of Education Meeting</title>
<description>July 22, 2014</description>
<jwplayer:source file="Manifests/BOE-07222014.m3u8" />
<jwplayer:image>Splash/THS-TV-poster2.png</jwplayer:image>
</item>
<item>
<title>Class of 2014 Graduation</title>
<description>June 19, 2014</description>
<jwplayer:source file="Manifests/Graduation-06192014.m3u8" />
<jwplayer:image>Splash/Graduation-06192014.png</jwplayer:image>
<jwplayer:track file="Chapters/Graduation-06192014.vtt" kind="chapters" />
</item>.....etc.

I have cross-domain files on both the streaming server and the server hosting the player/page. The manifest files are on the same server as the player and I've tried to load them from the streaming and web servers. Get the same error regardless of where the .m3u8 manifest file is served from.
1. Wide open cross-domain file on both severs:
<?xml version="1.0"?>
<!DOCTYPE cross-domain-policy SYSTEM "http://www.adobe.com/xml/dtds/cross-domain-policy.dtd">
<cross-domain-policy>
<allow-access-from domain="*" />
</cross-domain-policy>

Again, this is the page: http://www.librarymedia.net/Videogallery/Recent-test.html Only the first 3 have the single .m3u8 manifests (cross-domain error). The others do have a .smil source so they work.

Thanks for the advice help.

2 Community Answers

cgarcia

Best Answer 

So weird. On a hunch I used a different program to make the crossdomain.xml file thinking that maybe there was an issue with the way the xml file was encoded. Now the page is working on most computers, but not others. Must be an issue with our network because it seems to be working fine.

So the problem was probably the way the cross-domain xml file was encoded. The first was a plain text file made in TextEdit, the second (working one) was made with TextMate. Don't see why that would make a difference.

Thanks for the help Mark.

View in conversation

mark

User  
0 rated :

looks like you have fixed it. Looked at your rss and it only lists m3u8 sources and the page and videos are working for me.

cgarcia

Best Answer  User  
0 rated :

So weird. On a hunch I used a different program to make the crossdomain.xml file thinking that maybe there was an issue with the way the xml file was encoded. Now the page is working on most computers, but not others. Must be an issue with our network because it seems to be working fine.

So the problem was probably the way the cross-domain xml file was encoded. The first was a plain text file made in TextEdit, the second (working one) was made with TextMate. Don't see why that would make a difference.

Thanks for the help Mark.

This question has received the maximum number of answers.