Max Pareschi

This will probably need to be reworked again for develop, it's still based on 3.11.1, on which it resolves the bug completely. I've seen you switched place between extract_review_data_mov and...

The way we were thinking was to export the slate first, then rescan the collection on disk to see if the extra slate frame was rendered and was not in...

The bug is there from 3.9.2, possibly before it as well. #3407 made it consistent, so it’s easier to get it. We’ve been running a modified 3.9.2 ever since just...

Well the most consistent way would be to actually do away with all the checks about slate in every plugin apart from extract slate frame. I've noticed there's quite a...

That's what my pr was about, so yes if it's 3.11.1, but i need to check it again on latest develop. Something will surely break ;)

> Wouldn't be this easier? yes that can work, but do the representation files get updated autmomatically after updating the collection? if not we would also need to prepend that...

So leaving aside code quality, what i'm doing here is to use oiiotool to actually convert from one colorspace to the other. I'm using html since it's very easy to...

3.14.1, fresh from today. That being said this is present from 3.8.something, which was the first version we ever used. Production now is still using 3.9.2-nightly.1 and the bug is...

Confirmed that it's only partially resolved. After @BigRoy pr yesterday the menu entries work as intended. Instead the entries gets removed if the publish was made with "Use Existing Frames",...

I tried dumping the collected instances and the only difference that i can see here is this: ``` Use existing frames: ... "families": [ "review", "write" ], ... Local: ......