"log and capture" causing unexpected quits

Hello, so today I tested out an HX A1 on my macbook pro to see if my computer could handle editing the HD footage. So I selected the easy setup "HDV - 1080i60", created a new project, saved it, and clicked "log and capture", but FCP unexpectedly quit immediately after clicking. I tried multiple times and restarted my computer but it kept happening right after I clicked it. Why is it doing that?
As a side note, I've made dozens of movies using this version of FCP on my computer (SH, not HD) with this problem never happening before. Also, when I change my easy setup to regular NTSC right now and make a new project, "log and capture" works just fine. I also opened iMovie HD and captured and played back the 10 second test clip from the HX A1 perfectly.

I went to the apple store and the genius bar worker said he has seen this problem before. The only way he's gotten it to work is through a reinstall. So I'll try that soon and report if it worked.

Similar Messages

Final Cut Pro quits unexpectedly logging and capturing

If any of you are experiencing an "unexpectedly quit" when trying to log and capture, look at your error message panel. If it mentions "nsTODimporter plug-in" that's where you're problem lies. Go to your MAIN drive (not your HOME drive) and go to the LIBRARY. Look for your QUICKTIME folder and then for nsTODimporter.component file.... trash it. Your problems should be over.
Spoke to Tech support on this issue before I fixed it myself and they had me go through the dumping of preferences etc.... then dumping .pkg files for Final Cut, then a complete reinstall of FCP.... didn't do thing but was told by Tech support if that didn't fix it, I had a hardware issue and would need to take the tower in for repair.... NOT!!! Save yourself time and trouble and start with dumping the offending QUICKTIME plug in.
Hope that helps!
RC

This might be a clue:
http://discussions.apple.com/thread.jspa?threadID=1572190

FCP HD 4.5 quits when clicking Log and Capture window

I am running FCP 4.5 with a G4 dual 1.42 Ghz Tiger and everytime I click Log and capture FCP quits...I have uninstalled and reinstalled from my original disks and still no luck...have used FCP rescue...no luck.....
Really not having fun tonight...if there is any help out there I thank you in advance....
Sincerely
Kris

Welcome to the discussions, Kris.
Just to be sure, you did use the FCP Rescue for pre-rev5, right?
Next, what are you trying to capture from? Do you have anything else on the FW bus? An iSight camera can cause problems. I guess I should ask if you're trying to capture from FW.
Next, you re-installed your program, but FCP uses QuickTime to capture. Have you tried re-installing QuickTime? Use the procedure outlined in the top post in the discussions - the one about Camera Recognition - you may have a faulty install of QuickTime.
Post back,
Patrick

Log and capture freezes - please help

hi,
I'm using FCP 5 (studio). on G5 dual 2GH 1GB.
it has become a nightmare to log and capture. after few minutes from working with log and capture the applications freezes. I have to force quit FCP.
I trashed the preferences once, I re-installed, but the same thing is happening. I'm working on 2 projects, deadline is approaching.
I appreciate any helpful responses.
sz

Are you trying to record three video streams simultaneously? Or by a video amplifier, you mean a video switcher?
If you are using Capture Now, make sure you have set a capture limit. This is why:
When you use log and capture, the disk system is being asked by FCP to essentially "keep capturing until we tell you to stop ... and no, we don't know HOW much that will be either." It is stressful on the system to be continually wandering around looking for space to stuff those ones and zeros with out any sense of how many they have to accommodate. One solution available to the system is to allocate the ENTIRE empty space on the disk as the potential capture file. This essentially locks the machine as there is no headroom for basic disk operations.
However if you set a limit on capture now, say 60 minutes, the disk system can allocate the space and may seem to be less confused by the process. It still does not know EXACTLY how much you want, but it knows you will not want MORE THAN the limit and therefor can reduce some of the uncertainty.
Better yet is to record to a timecode addressable tape. This allows you to log the tape, then use batch capture. When you do this, the system knows EXACTLY how much space to allocate for each file and is very efficient.
Good luck.
x

Perturbing FCP 7 Log and Capture Question

