Wowza Community

Issues with JWPLAYER and Adaptive Bit Rate

I just tested in JW Player 6 and evidently the .rss playlist is deprecated, it no longer works. The smil version does work though.

file: "http://localhost:1935/vod/smil:sample.smil/jwplayer.smil"

However, you are using Wowza version 3.1.2 build1624, and support for smil in JW Player was added in 3.5. So you must upgrade to do this with JW Player 6. It should still work in JW Player 5, but I suggest upgrading Wowza instead of downgrading JW Player. You can upgrade with this patch:

http://www.wowza.com/downloads/WowzaMediaServer-3-6-2/WowzaMediaServer-3.x.x-3.6.2.zip

And while you at it you might as well apply the latest patch, which you would copy over the above upgrade patch

Richard

Did you copy old configuration files from the old version to the new, specifically /conf/VHost.xml? That’s my guess, since the rss version still works but the smil file doesn’t. If so, please revert.

Richard

You messed it up when you copied the old files, the change you need is in the new VHost.xml

Also, you changed the URL. It was correct before, now it is wrong. Go back to the URL you had before, and revert to the new configuration files. Or just re-install Wowza. It might be difficult to straighten things out after copying old conf files over the patch.

Richard

There is no automated way to generate smil file

Richard

Refer to the 2nd example is the JW Player 6 Guide

Richard

This still works:

http://s4.tilda.com.tr:80/vod/smil:onur.smil/jwplayer.rss

But this still does not work:

http://s4.tilda.com.tr:80/vod/smil:onur.smil/jwplayer.smil

I know you mucked up the conf files, so I recommend you do a fresh install. The above works in Wowza 3.6.2

Upgrade Wowza (correctly) or downgrade JW Player to version 5. I recommend upgrading Wowza. But don’t copy old configuration files over it, much of the upgrade is in those files.

Richard

Again, if you do a fresh install this will work. Try that.

Richard

I don’t recommend this based on what you have told me, but you can probably just add the necessary RequestFilter to the /conf/VHost.xml file. Search for “com.wowza.wms.http.HTTPProviderMediaList”, then replace the RequestFilter below that to this:

<RequestFilters>*jwplayer.rss|*jwplayer.smil|*medialist.smil|*manifest-rtmp.f4m</RequestFilters>

But fresh install is still recommended

Richard

Be sure to re-start Wowza after this change

Richard

Consider my prior suggestions

Richard

Are you using the jwplay.rss or jwplayer.smil?

Since only the jwplayer.rss feed works for you, and that works in JW Player 5, be sure you are using that

Richard

JW player uses Flash Dynamic Streaming, the user does not select quality, the player switches as necessary. Glad it’s working. They have a quality monitor plugin that shows the switching and other data.

Richard

What version of Wowza are you using?

In my test using 1936, the meta base value shows 1936.

http://localhost:1936/vod/smil:sample.smil/jwplayer.smil

sample.smil

<smil>
<head>
<meta base="rtmp://localhost:1936/vod/_definst_"/>
</head>
<body>
<switch>
<video src="mp4:sample.mp4" system-bitrate="1500000"/>
</switch>
</body>
</smil>

Richard

fair enough, I ended up copying player.swf to the same folder as index.php (as opposed to jwplayer where it was) and now the box pops up along with the quality monitor display, but no video. clicking on the play arrow just ends up with an ajax circle going round and round indefinitely. confirmed again I was able to access the ‘playlistfile’ value directly by putting it into the address bar.

Now I’m really losing it. When I look at the stream in the streammanager, my NGRPs are no longer listed. furthermore, the request for the RSS returns:

WARN server comment - HTTPProviderMediaList.onHTTPRequest: MediaList not found:

I really have no clue why the NGRPs aren’t listed like they used to be.

Sorry… after using VLC to investigate further, I realized that my origin server wasn’t functioning properly, therefore the Edge was messing up. Now I brought everything back up and I do see the NGRPs in the stream manager of the transcoder/edge server and the RSS is being generated again.

So now it appears to be working fine (the problem was upstream so to speak). I can’t tell you why I’m using stream manager to start the streams, but they don’t start on their own and I haven’t gotten to the point where I’m interested in figuring that out, but I will have to.

Now my remaining issue is incorporating mobile devices into it. I guess the RSS is strictly for flash devices, so I need to incorporate a fallback for HLS/HTML5 for the iOS devices. On that token, is there any way on the iOS device to tell what the bitrate is?

Thanks for the help so far, sorry I’m most of the problem.

I wanted to add my issue in this topic instead of openning a new one .

I am having trouble with wowza transcoder and jwplayer rss playlist.

Always saying , Playlist could not be loaded : No playable sources found.

Here is my embed code for jw player :

Loading video player…

Any help would be great.

Onur.

With changing the playlistfile error becomes : Error loading player : No playable sources found .

In that example they use playlistfile for vod . I am trying to play live stream with transcoder.

Yes , in my code there is no blank . when i remove blank the smile appears with “:o” :slight_smile:

I have replaced my code with :

<head>
<script src='http://s4.tilda.com.tr:8080/jwplayer/jwplayer.js'></script>
</head>
<div id='playerdiv'>Loading video player…</div>
<script type="text/javascript">
jwplayer( "playerdiv" ).setup( {
playlist: [{
                image: "/images/test.jpg", 
                sources: [{ 
                        file : "http://s4.tilda.com.tr:80/live/ngrp:onur_all/jwplayer.rss"
                }]
}],
primary: "flash",
controls: true,
width: "854",
height: "480"
});
</script>

Still having errors.

To make things clear , if i see "

http://s4.tilda.com.tr:80/live/ngrp:onur_all/jwplayer.rss

" within my browser or any text editor with my 3 streams that produced from transcoder addon , the wowza configurations are true , Right ?

Maybe my crossdomain.xml causes that error ?