Skip to main content
Participant
June 21, 2011
Question

air 2.7, ios, rtmfp bug - known problem?

  • June 21, 2011
  • 1 reply
  • 1011 views

Hello,

i have a little Video & Audio Broadcaster and Receiver Application, using rtmfp and cirrus.

As an Example, following Scenario:

1. Broadcaster: AIR Debug Launcher on my Laptop

2. Receiver: IPad App

=> Everything works as expected, the Broadcaster Application on my Laptop broadcast its live Audio/Video Stream, the Ipad App can receive it.


Now comes the strange part. When i switch the IPad App to the Broadcaster and my Laptop Air App to the Receiver, it does not work anymore; so the scenario is as follows:

1. Broadcaster: IPad App
2. Receiver: AIR Debug Launcher on my Laptop

In this Scenario the Receiver NetStream gets no NetStatusEvent.NET_STATUS after tring to play the Stream, the Broadcaster's NetStream fires no onPeerConnect Event.

This renders my app pretty much useless and iam interested to hear if this is a known bug or if iam missing something?
This topic has been closed for replies.

1 reply

chris.campbell
Legend
June 21, 2011

Hi,

Thanks for the heads up on this issue.  I'm not aware of the problem, but I've forwarded this along to our iOS team for their review.  I expect they'll post back shortly.  In the meantime, would you mind opening up a new bug report at bugbase.adobe.com and include any sample code that would help us reproduce the problem internally?  Please post back with the bug's URL so others affected can add notes and cast their votes.

Thanks,

Chris

Participant
June 21, 2011

Hi Chris,


could you be so kind and forward this code here:

http://codetidy.com/792

to the ios team? this is a very simple script which sends and receives a video stream via rtmfp.

it works on web, in the air launcher but not on ios after packaging.

it worked on ios when i used rtmp via red 5, but with rtmfp it does not, so it might be an ios / rtmfp related bug.

thanks for your help, i'll fill a bug request, as you described.

Participating Frequently
June 23, 2011

Hi,

I see that you have reported the issue at http://bugbase.adobe.com. For other developers facing the problem, the bug number is 2902363. Please feel free to post it for status updates.

Thanks,

Sanika