Weird Pixelation with Macbook Pro

I had this come up in one shot. I also did the log and transfer on my mac book pro, and I may have done it over the card and not on the hard drive. I don't really remember. I was using Final Cut 6. In my case, the problem was not as obvious, and I was able to fix it in Color.

I plan to upgrade to the new mac book pro very soon. I wonder if that would make a difference?
 
For you MBP guys getting an occasional glitch -- are you using firewire or USB drives or card readers? Can you try transferring through the MBP's onboard SDHC card slot directly to the internal drive? Or, is there anyone out there who can testify to already seeing such a glitch after using the internal SD card reader and L&T'ing to the internal drive? That would be an extremely interesting data point, as it would remove firewire or USB as a potential source of shy the glitching happens.

I can verify that the glitch occurs for me regardless of any of the variables you mention. I've tried Log and transfer from:

built in SDcard reader to internal drive
built in SDcard reader to external firewire drie
external usb drive to external firewire drive
external firewire drive to the same firewire drive.

Experienced some glitches in every situation. Most times i was transferring about 10-14 gigs of raw material.
The card was a panasonic gold 16gig
Mac book pro 13" 2.4ghz with 8 gigs of ram
os 10.6.6
FCP 7.0.3

"Log & Transfer" is the root cause of these problems, and I really wish it would just go away. Hopefully in the next FCP, Apple will recognize that recorded digital files do not need to be, and should not be, re-digitized into another format before they can be used.

I respectfully disagree with the second part of your statement. I find the L+T workflow fantastic. The ability to edit in a robust codec and still maintain a link to the raw footage is a very useful way for me to work. While the option to work natively would be great for many, and i'd welcome that ability, i certainly hope log and transfer doesn't go away. I just hope this small glitch can get fixed.
 
I also feel like ProRess can be a solid workflow in the right situation. I would like to find a solution for the glitch, and yes, of course native AVCHD would be nice for some situations.
 
I am using a Macbook Pro 2.66ghz Duo Core, 4GB RAM running 10.6.6 and FCP 7.

I am going to offload some more files tonight and see if the problem happens again. This time, copy the PRIVATE folder to the drive and do the Pro Res convert from there.

Fingers crossed this doesn't happen all the time.
 
Another 10 minutes of footage and the same problem occurred twice.

This time, I offloaded the PRIVATE folder to the drive, then did a log and transfer to Apple Pro Res 422 LT using FCP.

This isn't very encouraging.
 

Attachments

  • Screen shot 2011-03-09 at 3.05.51 PM.jpg
    Screen shot 2011-03-09 at 3.05.51 PM.jpg
    20 KB · Views: 0
Time to start looking at what might be taxing your system. When was the last time you did a clean up on the computer. I spent about 6 hours yesterday getting rid of weird stuff. The speed of my computer kicked up about 50%. What processor is in your computer? Which version of FCP are you using and which OS?

Thansk,

Jan
 
I am using a Macbook Pro 2.66ghz Intel Duo Core, 4GB RAM running 10.6.6 and FCP 7.0.3.

The problem is 100% on the import. I re-transferred the clip with the problem and the glitch disappeared.

This is disheartening, only because I will most likely have to buy a new $2500+ computer. Either that or just cut out the frames when it happens.

: (
 
I had just finished read this thread when I turned on CBS National News. There was one of the first story's running...Nancy Cordes on some Muslim hearing in Washington. She was walking down a hallway with Rep. King when that pixelated band appeared. Lasted all of a half second or so, but unmistakably the same artifact.
Don't know what CBS shoots with or edits with. Glad I read this thread first.
 
A moderator should make the title of this thread "Weird Pixelation with Macbook Pro"

I'd be interested to see if this is happening with the newer quad core systems. So far I think it's just been the duos.
 
Back
Top