Multicam with canons on avid workflow support

[Brian Merlen]

Hey, so we are doing a multicam shoot probably using C100 and C300 (but maybe 5D) and as a Red mostly kind of guy I had a few questions... (Avid has me locked out of their forums but I am finally resolving the issue and called them so sorry for the non red specific questions, I have a pretty firm understanding of r3ds and Avid, just not so solid on the canon stuff)

1 Have any of you used the plugin that converts the C300 MXFs to avid MXFs? I can't find a tutorial online

2 Do you think dumping and transcoding from MTS (on the Canon C100) while dumping from the C300 is going to be manageable in a multicam situation? We have an SNS Evo hooked to several Avid bays so I can try and jump around, the bays are Z400s, no ssds, very little ram and not matched sets I would imagine, we get by here on shoestring budget cuz its web content/new media mostly. The Post Super would love if we can avoid AMA linking... Our last gig had C100 MTS files, C300 MXFs, and 5D, we AMA linked to them all but its killing our playback so we went to avoid that situation if we can. The C300 plugin should save me on that camera once I figure out the workflow but I am not sure how fast the MTS will convert to DNxHD, or how much we will roll and I have some files to test with now but just any advice in general would help. My other idea is tethering the C100 directly to Avid via a Kona Card or Black Magic card with HDMI to avoid the transcoding, but not sure if the DP will go for it.

Thanks guys, and appreciate your timely help if possible, shoot is tomorrow...

 

[Vincent Accardi]

Hi Brian,

was going to suggest just to AMA and transcode to your Avid UNITY/ISIS/Local storage (depending on what you're using). That seems to have always been the best way for me when not using RED.

 

[Brian Merlen]

We run an SNS Evo (basically an ISIS emulator) and are having problems. Lots of bugs, error messages, and crashing, we are going to update the software for Evo and Avids but so far the problems persist whether we ama link OR import the materials off the C100/C300. We got through our rough cuts even without stability and are going to try to update the above to see if it fixes the bugs. We never had problems like this tethering our red, or with r3d files. Is anyone else having issues with C100 and C300 on Evo? Thanks