Wowza 3 + nDVR + OSMF Strobe Player + Android

Thank you, Richard, much appreciated!

Just LIVE STREAMING is a problem as well, not only DVR. Strobe with Wowza streaming doesn’t seem to work at all on Android.

For now I will just place a link on my page with RTSP url for Android devices… it is just that I liked the in-browser experience that is working for RTMP DVR streaming in FMS - Strobe just works there, no matter that you are on an Android. If this is done by Wowza, (or we find out why I can’t get it to work) it will be awesome.

Best,

Anton

I will do that tomorrow.

Best,

Anton

I sent an email to support@wowza.com . Hopefully I’ve provided enough information for the “bug”.

However user randall confirms that Android 2.2.1 plays the videos from the https://www.wowza.com/demo page. I can’t get them to play on my Gingerbread ROM, or on a ICS ROM.

Does anyone have any experience with Android + Strobe + Wowza on Android 2.3.7 or Android 4.0.3 ?

Thank you,

Best regards,

Anton

I found out at least one of the issues:

I am streaming with Wirecast 4.1.2 - when I turn off audio encoding (AAC) - I can see Video in Strobe via Sanjose HTTP streaming (DVR).

When audio encoding is turned on, I can sometimes hear some audio (after a lot of buffering), but Video never appears. It seems like this is a problem with Wirecast - Android - Wowza.

Will continue to post if I find something else… I am about to update to Wirecast 4.1.3 - hopefully it will be fixed then.

best,

Anton

Confirm the problem. When I stream with Adobe Flash Media Live Encoder, everything works as expected… apparently it is a compatibility issue with Wirecast… 4.1.3 audio encoding messes up Android + Strobe as well :confused:

Best,

Anton

Yes, it does work. I test under Mac OS X Lion - Firefox and Chrome.

Flash is updated on my Android device (currently 4.0.3 ICS ROM, but I also asked a number of people to check via their devices - Nexus S and Nexus. None of them played the live stream). Regarding the https://www.wowza.com/demo pages - some Android devices opened it, others didn’t… my current configuration 4.0.3 opens the demo pages, but is lagging a lot… I’m on HTC Sensation (dual-core).

Best,

Anton

I tried with all kinds of encoding settings for Audio, including the one mentioned. When AUDIO is set ON, the stream starts playing on Android 4.0.3, but there is no video.

On my previous ROM it was buffering forever.

Have tried RTMP so far. Will test RTP and the rest now. Thanks for the suggestions!


RTSP doesn’t work as well: I tried streaming MPEG-4 Audio - same problem as previously… can hear audio, but no video. If I change Audio to different encoding, it is not decoded at all, but video is shown.

http://www.mediafire.com/?2luddbodz3z6tef

Best,

Anton

I think it is not a Wirecast bug, because I tried FLME as well - when streaming with AAC audio - I get blank picture. When using MP3 rather than AAC, stream published by FMLE works fine.

Therefore it is a Android-Flash / Wowza - compatibility issue, AAC decoding problem? As I said earlier - this is working just fine on FMS (H264 + AAC live dvr streaming, viewable from a browser in Android) - I used to have Android flash support there, but moved to Wowza in order to test iOS support.

Unfortunately Wirecast doesn’t support MP3 encoding - only AAC. When publishing via RTSP/RTP, I have a choice between a lot of encoders for audio, http://www.mediafire.com/?2luddbodz3z6tef, but none seems to work (MPEG-4 Audio is hearable, but no video ; for the rest I have video, but no audio… possibly no decoder available) :confused:

Thanks for the support.

Best,

Anton

  1. Wirecast (H264 + AAC ; RTMP publish) to Wowza Server to Strobe using Flash HDS (sanjose) on Android 4.0.3 == no video (black screen) ; just audio

2.1. FMLE (H264 + AAC ; RTMP publish) to Wowza Server to Strobe using Flash HDS (sanjose) on Android 4.0.3 == no video (black screen) ; just audio

2.2. FMLE (H264 + MP3 ; RTMP publish) to Wowza Server to Strobe using Flash HDS (sanjose) on Android 4.0.3 == work ; both audio and video

3.1. FMLE (H264 + AAC ; RTMP publish) to FMS 4.0.2 to Strobe using Flash HDS (sanjose) on Android 4.0.3 == work ; both audio and video

3.2. FMLE (H264 + MP3 ; RTMP publish) to FMS 4.0.2 to Strobe using Flash HDS (sanjose) on Android 4.0.3 == work ; both audio and video

4.1. Wirecast (H264 Baseline + AAC ; RTMP publish) to FMS 4.0.2 to Strobe using Flash HDS on Android 4.0.3 == no video (black screen) ; just audio

4.2. Wirecast (H264 Main + AAC ; RTMP publish) to FMS 4.0.2 to Strobe using Flash HDS on Android 4.0.3 == no video (black screen) ; just audio ; (audio starts for some miliseconds, and then buffering starts) buffering 99.9% of the time, even though configuration was just like 4.1. and using LAN. My guess is that this is some decoding issue, and this is why it is buffering.

All of the above work just fine on Mac OS X Lion - Firefox and Chrome.

Best,

Anton

If it wasn’t for test 3.1. , I would say that there is a problem with AAC decoding on Android Flash Player… however as stated, it works.

I have no idea what else to test/try in order to get: DVR streaming on desktops + mobiles (Android (both browser and native player with RTSP) ; iOS native player).

Best,

Anton

Hi

What version of Wowza 3 are you using?

Have you tried the sample.mp4 file that comes with Wowza?

Jason

Not sure how to help. I get that in one setup it does work but the findings sure report to some sort of instability with Flash on Android 4. Have you reported this to Google and Adobe?

Charlie

hi,

I have same issue with my Google Nexus on Android 4.0.2 and last flash player installed

in all browser, for live streaming I get only black square or nothing

on my side, issue is still there even without audio

I confirm that on some other android phones, it works well

in wowza log I get :

Missing function: startTransmit

Missing function: stopTransmit

Nicolas

PS : maybe that could be that => https://bugs.adobe.com/jira/browse/FM-1534

These errors are probably just from a malformed Application.xml. Try getting a new copy from the /conf folder and re-configuring.

Richard

Hi Richard,

nope, I recreated application.xml per a new one and error are still there when I try to watch stream from my Galaxy Nexus…

Could it be linked with flash/android issue ?

tell me if you need more info

Nicolas

Richard,

no I’m using RTMP flash

I have a webpage with flowplayer inside and on all devices/hardwares (only a special link for iDevices to play m3u) I point to this page.

no RTSP because of what you explained : problem with firewall, even if there is fallback in TCP… it’s not a solution

I will follow what you asked me and will send mail with all info

regards

NIcolas