I have been using canon mxf (xf100) ever since cs6 and no problem.
I ingest and convert the files to single mxf files with the Canon XF Utility. (i find the folder structure a pain).
Dont use the Media Browser to ingest, just the project window.
Are you doing Multicam edits Ann? -
I see that on these forums you have been a big promoter of the MXF file format.
Can you provide a link for a description for the Canon Utility app for your conversion?
I made this video regarding the problem with MXF decode errors in Multicam Sequences in PP CC2015 - this was to describe the process for our needs internally in editing. Our Canon XF 305 are the only culprits that make this read error- our C100 does not seem have the issue with its MXF files. This tutorial describes the issue and goes through the Canon XF utility Software. If it helps anyone great - we still have not tested this process fully and can not say if this XF Utility software is the fix for the MXF read errors in PPCC2015.I could not take old media and make virtual footage - anyone with a solution here would be fantastic.
Ideally i wish either Canon would make a plug in for Premiere or vice versa. -
For your problem files why dont you try render and replace with dnxhd. See if that will help.
We have been rendering each video back in CS6 to .mov -that works - as stated in the initial post - it is a waste of time - I would like the .MXF files to work right out of the camera- in the software - like it used to do in CS6.
Tell us more about your computer system, GPU, RAM, CPU, hard drives, media drive, etc. Your post doesn't indicate what you're working with. You must have enough throughput in order to handle 5 streams of Long GOP video plus system overhead.
Red frames, as I understand it, indicate "dropped frames," indicating that your system likely is not powerful enough for the footage that you are using. Using the dropped frames indicator, are you experiencing dropped frames? Have you tried lowering the playback resolution? If so, does that help?
Other than more powerful hardware, have you tried recording at a lower data rate? Would that be acceptable? It sounds like transcoding the footage takes too long, but that is another thing I'd definitely suggest in your case.
We chatted about red-frames back with the update to CC2014. The initial release of cc2014 had no Red Frames - then I updated and started to see them lots. This new MXF read error has continued into CC2015. They look like this:
And populate fast:
Here are my system specs from my profile - I should have more that enough "juice" to run this:
I am waiting for cc2016 before I upgrade to El Capitan. To many projects on the go.
Internal drive is a SSD for my software - I run a new Mac pro ( Late 2013)- Keep my footage on the local server with a direct ethernet connection- and use a SSD for my Project files and cache connected via USB3.
I made this video tut to explore the problem with other staff here - take a look if you want- Any input you have would be of great value to me. Thank you for your time.
Ooops - we are recording at 35 Mbps at 60i to these Canon XF 305 Cameras.
This has been the process since CS6 - which handled these 5 cam multi-cam sequences just fine.
As I stated - CC did okay and CC2014 until the first update- its been read errors with the MXF files -very often since then.
Sometimes its not even a 5 cam multi-cam sequence- I can get these MXF read errors off a single cam sequence sometimes.
Sorry for your continuing issues. BTW, red frames don't mean dropped frames. They mean "bad" frames, or frames that cannot be used in decoding. We have been working diligently in reducing the occurrence of these from appearing.
I spoke with my colleagues in support this morning and brought up your case. Here's the advice.
- It appears that this may be a bug in the 9.1 version.
- Make sure that you are updated to 9.2.
- Here's how to tell which version you are using: FAQ: How to find which version of Premiere Pro you are running
- After you are updated, shut down Premiere Pro.
- Delete the Media Cache, and the Media Cache Folder: FAQ: How to clean (delete or trash) media cache files?
- Restart Premiere Pro.
Let us know if this improves your situation.
Was media cache deleted with Premiere Pro closed? Did you test a new project?
This issue is happening in all four of the editing stations with the same computer specs here.
This happens with anyone who attempts editing with these Canon.MXF files in many projects.
We have all updated to CC2015.2 and we delete our caches when we begin new projects and archive past ones.
(we delete our caches often) - and we turn our systems off a few times a week. So- we also tested this issue thoroughly, with hopes, at the new 2015.2 update.
Let it be know to you this:
The MXF files are written in segments/clips.
They all appear in the timeline as one clip in CC2015-
Where as in CS6, they appeared as they are written - in segmented clips.
We have no read error issues within CS6.
We never have a read error in the duration of the first clip of the .MXF in CC2015- It is always further down the timeline.
We feel that exporting these .MXF as one clip via the Canon XF Utility software could help in the future. But we are stuck with .MXF footage that wont read in Premiere CC as the Canon-Index-files are gone and we can not create the "Virtual Media" as described in the video link I posted. As a result we transcode this footage at every possible moment and juggle archiving with all of this "digital real estate" being used. I hope that your team can fix the issue for the next release.