Netstream publish problem

Hi,
I am facing a problem to publish and play a live stream from
FMS3. I am using flex3 (Action script 3 and FMS 3).
I have coded a demo application with server side script. You
can download this application and server side from this URL:
Demo app:
http://bang-dev.isprime.com/idma-test/FlashAngels/Amitabh/FMS_Issue/TestAppFMS.zip
Server side:
http://bang-dev.isprime.com/idma-test/FlashAngels/Amitabh/FMS_Issue/FMSTest.asc
Please find the issue and let me know, how to fix it.
To change the FMS server string: Go to Src >> Classes
>> InitApp.as >> line no 38 and replace your string.
Add a name at left side text field to publish the video.
Add a name at right side text field to play the video.
For the server side, just create a folder inside application
folder of FMS with name of “FMSTest” and put the server
side “FMSTest.asc “file there.
Let me know incase you face any issue while deploying it.
Thanks

The Clinet side code is a zip file, The code is really
simple, and there is only two files, one mxml ( you don't need to
see this, just needed to run the project.), and one class file
(InitApp.as).
You can easily find, code related to play, publish or
connect.
and Server side file is just text file, with just
acceptConnection method and few events with trace. Nothing else.
You can try on your local FMS 3.
Is there no one skilled, who can help me.
Let me know incase I could help you to make it easier and to
avoid confusions.

Similar Messages

Problem with connection ( NetStream.Publish.BadName)

Fri Sep 11 2009 08:52:10 : Session Started
Fri Sep 11 2009 08:52:11 : Audio Encoding Started
Fri Sep 11 2009 08:52:11 : Video Encoding Started
Fri Sep 11 2009 09:13:59 : Primary - Network Status: NetConnection.Connect.Closed status
Fri Sep 11 2009 09:14:04 : Primary - Disconnected
Fri Sep 11 2009 09:14:04 : Primary - Re-establishing connection, attempt 1
Fri Sep 11 2009 09:14:05 : Primary - Reconnected to FMS/3,0,1,123
Fri Sep 11 2009 09:14:05 : Primary - Network Command: onBWDone
Fri Sep 11 2009 09:14:05 : Primary - Stream[onetv] Status: Success
Fri Sep 11 2009 09:14:05 : Primary - Network Command: onFCPublish
Fri Sep 11 2009 09:14:07 : Primary - Stream[onetv] Status: NetStream.Publish.Start
Fri Sep 11 2009 09:14:58 : Primary - Network Status: NetConnection.Connect.Closed status
Fri Sep 11 2009 09:15:04 : Primary - Disconnected
Fri Sep 11 2009 09:15:05 : Primary - Re-establishing connection, attempt 1
Fri Sep 11 2009 09:15:05 : Primary - Reconnected to FMS/3,0,1,123
Fri Sep 11 2009 09:15:05 : Primary - Stream[onetv] Status: Success
Fri Sep 11 2009 09:15:05 : Primary - Network Command: onFCPublish
Fri Sep 11 2009 09:15:07 : Primary - Stream[onetv] Status: NetStream.Publish.BadName
Fri Sep 11 2009 09:27:20 : Audio Encoding Stopped
Fri Sep 11 2009 09:27:20 : Video Encoding Stopped
Fri Sep 11 2009 09:27:20 : Session Stopped
Fri Sep 11 2009 09:27:23 : Primary - Network Status: NetConnection.Connect.Closed status
Fri Sep 11 2009 09:27:23 : Primary - Disconnected
Fri Sep 11 2009 09:27:24 : Primary - Connected to FMS/3,0,1,123
Fri Sep 11 2009 09:27:24 : Primary - Network Command: onBWDone
Fri Sep 11 2009 09:27:28 : Primary - Network Command: onFCPublish
Fri Sep 11 2009 09:27:28 : Primary - Stream[onetv] Status: Success
Fri Sep 11 2009 09:27:28 : Primary - Stream[onetv] Status: NetStream.Publish.Start
Fri Sep 11 2009 09:27:28 : Session Started
Fri Sep 11 2009 09:27:29 : Video Encoding Started
Fri Sep 11 2009 09:27:29 : Audio Encoding Started
Fri Sep 11 2009 12:23:03 : Primary - Network Status: NetConnection.Connect.Closed status
Fri Sep 11 2009 12:23:09 : Primary - Disconnected
Fri Sep 11 2009 12:23:09 : Primary - Re-establishing connection, attempt 1
Fri Sep 11 2009 12:23:09 : Primary - Reconnected to FMS/3,0,1,123
Fri Sep 11 2009 12:23:09 : Primary - Stream[onetv] Status: Success
Fri Sep 11 2009 12:23:09 : Primary - Network Command: onFCPublish
Fri Sep 11 2009 12:23:11 : Primary - Stream[onetv] Status: NetStream.Publish.BadName
Fri Sep 11 2009 12:26:26 : Audio Encoding Stopped
Fri Sep 11 2009 12:26:26 : Video Encoding Stopped
Fri Sep 11 2009 12:26:26 : Session Stopped
Fri Sep 11 2009 12:26:32 : Primary - Network Status: NetConnection.Connect.Closed status
Fri Sep 11 2009 12:26:32 : Primary - Disconnected
Fri Sep 11 2009 12:26:37 : Primary - Connected to FMS/3,0,1,123
Fri Sep 11 2009 12:26:49 : Primary - Network Command: onFCPublish
Fri Sep 11 2009 12:26:49 : Primary - Stream[onetv] Status: Success
Fri Sep 11 2009 12:26:49 : Primary - Stream[onetv] Status: NetStream.Publish.Start
Fri Sep 11 2009 12:26:49 : Session Started
Fri Sep 11 2009 12:26:50 : Audio Encoding Started
Fri Sep 11 2009 12:26:50 : Video Encoding Started
Hy, this is from my log.
I connect the flash media encoder to flash media server, and after a short time it disconnect from server and try to reconect automatically, that is good, but IT DON'T CONNECT!!!
Stream[onetv] Status: NetStream.Publish.BadName
Fri Sep 11 2009 12:26:26 : Audio Encoding Stopped
Fri Sep 11 2009 12:26:26 : Video Encoding Stopped
Fri Sep 11 2009 12:26:26 : Session Stopped
Where is the problem??? What i can do to resolve this problem?????
I'm waiting for your answers!
Thanks

