In D10001#251700, @Sergey Sharybin (sergey) wrote:

I haven't checked how this worked originally

But this is something important to know.

I will try to check, but I am not sure where to start even. I remember 2.79 code to be quite messy and it was sculpted bit after bit into current shape. I am not sure if 2.79 code can be used as reference that is working as intended.

Building proxies with meta strips should recurse into meta strip

While it sounds reasonable, the interface is wrong then. Meta strip has proxy and timecode settings. So if proxy on a meta level is not possible, then the settings needs to be hidden from user.

I wouldn't disagree here, I guess this was meant to be convinient to build proxies inside metas recursively from top seqbase.
However if I hide build proxies button for metas, I would have to disallow recursive proxy building as well, so it is consistent.

Perhaps this could be handled better by UI to inform user that it will build proxies recursively, not sure.

I remember 2.79 code to be quite messy and it was sculpted bit after bit into current shape.

You don't need to check code: do a user-level check. Shouldn't take too much time.

However if I hide build proxies button for metas, I would have to disallow recursive proxy building as well, so it is consistent.

If the meta-level proxy is not implemented (at some point in time the idea was to create proxy for meta strip to act as some sort of cache), then it is better not to recurse inside. Meta strip can consist of many strips, and you wouldn't want to rebuild proxy for all of them.

In D10001#253447, @Sergey Sharybin (sergey) wrote:

I remember 2.79 code to be quite messy and it was sculpted bit after bit into current shape.

You don't need to check code: do a user-level check. Shouldn't take too much time.

However if I hide build proxies button for metas, I would have to disallow recursive proxy building as well, so it is consistent.

If the meta-level proxy is not implemented (at some point in time the idea was to create proxy for meta strip to act as some sort of cache), then it is better not to recurse inside. Meta strip can consist of many strips, and you wouldn't want to rebuild proxy for all of them.

Yes so up to 2.79 proxies could be rendered with per-project setting, otherwise it did nothing. Now disk cache should be used to make preview faster.
So I won't do this recursion.

Multicam and scene strip are cleared from poll function in UI as well.

So is Scene strips. As in, description needs some update.

In D10001#254415, @Sergey Sharybin (sergey) wrote:

Multicam and scene strip are cleared from poll function in UI as well.

So is Scene strips. As in, description needs some update.

I think you meant meta?