Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

difference in "resolve_ref" between release 0.8.1 and 0.9.0 #29

Open
Liametc opened this issue Sep 12, 2016 · 4 comments
Open

difference in "resolve_ref" between release 0.8.1 and 0.9.0 #29

Liametc opened this issue Sep 12, 2016 · 4 comments

Comments

@Liametc
Copy link

Liametc commented Sep 12, 2016

Hey Mark

I'm currently reading source clip components from within a composition mob. Every time I encounter a SourceClip instance, we call "resolve_ref()" to get the Mob ID. We then use the Mob ID to find the essence in storage. In version 0.8.1, "resolve_ref()" used to return a SourceMob instance, whereas in 0.9.0 it returns a null object. Using the latest version, how can Idetermine the essence for clips within a composition mob?

ref = source_clip.resolve_ref()
name = ref.name
mob_id = ref.mobID

Thanks

@markreidvfx
Copy link
Owner

SourceClip.resolve_ref() can return None if it is a null reference.
what is the value source_clip.mob_id? Is it this?

urn:smpte:umid:00000000.00000000.00000000.00000000.00000000.00000000.00000000.00000000

@Liametc
Copy link
Author

Liametc commented Sep 13, 2016

Yeah it was. What does this signify?

@sanfx
Copy link

sanfx commented May 13, 2019

well in the version 2 of pyaaf its just not there in source_clip .

AttributeError: 'SourceClip' object has no attribute 'resolve_ref'

@markreidvfx
Copy link
Owner

to get the mob in pyaaf2 use SourceClip.mob

a null reference signifies, the end of the reference chain.
typically sourceclips reference other mobs this way

CompositionMob -> MasterMob -> FileMob -> PhysicalMob

the PhysicalMob would have a SourceClip with a null reference because it doesn't reference anything

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants