Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy preview disabled – no video when trying to capture

  • preview disabled – no video when trying to capture

    Posted by Jenelle on March 15, 2007 at 6:30 am

    I am having trouble when trying to capture from my digi beta deck into FCP via an AJA Io. I have done this before & it has worked, for several years, but I can’t seem to get it working now. I have deck control, I can hear the audio, I can see the video on another monitor hooked up to AJA, but everytime I try to capture, I get the bars w/ “Preview Disabled” across it, a black window comes up (where video should be) and then the message “This operation could not be completed as there is no video”.

    I have powered down, restarted, changed easy setups many, many times.

    Any clues?

    Jenelle replied 19 years, 2 months ago 3 Members · 9 Replies
  • 9 Replies
  • Don Greening

    March 15, 2007 at 6:44 am

    You’re obviously very familiar with your system so I won’t bore you with the obvious things to check when making sure you’re hooked up properly. Have you tried trashing the Final Cut Pro preference files yet and then restarting FCP?

    – Don

    “Please take a moment to fill out your profile, including your computer system and relevant software. Help us help you.”

  • Jenelle

    March 15, 2007 at 6:56 am

    you know I did trash the preferences (saved on desktop), but then when I went into FCP I couldn’t find the preset I needed, so I ended up putting them back. How do you get a preset back if I were to trash them & am not given that selection?

    thanks

  • Steven Lambion

    March 15, 2007 at 7:32 am

    I don’t know if you have this problem, but when I have multiple video feeds, such as firewire, Final Cut Pro can’t figure out which one to choose so it brings up the black banner saying Video Preview Disabled. Also Final Cut Pro does errors like this if you are trying to capture a video feed that is not like the capture setting. Example: Capture a DV compression video feed to an h.264 compression clip. You seem to know what your doing though, so you’ll probably figure it out. It always seems to be some little thing you passed or didn’t notice.

    Good luck!!

    Video Specialist
    Apple Developer
    Owner of GranitWorks

  • Don Greening

    March 15, 2007 at 7:41 am

    Go to the easy setup menu and make sure the “show all” box is checked. It may have become unchecked when you trashed the old pref files and FCP created new ones at startup. If your AJA I/O presets aren’t there after that then you’ll have to somehow get FCP to again recognize the ones that are unique to the AJA setup.

    Also make sure you’ve trashed all the FCP pref files required. Here’s how to do it properly:

    https://www.kenstone.net/fcp_homepage/trashing_fcp_prefs.html

    You can also get a free program to trash your pref. files for you called FCP Rescue. Just google the name and it should come up. It’s a very widely used and invaluable little program.

    – Don

    “Please take a moment to fill out your profile, including your computer system and relevant software. Help us help you.”

  • Jenelle

    March 15, 2007 at 7:52 am

    thank you for all your help & resources!

  • Jenelle

    March 15, 2007 at 7:55 am

    thanks for all your help – I am sure this will resolve the issues.

  • Jenelle

    March 15, 2007 at 8:09 am

    it lost my AJA setup options when I did that – I will have to check later to see where those are stored…

    thanks

  • Don Greening

    March 15, 2007 at 8:30 am

    Okay. I don’t use a capture card so I can’t help you with that. Sorry.

    – Don

  • Jenelle

    March 15, 2007 at 7:15 pm

    thank you everyone for all the help – I got AJA on the phone – Jim saved the day – we installed the latest driver of the AJA/Io and that was the trick. Something was corrupted, since when I trashed the preferences I no longer had the AJA options. I updated FCP to the cross platform in January – sometimes that causes issues. It was fine a few days ago, but wasn’t yesterday.

    Thanks again!

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy