Multi-bitrate is not supported for RTSP, but the latest Android devices support Flash 10.1 so you can do RTMP or Flash HTTP streaming including multi-bitrate.
“Smooth streaming” refers to Silverlight HTTP streaming. If you mean smooth streaming generically, it depends on what you want to do. In general, HTTP multi-bitrate (including Cupertino/iOS, San jose/Flash HTTP and Silverlight/Smooth) streaming is probably better than RTMP dynamic streaming.
Again, I think HTTP is better than RTMP for multi-bitrate streaming. There are other good reasons to use RTMP (security, cuepoints, familiarity with certain player), but just in terms of best streaming, HTTP is probably better.
Wirecast is a good encoder that works with Wowza, however it will not work as the source of several multi-bitrate streams for any type of multi-bitrate streaming, because the streams are not key frame aligned…
Wirecast will work as the source for Wowza Transcoder to do every kind of multi-bitrate streaming. The Transcoder ensures key frame alignment.
FMLE (read the EULA) will work as source of several multi-bitrate streams to do every kind of multi-bitrate streaming without using Wowza Transcoder. The problem is EULA restrictions, and in some cases uplink bandwidth. I.e., it is easier to send one stream to the Wowza Transcoder than to produce each bitrate version with the encoder and stream all to Wowza over the network.
The F4M document contains errors URL missing from Media tag
/////
please note that i didn’t change any settings in any of xml files or data files , I have mystream.smil , also I tried to use “http://[myserver]:1935/live/myStream/manifest.f4m” it works fine , the problem is with multi-birate , so do you have any suggestions ?