Forum Replies Created

Page 1 of 5
  • I recently had this same obstacle. I got around it by creating a black solid layer above the comp that was being continuously rasterized, and then using a luma track matte.

    The black solid could change opacity and keyframe, and the track matte applied a universal opacity change accordingly.

  • Thanks Vishesh.

    I don’t think that’s a practical solution, unfortunately. The line thickness has been used without incident or issue in several projects. The weight of the line has successfully been used and adopted in the design standard for ongoing content in this bucket.

    The heart of the matter is not rooted in design aesthetics (I’m convinced) but a feature not behaving how its intended on my system (see above that another system rendered the identical project just fine).

    I would be open to suggestions on how to purge the issue out of my system however.

  • Ridley-

    Yes, that’s the effected zone for sure. I was able to port the project to another identical system on site and low and behold, the render is fine (same exact media, same exact project, same exact comp). Which makes me uneasy about fixing the issue on my machine.

    The long GOP suggestion is an interesting one, however, the same shapes are used in other comps with footage from the same shoot, and seemingly at random don’t experience the flicker.

    All footage is input and output as ProRes 422. This is of course transcoded from the native camera files (canon 5d mkIII).

    The user Vishesh gave me a project with essentially the same exact shape, and I used that in the same way I’ve used my own shapes with the footage from the project, and there was no flickering.

    I guess now, I need to figure out what needs to be reset/purged/deleted/changed/re-installed on my system.

  • Thanks Vishesh-

    Your set up is essentially the same as mine, and renders just fine. I also used the comp you created to nest over video footage, and parented it to a motion tracked null layer (as I’m doing in my project) AND reset your shape layer’s OFFSET (under trim paths) back to 0. And it all worked fine.

    I can’t break it if I try.

    Unfortunately, this is the same behavior I’m experiencing throughout my projects. I currently have 14 clips in THIS project that use a similar shape (made always in the same way, and in many cases created by duplicating and altering a shape comp). And seemingly at random between 25% – 75% of the rendered clips experience the flickering.

    I think at this point its safe to say I’m not necessarily doing anything wrong, and I’m having some system vomit.

  • … I want to add that I have created similar shapes throughout the project (circle and various different lines) using the same trim paths feature, without incident.

    I should ALSO ALSO add for sake of spec clarity that the video footage coming IN to the project is ProRes 422, and my output matches that. However I’ve tried rendering as ProRes 444 (just to give it something to think about) and as Animation. But I get the same results.

    visit Very Loud Ideas

  • Thanks Ridley-

    Looks like the creative cow upload is going bonkers. Here’s a dropbox link:

    https://dl.dropbox.com/u/64284203/nat_gym_burpees_02.mp4?dl=1

    You may want to set it in loop play to get a feel (kept it short for file size reasons).

    The flicker is most noticeable on this clip at the intersecting point of the line and circle (just to the right of S in BURPEES) and at the closing point of the circle as well. On a higher resolution version you would also see the same behavior on the end anchor point of the line (underneath the talents body).

    The perplexing part too is the flicker does not happen in the program monitor of AE, just upon rendering.

  • As a large company, updates must be scheduled and performed through a ticket system. This is hardly a new feature (trim paths) and unless you can back up the fact that this specific issue is resolved in an update, then I’ll wait for further feedback.

    Regards.

    visit Very Loud Ideas

  • Sounds cool, Mark. Do you have an example link somewhere I can view to see what you pulled off?

    visit Very Loud Ideas

  • True enough, Jason. My concern however would be the clothes/wind effect. Certainly we could exaggerate slow movements of the body, but the clothes are another issue. I think it may boil down to a bunch of trial and error 😉

    visit Very Loud Ideas

  • An interesting idea, Mark. Thanks.

    visit Very Loud Ideas

Page 1 of 5

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy