Wowza Community

Wowza 3 + nDVR + OSMF Strobe Player + Android

I am a bit lost in all of this take ndvr out of this and tell me this. Which of these combinations work:

Wirecast to Wowza Server to Strobe using Flash HDS (sanjose) on Android 4.0.3

FMLE to Wowza Server to Strobe using Flash HDS (sanjose) on Android 4.0.3

Wirecast to FMS to Strobe using Flash HDS on Android 4.0.3

Again, this is without ndvr involved.

Charlie

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

Try JW Player instead of Strobe. It handles RTMP very well. If you want to do Sanjose (Flash HTTP) streaming, you will need Strobe or Flash Media Playback (hosted version of Strobe).

Richard

Anton,

You do need to use Sanjose (Flash HTTP) streaming in that case, rtmp does not work with DVR. Have you tested with the Wowza DVR example players?

Richard

I’m not sure if we have any test results for DVR/Strobe/Android. I’ll bring it up tomorrow.

Android is often difficult for simple things right now.

Richard

Can you zip up your conf and the latest access and error logs from your testing, and send them to support@wowza.com

Include a link to this thread.

If you can, restart Wowza and run through some tests with the device

Richard

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

Richard

Nicolas,

Are you doing RTSP streaming to this device? That is what we recommend for Android at present, support for other stream types has been inconsistent. The usual problem reaching these devices is UDP ports, either blocked by a firewall or not mapped in a router, “port forwarding”. You want all UDP ports 0-65335 open. For RTSP streaming, review the following guide carefully (and note the jump in step 3 and the mobile testing page):

https://www.wowza.com/docs/how-to-troubleshoot-rtsp-rtp-playback

If that doesn’t help, stop Wowza, then delete or rename your access log, we want to get a clean test. Then:

1: Start Wowza

2: Start the encoder

3: Playback in Flash [wowza-install-dir]/examples/LiveVideoStreaming/client/live.html

4: Playback on device that is a problem

Then zip up and send conf and current access and error logs to support@wowza.com

Include info about the encoder, encoding details. Include screen shot(s) as necessary to show all if you want.

Include a link to this thread for reference.

Richard

I don’t think it is a bandwidth issue. I’ve been using the same connection for a long time and never had problems, and now i’m testing with much lower bitrate. I also tested on local LAN, using Developer edition of Wowza… testing also on Amazon EC2 with lickey edition.

Even the LiveVideoStreaming example with rtmp://server/app ; and then streamname, doesn’t work.

I noticed that if I change a bit the buffering values, or remove them all together, I get sound, but no picture on Android. My version of flash on AND is 11,1,112,61 (Flash-AS3) (according to LiveVideoStreaming example).

There are only a few parameters to be changed at Application.xml so I’m feeling a bit lost.

I test both LIVE app and DVR app…

smoothstreamingpacketizer,cupertinostreamingpacketizer,sanjosestreamingpacketizer

sanjosestreamingpacketizer is always present in the LiveStreamPacketizers,

cupertinostreaming,smoothstreaming,sanjosestreaming

it is present in the HTTPStreamers as well.

I’m starting to fell that the problem is in my device, but as I said - it is working with FMS streams, so I feel like it is a config issue.

In the log files on local, everything seems fine… I see the following lines when I start broadcasting:

INFO server comment - LiveStreamPacketizerSanJose.init[dvr/definst/tonyy]: chunkDurationTarget: 10000

INFO server comment - LiveStreamPacketizerSanJose.init[dvr/definst/tonyy]: chunkDurationTolerance: 500

INFO server comment - LiveStreamPacketizerSanJose.init[dvr/definst/tonyy]: playlistChunkCount:4

INFO server comment - MediaStreamMap.getLiveStreamPacketizer: Create live stream packetizer: sanjosestreamingpacketizer:tonyy

When I connect via the Android device, I see:

INFO sanjose connect 1973510429 -

INFO stream create tonyy -

INFO stream play tonyy -

no Errors whatsoever.

I tried both with those params:

expandedBufferTime: 5,

liveBufferTime: 12,

liveDynamicStreamingBufferTime: 14,

dvrBufferTime: 12,

dvrDynamicStreamingBufferTime: 14,

dynamicStreamBufferTime: 14,

and without them.

RTSP url does work on Android. Adobe Flash Player 11 installed… Strobe on other pages (for example FMS VOD) working.

Any ideas?

Best,

Anton

Even RTMP url works if added to a Video player, but does not show at all in Strobe :confused:

best,

Anton

JWPlayer doesnt’t support DVR. Also I am pretty sure it is a config issue not to be able to load Strobe on Android, so I will continue to test, in order to nail why is it happening.

I use Wowza 3.0.4 on EC2. Will try sample.mp4 now, but I wanted to test LIVE and DVR… VOD is not of particular interest for me right now.

Best,

Anton

Sorry for misleading you.

I know DVR works only with Sanjose. I publish the stream via the rtmp://server/app ; streamname, but in Strobe, I use the Sanjose URL: http://server:1935/app/streamname/manifest.f4m?DVR

As I said - it is working on a browser, it is working for iPhone and iPad (of course, not Strobe, but the iOS url’s that open the native player), but on Android, Strobe is not working… only RTSP url with a native video player. On Android I manage to get only sound. The picture is black - I tried H264 Baseline, H264 Main.

I want to get Strobe inside an Android browser if possible.

I checked a few Android devices, and a few different ROMs (Gingerbread + Android 4.0) - it is not working anywhere… just manage to hear the sound.

Best,

Anton

Just tried StrobeMediaPlayback_1.6.328 , debug-mobile.html

Doing a Sanjose DVR - which again works on browser. On Android I get:

Build 1.6.328 for Flash Player 10.1

Flash Player version: AND 11,1,102,69

Hardware Video Decoding: Yes

Hardware Video Rendering: No

Frame rate: 0.00 fps Dropped frames: 0

Buffer length / time: 7.32s / 4.00s

Memory usage: 10.05mb

Stream state: buffering

I’m having a hard time finding ANY video streamed by WOWZA to work on STROBE PLAYBACK 1.6 (OSMF 1.6) on ANDROID. Even the videos on Wowza website don’t work… they show only on desktops.

On the other hand, I have no problems displaying live/dvr/vod streams via Flash Media Server or Amazon Cloudfront (which I believe delivers using FMS).

I am starting to think that WOWZA and STROBE don’t work on Android at all…

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 http://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 http://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