Hi,

Thanks for moving to FMS 4.

There shouldn't be any problem /restriction recording on the server with 4.0.

1. Did you check the logs on FMS to see if there anything mentioned ? (core logs mainly).

2. How long is this few minutes ? Everytime the recording stops at the same time ? Did the FMLE recieved any notification or did it continue publishing ?

Also quickly share the server side script you wrote for record, so that it will be available for reference.

Thanks for your co-operation.

Anyone?  Hello, is this thing on?

Pretty bad issue here.  I sort of need the stream recording functionality in FMS to work.  As of this writing I just cannot make FMS "reliably" record live streams to files on the server.  It seems others have reported this same silent failure situation as well.  Is there anyone at Adobe who knows for sure if I'm doing something wrong in the code above or if there is a bug here?

Thanks in advance.

Thanks for the response.

No dice.  Made the change as prescribed above and get the same result. 

The two things that make this difficult are the silent nature of the failure (nothing in console or logs, and no NetStatus activity) and the lack of consistency in the end result - fails a lot, but succeeds once in awhile with no code changes.  Would expect either a total failure if the code is wrong or total success if it's right.  I may be doing something wrong, but these conditions make it difficult to troubleshoot.

ImAStreamer above gets the same result as me so we're either both doing the same thing wrong or FMS 4 and above broke recording somehow.  Where do I go from here?  Need somehow to get this working.

Thanks

I guess I could try that, but I'm not sure I see the point.  What type of issue with set up?  Did you have something in mind?  If there was one, then ImAStreamer above and others have the same issue.  Has anyone ever noted what such an issue might be?

Again, it's not a total failure.  It succeeds aboout 20-30% of the time.  A file is recorded successfully.  If there were a problem with the set up, I would suspect it wouldn't succeed at all.

If there were some problem in the code above, again, it wouldn't succeed at all.  What types of set up problems or code problems would lend to partial successes?

In order to test the livepkgr app I'll have to read about it and figure out how it works and such.  I can do that, but I was looking to get this working a little sooner than that.  ImAStreamer reported his problem June 11th, 2011.  Makes me think a solution might not happen in a timely manner.

I'll take a look at livepkgr here.

We were experiencing similar problems with the recording just stopping without any error or other information. While trying to find the error we started listening on the onStatus event on NetConnection which made the problem completely disappear. If we remove the event lister the problem comes back, every time.

netConnection.onStatus = function(info) {

                       trace('Connection Status: ' + info.code);

}

I won't claim any great experience with this development environment, so take this for what it's worth and I hope it helps.

We was experiencing this same issue and I noticed that we weren't keeping a persistent reference (read: global variable) to the streams doing the recording.  I started thinking what if the recording streams are being garbage collected (or something similar).  It seemed odd that this would be the case, given that streams often require explicit closing and the existence of Stream.Get/Stream.Destroy, but I figured why not give it a shot.  So I implemented a global map that housed the recording streams and the problem completely disappeared.

Anyway, as I said, I can't claim expertise, but maybe this will help you.