# RTMP Adaptive with HLS Adaptive Fallback **URL:** \ **Category:** Wowza Streaming Engine\ **Tags:** media-players-and-devices\ **Created:** [November 4, 2013, 4:40pm UTC](https://community.wowza.com/t/rtmp-adaptive-with-hls-adaptive-fallback/34306 "2013-11-04T16:40:44Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Leigh\_Spiegel](https://avatars.discourse-cdn.com/v4/letter/l/7c8e57/32.png) [@Leigh\_Spiegel](https://community.wowza.com/u/Leigh_Spiegel)\ **Post date:** [November 4, 2013, 4:40pm UTC](https://community.wowza.com/t/rtmp-adaptive-with-hls-adaptive-fallback/34306/1 "2013-11-04T16:40:44Z")
Hello, I can’t see an example so I’m not sure if it is even possible can you do rtmp adaptive with hls adaptive fallback? JWPlayer 6 works (but the rtmp is not adaptive) sources: [ {file: ‘rtmp://hostname/live/stream1’}, {file: ‘[http://hostname/live/smil:stream.smil/manifest.m3u8](http://hostname/live/smil:stream.smil/manifest.m3u8)’} ], rtmp: { bufferlength: 0.1 } So if in a web browser with flash plays the stream1 the HQ version with very low latency (about 1 second) great. If on iPhone plays the smil with adaptive HLS and about 6 seconds latency. I can’t figure out the smil setup need to go rtmp will adaptive streaming. Does Smil even work in RTMP mode? Appreciate some guidance on this, I suspect it’s unusually. End Goal, RTMP and have adaptive bitrate otherwise HLS adaptive bitrate. My Wowza listens on port 80 (as well as the default) so rtmp on port 80 works fine. ---
**Author:** ![Richard\_Lanham](https://avatars.discourse-cdn.com/v4/letter/r/c68b51/32.png) [@Richard\_Lanham](https://community.wowza.com/u/Richard_Lanham)\ **Post date:** [November 4, 2013, 4:27pm UTC](https://community.wowza.com/t/rtmp-adaptive-with-hls-adaptive-fallback/34306/2 "2013-11-04T16:27:26Z")
The 2nd example in the [JW Player 6 guide](https://www.wowza.com/docs/how-to-use-jw-player-with-wowza-streaming-engine) shows how to do RTMP Dynamic streaming using JW Player, and leveraging the Wowza server-side smil Richard ---
**Author:** ![Richard\_Lanham](https://avatars.discourse-cdn.com/v4/letter/r/c68b51/32.png) [@Richard\_Lanham](https://community.wowza.com/u/Richard_Lanham)\ **Post date:** [November 5, 2013, 4:25pm UTC](https://community.wowza.com/t/rtmp-adaptive-with-hls-adaptive-fallback/34306/3 "2013-11-05T16:25:43Z")
Speegs, The /conf/VHost.xml /HostPort (/Port “1935”) /HTTPProvider should look like this: ```auto com.wowza.wms.http.HTTPProviderMediaList *jwplayer.rss|*jwplayer.smil none ``` Not sure how yours lost the “\*jwplayer.smil” part, but it should work in Wowza 3.6.2 You might want to [upgrade to 3.6.3 using this patch](https://www.wowza.com/docs/wowza-streaming-engine-software-updates). Richard ---
**Author:** ![Richard\_Lanham](https://avatars.discourse-cdn.com/v4/letter/r/c68b51/32.png) [@Richard\_Lanham](https://community.wowza.com/u/Richard_Lanham)\ **Post date:** [November 6, 2013, 4:03pm UTC](https://community.wowza.com/t/rtmp-adaptive-with-hls-adaptive-fallback/34306/4 "2013-11-06T16:03:24Z")
Cool, thanks for the update, Speegs. Glad it’s working. Richard ---
**Author:** ![Leigh\_Spiegel](https://avatars.discourse-cdn.com/v4/letter/l/7c8e57/32.png) [@Leigh\_Spiegel](https://community.wowza.com/u/Leigh_Spiegel)\ **Post date:** [November 5, 2013, 11:02am UTC](https://community.wowza.com/t/rtmp-adaptive-with-hls-adaptive-fallback/34306/5 "2013-11-05T11:02:56Z")
> The 2nd example in the [JW Player 6 guide](https://www.wowza.com/docs/how-to-use-jw-player-with-wowza-streaming-engine) shows how to do RTMP Dynamic streaming using JW Player, and leveraging the Wowza server-side smil > > Richard Hello, I followed the guide but I think the server is not generating the extra stuff for jwplayer, my version is new enough, I think I’m typing the url correctly and my smil file in the content directory is very simple. I’m sure it’s something simple but I’m not spotting it. When I used this URL: [http://server:1935/live/smil:streamname.smil/jwplayer.smil](http://server:1935/live/smil:streamname.smil/jwplayer.smil) I get back: Wowza Media Server 3 Monthly Edition 3.6.2 build5334 In a browser. When I use this URL: [http://server:1935/live/smil:streamname.smil/manifest.m3u8](http://server:1935/live/smil:streamname.smil/manifest.m3u8) I get back the manifest file that looks like this: #EXTM3U #EXT-X-VERSION:3 #EXT-X-STREAM-INF:PROGRAM-ID=1,BANDWIDTH=800000 chunklist\_w1471970683\_b800000.m3u8 #EXT-X-STREAM-INF:PROGRAM-ID=1,BANDWIDTH=300000 chunklist\_w1471970683\_b300000.m3u8 My Smil file is like this: The SMIL URL works great for HLS with the manifest.m3u8. With the jwplayer.smil url I’m getting this Error: Mainfest not found or invalid in JWPlayer 6.6.3896 Premium edition. I also tried adding this to the Vhost.xml and using the .rss method but no luck. com.wowza.wms.http.HTTPProviderMediaList \*jwplayer.rss none Is there something extra I need to do to enable Wowza to generate a jwplayer.smil? Appreciate it if anyone can spot what I could be doing wrong or if I have my understanding completely wrong of how it’s supposed to work. Regards, Speegs ---
**Author:** ![Leigh\_Spiegel](https://avatars.discourse-cdn.com/v4/letter/l/7c8e57/32.png) [@Leigh\_Spiegel](https://community.wowza.com/u/Leigh_Spiegel)\ **Post date:** [November 6, 2013, 5:17pm UTC](https://community.wowza.com/t/rtmp-adaptive-with-hls-adaptive-fallback/34306/6 "2013-11-06T17:17:53Z")
> Speegs, > > The /conf/VHost.xml /HostPort (/Port “1935”) /HTTPProvider should look like this: > > ```auto > > com.wowza.wms.http.HTTPProviderMediaList > *jwplayer.rss|*jwplayer.smil > none > > > ``` > > Not sure how yours lost the “\*jwplayer.smil” part, but it should work in Wowza 3.6.2 > > You might want to [upgrade to 3.6.3 using this patch](https://www.wowza.com/docs/wowza-streaming-engine-software-updates). > > Richard Added that code and still didn’t work. Felt like I was going in circles so I completely re-installed everything and then added my customisations manually to the config files to to bring my setup back and fixed it. Was something in my config somewhere, but couldn’t pinpoint what it was. Anyone else having that problem, might be time to start over. Last fresh start I did was Wowza 2.0, so worth doing every now and then. Thanks for the help.