Well I don’t think a change in the
MediaDisplay should cause this one. Have you tried using the FlashCom app
watcher swf thingy and seeing what the logs say? You could watch the streams
and see what happens. When you say record the same name FLV 3x I’m not
sure what you mean. Are you capturing video and outputting or are you simply
overwriting the same FLV with new data? I don’t know if Flashcom might
need to be notified that the underlying content of the movie has changed, it
could be loading it all into memory and you’d need to do something in
server-side AS to tell it to dump and re-load?
Sorry, not much help,
Matt
FlexCoders,
We have an application that utilizes Matt and
Chris's class for
extending the MediaDisplay component to intergrate
Flex with Flash
Communication Server.
Interestingly, I can record an FLV with the same
name and have the FLV
stream live, into the component, only 3x before
the stream will not
show in a "live" format. The
MediaDisplay Component then displays
nothing or it displays a dated FLV.
After the 3rd recording, the Stream is recorded,
but subsequent
attempts to show 'streaming' video (of the same
name) fails.
My best guess is that this is a:
-Flash Communication Server Memory Issue
-Flash SWF, Flex Server, or or Flash Communication
Server Garbage
Collection issue.
-An issue with the MediaDisplay component.
Can anyone else shed light on their thoughts about
what it could be
and how I could go about debugging this issue?
Best,
Dave
Yahoo! Groups Links
|
