This content has been marked as final. Show 3 replies
Have you updated AE to 8.0.2 and have the latest drivers for your Matrox card?
If you reboot, does everything work OK again?
Here are a few tips that solve most issues:
- Jonas Hummelstrand
Mmh, this seems to be related to your Matrox card and CoDecs. Basically the way I picture it there are a few possible causes:
a) the Matrox preview plugin for AE is not compatible with CS3
b) you are using a buggy or outdated version of their CoDecs
c) something goes wrong when capturing your files and they have a dmaged internal stream structure
d) your graphics card is competing with resources of your video card and vice versa. They both get in the way of each other by attempting to "steal" the overlay buffers for accelerated display functions.
In all cases it seems some garbage ends up being saved in the AE project files for the good intention of fixing those issues, but it does the opposite, causing massive memory consumption and errors when re-opening. As Jonas suggested, update your AE and definitely also look into updating your Matrox drivers and complementary software. Also make sure that everything is configured properly. As a temporary measure I would simply try and disable the secondary monitor area created by the Matrox drivers to feed the video output. If this resolves the erratic behavior, you at least know who is to blame...
thanks for the advice, much appreciated, i have checked and seem to have all the right drivers, its still a new system and i got everything installed from the start, including 8.02 update and Matrox tools 3.1
You may be right in your thought that it is a Matrox/Abobe conflict, the list in the Matrox known issues document is huge, wish i could have seen it before i forked out 2k for the Matrox hardware.