[Tommy Dimmel]

Yep! You’re a life saver! As a token of gratitude and for anyone else struggling with this, I created a video that explains how to efficiently transfer any CC Light Burst 2.5 effects from their original layer into an adjustment layer within a precomp. Enjoy: https://www.youtube.com/watch?v=luvNHuti7Io

Some contents or functionalities here are not available due to your cookie preferences!

This happens because the functionality/content marked as “Google Youtube” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.

[Tommy Dimmel]

paste this in you 2D layers position:

this_comp.layer(“your3Dlayername”).to_comp([0,0])

Wow! It’s been 6 years since you posted this expression, but it’s EXACTLY what I was looking for! Thank you so much!!!

[Tommy Dimmel]

Thanks for posting this! Totally had to wait 3 hours last night for about 10 frames to get rendered, that didn’t even really have any outrageous use of CC Light Burst 2.5—just a slight use of it on 2 layers. Once tonight’s render is complete, I’m going to attempt this trick tomorrow. You may be a life safer! Thank you!

[Tommy Dimmel]

A little update here. I was using After Effects 13.2 when I originally had this problem, and then reverted to 13.1. Initially, this provided me with a few solid renders without any problems. But, the problems started popping up again. I troubleshooted in every which way: scanning through potentially problematic layers and effects, changing their sizes and removing them respectively, all to no avail. I read all about achieving optimum memory and performance and tried every suggestion and permutation thereof, also to no avail.

What I ended up trying last night that DID work was to instead render in Adobe Media Encoder, using the H.264 codec. I’m assuming that if I can render the same scene once and have it work, then render the exact same scene again and have it not work, and back and forth and so on, that there must be a bug somehow in the mix between After Effects, OSX Yosemite, and perhaps some of my 3rd party plugins. Especially since the error messages I was receiving were, in fact, erroneous in and of themselves: being told that I didn’t have enough memory available, when I clearly had more than enough. I was also getting bizarre, random error messages saying that certain assets within my project were “not a valid document” ( 51 :: 19 ), when these files were, of course, perfectly valid documents that never give me problems.

Either way, the fact that Adobe Media Encoder provided me a solid render last night makes me happy. I can press on!

[Tommy Dimmel]

…and I just saw your post about how to properly ask for compression help. Here’s that information:

Computer – I’m using a MacBook Pro Retina, 15-inch, Late 2013

Operating System – I’m using OS X Yosemite, Version 10.10.1

Software used including version number – I’m using Adobe After Effects CC 2014, 2014.2 release, Version 13.2.0.49 to create the video, and using Adobe Media Encoder CC 2014, 2014.2 Release, Build 8.2.0.54 to render the video.

Source codec – https://www.tommydimmel.com/images/my_photos/Composition%20Settings.png

Destination codec – https://www.tommydimmel.com/images/my_photos/Adobe%20Media%20Encoder%20Render%20Settings.png

Type of destination use – I want people to be able to view this video as close to its original quality as possible, streaming on YouTube and Vimeo

Thanks

[Tommy Dimmel]

Hi Craig,

Thanks for the reply! You’ve opened my eyes to a few things, and I will continue to tweak. I did exactly what you said, and it indeed produced a great looking render on my computer! However, once I uploaded it to YouTube, the video again came out looking terrible. I’m intuitively thinking that something about the black & white ‘TV static’ strobing that’s going on in this video is what’s throwing YouTube’s compressor a curveball. Here’s what it came out looking like:

https://www.youtube.com/watch?v=RAwS2xkBI60

Terrible.

I then adjusted the render settings, and went with a 300mbps bitrate and set the KeyFrame rate to 1. The video came out on my computer looking EVEN BETTER, but still when I uploaded this video to YouTube, it comes out looking terrible. See here:

https://www.youtube.com/watch?v=c8gNV2pR10Q

One of the most notable things is the fact that there are HUGE blurs and strange artifacts that YouTube’s compressor is creating out of my background. See here for a comparison of the two:

https://www.tommydimmel.com/images/my_photos/comparison%20youtube%20to%20original.jpg

It seems like YouTube’s compressor is getting totally bamboozled by this video. I’ve been working for months on this project, and I don’t know what the heck I’m going to do if this won’t upload right…ugh…. Any ideas?

[Tommy Dimmel]

Dan,

Thank you so much for this! Worked perfectly and you expanded my knowledge of expressions! Really appreciate it!

[Tommy Dimmel]

Thank you so much for responding to me!

Here’s the exact details I left out on my first post

Name of the main comp: “Heads”
Parameter to control: the position of the jaw on the head
Range of that control (on the y axis): 474.5 to 611.5 ***
***This control is to be the driver for the following parameter

Name of comp, which is nested in the above comp: “Head 3 Barf”
Parameter to control: A slider control
Range of that control: 0 to 1000

[Tommy Dimmel]

Noted.

[Tommy Dimmel]

Yes, I am. Thanks for sending that project file. Your project worked fine for me. I can also create a new project on my computer and suretarget works fine there as well. It’s just in this one particular project of mine. I have been racking my brain over this for 24 hours. Driving me nuts!!! I feel like I have troubleshooted almost everything!