Transcode your files to a format that works, then relink the media. I had only a small number of XDCAM EX clips, majority of the project was XDCAM HD422, so I transcoded the EX clips to HD422 and relinked the media. Worked for me. (I used Media Encoder 5.5 for the transcode)
Unfortunately the only workaround at the moment seems to be to transcode to another codec.
Adobe PLEASE!!!! fix this major bug!
I'm having the exact same problem with video shot on a Sony PMW EX1. Windows 7 CS6
There were NO problems with CS5.5.2
The clips play with NO problem in the latest QuickTime and FLV player, The ONLY problem is in Premiere Pro.
I encode most of my video to h.264 and the tears are in seen in the Premiere timeline and the encoded files.
I have hundreds of clips, some work, but intermitently for no ryme or reason, some tear for a just few frames just where you need the video. HELP!!!!
I've played with most of the settings, Mostly using 1080 29.97 30P some 720P
I've tried storing the video on a interal and external 2 drive RAID 0 and 5 drive RAID 10 with the same problem.
I'm already crazy but this is diving me insane!
The XFutility I have only allows transcoding to MXF format unless im missing something?
Barry, you did not miss anything, the XF-util only allows export to MXF. You should use f.ex. the mediaencoder of CS5.5 (if you have had that), I do and it works, like Cars says above.
I think we all hope for a fix soon, because it only gives us all extra work
Well not exactly, but still a bid bothersome
I have set up i watch-foldet in media Encoder on my CS 5.5. machine. On the same machine I have the XF utility. I export from the CF-Card with the XF utility (without auto subfolders) into the watchfolder as MXF. Then I fire up AME and it will automatic start encoding the MXF files to the format you have choosen into the output folder.
I have shared the output folder so that I can copy the footage to my CS6 machine and use it.
I know it would somehow be easier to edit it in 5.5, but I beleive in a soon fix, so I get to know CS6 more this way too, and when you first have set it up initially, it's close to ok besides the extra time of course...
Ove Ellemark wrote:
You can try to clear all the media cache, I think I did this when I got the MXF-files to work again in CS 6.0.0. (Maybe there is need for a backup first).
I will have a got at this workflow tomorrow morning, have some great footage to test with, and will report back as soon as I have done testing, will sure clear media cache first.
I just had a go with some files merged inside the Canon utility, and imported into CS6. I had no tearing of footage after a few hours of play. I had a few minor clips not playing audio, but after deletion of the XMP file for the clip, and after restart of PR all is ok.
It seems like audio will not play if the XMP files are corrupted or simmilar, can anybody confirm that?
The tearring problem exists in other projects with footage merged in prelude or premiere for me, and I cannot guarantie there are no tears in the canon merged files, but it seems ok.
Does Adobe understand this is a bug? Is anyone listening? I have hundreds of clips on my RAID I need to use and CAN NOT until Adobe fixes this random glitching issue. They play perfectly in the QuickTime player. They worked well in PP CS5.5.2. THEY TEAR in PP CS6.01, totaly unusable.
I know they are working on it and several people, including me, have uploadet material for them, but no fix yet as fare as I know.
Maybe you could enlighten us a bid more, Trent - since we all are axcious to get to work in CS6 and want our native files the most.
After reading the forum again, I noticed the replies from Adobe employees from June 3 - June 8 and there apppers to be an effort to fix this issue. Do you remember when patches were released for individual software issues? I hope Adobe's not waiting to bundle the fix with the next major CS6 Production Premium Suite upgrade in a few months.
On the plus side, I found the feaures in CS6 very productive, like it very much except that one bug that makes CS6 worthless for my EX1 workflow. Please have Al Mooney, Adobe PPCS6 Product Manager let us know when we can take the diapers of his new Baby. Untill then, it's back to the nursery for this stinker. I have a few projects due soon that can't wait so, I must uninstalling CS6 and reinstalling CS5.5.2.
I can provide XDCAM EX from Sony EX3 Camera 1920x1080 PAL 50i
Do you need my help? Sending files? Screenshots?
Hope you guys solve this soon because as a professional video company I can not work now on projects edited in 6.0.1.
I found out too late that this is a serious problem in PremPro 6.0.1 and have edited large projects for important customers.
Please make a fix a.s.a.p. and please do not wait untill the next big update.
So,... if I can be of any help, please let me know.
(Hoping to get a reaction)
The squeeky wheel gets the oil. Everyone experiencing this bug, please nudge Adobe to correct it.
Call Adobe Support and they will walk you through uploading your video file to their FTP server so they can study it.
Thanks for pursuing this Major big bug. Is there an Adobe team developing a fix?
I'm chomping at the bit to move to CS6 and a transcoding workaround would be to much work, double drive-space and usually slightly degrades quality. I must stay with CS5.5.2 until a fix is released. I was selected as a ACE PP CS6 certification exam Beta tester. With very little experience even though I purchased the CS6 upgrade 2 months ago, it will be interesting to see if I come close to passing. Let me know if you want some files shot on a Sony PMW-EX1 that are tearing in CS6 but not CS5.5.2 or FLV player.
Intel 9450 PC, Asus P5E Deluxe, 8GB RAM, Geforce 560 Ti 2GB RAM, External 2 drive RAID 0 USB 3.0
Can Adobe give us an update to any progress, the software is technically broken and unuseable for many professionals and has been now for quite some time. Whist its expected there are bugs in newly released software, such a major floor should have been fixed by now or at least a statement made to the community of current findings and progress. I feel confident sales will increase once the problem is fixed but am struggling to understand why this is taking sooo long especially concerning statements like made by professiobals for professionals when its fundamentally floored compared to previous versions?
Yes, it sure would be great to have the fix in short time, so there would be no need to transcode, and we could use PL again to offload cards
Thanks for all the work you put in on this, Trent & Co.
Having a few hours to tinker today with my EX1 CS6 XDCAM workflow, I uninstalled Avast anti-virus and Spybot Search and destroy. Rebooted and installed Windows Security Essentials. This made NO difference, tearing is as bad as ever.
I changed my page file to another SATA dive connected to my Asus P5E Deluxe motherboard and increased it's minimum size to double the 8GB physical RAM. This made NO difference, random inconsistent tearing just as bad but, Premiere opens faster.
On the NVIDIA on Geforce 560 Ti, 480 Cuda cores at 880 MHz, I changed the Deinterlacing, Use reverse telecine to off.setting NO difference
There are no tearing issues on a HP 8540 Elitebook laptop with a Quadro NVS 5100 M GPU. It has 48 Cuda core running at 550 MHz and 8GB RAM. I've converted my post production suite to a 15 inch screen laptop and external 22" HDMI monitor. I might go blind but it gets the job done.
Conclusion: using the same video files,
On a slower CPU Intel Quad 9540 and fast GPU 560 Ti there's tearing problems
On a faster i7 laptop processor and slower NVS 5100M GPU, NO PROBLEMS
All files play OK in the VLC player. All files worked in 5.5.2
Did you tried to install Direct X 10 or 11, This is very important tool. I tried it my self on XDCAM EX files and gave good results.
picture is stable.
The only problem that i am not happy with it is that when i import Sony XDCAMex Files on my timeline a yellow line is always visable, even when mercury engine is deactivated, in CS5 this will not happen. It might be a bug too, did you ever notice it?
I imported full hd M2t files on the same timeline and no yellow lines, playback is perfect.
it must be a problem from CS6 & XDCAMEX files.
pls try it and give feedback,
Same problem here by the way. CS6 and XDCAMEX files.
Problem is there when i:
- open the clip in source monitor from media browser
- open a brand new project, the clip alone from a new user (clean cache)
- open in After Effects same problem.
- And when i export the clip, all the glitches get printed onto the export
No problem if
- I open the clip with an outside program like VLC Player
- I open it in another computer where i have CS5.5
- And i convert the clip to Cineform
Right now I just converted all of my clips to Cineform and moving forward like that...
I'll try to get some sample clips to upload...
By the way I'm using
32 GB DDR3 1600 RAM
NVIDIA GTX 560 Ti video card
And working on a PC.
Wow, I'm a satisfied CS5.5 user with an XDCAM EX workflow. No upgrade for me, Adobe, until you get this fixed! Unbelievable that a company can release software that lacks working functionality when the same functionality works in previous versions.
I'm sure I'll be told some story of how hard it is to test everything and there's a lot of variables on the end users' machine, (ActiveX, hardware considerations) blah blah blah - oh, and that I need to upgrade my machine, too, or I'm asking too much of the software industry...
Of course, anything but the reality that I've been burned before... I have a business to run, and I can't afford to actually pay companies for their software only to be their software testing guiney pig...
Don't get me wrong, I love the working versions of Adobe's software, and I use their products all the time. That being said, I certainly feel they could do a better job of getting a working version of a product out the door before people invest their money (and all of their troubleshooting time) on something that just doesn't work.
It would be interesting to find out the percentage of XDCAM users are having issues and their hardware configuration.
I've been exchanging messages but not spoken to Vinay Tamta from Adobe's tech support team. He say's he's looking into the issue.
Yes, Adobe have been looking into this issue for a while now, would be great to know how far we are from a fix?
Currently I use an "old" PPRO 5.5 machine to transcode to UT via a watchfolder and AME, but sure would love to get into a less "complicated" workflow and to use prelude.
I was just on the phone with my very good friends at Adobe tech support. They had me create a new user account, uninstall and reinstall NVIDIA 301.42. As you most likely know by now, it did nothing to solve the problem. I am being pushed up to the next level of tech support and told they will get back to me.
Anyone want to wager on how many days until I recieve a call-back?
Who thinks we'll need to pay for an update CS6.5 to fix this?
I use a lot of XDCAM-EX material, but haven't seen this problem in my work. I have been able to repro this when importing XDCAM-EX files created with the Sony XDCAM Browser, but only via Drag-n-Drop and File>Import. When imported via the Media Browser, everything is OK. Files imported from directly from the SxS card folder structure are also OK.
So how are you guys importing your footage? Do you use the recommended way (Media Browser) or the old fashioned File > Import or Drag-n-Drop from Finder/Windows?
And do you use Sony's XDCAM Browser or Canon's software before importing to Premiere?
In CS6 you can access files from the memory card or copy the files to a drive other than the C drive then open the PP Media Browser select a clip and by placing it on the timeline or in a bin, you've importted it. I can open an existing CS5.5.2 project in CS6 and it creates a new project file keeping the CS5.5.2 project file intact. There's no importing like when you're digitizing an analog tape. Adobe supports native EX1 files or at least claims to support and did in CS5.5. The problem appears to be hardware related because the same clip that plays with no problems in CS6 on one machine, has problems on another machine that has no problems with the the clip in CS5.5.
New member, having same prob as everyone. Funny thing with me, is I copied the original footage and project files to my MacBook Pro. Loaded up the project, it found the files. All problems are solved. THere are no glitches anywhere.
Import to Encore and burn dvd, DL, BR with no glitches. This is not the solution, but it has solved my issue of needing to get this done.
Glitches are happening on the MacPro (2months old). MacBook Pro is new as well
Wierd thing tho, is I can burn a Bluray from the glitchy footage, and even though the footage is bad, the bluray is absolutely perfect. DL or DVD will have the glitches,
Probably just confuses things more.
Same problems here.
Just bought a new computer, new install with windows 7 and drivers and CS6 production Premium. I have glitches in the video I playback while editing. Shooting on an Sony Ex1r, firmware version 1.20 , xdcam ex, 1080p. Glitches are also present at export.
Glitch is in a frame, like described in first post, sometimes it looks like it repeats 3 or 4 frames. Sometime it looks like an area is grabled, like bad reception from digital tv, the little squares.
Old computer still runs CS 5.5 and can export files in H264 with no problems. I first thought it was my hardrives, not being able to keep up or something. Tried moving to other harddrive, but to no avail, mediacache cleaning and changing didnt work. I can add pictures if needed. My configuration is :
– Lian Li PC-8NB, 3x Scythe Slip Stream 500, Seasonic S12-II 620
– Gigabyte X79-UD5, Intel Core i7-3930K @ 4Ghz, Scythe Ninja 3
– 16GB (4x 4) Crucial DDR3-1600, 128GB Crucial M4
– 1x 2TB Western Digital Caviar Black 'FAEX', Silentmaxx HD Silencer Rev. 2
– 2x 2TB Western Digital Caviar Green 'EARX'
– nVidia GeForce GTX 570, AC Accelero Xtreme Plus II, Asus Xonar D2
– LG BH10LS38, Lian Li C-02B, Lian Li CR-36B
– Microsoft Windows 7 Professional 64bit SP1 NL
I have a ftp server and can provide footage if needed. It would be nice if Adobe could fix this.
I think I will install 5.5 for now.
Please call Adobe tech support, the more we sqeak the more grease we'll get.
Quote from my frequent correspondence Adobe tech support states "We are always here to assist you. Please contact us at 800 833 6687"
I have been talking to tech support about this issue for over 2 weeks and all I know now is Adobe tech support is FUBAR.
There is a system where you call 800 833-6687, punch a bunch of numbers to get through only to find you've been routed to Adobe Acrobat support. Then you're profusely apologized to and routed to Premiere Pro support. Total time is between 15 to 30 minutes before you get to the proper channel. Then you go through the rudimentary set of questions taking another 10 minutes, then when it's been obvious to for 5 minutes that the support person ran ito the Peter Principle after your first explanation of the issue, you are apologized to and with a sweetening politeness told to please allow me to put you on hold to ask my supervisor, then after a few minutes you are asked to perform some task you know the results of because you've tried it many time with no improvement to the problem. It's been about 40 minutes when you're asked if you would please allow the appropriate person to call you back tomorrow morning because it need to be escalated to a higher level. OK, I just shot an hour of time and got nowhere and I'm waiting for a call that comes at 5:46PM the next day and you guessed it, I was unable to answer it because I had gone home for the day. Now I find a email saying we tried to reach you and we really want to help so call us back at 800 833-6687 and not to reply to the with email. So the next day, I call the number and go through the exact same description as above taking another hour and waiting another day and miss the call back. Repeat procedure several more times and that's where I'm at, nowhere stuck in an endless loop of incompetency. Oh, did I mention Adobe's tech support is FUBAR?
If tech support was trained on troubleshooting half as much as they are trained on apologizing and thanking me for my patience we might have a solution by now.
Europe, Middle East and Africa