Initializing log and capture (FCP4)

[Tim Shirey]

I trashed the preferences and restarted FCP4 but the program still hangs
when clicking "log and capture".  I should add that FCP4 recognizes a camera
connection at start-up.  I have no problem capturing footage within iMovie
with the same daisy chain setup (camera > ext. HD > Pbook).  Also, I've
tried log and capture with the camera connected directly to the Pbook and
still can't call up the log and capture window.  The log and capture window
won't even come up with NO camera connected (except for once last week).

FCP4 also hangs when I open Audio/Video Settings > Capture Presents > and
then attempt to edit or duplicate one of the settings.  I started with the
default settings for capture (DV NTSC 48 kHz) and experimented with a few
other settings with no change.

Do I need to reinstall FCP4?  Would that possibly help?  If that would help,
is there something I need to remove before reinstalling FCP4?

I'm puzzled by all this.

Thanks for the help.

- Tim


On 7/4/03 5:06 PM, "Macintosh Digital Video List"

> You should probably start out by trashing the FCP4 prefs. Then give it
> another try.
> 
> Is there any reason why you might suddenly have trouble seeing the camera? A
> problem with the daisy-chain?
> 
> sb
> 
> On 7/3/03 4:18 PM, "Tim Shirey" <shirey at illustratedWORD.com> wrote:
> 
>> I am attempting to log and capture footage from my Canon GL2 which is
>> connected by firewire through the external firewire HD to the G4 PB, using
>> FCP4.  Every time I try to initialize the log and capture screen, it just
>> hangs and I have to force quite the program.
>> 
>> I used to do this under FCP3.  I should mention that I got the log and
>> capture screen to open ONCE last night when I reset the scratch disk
>> settings to the PB HD BUT (to confuse things more....) could not duplicate
>> the experience again.  The next time it went back to hanging indefinately
>> (showing the "initializing log and capture and the moving blue/white candy
>> cane progress strip).  I shouldn't have to limit my scratch disk the the
>> internal HD.
>> 
>> Any thoughts of how I can avoid the program hanging when I click on the "log
>> and capture" link?