Blender Kitsu: Improve Thumbnail Workflow for Sequences #21
Labels
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
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: studio/blender-studio-tools#21
Loading…
Reference in New Issue
Block a user
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?
Issue
When working on a sequence in a Kitsu project, the thumbnail is always rendered in Blender from the first frame of the Sequence or Shot.
Feedback
Thumbnail: have a script to make it possible and easy to choose another frame than the 1st to upload as a thumbnail (Beau)
Can we use current position of time cursor to set time point thumbnail? (in the case when playblast is generated from single strip)
[Blender_Kitsu] Improve Thumbnail Workflow for Sequencesto Blender_Kitsu: Improve Thumbnail Workflow for SequencesBlender_Kitsu: Improve Thumbnail Workflow for Sequencesto Blender Kitsu: Improve Thumbnail Workflow for SequencesOk after some investiagtion I think the best solution to this is to upload two revisions, one image with the desired thumbnail then a second with the intended playblast.
Need to check with @fsiddi if this is acceptable, confirming with the CGWire team if there isn't a better way. WIll follow up on this soon.
Got some feedback from the guys at CG Wire, they have a better method of doing this, so we dont need to do this double revision workaround. Newer versions of kitsu will come with a use current frame option when setting the thumbnail.
The change exists in the Kitsu code but cannot be accessed via gazu at this time. We need to contribute changes to GAZU to support this change before we can implement the change on the addon side.
Here is the relevant code:
063cd9ec3e
https://github.com/cgwire/kitsu/blob/master/src/store/api/tasks.js#L180-L186
Opened a PR with the above change https://github.com/cgwire/gazu/pull/289
I have loaded the GAZU module changes into our blender kitsu addon, and implemented this feature in the following PR
studio/blender-studio-pipeline#77
Closed by: studio/blender-studio-pipeline#77