Hi after quite a bit of testing we have worked out that there is some instability publishing in append mode to a network drive. Our setup is a clustered machine which hosts the live streams, a controller server with a Dell MD1000 rack attached to it with 2TB. Both machines are on a gigabit lan. The clustered machine bizarrely cannot fit a gigabit card so is using a usb gigabit interface, its playback and record path is set to something like file:\\computer\thepath for playback and file:\\computer\thepath\archive for the record path. When the subscriber tries to get the broadcast I have noticed the playback path is set to file:\\computer\thepath\streamname.flv is this a problem also ?
Anyway i've ticketed the faults caused by this, the broadcaster if trying to append a 100MB file after 25 mins simply cannot reconnect or stream. This problem has arisen after being disconnected at around 25 mins which is a pattern because it has happened regularly in the past. Another test today had the broadcaster client being disconnected after 65 mins. Appending and recording locally hasnt proven a problem, can reconnect fine and stream. What I have noticed however is that the archived file has its keyframe meta file generated even though it isnt being played back yet ? Any ideas ? _______________________________________________ Red5 mailing list [email protected] http://osflash.org/mailman/listinfo/red5_osflash.org
