Persistent Clip Marker on AeMoGRT

What's the latest on Responsive Design Time for AeMoGRTs in PPro? 

Is there a known issue or more likely user error? 

Thanks for your insights, Roland! Also, making AE Markers visible in AE Mogrts once they are used in Premiere is definitely being tracked as a request. 

Cheers,

Thanks Dacia - I knew, given some time, you'd agree.   😄

OH! While looking at this, perhaps there's a chance to also look into exporting Ae Markers, as part of the AeMoGRT. I'm still not convinced working with the Responsive Design Time feature.  😞 
So, Markers are a sufficient workaround.

And our last exchange, I brought up the matter of Iteractive Preview Caching for AeMoGRTs in PPro. I double+triple checked and this is a feature. After more digging, I THINK there is an internal limit at play. Specifically. if an AeMoGRT is compute-heavy and crosses a threshold, Iteractive Preview Caching doesn't happen.

I feel that a good test will involve three levels of compute-heavy AeMoGRTs will form a good basis for testing. So, basic, intermediate and heavy in terms of computation requirements. 

And thanks for the reply. 

Thanks for the reply. 

My expectation is that a fresh drag+drop, from the EGP onto a timeline should be fresh - no Markers, regardless of where/which timeline is the destination. If I ALT+Drag to create an instance/copy then I can understand the persistance of the Marker but not a fresh copy; which is the entire premise of drag a fresh copy from the EGP-Browser.