laxdefence5

Q: after 10.2 update- imported clips displaying black

I downloaded all updates for FCP, compressor, and system updates.  Currently running a brand new Mac Pro, 32GB RAM, dual GPUs, the whole 9 yards.  I am running my FCP library from a Caldigit 3 drive raid array, in raid 0.  After updating to 10.2, all of my camera clips show only black, no video, but i have audio.

 

There are no warnings at all in any of my projects or events, the clips are just black, with working audio.  I was successful in updating the libraries when i updated FCP to 10.2. The clips I have are recorded from a Panasonic AG-AC160, recorded AVCHD, 1080p24.  Any ideas?!

I can skim through audio, and the thumbnails appear for each clip in the events browser, but when i play them, All i get is audio, with a black screen in the viewer.  They were working fine yesterday, and the only thing I changed was the 10.2 update.  I'm stumped!

Mac Pro, OS X Yosemite (10.10.3), FCP 10.2

Posted on Apr 13, 2015 11:58 AM

Close

Q: after 10.2 update- imported clips displaying black

  • All replies
  • Helpful answers

first Previous Page 6 of 11 last Next
  • by wrrn,

    wrrn wrrn Apr 17, 2015 6:51 AM in response to cigame
    Level 1 (9 points)
    Video
    Apr 17, 2015 6:51 AM in response to cigame

    I'm happy with the speed of EditReady. Of course I'm choosing the simpler re-wrap option so it's faster than encoding.

  • by julian Gibbs,

    julian Gibbs julian Gibbs Apr 17, 2015 7:20 AM in response to laxdefence5
    Level 1 (0 points)
    Apr 17, 2015 7:20 AM in response to laxdefence5

    just upgraded an iMac with 10.10.3 first then upgraded fcpx and I do not have the black media issue only on our Mac Pro.

  • by laxdefence5,

    laxdefence5 laxdefence5 Apr 17, 2015 8:13 AM in response to laxdefence5
    Level 1 (0 points)
    Apr 17, 2015 8:13 AM in response to laxdefence5

    Could it be an issue with the new Mac Pros?  Specifically, the 10.2 update opened up the possibility of using both GPU's and hardware acceleration.  Could that possibly be an issue with AVCHD files from Panasonics?

  • by JBELL27,

    JBELL27 JBELL27 Apr 17, 2015 8:22 AM in response to laxdefence5
    Level 1 (0 points)
    Apr 17, 2015 8:22 AM in response to laxdefence5

    I'm experiencing the problem on a late 2010 mac pro and a late 2012 mac pro. It must have something to do with the way quicktime/FCPX handles avchd files. I can play them in stream clip just fine, but not in finder, quicktime, or fcpx. The new FCPX update claimed to add support for the Panasonic AVC-Ultra codec family - perhaps in adding that, they accidentally tweaked something for AVCHD.

  • by tubefingers,

    tubefingers tubefingers Apr 17, 2015 9:13 AM in response to JBELL27
    Level 1 (10 points)
    Apr 17, 2015 9:13 AM in response to JBELL27

    Having this problem on a late 2013 MacPro, but not on a MacbookPro 2008 model

  • by wvito,

    wvito wvito Apr 17, 2015 9:20 AM in response to julian Gibbs
    Level 1 (4 points)
    Video
    Apr 17, 2015 9:20 AM in response to julian Gibbs

    Are you importing AVCHD content?

     

    My order was the opposite and 10.10.3 didn't fix it, do you think if I unistall FCP 1.2 and reinstall it might work?

  • by FarmCatMedia,

    FarmCatMedia FarmCatMedia Apr 17, 2015 9:33 AM in response to wvito
    Level 1 (0 points)
    Apr 17, 2015 9:33 AM in response to wvito

    I'm doing a full reinstall of the OS to see if that does anything. The project seems to work on my MacBook Pro but not my MacPro (2013).

  • by yoink,

    yoink yoink Apr 17, 2015 9:51 AM in response to laxdefence5
    Level 2 (305 points)
    Apr 17, 2015 9:51 AM in response to laxdefence5

    2010 Mac Pro & 2012 rMBP confirmed so far.

     

    The 2010 here has a GTX680, 48GB RAM and a PCIe boot drive. We've not upgraded any other machines to 10.2 as a result of this issue.

     

    Apple was provided with a card image and a 10.2 FCPX library suffering from the issues.

     

    You can download the zip file containing the AF100 card image and FCPX Library here to run any other tests anyone may want: https://cp.sync.com/dl/9e93a777#e3ErhTl9CTmF28rx/tqutlNqOqd5yiNT1vJWaPQ2FiYMAugP JbfYQCTQ4/rlE/ujRwrekLFpbtXY5BxUMghDqQ==

     

    It's just 2MB since it's a 2s 1080p30 AVCHD clip.

  • by Doug Carraway,

    Doug Carraway Doug Carraway Apr 17, 2015 9:56 AM in response to laxdefence5
    Level 2 (244 points)
    Apr 17, 2015 9:56 AM in response to laxdefence5

    Same issue here.  AF100 1080p30 user.  All clips black in FCPX 10.2 on my new Mac Pro.  My 2012 MacBook Pro seems fine though.  I plugged my Pegasus RAID into it and was able to edit.  It crashed when I tried to export a Master File but did fine exporting an HD 1080 for YouTube strangely.  Shooting more this afternoon so I'll just shoot 1080p24 instead for now and use my MacBook if I need to.  Wish I'd seen this thread before I updated but I've never had trouble with any update before. 

     

    Doug

  • by Tom Wolsky,

    Tom Wolsky Tom Wolsky Apr 17, 2015 10:10 AM in response to yoink
    Level 10 (118,408 points)
    Apple TV
    Apr 17, 2015 10:10 AM in response to yoink

    The clip in the library is black and the media on the disk image doesn't import correctly. Looks like this after import.

     

    Screen Shot 2015-04-17 at 12.07.38.png

     

    Looks OK in the import window and looks OK in the QT player when played from the card, and shows the correct frame rate. The original clip that's black in FCP is in the bundle, plays in the QT player, but shows the wrong frame rate.

  • by JBELL27,

    JBELL27 JBELL27 Apr 17, 2015 11:39 AM in response to laxdefence5
    Level 1 (0 points)
    Apr 17, 2015 11:39 AM in response to laxdefence5

    Has anyone heard of any kind of update from Apple? So much work, so many deadlines. Everything is black!

  • by DimitriL1,

    DimitriL1 DimitriL1 Apr 17, 2015 11:47 AM in response to laxdefence5
    Level 1 (0 points)
    Apr 17, 2015 11:47 AM in response to laxdefence5

    No issues here. Using AVCHD footage from Panasonic AF-100, 24p, Retina iMac. Old projects coming up fine, new imports as well.

  • by yoink,

    yoink yoink Apr 17, 2015 11:55 AM in response to DimitriL1
    Level 2 (305 points)
    Apr 17, 2015 11:55 AM in response to DimitriL1

    DimitriL1 wrote:

     

    No issues here. Using AVCHD footage from Panasonic AF-100, 24p, Retina iMac. Old projects coming up fine, new imports as well.

    As the thread indicates, it's mostly 1080p30 and 1080p25. None of us seem to have issues with 24p footage.

  • by Tom Wolsky,

    Tom Wolsky Tom Wolsky Apr 17, 2015 11:55 AM in response to DimitriL1
    Level 10 (118,408 points)
    Apple TV
    Apr 17, 2015 11:55 AM in response to DimitriL1

    So far the only reports seem to be for 25p and 30p. Maybe something to do with the way the camera converts interlaced formats to progressive. 24p is natively progressive, has no interlaced form.

  • by Mac-walter,

    Mac-walter Mac-walter Apr 17, 2015 12:46 PM in response to laxdefence5
    Level 1 (0 points)
    Apr 17, 2015 12:46 PM in response to laxdefence5

    Hi Guys

     

    I just got this email from Apple's FCPX feedback.

    They're working on it and gave me a workaround using Compressor.

    It works for me and hope will help you too:


    __

     

     

    Hi Walter,

     

    This issue is one of our top priorities, and while we are currently investigating it, I may be able to offer you a temporary workaround that involves transcoding the affected media with Compressor:

     

    1. In Finder, locate your problematic AVCHD files. If you are using an external media location, this should be easy. If your media are managed in the library, you can consolidate it out of the library to an external media location.

     

    2. Use Compressor to transcode the problematic media to a high-quality format, such as ProRes 422, and target a folder on a very large volume since these new files will be larger than the originals. If you create a custom Location, you can choose an output folder as well as what you want appended to your file names. Something like “[Source]_PR” (for ProRes) would work well.

     

    3. In Final Cut Pro, locate the problematic AVCHD clips. If you are viewing your library in List View, you can find them by sorting by the codec H.264. Move these clips into their own event.

     

    4. If you have any optimized or proxy media created from these clips, they need to be deleted. Select the event, go to File > Delete Generated Event Files, and choose “Delete Optimized Media” and “Delete Proxy Media.”

     

    5. With the event still selected, go to File > Relink Files, choose Relink: All, click Locate All, and target the folder of transcoded media.

     

    I hope this temporary workaround works for you, and thank you for your patience and continued support. If you have any other questions, please don’t hesitate to reply.

first Previous Page 6 of 11 last Next