This repository has been archived by the owner on Sep 20, 2024. It is now read-only.
Resolve: 17 compatibility issues and load image sequences #1422
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![create-issue-branch[bot]](https://avatars.githubusercontent.com/in/36017?s=60&v=4){kind=small}
|
![hound[bot]](https://avatars.githubusercontent.com/in/3598?s=60&v=4){kind=small}
| # activate resolve from openpype | ||
| avalon.install(bmdvr) | ||
|
|
||
| file_processing(path) |
|
|
||
|
|
||
| if __name__ == "__main__": | ||
| path = "C:/CODE/__openpype_projects/jtest03dev/shots/sq01/mainsq01sh030/publish/plate/plateMain/v006/jt3d_mainsq01sh030_plateMain_v006.0996.exr" |
jakubjezek001
changed the title
| dirname, file = os.path.split(fpath) | ||
| _name, ext = os.path.splitext(file) | ||
| print(dirname) | ||
| media_pool_items = media_storage.AddItemListToMediaPool(os.path.normpath(dirname)) |
| clip_property = media_pool_item.GetClipProperty() | ||
| clip_name = clip_property["File Name"] | ||
| _clip_property = media_pool_item.GetClipProperty | ||
| clip_name = _clip_property("File Name") |
There was a problem hiding this comment.
local variable 'clip_name' is assigned to but never used
There was a problem hiding this comment.
Unless there was an optimization in V17 you will generally get faster response if you cherry pick the property of interest right away instead of getting all clip properties: clip_property = media_pool_item.GetClipProperty('File name')
There was a problem hiding this comment.
Yes, I have found out that in v17 None is returned if the GetClipProperty is on an audio clip and it was breaking other processes. This way it was more safe and if it is even faster than great.
|
so after @IgorRidanovic recomendation I had managed to fix the image sequence loading back to timeline |
This was referenced Jun 1, 2021
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
closes #1421
But I have found other new bugs on our code appearing after upgrading Resolve to last version at the moment 17.
I should admit that those api changes are realy frightening. There is no mention about this.