The NetStream.Publish.BadName status means an attempt was made to publish to a stream that is already being published by someone else. Is another client using the same stream name?
About the connections being closed, there a lots of conditions that could cause the connection to be lost. It may not be an FMS or FMLE error, it could be poor conditions on the local network, or between the local network and the server.

NetStream.publish for P2P NetGroup fails in the FMS 4.0 AS

Hi,
I recently tried to modify the system-provided codes in the "multicast" folder, and could not get it work. I pinned down the issue to be the function call NetStream.publish("p2p_pindao1", "live") always failed for me. The proof the function call failed including:
1. The returned value is false.
2. I got no further events beyond NetStream.Connect.Success, i.e. I did not get the expected NetStream.Publish.Start
The following are the testing codes
application.onAppStart = function()
var nc = new NetConnection();
nc.onStatus = testNetStatus;
nc.connect("rtmfp://localhost/TVLive");
trace("to connect");
function testNetStatus(info)
trace("TestNetStatus:" + info.code);
var gs = new GroupSpecifier("net.lysk.pindao1");
gs.serverChannelEnabled = true;
gs.postingEnabled = true;
gs.peerToPeerDisabled = false;
// Multicast address over which to exchange peer discovery.
//var p2pm = "224.0.0.255:30000"; // BUGBUG
// Must be enabled for LAN peer discovery to work
//gs.ipMulticastMemberUpdatesEnabled = true;
var ng = new NetGroup(this, gs);
ng.objNc = this;
ng.objGs = gs;
ng.onStatus = testNetGroupStatus;
function testNetGroupStatus(info)
trace("testNetGroupStatus:" + info.code);
var ns = new NetStream(this.objNc, this.objGs);
ns.onStatus = testNetStreamStatus;
function testNetStreamStatus(info)
trace("testNetStreamStatus:" + info.code);
if (info.code == "NetStream.Connect.Success")
if(!this.attach(Stream.get("mp4:sample1_1000kbps.f4v")))
trace("can not attach");
if (!this.publish("testpublish", "live"))
trace ("can not publish");
tracing outputs are the following:
to connect
TestNetStatus:NetConnection.Connect.Success
testNetGroupStatus:NetGroup.Connect.Success
testNetStreamStatus:NetStream.Connect.Success
can not publish
Your help in solving the problem will be highly appreciated.
Thanks.

em, it appears I was wrong in believing peerToPeerDisabled=true sufficed for P2P publishing, while multicastEnabled was for IP multicast. I will try out the answer. Thanks for the help.

NetStream.Publish.BadName

For some reason my Internet connection between FME and FMS is
not stable. When connection
with my live stream is dropped I can't reconnect to FMS and
I'm getting " NetStream.Publish.BadName"
error. It is because previous session (project) exists for
random time.
The only solution I made is to put FME in command line mode
in batch continous loop (as
FME exits on that error so the standard reconnect procedure
does not work) - it takes even
few minutes in few cases I was able to trace (many tries). In
GUI mode situation is much is
worse - there is dialog window that requires clicking when
that error occurs.
The other one is manual and requires someone watching stream
24/7 - vhost restart - plus all
clients are dropped. Baaad - it is better to make clients
wait for stream 2-5 minutes than force all of them
to restart live stream Flash player.
Is live streaming with FME + FMS designed to work only on
stable LAN connection?
Even if that is true such disconnects can occur - so this bug
is really anoying.
Does anyone found other solutions than mine?

The same problem with latest FME 3.2 and FMS 4.5 default live app. Setting PublishTimeout=-1 serverside and/or increasing reconnect interval in FME does not help.
Any workaround except custom live app with shared objects?

HI,Why every five minutes, the server - side NetStream.publish failure

RTMP spread to the FMS, and then create netGroup and NetStream objects on the server side, then the NetStream.publish (), the beginning of everything is normal, but after five minutes, very strange happens to be five minutes, the client node receives less thanstream had, and I monitor the status of this server-side NetStream no change is to publish the start, why the five minutes it will automatically stop publishing flow RTMP stream has been no problem in the transmission

i assume, from your post, that you are using FMS and are publishing a multicast stream.
if you are using the "Flash Media Development Server", prior to release 4.5, multicast streams time out after about 10 minutes. as of release 4.5, multicast streams time out after about 30 minutes. to see this and other limits of the Development Server, see:
http://www.adobe.com/products/flashmediaserver/helpmechoose.html
if that is not the problem, then if you are writing your own server-side scripts, perhaps you are not anchoring a NetStream, Stream, or NetConnection object properly and it is being destroyed by the garbage collector.
if you need more help with Flash Media Server, you should direct your questions to the Flash Media Server forums. the Codename Cirrus service is not based on FMS.

Primary - Stream[live_2521213_QPzTR2Uo] Status: NetStream.Publish.Rejected

Have anyone had this same problem on trying to bradcast from FMLE to Justin.tv??
I get this Log:
Mon Jun 14 2010 18:18:21 : Video Encoding Started
Mon Jun 14 2010 18:18:22 : Audio Encoding Started
Mon Jun 14 2010 18:18:26 : Primary - Disconnected
Mon Jun 14 2010 18:18:29 : Primary - Re-establishing connection, attempt 1
Mon Jun 14 2010 18:18:30 : Primary - Reconnected to FMS/3,5,2,654
Mon Jun 14 2010 18:18:30 : Primary - Stream[live_2521213_QPzTR2Uo] Status: Success
Mon Jun 14 2010 18:18:30 : Primary - Stream[live_2521213_QPzTR2Uo] Status: NetStream.Publish.Rejected
Mon Jun 14 2010 18:18:30 : Primary - Network Status: NetConnection.Connect.Closed status
Mon Jun 14 2010 18:18:35 : Primary - Disconnected
Mon Jun 14 2010 18:18:38 : Primary - Re-establishing connection, attempt 1
Mon Jun 14 2010 18:18:39 : Primary - Reconnected to FMS/3,5,2,654
Mon Jun 14 2010 18:18:39 : Primary - Stream[live_2521213_QPzTR2Uo] Status: Success
Mon Jun 14 2010 18:18:39 : Primary - Stream[live_2521213_QPzTR2Uo] Status: NetStream.Publish.Rejected
Mon Jun 14 2010 18:18:39 : Primary - Network Status: NetConnection.Connect.Closed status
Mon Jun 14 2010 18:18:44 : Primary - Disconnected
Mon Jun 14 2010 18:18:47 : Primary - Re-establishing connection, attempt 1
And it goes on and on every 5 secs, can anyone help me???

The only thing I can think of is there is an issue with your authentication. Have you changed your justin.tv password since you generated the XML file? In the justin.tv wiki it says
"IMPORTANT: Beware that the text box labeled "Stream" contains a key that is like a password for streaming to your channel. Be careful when you are broadcasting your desktop not to show that area!"
This implies to me that the XML file gets generated using the password that you use when you logged into justin.tv. I think if you generate the XML and then change your password the XML file expires. Try generating a new XML file, make sure to Open it in FMLE and try streaming again.

Using variable name for Netstream Publish() (actionscript)

Relatively new to Actionscript. In the netstream publish() or play() methods, can I pass variable names to the methods instead of hard-coding the stream name?
Example:
private function publishLiveStream():void
            ns = new NetStream(nc);
            ns.addEventListener(NetStatusEvent.NET_STATUS, netStatusHandler);
            ns.client = this;
          // blah blah other stuff...
           ns.publish("thefilename", "record");
I want to replace "thefilename" with a value passed from an input box or use dynamic naming (i.e. current date & time).

you can use in procedure using sunopisis technology
OdiExportMaster "-TODIR=/temp/" "-ZIPFILE_NAME=export.zip" "-XML_CHARSET=ISO-8859-1" "-JAVA_CHARSET=ISO8859_1" "-EXPORT_VERSIONS=YES"
or you can use (unix System)
OdiExportMaster "-TODIR=/#v_FileName" "-ZIPFILE_NAME=export.zip" "-XML_CHARSET=ISO-8859-1" "-JAVA_CHARSET=ISO8859_1" "-EXPORT_VERSIONS=YES"
Hope it will work
Thanks

Getting Problem while publishing Problem while publishing java.lang.IllegalArgumentExcep

getting Problem while publishing Problem while publishing java.lang.IllegalArgumentExcep while deploying persistance with ejb sample application into cloud. can any one please tell me why i am getting this?

Hi Goutham,
I am facing the same issue. Please let me know how you have resolved it.

Publishing Problems - a Solution?

For a long time I'd sympathised with all you people who'd been having publishing nightmares, even though I've been updating pretty much error free since iWeb 1.0
Then last night after updating my blogs and making a few changes, I finally got the dreaded error messages. Tried a few times, got frustrated, and decided to sleep on it.
Same this morning ... grrr ... but then I noticed that my iDisk had failed on auto-synchronisation.
I'd only mounted my iDisk recently to amend my Podcast feed, so on a hunch I unmounted iDisk, rehit the Publish button in iWeb, and holy shmoly – it worked straight off!
I reckon that publishing iWeb kicks off the iDisk auto-sync, and then you've got a conflict with iDisk and .Mac trying to outsync each other.
Anybody else found this? if this solves publishing problems for a few of you then great. If it works for a lot of you, even better. If the majority of you get sorted, then that's a revelation!
Dual 2.3 GHz PowerPC G5 Mac OS X (10.4.6)

