Gibran, I've always bought my XF300 footage in directly, and never use XF Utility. I move the entire directory into a named folder, search that folder for .MXF files, and move them out of their individual folders into the main folder. This has always worked for me. I just can't think why I would need the original file structure, but I keep those folders so I can rebuild if I ever need to. This has never given me the slightest problem in PP CS6 running on a Windows 7 PC, and originally also worked fine with After Effects. AE suddenly stopped accepting those MXF files a couple of months ago, and won't play previous projects that used MXF files. I thought the MXF issue was only with After Effects.
Trevor, I was only going on the numerous threads posted on this forum which listed errors with MXF files. True, alot of them were from last year but it's the first thing that jumped out at me when I went online to look for more information. I agree with you in one sense- I've had the same results whether I imported directly or through using Canon XF Utility. However, the footage works fine in that program and even works okay in Prelude.
It's this weird scrambling which is the confusing and annoying part...
I import from my Canon XF's via the media browser without problems into CS6 (6.03). Before 6.02 I had the "shearing" issue on my files, but for a long time, I have had no problems at all, and I have never seen what you experience - sorry.
UPDATE: Problem mysteriously solved....
I opened up an old project that didn't contain any MXF files while speaking to a technical support team member, and when I re-opened my latest project, the files were magically fixed. No clue why. I changed no settings and didn't import the footage in any different way.
The technical support member wasn't sure why either but suggested it may have been a display issue, and that it was best to ensure I had the latest drivers installed. Sound advice but a bit confusing as to why the errors occurred and why they went away!? A display issue makes sense but I made no settings changes at all, so confused as to how it fixed itself.
Anyhoo, back to the simple task of editing it!