In FMS there cannot be an archived stream called "stream" AND a live stream called "stream". The live stream will overwrite the archived one. So you don't have that issue with FMS. I do this all day long with FMS.
Jake On 12/6/06, Dan Rossi <[EMAIL PROTECTED]> wrote:
Costin Tuculescu wrote: > Hi Jake, > > I posted this in the JIRA about a week ago: > > http://jira.red5.org/browse/SN-4 > > Not sure if I posted it to the right category however. Let me know if > there's anything else I can do to expedite the solution. Thank you. > > Costin > I already had a ticket and its being ignored. It subscribes to the archived stream first before the live stream not the other way round as documented in the FMS API. So if you have a live stream of the same name as the archive it will start playing the archive and stop where the record is up to regardless if its still streaming or not. If you are now suggesting that we have to reroute the stream to archive via the application to work around this an example would be nice, it would be absolutely silly to expect to publish two streams at once, which i havent even tried but would double the required upload bandwidth. _______________________________________________ Red5 mailing list [email protected] http://osflash.org/mailman/listinfo/red5_osflash.org
_______________________________________________ Red5 mailing list [email protected] http://osflash.org/mailman/listinfo/red5_osflash.org
