The back-end servers in this case are feeding a live stream to Proxy Server. From there I have one application that connects to Proxy Server to convert the rtsp:// streams to rtmp:// for flash presentation. Simultaneously, there is a second application that connects to Proxy Server to record the streams to file. Both of these applications are behaving very well with Proxy Server (rtmp:// streams are working....recording is consistent)....just the unusual file issue in the case where both applications are running together. If I shutdown crtmpserver and leave just recording application running the recorded files are back to normal.
It's somewhat like a Rubik's Cube when putting things together in this fashion, but overall it's working better than I would have expected. I guess my question would be this: Assuming all back-end servers are live rtsp:// streams going to Proxy Server. Would each front-end client connection to Proxy Server be isolated from the other...would the characteristics of the stream provided by Proxy Server be as if each application was connected in isolation? Bob On Tue, Oct 22, 2013 at 1:11 PM, Ross Finlayson <finlay...@live555.com>wrote: > Unfortunately your description of your problem wasn't particularly clear; > it seems, though, that you should be investigating your recording > application(s), to figure out why they're not giving you what you want. > (In particular, you could investigate how well they handle packet (i.e., > data) loss, which is more likely when you have more streaming. > > However, you do realize - I hope - that when you stream through our proxy > server, there's only *one* stream coming from the back-end server (to the > proxy server), regardless of how many front-end clients are currently > accessing the proxy server. That means, therefore, that if your back-end > stream comes from a file (rather than from a live source like a network > camera), then only the first front-end client will get to see the stream > starting from the beginning of the file. Subsequent front-end clients will > (obviously) start receiving the stream from some later point. If that's > important to your recording application(s), then they shouldn't be > receiving the stream this way. (Instead, just copy the file directly :-) > > > Ross Finlayson > Live Networks, Inc. > http://www.live555.com/ > > > _______________________________________________ > live-devel mailing list > live-devel@lists.live555.com > http://lists.live555.com/mailman/listinfo/live-devel >
_______________________________________________ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/live-devel