I tried to digitize some HDV footage this afternoon, in theway I’ve always done it, but now suddenly it doesn’t work. Details to follow, but first my rig:
Mac Pro (Nehalem 2009) running Snow Leopard 10.6.8, NOFIREWIRE 400 PORTS
Final Cut Studio 2 with FCP 7
Sony Z1U HDV/SD videocamera connecting to Mac Pro via i.linkcable (aka firewire); I am using this to ingest because I can’t afford a deckat the moment. I know about thewear on the heads, etc., etc.
OWC Mercury Elite-Al Pro external media drive connected tocomputer via eSATA.
Here’s the scenario (keeping in mind that I’ve done thiscountless times in the past with no problems):
I connect the Z1U to the OWC drive with a 4-pin to 6-pinstandard FW 400 cable. I do thisbecause the Mac Pro does not have any FW 400 inputs but the OWC drivedoes. So I am in effect“daisy-chaining” and perhaps this is the problem.
I turn on the camera.
I start up FCP. It tells me: “Unable tolocate the following external devices: HDV (1440 x 1080) 60i.” After hitting “check again” a fewtimes, I hit “continue.”
I load my new project, into which I want to bring all thiswonderful HDV footage of my friends’ wedding. And, as I have done so many times, I hit command-8 to bringup the log and capture window.
To my horror, it says, “Unable to initialize capturedevice. Device is not connected orthe capture preset is not setup [sic] correctly.” Etc., etc.
I have read many posts here and elsewhere on similarproblems, so let me say what I have done:
I check Easy Setup: It says HDV – 1080i60, which is what it should say.
My Audio/Video Settings are:
Sequence Preset: HDV 1080i60
Capture Preset: HDV
Device Control Preset: Sony HDV Firewire
Video Playback: None
Audio Playback: Default
So now I go to my camera. It is set to output HDV. Component says 1080i/480i. i.LINK Convert is off. Down Convert says Squeeze, but I assume that’s meaningless since thei.LINK Convert is set to off. A/V>DV Out is set to off.
None of this makes a lick of difference, as far as I cantell.
I shut off the camera and disconnect the cable, thenreconnect the cable and turn it back on. No help.
I trash my FCP preferences, start FCP again, redo myprefs. Nothing.
I hit the reset button on the Z1U. Nada.
I do all this and then reboot the computer. Bupkis.
The footage was definitely shot in HDV. I can play it fine on the camerascreen.
I check the cable, which is brand new; it is firmly in placeon both ends.
Okay, so now I turned off the camera, quit FCP, ejected theOWC drive and turned it off. Iunplugged the eSATA cable. I wentand got my MacBook Pro and connected it to the OWC drive with a FW 800 cable. The camera was still connected to theOWC media drive via the i.LINK cable. I turned on the drive; I turned on the MacBook Pro; I turned on theZ1U. I started up FCP, and here’swhat happened:
It worked perfectly. No problem recognizing the camera, noproblem controlling it from the L&C window.
You might say that this solves my problem. But I prefer to edit on my desktopcomputer, and I am irritated that I can’t figure out what’s wrong. My suspicions are that it must havesomething to do with the cabling. FCP is working just fine with the Z1U routed through my media drive, theOWC. The only differences are thatmy drive is not connected to the computer via eSATA but FW 800. I see no differences in the settings.
Any insights?
Thanks,
Giraut

From what you say, I would suggest that the OWC enclosure does not utilize/energize the firewire interface when it is using the eSata.
This is just a guess.
Connect the Drive/Camera to your desktop via the FW800 cable: Mac Pro > FW800 Cable > OWC enclosure >FW 6Pin to 4 Pin Cable > HDV Camera. The speed difference between eSata and FW should be minimal as in each case you are limited by the FW400 connection at the camera.
MtD

Trouble logging and capturing

in the log and capture window, it says VTR OK at the bottom, but the preview is disabled - I can't see what I want to capture. Please help - urgent situation.

Not all Canon cameras have connection issues, but hanging around this site I've come to recognize their ability to connect in FCP is the most problematic of all the camera brands. If you have a Canon camcorder, and can not get it to connect up with FCP, the following is a way to sort through the issues and get it to work. Some are elegant - some are ugly.
Before we go any farther
-you should be using 'Firewire Basic' as the control protocol. If you aren't, go change it and try again.
-Also, verify that you have a solid installation of Quicktime. You may want to reinstall it using the 'delete receipts' method. Do a quick search here on the site - it is mentioned daily if not hourly.
With some confidence that the software installation and camera settings are correct ... the most direct solution is to purchase another, non-Canon device to use as your capturing machine. The Sony DSR-11 is highly recommended for DV work. A deck will save wear and tear on the camera's lightweight drive mechanism and will allow you to permanently connect a NTSC/PAL monitor for proper viewing. If you are working with HDV, you may have other issues ...
Beyond that, the path you take depends on the model of computer you own.
1. If you have a G5 tower or a MacPro, capture to a second internal drive with only the camera attached. If you need to move material to firewire drive, disconnect the camera. A second internal drive is quite inexpensive these days if you do not already have one.
2. If you have a G5 tower (PCI) MacPro (PCI), G4 powerbook (PCMCIA) or MacBookPro (Expresscard 43) with an available slot, purchase the appropriate firewire card for the slot. Connect your camera to the card and you should be good to go. The new card creates a unique bus and will avoid collisions with the external drives.
3. If you do not have a slot or a second internal drive and you are stuck with the camera, welcome to the camera/drive shuffle.
- shut down and remove the external hard drive(s) from the system
- connect the camera directly to the firewire port of the computer
- start the camera then the computer
- capture to your internal (system) hard drive
- shut down the camera and computer
- disconnect the camera and reconnect the external hard drive(s)
- start hard drive(s) and computer
- move captured files to external hard drive(s)
- edit
If you output back to tape or wish to view your work on an external Video (NTSC or PAL) monitor, you need to set up the camera to use the firewire out as the A/DV converter or VTR - which means reversing the steps:
- copy the file back to the internal drive
- shut everything down
- disconnect the external drive(s)
- connect the camera to the firewire port (and the TV to the camera if needed)
- start the camera then the computer
- play the file.
One caveat here - You may have difficulty getting the file back to tape without dropping frames. Playing files off of the system drive is very demanding and they may have a hard time keeping up.
All in all, if you do not have the option for second bus (i.e. iMacs, eMacs, iBooks, MacBooks) you may want to think about a computer with expandable options next time.
There is the option of capturing using iMovie, but that brings on it's own set of problems and is not recommended.
Good luck.
x

Logging and Capturing

