Possible missing "farm" check in ExtractColorspaceTranscode

General
1

Hi,

I was just recently exploring the publishing process from within Nuke using existing frames / existing frames - farm.

I noticed, that the ExtractColorsaceTranscode Plugin is being executed locally during the publish process for both settings, which I think is not intended.
When comparing the plugin settings to these lines in the oiio_post_process plugin

I see that this part is missing in the ExtractColorsaceTranscode plugin.

Is this intentional or do some other plugins rely on that logic?
If not, I would create an issue/PR for this.

Cheers

2

I think that if there is a representation already locally - even if targeting farm it should process it. The real question is - what issue are you facing, and why does it have a representation? (otherwise it should skip processing anyway)

3

If I publish the instance with use existing frames - farm - it still processes the ExtractColorsaceTranscode plugin during the local publish.

In some use cases, for example very long shots, I actually do want a farm machine to do all the heavy work - I mean that should be the purpose of these two settings.

My point is, the plugin should not be processed twice (if setting the render target to use existing frames - farm) since the publish farm job does it anyways, right?

4

Correct - it should not be processing those images (especially not twice)

But perhaps that local instance should not be adding them as representations to begin with if they are not to be integrated at that point in time.

@iLLiCiT what do you say:

  • be more careful about what to add to instance.data["representations"] and only put things there once they will be published in current session
  • or skip the plug-in using if instance.data.get("farm", False)

The latter might be easier to fix this case. I’m mostly thinking what base strategy/goal we should set out for here though.

5

be more careful about what to add to instance.data["representations"] and only put things there once they will be published in current session

Yes, we should not create the representation if the current publishing is not processing it, I think that will actually trigger more logic than just this.

or skip the plug-in using if instance.data.get("farm", False)

Yes. Even if we’re careful about representation we don’t have a reason to run the plugin if the instnace is marked for farm publishing.

1 Like
6

Thanks - PRs are welcome @sebastian.brandhuber for the areas you feel comfortable with. :slight_smile:

1 Like