I recently upgraded to Premiere CS6, and in CS6 opened a version of a project I'd started in CS5.5.2. I'm working with XDCAM EX footage, editing natively. I'm working with Mac OS 10.7.4, 2010 Mac Pro, NVIDIA QUADRO 4000.
When I play my there are tearing artifacts across many of the clips, and there weren't any in the CS 5.5.2 version. I opened the project in CS 5.5.2 and the same sequence plays fine.
I've tried cleaning the media cache, trashing my preferences, repairing my disk permissions, and creating a new project in CS6 and importing my sequences into it. Same problems.
I've also had some clips go offline mysteriously, when I try reconnecting (in 5.5.2) I get an error saying there are no video or audio streams and it can't re-connect. The clips play fine in VLC player. But, if I boot from the clone of my OS drive that I created before upgrading to CS6 I don't get any offline clips.
Message was edited by: digitalkiln
Here's what I'm seeing in CS5.5.2, plays back fine:
Here's the same frame sequence in CS6, you can see the tearing across her mouth:
I have another CS6 Project with XDCAM EX files and this problem isn't happening. When CS6 imports the files does it create any other types of files that might be corrupted?
At first I couldn;t even see the difference in your screenshot, bu tthen I noticed it... right there at the mouth... and that's all throughout the clip?
I wish I could be of more help but I just can;t repro anything at all.. I'll post back if I start seeing anything like that.
It's not a constant line, sometimes it's rectangular boxes.
Jim: The glitches show while playing or pausing the sequence or clip in Premiere CS6 and if exporting to a file. Everything works fine in CS5. It's not a matter of encoding it wrong or not viewing it correctly, CS6 is adding glitches to the clip that aren't there in CS5.
I don't know the specifics of what Jim is driving at, but I do know that
different things happen upon export for disc, and if the problem is not
present on the disc, it'll help narrow down what the problem could be...
Same problem here. Visible on computer monitor AND on external monitor.
Haven't tested rendering yet. Included a screenshot:
Mixed timeline with XDCAM HD422 from Sony PDW700 and XDCAM EX from Sony EX3. (all footage 1920x1080i)
Blackmagic 1080i uncompressed timeline.
Single frames like this appear in the footage, artefacts not always in the same place, seems like something goes wrong when the footage is decompressed. This occurs only in the XDCAM EX (mp4) footage, XDCAM HD422 (most of the sequence) is all fine. The XDCAM EX footage itself is of course fine, and plays back normally in v5.5.
The artefact looks different in the source monitor, when viewing footage in the source monitor, somehow it takes the external signal a second or so to display interlacing. After a second or so, the artefact is sometimes in another place or disappears alltogether. Re-importing doesn't help.
Mac Pro Mid 2010
internal Raid0 with 2 drives
Nvidia Quadro 4000 Mac
Cuda driver 4.2.7
Mac OS 10.7.4
BTW: "Strange" behaviour when viewing in source monitor due to the fact that it was set to 1/2 resolution and 1 field only for playback. Brand new install, did change that for the program monitor, but not for the source. The bad news is that these artefacts indeed also show up in rendered material.
Filed a bug report, hope they fix this soon! (hopefully a bit sooner than that XDCAM HD audio bug in 5.5...)
Yep, looks like it. I really hope they can do something about it soon. Crazy situation with these bugs. XDCAM HD has this annoying audio bug in Pr5.5, and in Pr6 it finally works normally. XDCAM EX was ok in Pr5.5 and is broken in Pr6. So with a mixed HD/EX format timeline, there's always something that doesn't work as it should. One starts thinking about transcoding the whole lot anyway :-(
So here we are, eagerly awaiting Pr6.0.2.....
I am having the exact same issue. I actually called Adobe. All they could offer at that particular point was to make sure that my Quicktime was updated and that I had downloaded CS6.1. It is beyond frustrating. I am also using an XD Cam. The tears show up in different places. It happens in AE too. I renedered the clip out and the artifacts were still present. I am about ready to send it back. The artifacts are not present in CS5.5.
In the past 6 months working with PP I've asked myself the same question about transcoding many times, haha. I guess the extra cost of the NVIDIA Quadro 4000 makes me feel like I need to get my money's worth for Mercury Playback.
Thanks for taking the time to post, this will help bring this to Adobe's attention as a serious problem. There are a lot of us who are professional users that don't spend a lot of time posting on forums, etc, and it's important for our voices to be heard.
Ok to heighten fear this is also prevalant on PC CS5.5 AND CS6.01. Complete reinstal and update with updating quicktime to latest version has NOT solved the issue.
As posted earlier Im getting these errors from Canon XF100 and XF300 cameras. The XF300 is worse with pixelated frames that render out on finals. Another issue is a random frame pops in now and again from a second earlier or later? Here is video snap shot evidence.
I have tried editing a different project in CS5.5 with HDV 50i footage from XF100 and XF300 and getting same errors regularly especially in multicam. I have noticed that if I elongate the clip the error dissapears so I think seems more prevalant near cuts on short clips?
THIS NEEDS FIXING ASAP we have businesses to run!
Some more screenshots, maybe one can see better what is happening here:
In this case the "tear" happened twice in one frame:
and a closeup of the place where it goes wrong:
and the other place, a bit lower to the right of the wheel:
Looks like some data corruption happening somewhere on the way? It occurs in BOTH fields (1080i footage) at the same place in the frame. Screenshots were taken from the program monitor displaying both fields. Hope this helps Adobe people fixing it.
Are there any people working with XDCAM EX footage on a MAC that DON'T have this problem? Could they please they report their config, OS version etc.?
Hi Roddy, just saw your post after I sent mine. So apparently it's not only a Mac problem. For me it seems that a lot of motion in the frame also has something to do with it? Is your footage progressive or interlaced?
I agree very much with your last remark:
Roddy Mc wrote:
THIS NEEDS FIXING ASAP we have businesses to run!
I haven't upgraded any drivers.
I just installed CS6 "on top of" CS5.5. Then took a project I was working on in Pr5.5.2 and opened it in Pr6.0.1, saved as a new version, started editing, and ran into the problem as described.
I can still open the original project in Pr5.5.2 and everything plays fine!
So to me it seems to be clearly a Pr6.0.1 issue.
Ok I have reinstalled drivers from past and tried it out on CS6. Firstly CS6 wouldnt allow me to run with mercury acceleration (cuda) enabled? so in my nvidea settings i wend to 3D settings and changed the acceleration mode to compatibility which got me in to CS6 with Cuda enabled using older drivers of the Geforce 570 GTX. Seems funny this card IS in the supported cards list just CS6 wont allow that driver has to be a recent driver to pass?
Anyhoo tried multiple goes at rendering a clip with an error and NO WAY HOSE, tried field order, blending different bitrates, with and without acceleration but the error is always there sometimes displaying differently but all ways there.
DEFO NEEDS FIXING.
I have been able to reproduce this issue, but so far only with XDCAMEX .mp4 files separated from their camera structured folders. For all of you that are having these issues, did you happen to modify the camera structured folders at all or remove the .mp4 file from the folders created by the camera? I am continuing to investigate and would appreciate anyone that can provide small sample files. You may PM me and I can send deatials on where to post files if you do not have a location to post files to.
That's too bad. Are you Mac or PC? Perhaps you could include your basic setup to help the Adobe team narrow this down. Seems like a Mac issue so far.
I have had the issue on PC with Canon XF footage: