Just to be clear, I'm not saying to not use RB in your production.  I'm trying to get your help isolating the cause of the issue you're encountering.  For example, If the issue doesn’t occur when RB is not applied, then we can eliminate RB as the culprit.    ... View more

This is sounding more like a problem with formats.  Try exporting the same comp without RB applied to any layers, then see if you still get the flickering with the rendered QT clip. ... View more

Hi SundayGladitator, We fixed the flash frame issue for most cases, except for a few intermittent edge cases that are difficult to reproduce.  The flash frame only occurs while adding foreground/background strokes on non-base frames in the layer panel, meaning you should not be seeing flash frames during propagation or when previewing propagation results.   Are you seeing a flash frame/flickering when previewing in Ae after using roto brush?  Or do you only see the flickering after exporting a comp through the render queue?   If issue occurs during preview, then this could a render thread problem.  If issue occurs on output, then this could be a formats problem.   Please report back with your findings. Thanks. ... View more

I'm keeping a record of your results when using RB2 and adding them to our internal database for potential feature enhancements and bug fixes. So, thanks for keeping us up to date. Regarding the Ae warning on start up, that is a known issue and is harmless.  Should be fixed soon.  ... View more

Hey PitcherGiffer.  Based on your recent findings it appears that Ae is running out of memory.  Resulting in purged frames.  In a previous thread, I inadvertently gave you the wrong instructions regarding the Memory settings in AE.  You need to enable “Reduce cache size when system is low on memory” in the Ae Memory & Performance setting (i.e., click the check box).  Are you running Ae on Big Sur?  If so, that could be compounding the problem.  No solution yet for that, but we ‘re actively working with Apple to improve performance of RB2 on macOS 11.   Ae memory prefs setting ... View more

To speed things along, please go ahead and send us the project and source footage: In the Project panel, select the composition that contains the footage with Roto Brush applied. Go to File > Dependencies > Collect Files In the Collect Files dialog: Set "Collect Source Files" to "For Selected Comps" Enabled the "Reduce Project" checkbox Click "Collect" and select a location to collect the project file and footage Zip up the folder containing the newly-collected project and footage. Add the .zip to your Creative Cloud storage ( or Dropbox, OneDrive, etc ) and email a link with a brief description of what you were experiencing to rotobeta@adobe.com. All footage submitted will be kept confidential and will not be shared with third-parties. ... View more

Thanks for posting the video.  I see exactly what you're describing.  You have a few seconds of propagated frames, the CTI is parked downstream from the base frame on a propagated frame, you add a foreground/background stroke, and the propagated frames are re-propagating.  Expected behavior is to wait until the CTI has moved from the current position before initiating propagation.  It could still be a memory issue, but more likely you found a bug.  I need to investigate further and see if I can reproduce in-house. Thanks. ... View more

Hey PitcherGiffer, Sounds like you may have run into an issue we recently fixed with cache markings not drawing for propagated frames, possibly forcing a re-render.  More likely, Ae might be running out of memory when attempting to render a propagated frame.  In the latter case, try changing Ae Memory & Performance setting: check “Reduce cache size when system is low on memory”.  That might take care of the issue.  Regarding the cache markings, that fix was checked into a recent build of AE 17.6 beta.  Please try updating to the most recent build if you don’t already have it installed.  Please let us know if either of these solutions works for you.  Thanks. ... View more

What you're encountering appears to be a bug.  A couple of suggestions. 1. Try changing toggle settings (switch between alpha, alpha boundary, etc.).  That might force a redraw of the layer viewer to correctly display your line segmentation. 2. Try moving the CTI to a new frame within the span.   We just this week released to the public a new version of AE (17.5) that includes Roto Brush 2.  It’s a major overhaul to the rotoscoping experience in AE, includes many bug fixes, UI improvements, and has faster and better segmentation results.  For reference, here’s a link to the most up to date help file on Roto Brush and Refine Matte workflow: https://helpx.adobe.com/in/after-effects/using/roto-brush-refine-matte.html Thanks   ... View more

This looks like the expected behavior based on the screen shot (i.e., I'm not seeing the black outline). Take another shot, but this time place a light color solid layer underneath the roto layer, so I can see the outline better.  Thanks.   ... View more

Please post a pic of your comp, layer and timeline panels and I'll see if anything obvious stands out. Thanks. ... View more

OK.  Thanks for the update.  ... View more

A warning dialog should appear if you attempt to draw a stroke while propagating frames, advising that strokes can't be added until the current frame has finished rendering.  And AE should not be locking up.  I might have better luck reproducing what you’re encountering if you could post a screen recording?  Thanks.     ... View more

Interesting. I'm unable to reproduce based on steps.  Do you encounter the error each time you adjust the span?  Can you please provide a screen shot of your Layer Viewer prior to adjusting the span?  Or a screen recoding would be even better.  Thanks. ... View more

Yes, that's correct.  Previewing in general is broken in Layer and Footage panel views.  Issue is not specific to Roto Brush but affects ability to view propagation in real-time.  We're actively working on fix.  In the mean-time-you can work around the problem by moving the CTI to your target frame to induce propagation.   ... View more

We ship when the feature is ready for public release.   We’re getting close.  We make that decision partially based on feedback from our Beta users.  So thanks for contributing.  ... View more

Yes, this is a known issue, AE stops responding when previewing in the Layer panel.  A fix should be available soon.  In the meantime, continue moving the CTI to start propagation.  Thanks ... View more

Could be a couple of things occurring.  The Freeze button will only appear if Roto Brush & Refine Edge is selected in the View popup menu in the Layer Panel.  So check that first (i.e., make sure you don't have Masks or something else selected).  Regarding "propagating frames over and over again";  If possible, please send us a screen recording to rotobeta@adobe.com.   The frame count when propagating could change if you move the CTI while propagating or modify RB effect parameters.  I'd like to see a screen recording of that too.  Thanks.    ... View more

Another good catch!  I can reproduce what you're seeing, although it's intermittent for me.  But you're correct, a flash frame does occur.  It has something to do with adding background/foreground strokes at a non-base frame location after propagating a lengthy clip (around 30 seconds).  We're working on fix.  Thanks for your help.   ... View more

Yes, we're fixing this issue.  The build will be available soon.   ... View more

That doesn't sound good.  We may need to get the Ae project and source from you so we can analyze in-house.  We're going to be reviewing all the recent forum post for RB2 with our dev team and follow up soon.  Please stay tuned.  Thanks.  ... View more

We've had some recent breakage occur with RB 2 that we're currently investigating.  I'll follow up as soon as I have an update.  I might need more info from you as well.  Thanks for reporting.  ... View more

Yes, that could also be the cause.  It's a known issue that we recently fixed.  A build with the fix should be available very soon. ... View more

Fixed in build 17.5 x10.  Please try it and report back if you're still encountering this problem.  Thanks.  ... View more

It's working again, in build 17.5x010.  Follow this forum thread for deails as we update the post: https://community.adobe.com/t5/after-effects-beta/rotobrush-2-no-longer-working/td-p/11403445?page=1 Thanks. ... View more

That doesn’t sound good.  Any chance we can get a copy of your project and source so we can attempt to reproduce in-house? See instructions below for how to do that.  Thanks.   In the Project panel, select the composition that contains the footage with Roto Brush applied. Go to File > Dependencies > Collect Files In the Collect Files dialog: Set "Collect Source Files" to "For Selected Comps" Enabled the "Reduce Project" checkbox Click "Collect" and select a location to collect the project file and footage Zip up the folder containing the newly-collected project and footage. Add the .zip to your Creative Cloud storage ( or Dropbox, OneDrive, etc ) and email a link with a brief description of what you were experiencing to rotobeta@adobe.com. All footage submitted will be kept confidential and will not be shared with third-parties. ... View more

Sounds like you may have discovered a display problem that RB is exposing.  Unfortunately we haven’t been able to reproduce in-house.  Would you be willing to work with us to help us get a repro case?  We’d probably need your project, source, AE preferences, system specs, log files, and possibly do a remote screen share.  If so, please send an email to rotobeta@adobe.com, and I’ll follow up with you. In the meantime; try purging all memory, try switching comp renderer settings, enable/disable hardware accelerate preference, and try various preview settings (e.g., fast previews, viewer quality).  Then report back here is you have any luck.  Thanks.     ... View more

Good catch.  It occurs when the layer is clipped as a result of zooming, which is almost always the case when using roto brush to define segmentation.  This is a known problem that we're actively working on fixing.  Should be addressed soon.   ... View more