[Chris Chandler]

I know this is pretty dead by now, but FYI in case someone comes across this in a search like I did…

You can map the “multiclip angle” command listed above to whatever your normal match-frame key is. It’ll match-multiclip for those, and it will function like a normal match-frame on non-multicam clips. No need to map it to an additional key

[Chris Chandler]

Thanks for the suggestion. I’m onto a different job now so I’m unable to do any more trial and error with the source media. I’ll pass your suggestion along, though, and see if the editor wants to try it. I think he’s resigned to losing that one clip and cutting his losses because we were able to recover other material that was high priority.

thanks

[Chris Chandler]

Unfortunately it has already been copied to a drive. I went in today to troubleshoot some other clip issues (different problems all together), but was unable to solve this one.

To attempt the ‘media restore,’ I copied the BPAV folder onto a freshly formatted card, and then put it into the camera. I’ve done that for other issues and it has worked, and you can access all the clips in the camera in media mode, just like a freshly shot card.

All other card volumes on the drive, as well as the cards that still had data on them and had not been reformatted, operate fine in Clip Browser (and everything else, for that matter)

[Chris Chandler]

I assume you figured out a solution for your hang-up by now, but perhaps you will still get an email alert when I post this–

You describe importing XDCAM EX footage from AMA at 15:1, editing with that imported footage, and then being able to re-link your sequence back to the original AMA footage. Can you tell me how you did that?? I’m running into issues trying to figure out a proper workflow for a feature doc, and the ability to link BACK to original AMA virtual volumes is the missing link, which I can’t figure out for the life of me.

thanks

[Chris Chandler]

Did more trial and error testing, and this is where I’m still at:

The best I’ve determined is that AMA solves the issue of logging in the field without having to create new media wonderfully, but then getting to the next step of creating a safe Avid-native offline/online workflow is where I’m stuck. Would we be backed into working AMA the entire way up to consolidation/transcoding a rough cut? After transcoding from AMA to the Avid media drive, if that drive goes kaput, can you rebuild the project from the source material? It seems like with XDCAM that’s easy to do, but not with unwrapped XDCAM EX source material.

Any recommendations?

[Chris Chandler]

Perfect. Thanks Michael

[Chris Chandler]

Perfect. Slowly but surely, scripting is starting to make a tiny bit of sense. Thanks a lot

[Chris Chandler]

Thanks, Mike and Dan. Using the link that Mike sent, I changed my expression so that it rolls more realistically, but I can’t find on that site where he uses keyframes to define the rotation at a given point. I think that method would be ideal if someone can’t point me to how I might do that (right now, any keyframes I try and tack on to rotation are overridden by the expression).

Dan: perhaps an offset would work? Here’s where I’m at right now, my expression is:

distance=position[0];
circumference=width*Math.PI;
distance/circumference*360;

The end point that I need to reach is that at position 543.5, 240.5, rotation must equal 0. Right now, with the above expression, the rotation at that position is 4x +8.4

The most user-friendly method possible to achieve that result would be awesome haha. I’m more familiar with keyframing from editing than I am writing script