Colin,
> What I think you're seeing is the frames left in memory from the
> previously viewed video.
I was thinking that this is explained by QuickTime 6's "skip protection",
which combines a big buffer and faster-than-realtime media delivery to
provide a better streaming experience.
(QuickTime probably tends toward re-using already-allocated buffer memory,
rather than constantly allocating and de-allocating memory.)
If I'm wrong, I'll owe you a slice the next time I'm in the area. :O)
-- Charles
-----Original Message-----
>> Wouldn't it be better being able to limit the buffer to about 10 seconds?
>
> A QuickTime engineer may have a better answer, but I assume this is done
for quality-of-service purposes. PC memory is (relatively) cheap and
plentiful, and a large buffer can hide most internet traffic hiccups.
You may not be thinking far enough back in time, but you're basically right.
With QuickTime 2.0 came the Data Pipe (tm). The way that works is that
frames are loaded into memory ahead of where you are playing, and remain
loaded behind where you have played, and when the end of memory is reached
it loops around. By doing this the playback can be at the data rate of the
system, and isn't affected by brief changes.
What I think you're seeing is the frames left in memory from the previously
viewed video. If you happen to jump back a bit in the movie you would do so
very quickly, as the frames are still in memory. That memory though is
marked as purgeable, and if it's needed by anything else it can be freed up
by the system.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
QuickTime-Users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/quicktime-users/email@hidden
This email sent to email@hidden
