Premiere Pro CC and Canon MXF problems

[Michael Williams]

I’m curious about a possible workaround. I’ve never used Prelude before, but if I was able to ingest the spanned clips into Prelude with the correct timecode, how would I move those new versions of the clips from Prelude to Premiere?

thanks again,

Mike

[Kevin Francis]

Have you tried a new CC project and importing the files into it instead of the CS6 upgraded project? Also, we find it works best to transcode to ProRes if you’re doing a major edit- a little more hassle on the front end (not much!) but way easier during and after the edit.

[Paul Neumann]

Mark and ingest your clips in Prelude, highlight, right click, send to PPRo.

If you have a project open they will land in the Project bin. If you don’t it will create a project to the clips specs and put them there.

[Michael Williams]

I think this is my way forward. I just brought all of the spanned clips into prelude and it seems that they have the correct timecode. So now I should be able to replace those sections in my original project and move forward from there.

Still not sure what happened, but at least I can move on with the project from here.

thanks for all your help.

mike

Michael V. Williams
producer/editor
http://www.vernonvision.com

[Michael Williams]

yes, I tried that and it didn’t help. perhaps I will go back to my old process of transcoding pre-edit in the future.

thanks,

mike

[Tim Kolb]

[Michael Williams] “perhaps I will go back to my old process of transcoding pre-edit in the future.”

I can certainly understand that sentiment, though something is definitely wonky in this scenario (not implying it’s your fault, just that this isn’t really a common issue)…

If you start a new CC project and use the Media Browser to import a file you know is one of the oddly behaving spanned clips, what happens then?

TimK,
Director, Consultant
Kolb Productions,

Adobe Certified Instructor

[Frank Tourv]

I have resolved the c300 problem(and i had plenty of stuff shot with it), by deleting the .xml,.cif,.sif and occasional .cpf of every folder. I use the finder and delete them in bunch(and dont forget to empty trash),only leaving the .mxf. Note that once you have done that, you need to create a new project, clean the media cache and then re-import every c300 files. So far that handled it completely.

[Michael Williams]

Interesting, Frank.

pardon my ignorance of the format, but if we delete all of those files (which I always assumed were for metadata) to make it work correctly, then why are they created in the first place?

thanks for the info.

Mike

[Frank Tourv]

the metadata is there for the Canon XF utility app and the c300 itself which is somewhat useful for viewing clips and transferring, but i find it more useful to do an all adobe workflow using Prelude to get data off the cf card to two separate harddrives simultaniously and previewing my footage. After that, i send my stuff to premiere(you can also skip the prelude part and just drag and drop your stuff through finder also).

Note that deleting these will unable final cut X from importing these MXFs using the canon XF plugin for fcpX. In a weird way, fcpX needs the metadata, while premiere doesnt want it. This is a flaw from adobe only related to the canon c100/300/500 – dslrs dont cause this problems, so does XMLs from Sony cameras.

[Michael Williams]

Interesting. I think I will try your approach with prelude on my next project with the Canon xf files.

Thanks, Frank.

mike