As a result of this thread: http://discussions.apple.com/message.jspa?messageID=3857627#3857627
I did a test of various ways to capture footage into FCP. Sorry for saying this again but I’m new to FCP - after 20 some odd years editing with proprietary, Avid and Premiere Pro NLE’s. I mention this [again] because it is hard to teach an old dog new tricks, and some of the bias that I’ve gathered along the way might show up in the way I approached this.
I have four one hour HDV tapes recorded on a Sony HC1; I used the same camera that created the tapes to down convert and capture standard definition NTSC anamorphic DV. Each taped averaged about 70-80 clips.
Tape 1
The first tape I logged the clips using the controls in the log and capture window. Fairly straightforward, but the HC1 was not very responsive to the J/K/L keys and the image in the capture window was very low resolution during scrubbing and searching. This made the process of logging slower than it should be. Once logged, batch capturing was fairly quick [about 1:12:00:00 to capture a 60 minute tape] and pretty much what I expected.
This was not a very efficient way to capture 70-80 clips, a lot of time wasted with pre and post roll. If you had fewer, 20-50 this might be the better way to capture but for what I was doing this was my least favorite way.
Tape 2
After entering the clip information into the log window I hit K key and capture “Now” button and captured the entire tape. I was a little concerned at what would happen when timecode ran out at the end. Nothing happened, it stopped and the clip appeared in the capture bin – all was good.
Once captured I created a custom Browser window with only the columns I wanted to log and make subclips: [following Steve Braker’s instructions]
1) Loaded the master clip into the viewer.
2) Set in and out points for the first clip.
3) Command-U to create a subclip.
4) Re-named the subclip, added description and label.
5) Click in Viewer and
6) Repeated steps 2-5 until 70 clips later it was complete.
Steve suggested deleting or moving the master clip, however checking the folder in the finder where the master clip was store revealed that this process didn’t produce individual clips. Apparently the subclips are simply pointers to the master file so I didn’t delete it.
This process was surprisingly fast but I still ended up with a single file that was approximately 5GB’s which made this process almost useless for working with subclips in Motion2 for example.
Tape 3
Marked an [in and out] in 20 minute intervals to create three master clips for this reel.
1) Loaded the master clip part 1 of 3 into the viewer.
2) In the Mark menu selected DV Start/Stop
3) After FCP placed markers at the scene breaks I “clicked the disclosure triangle” next to the master clip to reveal all of the markers in the Browser.
4) Selected all of the markers to highlight them
5) Chose Modify>Make subclip after which the subclips appeared in the same bin as the master clip and markers [note* at this point I checked my hard drive to find there was still only one contiguous master file for these subclips.
6) Re-named each subclip, added description and label and then placed them in a separate bin and placed the subclips that I didn’t want to keep in a bin to be deleted. [temp trash]
7) Highlighted the subclips that I wanted to convert to Independent clips
8) Chose File>Media Manager
9) Chose Use Existing from the “Media referenced by selected clip” drop down.
10) Selected the “Delete unused media from selected clips.”
11) Chose Clip Names from the “Base media file names on” drop down (Oops, sorry that’s for a PC) pop-up menu.
12) Un-checked the “Duplicate selected clip and place into new project.” This placed the independent clips in the same folder on your hard drive as the master file for the subclips. I suspect although I did not test it that if I had this checked I could choose a different folder?
13) Held my breath and clicked OK!
14) That’s when FCP started treating me like a total idiot “are you sure you want to do this, you’d better be because there’s no going back. Are you really, really sure…” Anyway for me since this is the only project on this machine I didn’t even read the warnings [yes I am an impatient idiot] **** the torpedoes full steam ahead..
15) Done! NOT Quite yet. You’d think that since I un-checked the “Duplicate selected clip and place into new project,” that FCP would be smart enough to place the new clips in my project window. Didn’t happen, had to control click and import files.
This process requires a bit more explanation. I had 16 subclips that I converted to independent clips, after which I deleted all associated subclips and markers. When I imported files there were only seven clips in the folder where the master clips was saved [now deleted as part of this process].
On further inspection all of the footage that I wanted was there, HOWEVER, by using the DV Start/Stop to create markers and then using those markers to create subclips if there are two or more clips with continuous timecode it consolidates them into one contiguous clip thereby defeating the purpose of creating the subclips in the first place. I’m guessing but if I hadn’t deleted some of the subclips I didn’t want to convert I would have ended up with the same large file with a different name.
The manual recommends that you delete the master clip from the Browser before converting the subclips into individual clips. I was suspicious of the need to do this so I left it and after the conversion it did what I expected, became offline. It was a good thing because I could use it to recapture. Also, any logging with description and labels etc is history it is not included in the new independent clip.
Tape 3 Part 2
I won’t bore everyone with going through the steps I’ll just explain how this one was different.
1) I didn’t use the DV Start/Stop option, instead marked I/O separately leaving at least 2 frames between edits to make sure there was discontinuous timecode.
2) I also didn’t bother naming or logging at this point and left whatever ridiculous name the subclip process assigned.
3) The settings in the Media Manager were all set from the previous conversion hit OK [this time read the warnings which would have done nothing to correct the previous attempt].
4) 12 subclips went in and 12 new independent clips came out.
5) Once I had the new clips I logged and added descriptions and labels etc…
Although this sounds like a very convoluted process, and it is certainly much more difficult than it needs to be, by the fourth tape it was predictable and quite fast.
I will say though that because FCP consolidated any continuous clips without warning you really have to pay attention to detail. And it would be nice if we could use the log & capture window for this process so any descriptions, labels etc would be carried forward to the new clip.
Certainly not as easy to accomplish as it is in PPro but definitely possible. There might be more functionality that I just missed, if so please let me know. Anything that can be done to simplify this would be helpful.
Mac Pro. 5GB RAM. 1TB SATAII RAID 0. Mac OS X (10.4.8) FCP 5.1.2

