Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy FCE Quits when trying to Capture

  • FCE Quits when trying to Capture

    Posted by Joe Garvin on May 24, 2006 at 6:41 am

    I noticed a few other people have recently been having problems with Final Cut Quiting when trying to Capture.
    Has anyone found a reason ?

    I have a G4 laptop with OS-X 10.3.9
    and Final Cut Express 2.0.3

    I have tried different decks and Firewires
    trashed the prefs
    and FCE still quits so it must be a software problem or conflict.

    It was working fine a few months ago. since then I ran a software update
    ( Not for FCE, I have had 2.0.3 for a while ) and a whole bunch of items were updated

    here is one symptom… If I try to capture with a deck with a firewire cable plugged into my G4 laptop as soon as I click on “Capture” The FCE program Quits
    BUT if I unplug the Firewire cable and Click on “Capture” I Get the Capture Window like I normally do but with a warning that no device was detected ?

    Can I re-install FCE 2.0 and then do the Update to 2.0.3 ?

    Anyone have any ideas what might be causing this problem ?

    Thanks
    Joe

    Joe Garvin replied 19 years, 11 months ago 2 Members · 4 Replies
  • 4 Replies
  • Joe Garvin

    May 24, 2006 at 4:51 pm

    I just learned that FCE also quits when trying to print video to a recorder
    and will not even let me export to a quick time movie.

    every time the program just quits

    The project I’m working on is a group of about 180 photos that were scanned and imported into FCE
    I learned of these problem when I tried to capture some video to add to the project.

    that when the program would just Quit….Now I’m trying to transfer my work to tape or even a QT movie so
    I can use my other editor …..I should have just used my reliable Media 100 from the start……..

    I have had FCE for two years with NO PROBLEMS now it just quits all the time

    What was in that UPDATE 2.0.3 I never had this happen before ????

    Any Advice would help
    thanks
    Joe

  • Todd Gillespie

    May 25, 2006 at 4:50 am

    Definatly try reinstalling.
    You can alway run the updates with a reinstall.
    I’m not up to date with my FCE configs, so make sure it’s not an OS problem.

    Don’t be mornful about Media 100, it can give you just as many problems.

    Did you try a different HD for capture?

    Good Luck,

    Todd at UCSB
    Television Production

  • Joe Garvin

    May 25, 2006 at 4:37 pm

    todd
    thanks for your response

    I am trying to track down the conflict
    from looking at different forums there are many people with the exact same problem and symtoms

    it seem that Final cut express will NOW not recognize any DV device
    and even more people are having the same problem withthe new HD version

    I’m still using the regular final cut express ver 2.0.3

    It may be related to my latest upgrade of Quicktime 7.0.4

    I found an article by apple warning of DV device problems related to Quicktime 7
    it recommended to trash the QT receipt package and re-install the lates version of QT which would be 7.1

    That will be my next attempt at this problem
    I have already re-installed the old original version of FCX ver 2.0 and still can not get any results with mt DV deck or camera …. It’s like my computer just quits the program any time I try and connect via firewire to and DV device

    Maybe it’s APPLE’s way of making us to upgrade ?????

    If I found out what is causing the problem I let everyone know
    OR If you know of anybody which is suffering the same symptoms maybe we can work together to find a cure,

    thanks
    Joe

  • Joe Garvin

    May 25, 2006 at 8:23 pm

    The problem was Quicktime version 7.0.4

    I just down loaded QT 7.1 and all seem to be working fine again

    So the conflict is a bug in version 7.0.4
    which will not allow FCP or Final cut express to recognize any DV device and the program
    just quits.

    Hope this helps anyone with the same problem

    Joe

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