My message to Apple stated:
"My pages go through the "create" process then start
on the "publishing" process then come back with an
error message that tells me to check my internet
connection (which is fine at 2 different locations. I
spent 13 hours fighting this yesterday. It has
created a major problem for me -- and this just after
I paid an extra hundred dollars to upgrade my
broadband. Your telephone people tell me you're
working on this. Please advise when it will be fixed
so I don't waste another 13 hours today."
Regards,
Richard M.
Richard, thank you for writing this. I would like to know how this all shakes out, and I am glad that it is an Apple server problem and not mine.
Meanwhile, I want to say how helpful it is to have this iWeb forum, and also thank the very generous and thoughtful souls who take the time to help beyond what normally would be expected. Those people know who they are, but I also am grateful to everyone.
For example, I was greatly relieved to read that I was not the only person getting Network Failure messages, since it meant that probably I was not working with a defective application -- one that started out fine but somehow went south on me and would not be replaced by Apple. This may seem a trifling thing to some, but when you are in a spot that you perceive as Hot, assurance from the outside is very much appreciated.
I hope that when you all finish your websites, you post the URL so we can all see it; after all, in a sense we are all comrades in arms (because sometimes it can seem like a war, due to the Fear Factor) and our fates are somehow connected even though we are all so-called strangers.
— Lorna in Southern California

Unexpected Publishing Problems

I have been using iWeb for almost two months with no publishing problems. I publish to a folder then ftp it to my yahoo server. However, last night I began to experience publishing problems. iWeb publishes just the first five pages of my site then I get a message that an unexpected error occurred. No other clues as to why it could be happening.
The last change I made was an adding a podcast. I deleted that podcast thinking that maybe iWeb didn't like the taste of it and tried to publish but it still won't work. I've tried about 10 times, with my screen saver turned off, battery charger plugged in, and no other apps running.
Please help me!
Ruben
G4 17 inch Powerbook Mac OS X (10.4.5)

Here's the latest...
I realized that iWeb stopped publishing at the same page (I have 30+ pages on my site. It would always stop at the fifth one). So, I rearranged the order of that page, dragging it down to the very bottom of my site list. When I went to publish to folder, iWeb published everything then stopped again at that specific page. So here I thought I had isolated the issue.
I created a new site and dragged the problematic page into it. I then created a brand new page in my main site and copy/pasted the old content into it. Ergo: a whole new page. I went to publish with iWeb cranking along nicely until it got to the NEW version of that page and then it crapped out. Again.
I am guessing that one of the images (or who knows what, really) is messing with iWeb's fragile ego. I am going to reconstruct the page with brand new copies of the images that were on it. Images, by the way, that published fine for almost a month and that I didn't alter at all.
Wish me luck all. I'll keep you posted.
Ruben

NetStream.Publish.Failed

I'm trying to connect 2 swfs over Stratus and the second client is getting NetStream.Publish.Failed when I try to publish a stream. They both have connected to Stratus via the NetConnection and one can publish a stream but the second can not. I've made sue that each swf is using a different name to publish. I can't find this error listed anywhere in the documentation it only listed NetStream.Publish.BadName. I'm using the AIR 2 RC1 beta sdk from adobe labs set to publish for 10.1.
Are there any other reasons why i would be getting NetStream.Publish.Failed?

I found out why it was failing. I was entering the peerID I wanted to allow connection from instead of allowing any direction connection.
so I had:
stream = new NetStream(connection, farID);
stream.publish( channel );
where is should be:
stream = new NetStream(connection, NetStream.DIRECT_CONNECTIONS);
stream.publish( channel );
then the other client needs to use both my farID and name of my stream in order to connect

Publish Problems

More Publish Problems!
Ok... So now that I have been working on my sites when I publish I get "Publish Error" an unknown? Help... I am using iWeb 1.1.1 and thought that this word be an easy way for students to get access to some pod casts... Now what? This worked before using 1.1.1
Sometimes it works and most of the time it will not publish? What can I do?
Thanks
David
imac G5 and an older G5 + a Powerbook and an iBook Mac OS X (10.4.7)

Oh my god I am not a lunatic idiot after all!
I am currently in discussion with Apple Support for exactly the same problems as you guys, all I did was add a new video to my site. The first few times the update timed out as it was taking more than 30 minutes to upload (I am on broadband and the new page was only 7 meg). Then I got the ".Mac servers were busy please try later" message, then I got the "check your isp.." gubbins. Then when I tried again it said the update was successful but when I visited the site (via a number of different computers and networks) I either could not access the site at all, or it partly loaded, or the welcome page loaded correctly but when going to other pages I got nothing!
I am currently waiting for Apple Support to " get back to me"
MacBook 1.1 White 1.83ghz iBook 12 iBook 14 Mac OS X (10.4.7) Remember, A good friend will bail you out of jail, but a best friend will help you bury the body!

NetStream publish and play synchronize buffers

NetStream publish and play synchronize buffers

I haven't tried to run your code, but something obvious is
the server-side code. It doesn't do anything.
When you publish a stream, you need to tell other client to
connect to it... manually. There are three thing to account for. A
client connecting needs to subscribe to all existing streams. A
client connecting needs to inform all existings clients that it has
published its stream and give them the stream name so they can
subscribe. The client needs to receive stream names of any new
(future) connecting clients so it can subscribe to their stream.
First you need to publish your stream... lets say this is
client A and publishes a stream named stream_A.
1. Then you need to send the stream name (stream_A) to all
other existing clients, so they can subscribe to it.
2. Then you need to receive the names of existing clients
streams, so the client can subscribe to them.
The logic in step 1, will handle any new clients connecting
in the future.
If anyone sees any errors in this or has a better method..
please feel free to add to it....

NetStream.publish() to AMS ends up with 1kb file.

I'm using Adobe Media Server 4.5 and the FLEX 4.6.0 sdk.
I have an .swf application that connects to Adobe Media Server over RMTP, takes audio and video input from the user's webcam and mic, and does a NetStream.publish() to stream the file to the server. When the user is done, I do a NetStream.stop(). On occasion, the resulting file will end up with a size of 1kb.
What's causing this and how can I prevent it, or otherwise end the session and inform the user that something went wrong?
Alternatively, these forums seem dead, so does anyone know of a place where my question might be better suited?

Solved by changing the frame rate of the footage (image sequence) into any other frame rate, then change back to desired frame rate. In my case, after load the image sequence >check inspector of footage >change current frame rate (from 24fps to other fps) >change back frame rate to 24fps. Same bug in version 3.5.2. Hope it helps.

Another user with publishing problems -- proof that it is .Mac related

Just before Christmas I started getting the dreaded "Publish Error: There was an error updating .Mac" message every time I published. I read all the previous posts, even the ones dating back to October. I think I can conclusively show that the problem is on the .Mac backend, and not at all on my computer. Here is what I did: first, I created a temporary .Mac account; second, I moved my Domain file for safe keeping and did not replace it; third, I logged into the Guest User account that is now available in Leopard. I then attempted to publish a single page website from iWeb from both my normal login and the guest login to both my normal .mac account and the temporary one. (To switch between .Mac accounts I used the system preferences panel when iWeb was not running). The results are as follows:
.......................Regular .Mac.......Temporary .Mac
Normal Login..Publish Failed......Publish Succeeded
Guest Login.....Publish Failed......Publish Succeeded
This tells me that there is no problem on my computer, or with my network connection, and the problem is squarely on the .Mac side of things.
I sent this message off to the standard help page, and got the standard form letter back. In reply I asked them to reset my .Mac account so it would appear "new". I'll see what they say.
It would be interesting to see how many other people with "publish" problems can repeat this test.
-=[doug]=-

I've done what appears to be the standard littany of things:
1) Confirmed that I am running the latest version of iWeb (2.02) on 10.5.1 (although the problem persists when using my backup of 10.4.10 that includes the ilife update)
2) Changed my .Mac password, even though it was less than 20 characters
3) Published all of my previous website to the temp .mac (in chunks to avoid the space limitations)
4) Successfully published my site to a folder
5) Successfully uploaded that folder to my iDisk
6) Attempted to republish and republish all multiple times
7) Deleted iWeb's plist
8) rebooted
9) logged out and back into my .Mac account
10) confirmed that there is no password protection on my site
11) confirmed that there are no comments on my site
12) deleted assets.[membername].plist from the Domain file
13) Confirmed that my password in Keychain is correct
14) Run Keychain First Aid
15) deleted Sites.RSS from my iDisk
16) deleted the website and index.html from the iDisk
So, I have done a fair amount of ground work here, and am not just spouting off against Apple/.Mac. However, I still claim that the fact that I can successfully publish to a temporary .Mac account while the exact same iWeb content fails when being published to my normal .Mac account implies that there is something wrong with my .Mac account -- it is almost as if Apple is trying to eliminate its paying customers (since there are no problems with the free account).
-=[doug]=-

Netstream publish problem

Similar Messages

Maybe you are looking for