Help with publishing to Kitsu

General
,
1

Hi everyone!

I’m getting a problem while trying to setup AYON to work with Kitsu.
This is where I’m stuck right now ayon_core.pipeline.publish.publish_plugins.KnownPublishError: Kitsu id not available in AYON for '/sequences/KBR/KBR_0010'

Trying to render out a test and have it show up in Kitsu, but it keeps failing at the ‘Kitsu entities’ stage.

I’ll provide additional info as needed.

2

Does syncing the project fixes the issue?

Also, Tagging @Danell he is the god father of kitsu addon.

3

It goes through when I sync the project again, but doesn’t update anything in Kitsu and there is no reviewable in Ayon.

What would the correct workflow be?

So far, I have a project with all the shots created in Kitsu, setup with all the tasks that I need, but they lack some information like framerange, FPS, etc. For that I have a timeline in Nuke Studio which I want to transfer the shot information to.

This is what I’m trying to do:

  • Publish the shots (or update the shots that exist in KItsu)
  • Publish the plates
    (this would then generate the folder structure)
  • Have previews visible in all the shots in Kitsu
  • Get reviewables to show in Kitsu and Ayon after rendering shots out of Nuke

I have managed to get all of that done, but without the Kitsu part. It’s the Kitsu part that’s troubling me.

If it’s not possible to use the shots that are generated in Kitsu, I don’t mind generating them in Nuke Studio and Ayon and then syncing them to Kitsu, but not sure how to do that.

4

I gave syncing a test run and it’s omni directional from Kitsu to AYON.
I’m not about the recommended workflow to publish shots to Kitsu.

So, pushing your shots to Kitsu and sync to AYON result in missing shot information. and Pushing your shots to AYON creates them with full information but result in not syncing them to Kitsu.

Not sure if there’s a way I’m not aware of to sync them from AYON to Ktisu.
Hope @Danell can provide some insights.

Also, Tagging @murphy and @jakub.jezek for further assistance.

6

Thanks for the tags, hopefully we can find a solution.
If there’s any more info I can give, I’ll try to be more descriptive.

7

Found a fix for the publishing to kitsu issue. Looks like there was a mismatch with the task names. If there’s a space in Kitsu and the Ayon production tool, there has to be an underscore in the actual project. Took me a while to notice.
image

There is still that ‘issue’ (or missing feature?) about the syncing of generated shots out of Nuke Studio to Kitsu through Ayon, but that one is less important.

2 Likes
8

As far as I know, This shouldn’t affect the pipeline as entities are matched by kitsu ID.

9

In Kitsu they have spaces.
image

In Ayon I needed to put underscores.
image

10

As far as I know about syncing feature in kitsu addon, it creates matching entities on AYON with label (any characters I think) and name (uppercase, lowercase and underscores)

Labels of created entities with the sync feature can be renamed as they still preserve the kitsu ID.

image
image774×238 11.8 KB

On the other hand, An issue can happen when creating folders on AYON side (manually or using Nuke addon) and publishing won’t work because, kitsu ID is not set.

Also, I gave it a try on my side to create the asset in both AYON and kitsu (with matched names) and syncing project didn’t set the kitsu ID for the matched entity (by name).

In browser tab, you can right-click any entity and select details

image
image664×800 28.6 KB

Then, you’ll be able to find the kitsu ID.
image
image1965×901 80.6 KB

1 Like
11

Thank you for the clarification!

Now I understand this a lot more.

12

I’ve also created this issue. Once it’s resolved, published shots from Nuke/Hiero (with the exact same names on Kitsu) should receive the Kitsu ID when the sync is triggered.

1 Like