AVI files imported into Corel appear in negative coloration

[BentPennies]

Has anyone ever had any problems importing AVI files into Corel 12 and having the AVI file appear in negative coloration?


AVI files that are created in Corel and exported or saved appear in normal coloration when reopened in Corel or any other media player.

I would like to use Corel to add some graphics to only shot AVI files.

Does anybody know how I can correct this problem?

 

[javabearSTL]

Photopaint is not an AVI editor, although it can open AVI files. Your best bet would be to use an actual "movie editor" to place other graphics and text in "movie" files.

 

[BentPennies]

It seems everyone asked me that question "why am I using Corel as an editor?" To answer: I'm not. I use Premiere for my NLE. However there are some things that are simply beyond its program capabilities. That is why I'm using trying to use Corel. I wish to place some simple graphics in the AVI file on a frame by frame basis, as an animation. I know that it is possible to create animations with Corel PhotoPaint 12 because I've done so and have saved them as an AVI file. They open and play fine in all applications The problem is opening AVI files that were not created/captured in Corel appear in negative coloration. I am not able to use the color manager to correct the problem. Perhaps I am mistaken but an AVI file is an AVI file and should be readable/playable in the correct coloration in any program that supports the AVI format. Obviously there's a problem in Corel's codec.

So my question is has anybody run into this type of problem?
Is there a fix for the negative coloration aspects of imported AVI files? Or to I absolutely have to use another program such as Adobe Aftereffects? (extremely expensive option here)

Even if I can't use Corel for the animations
I would still like to fix the coloration problem. Any help is greatly appreciated.

Thanks in advance.

 

[javabearSTL]

Nope, not all AVI files are the same - it can depend on whether or not compression was used... and even then what TYPE of compression was used. And especially if you're using an Adobe product to edit it originally, there's a good chance that the Adobe product is throwing in some proprietary code that's causing the problem.