On CS6 there are occational visual glitches that resembles DV drop out. A 1 hr spanned clip has audio going out of synch, audio length not matching video lenth.
Camera: Cannon XF100
Footage : 720p 60fps 35mbs
system Windows 7 Pro
premiere CS6.01
Core I7 930
16 GB ram
sysem drive: 128GB SSD
2 X 1TB media drives
GTX560
The same clips copied from the same flash card to a CS5 system plays without visual or audio glitches.
Core I7960
CS5.03
12GB ram
1tb media drive
gtx480
Any clue to why CS6 is having issues with the same footage CS5 is working beautifully with?
May be related to this? http://forums.adobe.com/thread/1004369?tstart=0
I also use the XF100 and have just about the same system setup as you (24GB RAM, Core i7 2600). I have not observed any video glitches, but it doesn't mean I don't have them. I just finished my first big shoot using two XF100's and I'm going to edit in CS6, so you have me a little concerned.
Could you describe the issue more? Does it happen at the clip breaks? How can you tell the audio doesn't match video length? Are they different lengths on the timeline? It could be that it's the conformed audio file.
How are you pulling in the video? I've found that if I allow CS6 to interpet the spanned video as a single clip, it will conform the audio and it takes forever. I have found it much more productive to just copy the individual MXF files to my system, and only the MXF files. Then import them as assets and PPr will not conform the audio, it will just create PEK files for the audio waveforms. I then select all the separate ~2GB clips and drag them to the timeline and they play fine. For the multicam, I'll just bring in the first MXF file from each camera, sync them by timecode, then bring in the rest of camera "A" and the rest of camera "B". Again, I haven't observed any issues, but it doesn't mean there aren't any.
Using CS6, the glitch is noticeable when the video is playing or when one is shuttling through the frames. When I pause on the affected frame, I see the glitch for about 2 seconds, then it clears.
I loaded the same footage on the CS5 system, and I can not reproduce the glitches at all.
* I posted the wrong processor on the CS6 system. It should be I7-2600K, not a I7-930.
So this is how the audio glitch manifested. The audio went out of synch about 1\2 way through the shot.The length of channel 2's audio is shorter. I tried to delete all media caches then re-import the clip, but the results were the same.
CS5.03 imported all of the video segments separately, but intact, without glitches.
I'm really sure the audio thing is a problem with conforming the audio. I suggest you try this: Copy the MXF files from the souce folder (the CONTENTS folder of the memory card) to another location on your system. Just the MXF files. Import those into PPr. If you keep the folder structure or the supporting XML files of the flash card, PPr will try to make one clip out of the spanned files. By putting just the MXF files in a folder, PPr will treat them as individual files and more importantly, it won't create the CFA conformed files.
You might be able to prove this by exploring the media cache folder on your system and looking for a CFA file for every clip. I'd bet one is missing, or a lot smaller than the rest. From your timeline grab, it looks like one of the audio tracks is around 7 minutes shorter than the other or the video track. A 35Mbps 720p60 file is ~2GB or roughly 6min 57sec long.
Of couse, I could be very wrong (probably)....
Your advice seems workable, however the visual glitches appearing on one system and not the other is beyond me. They appear on specific frames on the CS6 system, and there is no trace of them on the CS5 system.
This is the 1st project I've loaded on the CS6 system, and the 1st time I've used this particular XF100 ( we have 5 XF100s ). I thought it might be the flash media until I loaded it on the CS5 system.
Disappointing.
Stephen,
Read post #74 in this thread: http://forums.adobe.com/thread/1009064?start=50&tstart=60
In Canon XF Utility, use either Merge Each Clip or Merge All Clips if you have spanned clips. (You have spanned clips)
Then, delete all Media Cache Files and the Media Cache Database in Premiere Pro CS6 and import the footage. (You can find the file paths in Edit > Preferences > Media)
/Roger
I thought mabye because CS6 can not be perfect to deal with the Canon MXF.
Look your mxf files:
Camera: Cannon XF100
Footage : 720p 60fps 35mbs
And Adobe Premiere Pro CS6 offers full native format support for the HD and SD video formats used by
Canon XF MPEG-2 codec.
You can try to process the XF100 1080/50Mbps files.
Averdahl wrote:
Stephen,
Read post #74 in this thread: http://forums.adobe.com/thread/1009064?start=50&tstart=60
In Canon XF Utility, use either Merge Each Clip or Merge All Clips if you have spanned clips. (You have spanned clips)
Then, delete all Media Cache Files and the Media Cache Database in Premiere Pro CS6 and import the footage. (You can find the file paths in Edit > Preferences > Media)
/Roger
I know Adobe is working on it, for now use the method Roges is describing, it has worked for others too as far as I know.
/Ulf
Different projects have called for different XF formats.
The camera can only do 1080i, whether 35 or 50mbps. If you want 60p, you must shoot 720.
The Camera has selectable mbps from 25 - 50. I have a done many projects with each with CS5X and have had minimal glitches.
Again this is the first CS6 project, so I really don't know what the issue is.
Hi there
I have had the same happen to me once, I deleted the xmp files, and all was good again.
For me it was on MXF files created via the XF utility. It has only happened once for me on a few small clips. It was the whole clip, and the waveform was fine.
Don't know if anybody alse have seen this, but as said I have only had it once - so far :)
Ulf
Thanks for the reply mate,
Yeah I tried deleting the XMP files but didn't work. And I usually just copy the files from a card reader to the hard drive without using the XFutility. I really like all the features in CS6 and this just ruins everything. I hope I'll find a fix for this soon or else it will be putting $3K into the garbage and switching back to CS5.5 ![]()
North America
Europe, Middle East and Africa
Asia Pacific