studio/blender-studio-tools
13
32
Fork 19
Code Issues 21 Pull Requests 4 Projects Releases 1 Activity

Blender Kitsu - Executing Create Playblast for Asset type results in Traceback Error #289

New Issue
Closed
opened 2024-05-03 11:43:09 +02:00 by Pete Draper · 5 comments
Pete Draper commented 2024-05-03 11:43:09 +02:00
Copy Link

Note: this does not occur with Shots. Have not tested with Sequence or Edit.

Login is ok, performed playblast for Shot, fine. Switched to Asset type and selected correct Episode, Asset Type, Asset and Task Type. Set the version number and enabled Create Playblast.

Any of the resulting options in the Create Playblast results in an error.

Note2: Instead of outputting an MP4 for assets, stills are preferable - please add that option instead of producing a full mp4 sequence.

Resulting error on clicking OK:

Python: Traceback (most recent call last):
  File "/Users/petedraper/Library/Application Support/Blender/4.1/scripts/addons/blender_kitsu/playblast/ops.py", line 184, in execute
    self._get_kitsu_task(context)
  File "/Users/petedraper/Library/Application Support/Blender/4.1/scripts/addons/blender_kitsu/playblast/ops.py", line 131, in _get_kitsu_task
    self._task = Task.by_name(self._entity, self._task_type)
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/petedraper/Library/Application Support/Blender/4.1/scripts/addons/blender_kitsu/types.py", line 916, in by_name
    task_dict = gazu.task.get_task_by_name(asset_shotdict, task_type_dict, name)
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/petedraper/Library/Application Support/Blender/4.1/scripts/addons/blender_kitsu/wheels/gazu-0.9.4-py2.py3-none-any.whl/gazu/cache.py", line 197, in wrapper
  File "/Users/petedraper/Library/Application Support/Blender/4.1/scripts/addons/blender_kitsu/wheels/gazu-0.9.4-py2.py3-none-any.whl/gazu/cache.py", line 91, in insert_value
  File "/Users/petedraper/Library/Application Support/Blender/4.1/scripts/addons/blender_kitsu/wheels/gazu-0.9.4-py2.py3-none-any.whl/gazu/task.py", line 388, in get_task_by_name
  File "/Users/petedraper/Library/Application Support/Blender/4.1/scripts/addons/blender_kitsu/wheels/gazu-0.9.4-py2.py3-none-any.whl/gazu/client.py", line 350, in fetch_first
  File "/Users/petedraper/Library/Application Support/Blender/4.1/scripts/addons/blender_kitsu/wheels/gazu-0.9.4-py2.py3-none-any.whl/gazu/client.py", line 206, in get
  File "/Users/petedraper/Library/Application Support/Blender/4.1/scripts/addons/blender_kitsu/wheels/gazu-0.9.4-py2.py3-none-any.whl/gazu/client.py", line 326, in check_status
gazu.exception.ServerErrorException: data/tasks?name=main&task_type_id=b4abf452-ca48-4175-9089-f506f8d5fee8&entity_id=
Note: this does not occur with Shots. Have not tested with Sequence or Edit. Login is ok, performed playblast for Shot, fine. Switched to Asset type and selected correct Episode, Asset Type, Asset and Task Type. Set the version number and enabled Create Playblast. Any of the resulting options in the Create Playblast results in an error. Note2: Instead of outputting an MP4 for assets, stills are preferable - please add that option instead of producing a full mp4 sequence. Resulting error on clicking OK: ```bash Python: Traceback (most recent call last): File "/Users/petedraper/Library/Application Support/Blender/4.1/scripts/addons/blender_kitsu/playblast/ops.py", line 184, in execute self._get_kitsu_task(context) File "/Users/petedraper/Library/Application Support/Blender/4.1/scripts/addons/blender_kitsu/playblast/ops.py", line 131, in _get_kitsu_task self._task = Task.by_name(self._entity, self._task_type) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/Users/petedraper/Library/Application Support/Blender/4.1/scripts/addons/blender_kitsu/types.py", line 916, in by_name task_dict = gazu.task.get_task_by_name(asset_shotdict, task_type_dict, name) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/Users/petedraper/Library/Application Support/Blender/4.1/scripts/addons/blender_kitsu/wheels/gazu-0.9.4-py2.py3-none-any.whl/gazu/cache.py", line 197, in wrapper File "/Users/petedraper/Library/Application Support/Blender/4.1/scripts/addons/blender_kitsu/wheels/gazu-0.9.4-py2.py3-none-any.whl/gazu/cache.py", line 91, in insert_value File "/Users/petedraper/Library/Application Support/Blender/4.1/scripts/addons/blender_kitsu/wheels/gazu-0.9.4-py2.py3-none-any.whl/gazu/task.py", line 388, in get_task_by_name File "/Users/petedraper/Library/Application Support/Blender/4.1/scripts/addons/blender_kitsu/wheels/gazu-0.9.4-py2.py3-none-any.whl/gazu/client.py", line 350, in fetch_first File "/Users/petedraper/Library/Application Support/Blender/4.1/scripts/addons/blender_kitsu/wheels/gazu-0.9.4-py2.py3-none-any.whl/gazu/client.py", line 206, in get File "/Users/petedraper/Library/Application Support/Blender/4.1/scripts/addons/blender_kitsu/wheels/gazu-0.9.4-py2.py3-none-any.whl/gazu/client.py", line 326, in check_status gazu.exception.ServerErrorException: data/tasks?name=main&task_type_id=b4abf452-ca48-4175-9089-f506f8d5fee8&entity_id= ```
Pete Draper commented 2024-05-03 11:45:45 +02:00
Author
Copy Link

Additionally, having the ability to disable the stamps would be useful. I've disabled them in the script but having the ability to control what is baked in would be very useful.

Additionally, having the ability to disable the stamps would be useful. I've disabled them in the script but having the ability to control what is baked in would be very useful.
Nick Alberelli commented 2024-05-06 17:06:25 +02:00
Member
Copy Link

@PeteDraper
I will look into this issue.

Note2: Instead of outputting an MP4 for assets, stills are preferable - please add that option instead of producing a full mp4 sequence.

What do you mean by this?

Additionally, having the ability to disable the stamps would be useful. I've disabled them in the script but having the ability to control what is baked in would be very useful.

This could be a useful feature, we did earlier just rely on the Blend file to control what metadata is stamped but this was not a good solution for the studio. I would consider making that an option in the preferences, but that should be opened as a seperate issue.

@PeteDraper I will look into this issue. > Note2: Instead of outputting an MP4 for assets, stills are preferable - please add that option instead of producing a full mp4 sequence. What do you mean by this? > Additionally, having the ability to disable the stamps would be useful. I've disabled them in the script but having the ability to control what is baked in would be very useful. This could be a useful feature, we did earlier just rely on the Blend file to control what metadata is stamped but this was not a good solution for the studio. I would consider making that an option in the preferences, but that should be opened as a seperate issue.
Nick Alberelli added the
Kind
Bug
Kind: Community
 labels 2024-05-06 17:06:36 +02:00
Pete Draper commented 2024-05-06 17:17:20 +02:00
Author
Copy Link

@PeteDraper
I will look into this issue.

Note2: Instead of outputting an MP4 for assets, stills are preferable - please add that option instead of producing a full mp4 sequence.

What do you mean by this?

currently, when publishing to an Asset type, which is normally model, texture, shading etc, a single frame is sufficient instead of a sequence render / playblast which is at present the only option. Having a single frame grab would be useful.

Additionally, having the ability to disable the stamps would be useful. I've disabled them in the script but having the ability to control what is baked in would be very useful.

This could be a useful feature, we did earlier just rely on the Blend file to control what metadata is stamped but this was not a good solution for the studio. I would consider making that an option in the preferences, but that should be opened as a seperate issue.

ok sure - I've purposefully disabled the overlays by default as we have separate watermarking here which is custom to our pipeline; kitsu holds all of the versions but also triggers external scripts to watermark for client exposure which are then exposed within kitsu itself in a separate task

> @PeteDraper > I will look into this issue. > > > Note2: Instead of outputting an MP4 for assets, stills are preferable - please add that option instead of producing a full mp4 sequence. > > What do you mean by this? currently, when publishing to an Asset type, which is normally model, texture, shading etc, a single frame is sufficient instead of a sequence render / playblast which is at present the only option. Having a single frame grab would be useful. > > > Additionally, having the ability to disable the stamps would be useful. I've disabled them in the script but having the ability to control what is baked in would be very useful. > > This could be a useful feature, we did earlier just rely on the Blend file to control what metadata is stamped but this was not a good solution for the studio. I would consider making that an option in the preferences, but that should be opened as a seperate issue. ok sure - I've purposefully disabled the overlays by default as we have separate watermarking here which is custom to our pipeline; kitsu holds all of the versions but also triggers external scripts to watermark for client exposure which are then exposed within kitsu itself in a separate task
Pete Draper commented 2024-05-06 17:58:04 +02:00
Author
Copy Link

ok don't know why it was closed... my bad

ok don't know why it was closed... my bad
Nick Alberelli commented 2024-05-08 19:30:03 +02:00
Member
Copy Link

I will look into the Asset Playblast issue

The other issue you pointed out related to metadata burn ins I am tracking in a seperate issue studio/blender-studio-pipeline#295 which I have closed with a recent commit b16e44df98

I will look into the Asset Playblast issue The other issue you pointed out related to metadata burn ins I am tracking in a seperate issue https://projects.blender.org/studio/blender-studio-pipeline/issues/295 which I have closed with a recent commit https://projects.blender.org/studio/blender-studio-pipeline/commit/b16e44df98e0c5d70f748bf6ad79d1969563939b
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
Kind
Breaking
Breaking change that won't be backward compatible

  
Kind
Bug
Something is not working

  
Kind: Community

Issues opened by members of the community / outside the studio

  
Kind
Documentation
Documentation changes

  
Kind
Easy
Simple to complete

  
Kind
Enhancement
Improve existing functionality

  
Kind
Feature
New functionality

  
Kind
Proposal
A proposal or idea that requires feedback

  
Kind
Security
This is security issue

  
Kind
Studio Request
Requested by a user at the Blender-Studio

  
Kind
Testing
Issue or pull request related to testing

  
Priority
Critical
The priority is critical

  
Priority
High
The priority is high

  
Priority
Low
The priority is low

  
Priority
Medium
The priority is medium

  
Reviewed
Confirmed
Issue has been confirmed

  
Reviewed
Duplicate
This issue or pull request already exists

  
Reviewed
Invalid
Invalid issue

  
Reviewed
Won't Fix
This issue won't be fixed

  
Status
Abandoned
Somebody has started to work on this but abandoned work

  
Status
Blocked
Something is blocking this issue or pull request

  
Status
Need More Info
Feedback is required to reproduce issue or to continue work

No Label
Kind
Breaking
Kind
Bug
Kind: Community
Kind
Documentation
Kind
Easy
Kind
Enhancement
Kind
Feature
Kind
Proposal
Kind
Security
Kind
Studio Request
Kind
Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: studio/blender-studio-tools#289
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?