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?
If this is the root of our problems, my following question would be:
For those "mismatched folders": Can I rename the enclosing folders to match the files they contain without screwing up my project? It would be something I would want to try out. Unfortunately I haven't delved into relinking media quite yet, but maybe someone else has? Ideally I would like to make a copy of the Media, correct the folder names, and relink the project.
Maybe someone can give me a hint if this is at all possible and roughly how to do this.
In my case the folders/files match, so this wasn't what is causing the error for me (and they played fine in 5.5.2). I have tried importing the .mp4's individually and by importing the whole BPAV folder into Premiere and all caused the same problem. Thanks for your efforts investigating this.
First of all, thank you for the additional information.
Renaming the folders should not screw up anything with your Project. You will likely need to relink the media, folder by folder that was changed, when you reopen the Project, though. Before you reopen the Project with renamed/matching folders names, I would also recommend that you delete your Media Cache (on Mac: Users/<your user name>/Library/Application Support/Adobe/Common/Media Cache & Media Cache Files folders. After deleting the Media Caches, then open the Project, relink files.
Thank you, Gerry. That is good to have confirmed. Sounds like there are a few cases to reproduce this issue. Based upon my initial findings, I do have an issue logged for dev engineering to look at. I will also continue to add all of your additional information. All of your help is greatly appreciated!
Ok, will try this. I think I have Media Caches on a different drive, but I'll find them and get rid of them.
I have to make one important correction:
This particular folder I received on a harddisk from the cameraman. He had left the camera running on a couple of occasions and deleted some long-ish files himself. I can see from the mediaprofile xml file (MEDIAPRO.XML in the root) that there were quite a couple of takes that were deleted. So that folder has been messed with. Though it worked in 5.5 as it was...
I do have another folder that I personally copied from a camera flash as I said, will do some tests with that now.
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
He he, I was thinking the same thing and have been running some tests for the past few hours. I used some known problematic files, transcoded to OP1a and H.264 via Prelude and so far the transcoded files did not appear to have the same tearing issues. Now, don't take this as gospel, but it may be a workaround option for some of you. I'll run some more tests tomorrow. Thanks for the feedback.
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?
Well, still good to know, Carl - great you found out saved others some time.
If you have the Canon XF-xxx, the newest XF-utility (1.2) offers to join spanned clips into one large MXF fie that is easier to transcode in CS5.5 AME f.ex.
Don't know about Sony though, but I think they have a simmiar utility.
I think I'll go that route until now just to be sure - glad I still have a PC with 5.5 installed :)
Hope for a fix soon
I have used the Canon XF utility to join the clips and they play fine in 3rd party players like media player, VLC player and even the source monitor. But in the edit the tears are still there? I would upload a raw section but each clip is 2 GIG in length 8(.
is there any light at the abobe factory?
Using the latest drivers for everthing and machine is fast enough?
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.
FYI to Adobe folks… Hope this helps you guys narrow down the problem. I’ve
had no issues with XDCAM EX .mp4 footage from a JVC GY-HM700u on a PC. I
can test footage from that camera on a Mac this week if needed.
From: UlfLaursen email@example.com
Sent: Monday, June 04, 2012 9:51 AM
Subject: Re: Problems with XDCAM EX Footage Problems with XDCAM EX Footage
Re: Problems with XDCAM EX Footage
created by UlfLaursen <http://forums.adobe.com/people/UlfLaursen> in *Premiere
Pro CS5, CS5.5, & CS6* - View the full
One mroe request to anyone that wants to help track this:
Try changing your Paused Resolution and Playback Resolution (should default to 1/2 at playback and 'Full' at paused with a sequence to match a 1080p 24 XDCAM EX file) and let us know if that has any effect on what you see.
I switched back to the default settings from full/full and noticed that when I was one frame ahead of the "split" screen and moved back one frame it appears normal for a moment, then the split comes up again.
So, what's happening for you is that playback rendering is correct but paused rendering is not, right? That's the opposite of what I just saw, so it isn't apparent that one or the other is broken. Still it may be a potential workwrounf for some of you to jsut set your playback res from 1/2 to fulll... that fixed the problem on my system. I have no new info on the export portion of the OP's problem at this time.
Both playback and paused are rendering are incorrect. I'm not really sure if I can explain it better than I did in my previous post. I can PM my phone number if you want me to explain it better,
Please check your footage! I have notice in the multicam edit when I cut to the camera (MXF CanonXF300) the first two frames on some clips are the same causing a verry brif pause.. ergo frame 1 and 2 are identical. If this was 25p I could understand this but as its interlaced it poses a funny question?
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.
I just had another go at a 1:30 hr. long XF clip. I edited for arround 15 min. into it, and suddenly there was heavy tearing in the source monitor for ½ min or so. I rewinded and paused for 10-15 sec. and in the same place there was only one left. Don't know if this mean anything, but before it came, I had heavy JKL activity joggling back and forth through the clip.
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.
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.
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).
Having the same issue after uppgrading to 6.0.1 with my C300 files (.MXF). Not at all good when on a deadline...
Visual issues included in the rendered result. There also seems to be some kind of color error, look at the screen capture of her face.
I'm on a iMac, Mac Intel , OSX 10.6.8. 16 Gb RAM, ATI Radeon HD 4850
Contact me at: firstname.lastname@example.org if more info/files/captures are needed.
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.
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.
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?
Sorry, no expert, Roddy, but could you not use the utility (sony or canon) to create the MXF files (like other users have posted above) and then replace the footage with these "correct" files, without having to reedit everything? Just a thought - maybe someone ese can clear it up, if it's possible at all
Europe, Middle East and Africa