cwdjrxyz wrote:
Perhaps the best way to handle this sort of thing is to use the XML
language SMIL, which has a huge number of simple to elaborate
transitions built in, and they can be precisely timed. However, most
browsers do not support SMIL yet. However recent versions of the Real
Player have SMIL support built in. This would not be a good choice for
a general web page, because many people do not have a recent Real
player installed or another player or lesser known browser that will
support it. However, it might be an option for a private page or a
network.
I have a page written in SMIL at
http://www.cwdjr.net/ram/realmix.ram
that uses several of the SMIL transitions. The .ram url I give is just
a Real redirector file that forces the Real player to open the actual
SMIL xml page that has an extension .smil. The reason for this is that
Apple's QT player has a bit of SMIL support, but not the nearly full
SMIL 2 support needed for many SMIL pages. Depending on how you set up
your players, the .smil page could go to the QT player rather than the
Real player if you do not use the .ram redirector file.
The most important thing is that you have the most recent Real player,
or perhaps one or two before it. The browser does not matter, as the
SMIL is processed within the Real player. In fact, you may even be able
to bring up the Real player without first connecting to the web and
enter the url of the .ram. The player may then connect. This page will
work on a very good 56 K dialup connection. However a broadband
connection is best. For a slow dialup connection that can not keep up
with the page, often the page will work properly the second time. The
Real player has a special Real cache. If you call video, images, music,
etc urls with chttp... rather than http..., as I do here, this signals
the Real player to store in the Real cache, which reduces the bit rate
needed on a second pass. It may take a bit of time for the page to
start, as much has to be set up after you connect to it.