Hi Trent,

Uploaded sample file and sample project.

While copying files, purely by coincidence, I noticed something strange about the directory structure: For some files, the MP4 filename doesn't correspond to the containing folder name. Usually this is the case, but sometimes not.

So in most folders things look like this:

But sometimes this happens:

This was copied directly off of a flashcard from the camera. For the file that almost always gave me trouble (200_0040_01) the names were ok, and this file alone in a sequence is ok, but once it is edited together with a file whose folder name doesn't match, there is trouble.

Can people with this problem please check if they also have this kind of "mismatch" in their camera file structure?

Thanks,

Carl.

Ok, tested with an original, "clean" folder structure, all cachefiles and folders deleted. Started with a brand new project, imported whole folder, ignored the "a lot of files not recognised" message. Made a sequence by dragging a clip onto "new item" icon. Set some in and out points on a couple of clips in icon view (cool feature BTW), automated to sequence. No improvement.

So unfortunately the problem persists...

And I was almost getting excited about at least a possible workaround

Do you think that a temp workarround could be to use prelude to ingest and transcode to another codec in the same process, f.ex. DNxHD, or would it be safer to transcode outside CS6

Thanks

Ulf

Unfortunately I have to spoil this party

Just used Prelude to transcode problematic footage to XDCAMHD422 in OP1a MXF container. Unfortunately still tears, also in the transcoded files that were sent to Premiere.

Back to compressor?

As far as I know several people (incl. myself) have uploaded footage to Adobe, and I beleive they are working on it. I think the only workarround in the meantime would be to edit in 5.5 or use AME inside CS5.5 to transcode for use in CS6.

Ulf

Agreed stiil showing tears with XF300 footage and even if not seeing a tear, when you render it out theres definatly a tear.

Hi James,

Did some further tests with your suggestions. My observations are:

I tried switching the playback res to 1/2, and on one occasion the problem disappeard TEMPORARILY, but came back. This happened once, I could not reproduce it. Also sometimes when switching back to full playback res, the problem disappeared briefly but returned on other frames of the same clip.

The only constant things I can find is that:

1. The tearing almost always occurs in the same clips, often in different places, but always in certain clips.

2. When the application is just started, playback is clean. There is something that triggers the problem, can't figure out quite what, sometimes it seems scrubbing or playing other clips or some combination.

3. As soon as a "tear" happens in a frame, it stays there, always in the same frame, on the same place in the frame, at every playback, until the application is restarted.

Testing with CUDA GPU accelleration enabled and external monitoring (Blackmagic) enabled.

Well, I just worked through my own workarround, with one PC with AME 5.5 on and a watchfolder setup, where my XF footage goes, and the output folder shared with my CS6 PC.

I convert to XDCAM HD OP1a MXF files. I find the files much more responsive in CS6 while scrubbing and navigating throughout the timeline, and I find the preview at ½ resolution much better than the org. files on the same setup.

/Ulf

Actualle, Trent, often while scrubbing the "tearing original" MXF files on the timeline with my shuttle device, it is as if frames are mixing in the very beginningvof a "scrub" where the frst few seconds seems to be from te start of the clip allthough I am f.ex. 4-5 min inside it.

After the few seconds of "wrong" footage it goes back to the correct place in the clip.

Could it be some kind of indexing problem, perhaps.

Ulf

Its good to hear your seeing what we are seeing, good luck in finding a solution soon I have aproject on the time line ready for finaling witha disgruntled client. I have explained the situation and also the fact its being looked at, fingers crossed theres a patch/fix for the issue soon 8).

Roddy

Thanks everyone for your feedback. It's pretty elusive and seemingly random, but we're still looking at it. keep the cooments coming as you find new info.

James,

It seems to work with files from Canon EOS C300 if one use the free Canon XF Utility and export each card to .MXF files. Importing a folder full of .MXF files works while the very same footage in it's un-touched folder gives the issue reported by other users. It seems like there is someting in the original folder/file structure that "offends" the importer in some way.

When exporting to .MXF with Canon XF Utility you end up with a folder full of the original .MXF files and no other files such as meta data files, etc.

Canon XF Utility: http://usa.canon.com/cusa/professional/products/professional_cameras/c inema_eos_cameras/eos_c300?selectedName=DriversAndSoftware

/Roger

Roger and I worked with this issue on an end user basis today and this way works great for me in CS 6.0.0 (reinstalled the suite in hope of a solution and this made the bug appear in CS 6.0.0 also). The files are running without any visual errors, I've checked 138 C300 files to get to this conclusion.

Trying to import the same files from it's native folder including other files gives visual errors. Only tried .MXF-files.

Any news yet from the adobe team? I ask as my trial 30 days is coming to an end with project still on the timeline with tears.

The main reason for myself trilaing the software released as working and on sale was to test the multicam beyond 4 cameras. I would have expected this to be all ok apart from this unusual tearing bug which has reared its ugly head.

If there isnt a solution within roughly 7 days I have to redit the whole thing back in CS5.5 without 3 cameras. Thats 6 x 2hr shows to completely start again from scratch. I would be very greatful for any updates and will happily contribute where possible. Can the trial period be extended at least to a solution as im sure I wont be Purchasing the production premium cs6 until this is fixed?

Roddy