[Chris Wright]

Photoshop comes with a free Adobe Gamma ICM profile creator in windows-control panel. I can’t guarantee perfection because low end LCD’s aren’t as accurate as professional ones. But you’ll definately be better off.

You’ll use SD-TV color color management for project settings and view simulate output.

The broadcast spec out 16-235 levels so that the NTSC won’t get line crawl use a gradual change so its a legal signal, but Color finesse does a better job.

For starters…

use photoshops’ Adobe gamma in control panel, adjust each red, green, blue, and save the icm file at gamma 1.8(mac) or 2.2(win) gamma, then setup AE with color management.

you need to give your project’s Working Space a color profile in order to use a color managed workflow (this includes simulated outputs). You can do this in Project Settings (cmd-opt-shift-k on Mac, ctrl-alt-shift-k on PC).

Each file has an interpret color management plus AE has blend color, legacy colors, etc. all these plus you need the exact same codec versions, gamma calibrated monitor…

plus how you are viewing them back out. Quicktime player preferences could be different too. Use your scopes rather. Do a full render-loop, export/import file, with no color changes, there should be no change in gamma. That way tests for a correct color management setup.

Now unless, you have software like powerstrip that changes your LCD to interlaced 59.94 hz, you won’t be able to check for line flicker. But a 10 cent dvd-r can do that, can’t it? A long time ago I used to change my monitor to interlaced and send out composite to TV before I had decklink/aja, but there’s noten like a shoestring budget, is there?

[Chris Wright]

very first thing I would try is hold down CTRL+ALT+SHIFT as you open AE. That will reset AE’s preferences to default. That fixes a lot of stuff.

Then I’d check what’s running in the background. Too many hard drive read ‘n writes the same time adobe stuff tries to open. then virus/malware check with AVG or Trend Micro.

They find 99.999% of stuff. heck AVG has a free version you can download and trend has a free online check called housecall too.

I’d recommend getting these fixed before April 1st, because you might have a sleeper trojan that will turn on on that date.

[Chris Wright]

you need to create a pixel plugger that removes single pixels that don’t belong next to a widely different luminance and ignore larger groups of them so you don’t have to mask. That way, we could automaticaly remove specks of any color.

You also need to create auto-debanding plugins that remove banding and interpolate the missing colors so we don’t have to “noise up” to hide them.

And an auto fps changer that makes timewarp changes fps easily.

And update all the plugins to 32bpc so we can use them all without fear of highlight errors.

and reverse compatibility plugin for older AE’s to import newer projects.

[Chris Wright]

It could motion track out the people and then you could create mattes and invert mattes for AE. It makes roto a lot faster and simpler, think working at 10 frames invervals, not 1 frame. That’s like 10x faster!

[Chris Wright]

if you don’t want to mess with a pitch or duration change of your clips, you can use optical flow plugins like timewarp and twixtor to change the framerate and leave the duration and audio pitch the same.

But then you run into pitfalls of the plugins getting confused and created gloopy cuts unless you separate the clips manually or use dynamic link on original premiere cuts.

Simply dropping different fps into different fps comps can make AE drop frames or stutter without plugins, that’s why interpreting them as something they are not works so well, at least down to to a point.

[Chris Wright]

it looks like the fix created other problems, use a workaround for now. heh, try 32bpc and see if it still crashes.

“Exposure effect: negative offset values render garbage/underflow in 8bpc and 16bpc. (49294)”

[Chris Wright]

I’m guessing you don’t have Mocha or CS4. You could try garbage mattes with color keys to speed up the roto refinements if the backgrounds are simple enough.

[Chris Wright]

this is 3rd in the list of things the 9.01 update fixes.

[Chris Wright]

SWF’s can cause crashes if they are the source footage. There’s too many compression schemes for AE to know them all. Make them uncompressed first, then red will go away.

[Chris Wright]

ok, this is actually funny, adobe has free projects available here

old film project makes dirt, scratches, flicker , jitter,vinegette, etc.

https://www.adobe.com/cfusion/exchange/index.cfm?from=1&o=desc&cat=235&event=productHome&s=3&l=-1&exc=21