[Jim Turner]

Ok, thanks, I think I got it!

I thought that if I created a 1920×1080 comp, and then backed up the camera, it would reveal the edges of the comp; hence the enormous comp. What I didn’t realize is that AE would keep generating pixels to accommodate the entire field of view.

I now have a 1920×1080 comp, with my 1920×1080 assets, plus the (same) enormous background plate. I pushed the plate waaay back in the z axis (16,000 px), and pulled the camera waaaay forward in the z axis (-200,000 px), left the assets at 0 px, and everything seems to be working out.

Thanks!

[Jim Turner]

Well, this is just a nightmare. I’ve decided it’s cursed.

Long story short, I determined which asset was causing the problem by deleting things until an export worked. Then, after several iterations, I eventually replaced that video asset with a still image — and it STILL happens. It’s as if simply having three things in that particular configuration on the screen causes the glitch. It makes absolutely no sense.

Nevertheless, the only solution I have found is to remove one of the assets entirely and reconfigure the screen with only 2 assets. It doesn’t seem to matter which 2 I keep — as long as there are only 2.

If anyone can provide some insight, I would love to know what is actually happening. But for now, I can’t keep screwing with this, so this is now the final version.

Thanks again, Merlin, for your help!

[Jim Turner]

Thanks, Merlin!

I just tried something similar, which still failed to fix the problem. I didn’t go as far as transcoding the assets, but here’s what I did:

[Jim Turner]

The text was created with FCP’s text generator. It looks pristine in the original video, before I pull it into AE. Here’s a link to the same video, starting right at the beginning of the same title sequence:
https://youtu.be/NVLfGsB09x8?t=3m36s

Are you saying that if it were interlaced, it could look good on its own, and the problem would only show up in AE?

I don’t know much about FCP’s text generator. I usually use Photoshop for titles, and this was actually the first time I’ve used it (it seems like a faster method to accomplish the same thing). But the source video is certainly progressive – 30p. (The AE project is 24p, but I transcoded the video into 24p using first MPEG Streamclip and then Compressor. But again, after being transcoded, the 24p video looks sharp on its own.)

Do you think it might be because I used FCP’s text generator? I don’t know why that would be, but then again, I have no better idea, either.

Thanks again!

[Jim Turner]

Walter,

Thanks for the suggestion! But no, it’s not interlaced. I tried re-exporting another version of the troublesome video, this time going directly from FCP to Compressor like I normally would. This showed a significant improvement in the AE project (even though the actual video is indistinguishable from the first), but still noticeably jagged on the titles.

I didn’t know what else to do, so I accepted that as the final product. If you’re interested, you can see it here:
https://vimeo.com/63611167

The last video is the one in question; the jagged titles are at 3:51 and 4:06.

Anyway, thanks again!

Jim

[Jim Turner]

How do you get a preset for AVCHD? I googled but came up empty. Can you download more presets from Adobe somehow?

I’m having the same issue. Tried the m2ts trick; didn’t work. Tried following Art’s directions; didn’t work. My best idea right now is to use FCP7 to transcode everything to ProRes before importing into CS6. And that’s just stupid.

Jim

[Jim Turner]

I think I’ve resolved this. I still don’t know exactly why it was happening in the first place, but it seems that if I export the file via Send to -> Compressor, the problem goes away. I’m using all the same settings, but there it is.

Hopefully this will help someone down the road. Thanks, Daniel, for your post.

Jim

[Jim Turner]

We’re using animation because the graphics look really crisp. (In theory, it should be the highest quality export, no?) We then use the animation export as the source to create the other versions we need for posting in various places on the web.

Jim