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

How to definitively determine any Bin Item's start TC? #25

Open
communque opened this issue Nov 10, 2023 · 4 comments
Open

How to definitively determine any Bin Item's start TC? #25

communque opened this issue Nov 10, 2023 · 4 comments

Comments

@communque
Copy link

What I'm looking to achieve is the PyAvb equivalent of being on Avid, executing the "Find Bin" command (i.e. reveal bin item), and reading what's in the Start column.

In PyAvb that's proving challenging, requiring different approaches depending how the clip was generated.

For instance a drag-and-drop imported master clip requires an elaborate iteration of components to get the component of the component of the component that "knows" the start frame.
Meanwhile a drag-and-drop imported .png file with alpha channel, although similar, requres a nuance to the above
Meanwhile an ALE-generated master clip imported to Avid by way of drag and dropping a media files databases has the bin info available immediately without much complication.

Gleaning all this through trial and error. Wondering if anyone is aware of a single reliable way to get any source clip's start TC.

@mjiggidy
Copy link

mjiggidy commented Nov 10, 2023

I think there's no way around a bit of "elaborate iteration" (I like that term!), although I'm sure Media Composer must have a faster way.

My method has been to write a recursive method that mimics Avid's "Matchback" function, first to get to the original masterclip, and then dig deeper to get to the SourceMob to get the tape/file and start timecode info.

I have limited resources to test, since for "real world" examples I only have the show that I'm working on at that time as an AE, but the technique I mentioned has been working in most cases for me so far (dailies from a lab, "hard imported" things, UME-linked things).

It might be helpful to enable the wiki on this repo so we can more easily share tips and tricks?

@communque
Copy link
Author

RE "recursive method" -- hah, you too. Was hoping there was a method "getStartTcNoMatterWhat()" that I'd somehow overlooked.
So far I've been able to handle drag-imported master clips, drag-imported png files, and the ALE-generated files mentioned above.
But for an AMA-linked ProRes file no luck whatsoever.

@communque
Copy link
Author

@mjiggidy How about group clips?

@mjiggidy
Copy link

mjiggidy commented Nov 28, 2023

@mjiggidy How about group clips?

Group clips you can treat like subclips with the addition of a "selected track" index. So I just do the usual matchback process on the selected track to eventually get to the selected masterclip and derive the info I need. (As far as I know, a Group Clip doesn't have its own timecode or source mob, it just adopts from whichever source is selected at the time, I believe?)

I'm most certainly not an expert on this topic, but that's what has generally been working for me so far.

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

2 participants