the least amount of local resources would be used by having one netstream instance and switching the stream when desired. because those streams are downloading so there will be a (brief) delay when switching.
if that delay is not acceptable then you have to do what you're currently doing with multiple netstream instances so you can switch among any of the paused instances.
thanks, kglad for a fast answer. a brief delay is acceptable, only if not brief enough, it could be confusing for the user. i've been monitoring RAM usage for flashplayer and what seems to demand the most of it is having more than one file playing at a time or scrubbing along the timeline. video files are 720p encoded @ +/-5MBs.
your solution is the simplest one, which normally implies it will be the most efficient. i will have to, at least, try both.
just finished testing with just one video object one netconnection and one netstream and since the files are (and will be for the final demo and app) local, there is no distinguishable delay when I load them and switching between videos bearly increases RAM or CPU use, so, yes! one single object for all flv's is the best solution. thanks again, kglad, for putting me back on the simplicity track!
1 person found this helpful
there's no flash or blink as you change from one flv to another? i would expect there would be because harddrive access is not instant, at least, not with my harddrive.
in any case, you're welcome.
no, no flash nor blink, just a slight freeze which is acceptable since it coincides with the image changing moment and is not distracting and almost unnoticeable.
that's good to hear.