When you delete the master clip from the browser, you aren't deleting the media file it referenced. So the subclips reference that same original captured QT movie, it's just not in your project.
It will work. try it. It's how I've been working for about 6 years now. I don't have problems with subclips at all doing anything I want to with them.
Subclips are nothing more than reference files that reference a portion of a master clip. A Master clip is nothing more than a reference to the media file that you're capturing... it's not the media it's a reference to it.
Subclips are how FCP was really intended to be logged I think. I don't like long captures at all, and would prefer to actually capture the way you did the first time... but because it takes longer, I usually don't have time to do things that way. However, if you do things that way, you can add descriptions etc. to the logged clip in the Log and Capture window, if that helps your workflow.
The responsivness you lack with your HDV camera is because it's HDV... HDV doesn't contain all of the pixels of every frame, so to see a single frame the computer has to do a lot of processing to show it to you. It's an MPEG stream, which uses whole frame information every 8 or 15 frames only. The rest of the frames are the difference between the frames only on the recorded tape, thus the work and slow response to HDV logging and capturing.
P2 on the other hand, would make ALL of this MUCH easier to deal with. For one thing, each take is an individual file, and it's an all I frame format so it's easier for the computer to deal with. It renders 8 times faster than HDV does... no "conforming" necessary.
Jerry

Crash upon opening Log and Capture

I'm working with a friend to solve her FCP problem. Everytime she opens the log and capture window FCP crashes. When she starts up FCP they are greeted with the DV NTSC Device is not connected message even if the camera is conected and on. Doing a refresh AV devices does nothing. iMovie recognizes the camera just fine and will control it and capture from the camera which is a Panasonic PV-GS500. I have had her trash her preferences, do an un-install and re-install and repair her permissions on the computer as well. What could be causing this? Does anybody else have any more suggestions?

A few questions back to you, Andrew.
Has this camcorder ever worked with her Mac & FCP in the past, or is this the first try hooking the two together?
Have you tried using a different firewire cable, and/or connecting the camera to a different Mac with FCP installed? Or, have you tried connecting a different camcorder to her Mac?
Does FCP crash when opening Log & Capture even if, in fact, nothing is connected?
A little info about the Mac might be useful, like which model is it, which version of the OS, Quicktime, and FCP are installed?
With my G4, an older OS and a previous version of FCP, sometimes the same thing would happen to me (FCP didn't recognize a camcorder was attached). Changing the startup sequence around usually did the trick -- like start the Mac, then plug in the firewire, turn on the camera, open FCP. Or, plug in firewire, turn on camera, turn on Mac, etc. etc.
MBP 17" w/max memory; and a souped-up G4 that's still useful Mac OS X (10.4.8) FCS, CS2 pkg

Trying to capture DV material, log and capture spinning beach ball

I have not worked in DV for quite awhile. I am trying to just capture a few minutes and the log and capture window gives me the beach ball of death when I hit capture now. If I hit play all seems fine, but try and capture and the beach ball shows up. What gives?
Best.
Tom

Problem solved. Bad Cable.

Cannot log and capture!!

hi,
for some wierd reason i cannot seem to log and capture from my Canon XM2 anymore, and has only been actin up recently. bought new firewire 4-6pin, camera and cable works fine from my college's mac pro.
basically, sometimes when i try the log and capture, bottom reads "vtr ok" and i can operate the camera - but only for a few seconds! then it changes to "no communication". other times i'm not even lucky to get this far; fcp won't read the device.
Checked system profile, it reads my camera plugged in... but i still have my suspicions the firewire port may be blown
is it possible the new 6.0.3 update may have caused this capturing problem? it seems to be working fine before i updated...
anyone recommend i reinstall FCP6?
any help is seriously appreciated as i need to get this up and running urgently for an assignment..
Thnx
OptikroniX
FCP 6.0.3
Canon XM2
MBP 17"

no i don't, just the camera.
also.. i've tried capturing in Quicktime and seemed fine. then it stopped working after a while. thats also hit and miss at times :S
i tried time machine. to replace fcp 6.0.3 with 6.0.2... however other files from the pro kit 2008-1 update are too new for FCP to run properly..
is there a way to reverse the update?
Message was edited by: OptikroniX

Log and capturing

whenever i try to log and capture, FCP quits when its "initializing log and capture" im pretty new to this. can someone please help?

What version of FCP are you using? And are you using QuickTime 7?
You may try this:
http://docs.info.apple.com/article.html?artnum=301852

Unable to Log and Capture AND make FCP a boot disk

I am unable to go into Log and Capture mode in FCP 4. I can capture from firewire using I movie just fine so I know the sytem works. The minute I open Log and Capture from within FCP (with the JVC Mini-DV camera hooked up thru Firewire), it crashes. Help. I upgraded from FCP 3 to FCP 4 a couple years ago and it hasn't worked right since. Would re-installing the FCP 4 upgrade work? Also, my system works very sluggish. Please explain to me how I would make the veersion of FCP 4 my boot disk. I realize that I can't have the FCP 4 application and the media on the same drive but is there a way to partition one of my drives and make FCP one of the startup disks? Hope this isn't too confusing. Thanks.

First off, FCP 4 was darn unstable. FCP 4.5 is a free upgrade and is STILL the most stable version out there. FCP 5 is getting there.
Secondly, try:
Shane's Stock Tip Mantra: If the program was working fine, and now isn't, or just isn't working the way it should, the first things to do are:
1) Trash your FCP preferences. Download the appropriate version of FCP Rescue at http://fcprescue.andersholck.com/ and run it.
2) Open the Disk Utility and Repair Permissions.
As for partitioning the hard drive, that isn't necessary. Hasn't been since FCP 3.
Shane

