Switching Cameras in existing Selectors

[russellaugust]

Anyone have any success switching cameras on a Selector in an existing AAF? I'm baffled by it using "Selected" and "Alternates" as the system, as opposed to what .avb files do with selector.selected = index_of_selected_clip. It makes me think it's there someplace and I'm overlooking it.

There is:
<aaf2.misc.TaggedValue _AAF_SELECTED = 0 at 0x105d948b0>

Which does correctly point to the selected track but it doesn't appear to change anything when modified.

Would love to hear from anyone who might've solved this. Was hoping that this might've led to some success @XDeschuyteneer.

[russellaugust]

Curious if anyone else has anything to add to this:

I’ve found that I need to physically move elements between SELECTED and ALTERNATES. This can change the camera order in the timeline (e.g., A, B, C might switch to A, C, B when switching to next camera). To handle this, I created a function that pops the source from ALTERNATES, replaces it with SELECTED, and adds SELECTED to ALTERNATES to emulate a camera switch.

However I’m struggling to retrieve the selector/group names and the Name of the contents. Is there a simpler way to get this information, e.g. a get_mob() convenience function? Seems like it should be easier to discover the simple display name of the asset.