Adaptive provider oddness

This thread may refer to an older version of JW Player! Check our articles for the most up-to-date information.
This Q&A thread was imported from our previous system and could apply to an older product.
  • A single stream within the group works fine, but the named group results in a JW error "Cannot load M3U8: crossdomain access denied" which makes no sense since it works for the single stream. The crossdomainxml is set to allow all. Any idea why this would be? Here is more detail:

    Single stream access - This works fine:

    bc.. http-[server]/livetc/livetc.mp4_360p/playlist.m3u8


    ... which returns this ...

    bc.. #EXTM3U
    #EXT-X-VERSION:2
    #EXT-X-STREAM-INF:PROGRAM-ID=1,BANDWIDTH=590691,CODECS="avc1.77.30, mp4a.40.2",RESOLUTION=640x360
    playlist.m3u8?wowzasessionid=1077203360



    ... and the url in there returns this ...

    bc.. #EXTM3U
    #EXT-X-VERSION:2
    #EXT-X-ALLOW-CACHE:NO
    #EXT-X-TARGETDURATION:14
    #EXT-X-MEDIA-SEQUENCE:17
    #EXTINF:12,
    media_17.ts?wowzasessionid=1077203360
    #EXTINF:8,
    media_18.ts?wowzasessionid=1077203360
    #EXTINF:10,
    media_19.ts?wowzasessionid=1077203360




    Named group access - this results in a JW error "Cannot load M3U8: crossdomain access denied"

    http://[server]/ livetc/ngrp:livetc.mp4_all/playlist.m3u8

    ... which returns this (!! notice the difference in paths compared to single stream) ...

    #EXTM3U
    #EXT-X-VERSION:2
    #EXT-X-STREAM-INF:PROGRAM-ID=1,BANDWIDTH=891331,CODECS="avc1.77.31,mp4a.40.2",RESOLUTION=896x504
    /livetc/_definst_/mp4:livetc.mp4_source/playlist.m3u8?wowzasessionid=1267048161
    #EXT-X-STREAM-INF:PROGRAM-ID=1,BANDWIDTH=548036,CODECS="avc1.77.30,mp4a.40.2",RESOLUTION=640x360
    /livetc/_definst_/mp4:livetc.mp4_360p/playlist.m3u8?wowzasessionid=1267048161
    #EXT-X-STREAM-INF:PROGRAM-ID=1,BANDWIDTH=248036,CODECS="avc1.66.12,mp4a.40.2",RESOLUTION=284x160
    /livetc/_definst_/mp4:livetc.mp4_160p/playlist.m3u8?wowzasessionid=1267048161

    ... accessing one of the referenced playlists returns this (looks similar to single stream's second response) ...

    #EXTM3U
    #EXT-X-VERSION:2
    #EXT-X-ALLOW-CACHE:NO
    #EXT-X-TARGETDURATION:14
    #EXT-X-MEDIA-SEQUENCE:9
    #EXTINF:8,
    media_9.ts?wowzasessionid=1267048161
    #EXTINF:10,
    media_10.ts?wowzasessionid=1267048161
    #EXTINF:12,
    media_11.ts?wowzasessionid=1267048161


    Any idea why the path differences in the initial replies of single stream vs. name group causes JW to throw a crossdomain.xml issue? Is JW getting confused by the full path?

    Thanks!

  • This is indeed some sloppy programming from my part. The code doesn’t correctly detect domain-absolute URLS. I’ll look into it:

    http://developer.longtailvideo.com/trac/ticket/1617

    For now, if you refer to full absolute paths (http://example.com/playlist.m3u8) or to relative paths (../../playlist.m3u8), things should work.

     
    Up Down 0 rated
  • Thank you for looking into this, Jeroen! JW player has worked beautifully for our RTMP streaming needs for many years. I'm hopeful that we can also use it for HTTP adaptive streaming as our organization begins to adopt this new technology (primarily to enable Wowza nDVR which requires it).

    I'll look forward to hearing any updates. I'll also look into configuring Wowza to use full absolute paths for now.

    Up Down 0 rated
  • Dear Jeroen,

    I have exactly the same problem as Daved, but relative path solves the problem.

    The M3U8 files generated by Real 14 Helix Server can't be read by the Adaptative Provider plugin.

    My video server generates by default a M3U8 like that :
    bc.. EXTINF:10,
    /xxxxx/broadcast/live.mp4-20120315-102813-archive/1-82293.ts
    #EXTINF:10,
    /xxxxx/broadcast/live.mp4-20120315-102813-archive/2-90631.ts



    With relative path, it works GREAT !!! :]
    bc.. EXTINF:10,
    ../live.mp4-20120315-102813-archive/1-82293.ts
    #EXTINF:10,
    ../live.mp4-20120315-102813-archive/2-90631.ts



    We just have to change our server config to change base path during m3u8 live generation.

    Thanks Jeroen for this great job !!
    Best,



    Up Down 0 rated
  • Good to hear! I will also fix the usage of server-absolute paths in a small, upcoming update.

     
    Up Down 0 rated

This QA is closed.

Still don't have JW Player? Get It Here