Log and capture problems for HDV using FCP 5.0.1

I cant seem to get a picture in my log and capture browser when using HDV. The screen says my camera is connected, I see timecode correctly rolling in sync with my cameras timecode, I can use the controls, but no picture on the screen?
When I hit capture now, the capture screen pops up and gives a message "waiting for data from device".
we shot at 720p at 25fps, there is no capture preset for this in my version of FCP. Could this be the problem? Please help!!

Thanks for responding.
It's a mac osx 10.4.11 and a 2 ghz intel core duo. I'm using easy set up in final cut pro, but there is no option for hd fire wire basic (which apple support told me to look for). The only hd options are 1080i50, i60 and 720 p30. The other hd options are for the apple intermediate codec. When I use the easy set up for hd 1080i60, then go to log and capture, it doesn't give me the preview window to set in's out, batch capture etc. It only lets me capture straight from the camera and I have to manually stop it and start it which is a major pain. Plus the clips need to be rendered once I put them in a timeline. I've shot and edited on mini dv with final cut for nearly 7 years, but now that i've tried to upgrade and shoot hd mini dv, all of these problems have arrived in capturing. I'm starting to think my version of final cut pro (5.0.1) just doesn't work with hd, unless it's very time consuming. Any ideas?

Log and Capture in FCP 6.0.5 flash red frames

So I have been having a very odd and troubling issue during my log and capture stage in post production, whenever I try to import a tape into FCP I get this intermittent red colored frame that flashes for what I could only guess is a frame and it happens probably every ten frames or so; I've tried every combination of hardware troubleshooting from a different deck and camera, tapes from all different times and cameras and formats, different firewire cables and even different firewire ports.
Has anyone has any experience with this or even anything like this, and if so how can I make it stop, I have even tried that final cut maintenance program and basically everything short of a clean reinstall... do I really have to go that far!?

Some users have success with the newer drivers others not so fortunate.
Read through this thread:
http://discussions.apple.com/thread.jspa?threadID=2676952&tstart=0
Al

No Audio during Log and Capture

Hello, I have FCP 6.0 and am unable to hear my audio during log and capture. I have this problem on all 5 G5 Macs that I have, and have tried different editing docks and cables. I have used FCP for more than 5 years and have never had this problem. iMovie has audio during capture, so I am convinced that there is a pre-set in FCP that I don't have checked properly, but I've been over them many times and still have no answer. I searched past forums and didn't really find anything helpful to me.
My pre-sets are set to DV NTSC 48kHz and the playback pre-sets are set to default. I can hear audio of my clips after I log and capture, but I still need to hear audio during importing. I'm more confused than anything. If anybody has had this problem before or any suggestions for me, I'm all ears.
Thanks.
John

... as Bogie says.
However... this is a non-feature that dates back to slower CPU days... yet, still with all the different formats and such I (ME!!) I believe it's still good practice to leave it off.
Devoting as much CPU work to the capture process lessens the chance for something to go wrong. You can easily monitor the audio directly out of the deck as needed.
Sure -- octo cores need 30 apps open just to get your money's worth and I'm sure you won't have any issues using an 8th of one to send audio thru itself while the other 7 and 7/8ths are used for capture... but who wants to risk it?
Not me... I'm to old to change my ways.
Blast you FCP v1.2.5 on a beige G3 with 7gig and 15gig hard drive -- you taught me well.
CaptM

"log and capture" causing unexpected quits

Similar Messages

Maybe you are looking for