Bony
03-21-2003, 04:57 PM
Hello,
The latest version of Aura 2.5b doesn't appear to respect the bit depth settings of Quicktime.
I have tried the following setting when exporting a quicktime:
Compression setting is PNG, with best compression.
It seems no matter what bit depth you choose, the quicktime is always saved as a 32 bit file.
I specifically don't want an alpha channel, so I've tried the "millions" setting and when I do an info on my QT file it always says the bit depth is "millions+." It does this no matter if you choose 24 bit or 16 colors, etc.
I am using quicktime Pro 6.0 and have not tried this on earlier version of Aura.
I have tried it on stand alone Aura 2.5b as well as Aura Vt and get the same results.
I have tried it with the "none" setting as well as the PNG and it does the same thing.
It does it wheter "save alpha" is turned on or off in Aura under export settings.
This doesn't appear to be a QT bug as these settings work fine in other applications such as Framecycler Pro, etc.
Is this a known bug? Is there a work around?
Cheers,
Bony
The latest version of Aura 2.5b doesn't appear to respect the bit depth settings of Quicktime.
I have tried the following setting when exporting a quicktime:
Compression setting is PNG, with best compression.
It seems no matter what bit depth you choose, the quicktime is always saved as a 32 bit file.
I specifically don't want an alpha channel, so I've tried the "millions" setting and when I do an info on my QT file it always says the bit depth is "millions+." It does this no matter if you choose 24 bit or 16 colors, etc.
I am using quicktime Pro 6.0 and have not tried this on earlier version of Aura.
I have tried it on stand alone Aura 2.5b as well as Aura Vt and get the same results.
I have tried it with the "none" setting as well as the PNG and it does the same thing.
It does it wheter "save alpha" is turned on or off in Aura under export settings.
This doesn't appear to be a QT bug as these settings work fine in other applications such as Framecycler Pro, etc.
Is this a known bug? Is there a work around?
Cheers,
Bony