#MCI/DLL & Palette shift
2 messages in this thread
I have a few questions about FLI/FLC support under Windows. No matter what I
seem to try, I cannot get rid of the palette flash when using the AAPlay.DLL
and MCIAAP.DRV to play flics. So my first question is, when in 256 color mode
and showing a bitmap with a 256 color palette, can a flic be played with the
Autodesk DLLs and drivers that will not cause a palette flash? Can the flic be
made to play with the current palette, such as the one used to display the
bitmap? I have tried having matching 256 & 236 color palettes, etc. Is there
anything that can be done?
Second, it seems to me that the MCIAAP.DRV was not fully developed. Why were
so many commands excpected of an MCI annimation driver no implemented? For
example, why can't a window handle be given to the driver with the Window
command? Also, why does the palette seem to get automatically realized, but
the realize command does not get recognized?
Third, large companies such as Asymetrix are pointing the finger squarely at
you "Autodesk" when they are approached about such issues as the flic palette
flashing, yet your product seems to have been reletively untouched (DLL &
Drivers) since it first appeared several years ago.
Is this Windows player software not supported anymore? If so, why?
Macromedia's Authorware supports playing flics internally somehow and does not
use the AAPlay code. And other small developers have written stand alone
Windows flic players, too. Is this the only way to go?
It would seem that with all the advantages of the Autodesk flic format over
AVI, etc. that you would somehow support it's users and developers better. Is
it that your Windows focus has changed to AVI support?
Finally, if you are not making any plans to improve upon the standard Windows
flic playback tools, is there anyway we could get the DLL code so we don't have
to start from scratch?
<<Palette>>
FLC files are not truly aware of Windows. As such, there is often a palette
flash between aniamtions/bitmaps. Each time a new animation/bitmap is loaded,
the Windows player performs a palette reinitialization. There is no way to turn
this off, it is hard coded into the player. As a result, the palette will
reinitialize even if it is not required.
While you can not get rid of this entirely, you can minimize the effect. Use a
palette of 236 colors, leaving the first and last 10 palette positions unused
within the aniamtion. Those are the postitions that Windows will try to take
control of. Also, use a common palette for all animations/bitmaps if possible.
<<MCI driver control>>
There were only a specific set of MCI commands that are supported in the MCI
driver. A list of those supported commands accompanies the MCI driver when you
download it from the forum. I can not say for sure, but I think the reason many
commands were not implimented is because of the way that the Animation Window
is created. The player window is really two windows. First there is the child
window, the one you create from your application. Then there is a second
borderless windows that is carefully laid on top of the child, only its not a
child window, its a parent window of the AAPLAY.DLL. This is often why it
can't be controlled, because it really isn't owned by the application that is
using the DLL.
<<Third, large companies such as Asymetrix are pointing the finger squarely at
you "Autodesk" when they are approached about such issues as the flic palette
flashing, yet your product seems to have been reletively untouched (DLL &
Drivers) since it first appeared several years ago.>>
You are correct.
(Well, what do you want me to say? That is a statement, not a question. <g>)
<<Is this Windows player software not supported anymore?>>
Sure. I am supporting it right now. I think what you are asking is are we
developing this software any more. The answer to that is yes, and the focus for
that development is being placed into Animator Studio. As for companies that
are writing their own code to play FLC files, that is always an option for a
company that has the resources. The FLC format and our developers kits are both
available.
<< Is it that your Windows focus has changed to AVI support?>>
I am not sure how to answer this question. Autodesk has a made a commitment to
Windows, but I am not aware of a policy of one file format over another.
Animator Studio can import both AVI and FLC files. Also, even with the release
of AA Studio, we continue to sell Animator Pro. So I guess I would have to say
no, I am not aware of any bias towards AVI.
<<Finally, if you are not making any plans to improve upon the standard Windows
flic playback tools, is there anyway we could get the DLL code so we don't have
to start from scratch?>>
That is not a question I could answer. The Product Manager for all the Animator
software is Brent Blackett. He is the only person who would have the authority
to release source code. He can be contacted at the main Autodesk number
415-507-5000 or on the internet at brent.blackett@autodesk.com.
-Brian