Slow fps causes stream timeout

[dmazan]

Playing a 1 fps flv with the vod application starts to play fine (shows fine on
the vodtest player). But watching the server adminisrtator shows the outbound
stream as "idle." 60 second later the stream times out and closes. Play a
stream with higher fps and the outbound stream shows that it is playing and
doesn't timeout.

So the question is where is the threshold set that determines when a stream is
considered idle and where is the timeout period for an idle stream set? Plenty
of settting for idle clients but I can't find anything for idle streams. Maybe
I am just misssing it.

[fmslove]

does the 1fps video plays on the flash player for 60 second before FMS closes it?

OR
You have never been able to watch your 1 fps video playing ?

[Nikhil Kalyan]

i have tried playing a 1 fps video file with the vod application and using the
sample client application that comes along with vod application on FMS3 and it
played for the full duration without any issues.
so,
Can you just provide more details of the exact scenario you tried ? it can
help look more into the problem :smile;

[Graeme Bull]

If I were to put in my 2 cents, I would say you are seeing normal behaviour. A
60 second video at 1 FPS is 60 frames. In normal video that would be about 2 to
4 seconds. Most likely the video is buffering so fast that it then just goes
idle after that.

[dmazan]

Sorry I was not clear. The video is 25 minutes long, one frame per second. It
starts playing. That is it starts playing properly in the vodtest player, but
the FMS console shows the stream is idle. After 30 seconds, the player stops
playing the stream. The server log shows a code 408 which is a request timeout.

It seems clear that the 1fps stream falls below some threshold that the FMS
needs to show a stream as active. Need to identify where that threshold is set
and how to modify it. Second, need to identify where the timeout duration is
set and, alternately, modify that.

Duffy

[fmslove]

you can monitor the data transfer from FMS to the client using Admin console;
that should give an idea in case FMS is showing it idle just because it has
sent all the data in one go.

What are the other specifications of the file:
Codec:
Bitrate:
Total file size:
Seems like this it is very dependent upon the video file. If possible, I would
like to take a sneak peak in that video file;

I guess status code 408 is for client disconnect.