Crashing after Log and Transfer

I am experiencing a FCP crash after using Log and Transfer to import P2 files.  The material is on an external FW800 drive.  I go to Add Custom Path in the Log and Transfer dialog box, point the software to the CONTENTS folder of each captured P2 card, the list populates with the clips, I drag the files into the que, and they import as usual.  All is well and good until I X out of Log and Transfer, and when I do that, FCP crashes.  I have not experienced this when capturing directly from a camera. This has happened over and over since beginning this project, and we are still yet to get all the material into the machine for editing. 
Also, in case it is pertinent, I am using a MacBook Pro 2.2 GHz Core i7 machine with 8GB RAM.
Any ideas or has anyone else experienced this?  Thanks in advance!
-Van

First thing I'd try is trashing your preferences.  Google preference manager from digital rebellion.  It's a free download and in invaluable.  It's so cool you'll WANT to pay for it.  It allows you to store a good set of preferences, trash them when they get funky and then restore the good set, including all the cool stuff you created.
ANYWAY,  I'm in the habit of saving every which way from Tuesday after something interesting has happened, like a capture or L&T.  I know that's not a solution, but a best practice.  hopefully a pref trash will set you right.

Similar Messages

  • Help!  Final Cut Express crashes on Log and Transfer

    Hi,
    I am using a Canon Vixia HFS20 (AVCHD) and a Mac Book Pro (running snow leopard) , with a 1 tb My Book as scratch disk.
    I have upgraded the software.
    In Easy Setup, I selected AVCHD 1920x1080i60, after checking the camera and seeing that it is recording with 60i.
    Log and Transfer opens, but then final cut express immediately crashes.
    Please advise! Thank you so much,
    Anne

    What happens if you remove the external drive and try a test capture to the MAC directly?
    How is the external connected? eg. USB
    Is the external formatted to MAC OS Extended?
    Al

  • FCP 7 crashes in log and transfer (NSMallocException)

    FCP 7 crashes about 50 minutes or so into log and trasfering my AVCHD footage. It throws a "NSMallocException" error as follows:
    Application Specific Information:
    *** Terminating app due to uncaught exception 'NSMallocException', reason: '*** -[NSConcreteMutableData appendBytes:length:]: unable to allocate memory for length (73874)'
    *** Call stack at first throw:
    Is there any way around this painful problem
    Or are there alternative ways of transfering AVCHD clips into pro res without using FCP log and transfer?

    The capture scratch is to an external Raid with about 2TB free.
    Clip2Wrap2 looks great, I'll give it a try. My main concern is that it might be slower than FCP. I've got two weeks of filming to do, with 6 programs a day. I'm trying to the footage copied to the computer, then have it transfering into final cut while the next section is being filmed. So it needs to transfer fairly quickly. I've tried a few other AVCHD converters, but they're painfully slow.

  • FCP crashing on log and transfer

    I have been experiencing this problem for quite some time and sort of got used to it. However I thought I'd throw it at the FCP experts and see if they have an answer. I shoot on AVCHD virtually every time I go to "Log and transfer" and select any file either in multiples of singly, the programme crashes. I reopen it and from then on it works perfectly, until I eject one card and replace it with another and then more often than not the programme will crash again. On occasion it works fine, but 90% of the time FCP will crash on the first transfer until it is reopened.
    I encode the AVCHD to 1920x1080 50i Pro res LT. I have tried other settings and it still crashes.
    Any ideas?

    Have you tried copying the card to a local hard drive?  Make sure you copy the entire card contents and maintain the folder structure.  It's also crucial that you back up the cards, so this isn't a bad way to start. 
    Not sure what's going on in your case, but I gotta say that I've found a lot of card readers are problematic to say the least.   Have you tried different card readers or connecting the camera directly to the mac via usb?

  • ARTIFACTS AFTER LOG AND TRANSFER! please help!

    i was given a p2 card to log and transfer. after my first attempt to log and transfer, the sound was way out of sync and the video was strobing. then i deselected the option to remove advanced pulldown and drop frames from the settings preferences. i then log and transfered again and this seemed to fix the initial problems. however, now my clips have artifacts every few seconds that look like little patches of random colors. what are these and how can i fix them. any help is greatly appreciated. thanx.

    In the L&T window...play the footage. Can you see them there? If you don't have P2CMS from Panasonic, download it and use it to view the footage. See if this break up is on the original footage.
    I have seen this, but it appeared on the master footage.
    Shane

  • Constant crashes during log and transfer

    Whenever I try to use log and transfer to import a clip FCP crashes. Here's some info on my system
    Mac Pro 6 Core 3.33GHz 8GB RAM
    FCP 7.0.3
    Mac OS 10.6.4
    Source footage is AVCHD recorded to SD card from a Sony NX5U
    Tried importing directly from the SD card as well as copying the entire SD card folder structure to a local drive - neither works
    I have tried different cards, different cameras (same model), and different computers and all do the same thing.
    Here's a crash log from the most recent crash:
    Process: Final Cut Pro [391]
    Path: /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro
    Identifier: com.apple.FinalCutPro
    Version: 7.0.3 (7.0.3)
    Build Info: FCPApp-1008261348~8
    Code Type: X86 (Native)
    Parent Process: launchd [189]
    Date/Time: 2010-10-07 16:35:12.845 -0500
    OS Version: Mac OS X 10.6.4 (10F2521)
    Report Version: 6
    Exception Type: EXC_BREAKPOINT (SIGTRAP)
    Exception Codes: 0x0000000000000002, 0x0000000000000000
    Crashed Thread: 44
    Application Specific Information:
    * Terminating app due to uncaught exception 'NSMallocException', reason: '* -[NSConcreteMutableData appendBytes:length:]: unable to allocate memory for length (82341)'
    * Call stack at first throw:
    44 CoreMediaIOServicesPrivate 0x0103389a ZN8MIOGraph15PullOutputUnitsEbRbS0_S0 + 348
    Thread 44 Crashed:
    0 com.apple.CoreFoundation 0x978daa07 __TERMINATING_DUE_TO_UNCAUGHT_EXCEPTION__ + 7
    1 libobjc.A.dylib 0x94bca509 objcexceptionthrow + 56
    2 com.apple.CoreFoundation 0x9788f8e8 +[NSException raise:format:arguments:] + 136
    3 com.apple.CoreFoundation 0x9788f85a +[NSException raise:format:] + 58
    4 com.apple.Foundation 0x91cb9835 _NSMutableDataGrowBytes + 1154
    5 com.apple.Foundation 0x91cb9343 -[NSConcreteMutableData appendBytes:length:] + 75
    6 com.apple.AVCHDPlugin 0x49499cd1 0x49489000 + 68817
    7 com.apple.AVCHDPlugin 0x49493db3 0x49489000 + 44467
    8 com.apple.proapps.MIO 0x00faa2cb TundraPluginCallbackProc + 355
    9 com.apple.TundraComponent 0x47b87d44 TundraUnitHALInputEntry + 12756
    10 com.apple.TundraComponent 0x47b2037d 0x47b13000 + 54141
    11 com.apple.TundraComponent 0x47b546bf TundraUnitMPEG2DemuxEntry + 22037
    12 com.apple.TundraComponent 0x47b8f5e6 TundraUnitVDIGInputEntry + 13711
    13 com.apple.TundraComponent 0x47ba44ff TundraUnitMPEG2MuxEntry + 11138
    14 com.apple.TundraComponent 0x47b2037d 0x47b13000 + 54141
    15 com.apple.TundraComponent 0x47b546bf TundraUnitMPEG2DemuxEntry + 22037
    16 com.apple.TundraComponent 0x47b8f5e6 TundraUnitVDIGInputEntry + 13711
    17 com.apple.TundraComponent 0x47ba5f6a TundraUnitMPEG2MuxEntry + 17901
    18 com.apple.TundraComponent 0x47b2037d 0x47b13000 + 54141
    19 com.apple.TundraComponent 0x47b546bf TundraUnitMPEG2DemuxEntry + 22037
    20 com.apple.TundraComponent 0x47b8f5e6 TundraUnitVDIGInputEntry + 13711
    21 com.apple.TundraComponent 0x47ba5f6a TundraUnitMPEG2MuxEntry + 17901
    22 com.apple.TundraComponent 0x47b2037d 0x47b13000 + 54141
    23 com.apple.TundraComponent 0x47b546bf TundraUnitMPEG2DemuxEntry + 22037
    24 com.apple.TundraComponent 0x47b8f5e6 TundraUnitVDIGInputEntry + 13711
    25 com.apple.TundraComponent 0x47b8ffe1 TundraUnitVDIGInputEntry + 16266
    26 com.apple.TundraComponent 0x47b2037d 0x47b13000 + 54141
    27 com.apple.TundraComponent 0x47b546bf TundraUnitMPEG2DemuxEntry + 22037
    28 com.apple.TundraComponent 0x47b8f5e6 TundraUnitVDIGInputEntry + 13711
    29 com.apple.TundraComponent 0x47ba44ff TundraUnitMPEG2MuxEntry + 11138
    30 com.apple.TundraComponent 0x47b2037d 0x47b13000 + 54141
    31 com.apple.TundraComponent 0x47b546bf TundraUnitMPEG2DemuxEntry + 22037
    32 com.apple.TundraComponent 0x47b8f5e6 TundraUnitVDIGInputEntry + 13711
    33 com.apple.TundraComponent 0x47ba5f6a TundraUnitMPEG2MuxEntry + 17901
    34 com.apple.TundraComponent 0x47b2037d 0x47b13000 + 54141
    35 com.apple.TundraComponent 0x47b546bf TundraUnitMPEG2DemuxEntry + 22037
    36 com.apple.TundraComponent 0x47b8f5e6 TundraUnitVDIGInputEntry + 13711
    37 com.apple.TundraComponent 0x47bb262a TundraUnitAudioOutputEntry + 18972
    38 com.apple.TundraComponent 0x47b2037d 0x47b13000 + 54141
    39 com.apple.TundraComponent 0x47bb1ed8 TundraUnitAudioOutputEntry + 17098
    40 com.apple.TundraComponent 0x47bb1e7e TundraUnitAudioOutputEntry + 17008
    41 com.apple.TundraComponent 0x47bc9519 TundraUnitBFrameFileOutputEntry + 25068
    42 ...ple.CoreServices.CarbonCore 0x973bad19 CallComponentDispatch + 29
    43 ....CoreMediaIOServicesPrivate 0x0104e66e TundraOutputUnitComponentCallRender + 49
    44 ....CoreMediaIOServicesPrivate 0x0103389a MIOGraph::PullOutputUnits(bool, bool&, bool&, bool&) + 348
    45 ....CoreMediaIOServicesPrivate 0x010345d4 MIOGraph::PullAndProcessThreadEntry() + 632
    46 ....CoreMediaIOServicesPrivate 0x010356db MIOGraph::_PullAndProcessThread(MIOThreadPriv*) + 495
    47 ....CoreMediaIOServicesPrivate 0x01041433 start_thread + 61
    48 libSystem.B.dylib 0x95bd281d pthreadstart + 345
    49 libSystem.B.dylib 0x95bd26a2 thread_start + 34
    Any thoughts? One of the lines in the crash report say unable to allocate memory, but there is plenty of free memory when this happens (2GB+). Also, I don't think it's bad RAM since this happens on multiple computers.

    I'm having the exact same problem trying to edit a church service shot with the Sony HXR-NX5U recording AVCHD on SDHC cards. I'm using Final Cut Pro 7.0.3 on a Quad Core Intel Mac Pro running OS 10.6.4.
    Some of the shorter clips logged and captured successfully, but the 1 hr. clips crash each time I try. Shane Ross recommended locking the SD cards before log & capture. I failed to do this with the first attempt, but did so afterward. Then I archived the cards by making Disk Images of them. Shane says that a Mac will write code on an unlocked SD card when first inserted and that this can interfere with editing work. Could I have hosed my data by not locking the card the first time?
    This is very depressing, because if I can't depend on the recorded source footage, the cam becomes a very expensive paperweight. I am extremely disappointed with FCP.
    Peter

  • Crashes Upon Log and Transfer no Perian on system

    That's basically my issue, trying to import AVHCD. I cannot locate any "Perian" anywhere on the system. I deleted preferences as it still crashes, it had worked fine previously but randomly is not. Any help would be appreciated.

    The only thing that has changed is that it crashes. I go into Log and Transfer, and sometimes once in it crashes before I can do anything else, and others when I select a custom path, the camera doesn't come up immediately anymore and the external hard drive we copied the SD files from the camera also results in it crashing. None of these were changed either.

  • Trying to delete original files on card after Log and Transfer in FC 7

    Log and transfer is working great. But how do I delete the original files on my 32 gb class 6 card? Can't just select and hit delete. In fact theres a typo in the pop up box, "Warning, The selected media cannot deleted". They forgot the "be". Weird.

    Hi,
    as you have seen already, you can't delete those files using the L&T menu; however you can delete those files either from within the camera's menu or accessing the card directly from the OSX.
    Regards,
    Armando.

  • After Log and transfer, does FCE creat a copy of the clips on my camcorder?

    Where does it save them to if yes?
    Thanks for any input

    Welcome to the world of digital video. Yes, it does consume large amounts of disk space, and you should expect to purchase one or more external FireWire hard drives if you get into this in a meaningful way..
    When you log & transfer your video with FCE, the video is transcoded to Apple Intermediate Codec for editing. Depending on how you shoot (720 vs 1080) your video will take 25GB-50GB per hour of video. Here's more info about AIC -> About HDV and the Apple Intermediate Codec.

  • Date of video recording missing after "Log and Transfer"?

    Hello, I am importing AVCHD video from Sony HDR-SR10. The clip item properties have not imported the dates when the video was recorded. It just has a date of Last Modified.
    Is it hidden anywhere or can I add it to the file/clip?

    Hi
    OR - there is a Paper and Clip solution - Tedious but working.
    (At least with old SD-video from miniDV tape Cameras)
    A Double import/Capture is needed
    a. via FireWire - the full quality video (without meta data)
    b. analog out from Camera (set to show Date & Time) - to an A/D box and import
    this
    (alt way Camera to a VHS/VCR then back to or via Camera to Mac)
    Now put High quality sequence on track 1 and analog copy on track 2
    crop analog copy on track 2 to show Date & Time Only.
    Yours Bengt W

  • SONY XDCAM LOG and TRANSFER CRASHING FCP

    I am trying to log and transfer xd cam footage. every time i open the log and transfer window, FCP crashes. What is the cleanest way to get rid of the xdcam plugin.
    the error message reads:
    The application Final Cut Pro quit unexpectedly after it was relaunched. The problem may have been caused by the SonyXDCAM plug-in.
    I have tried to get rid of it and obviously failed because i keep getting that message which tells me it's still there.
    Can someone give me a step by step on how to get rid of it?
    Model Name: Mac Pro
    Model Identifier: MacPro3,1
    Processor Name: Quad-Core Intel Xeon
    Processor Speed: 3.2 GHz
    Number Of Processors: 2
    Total Number Of Cores: 8
    L2 Cache (per processor): 12 MB
    Memory: 8 GB
    Bus Speed: 1.6 GHz

    Shane's Stock Answer #44: FCP acting weird or unusual. Just not like is normally should
    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 Preference Manager from Digital Rebellion: http://www.digitalrebellion.com/pref_man.htm
    http://www.kenstone.net/fcphomepage/trashing_fcpprefs.html
    2) Open the Disk Utility and Repair Permissions.
    3) Shut down for 10 min. Go for a quick walk around the block and get SOME exercise today. Come back, turn on the computer and see how things are.
    4) (optional) Do the Hokey Pokey and turn your self about. Results may vary.
    Shane

  • Log and transfer inevitably crashing FCP

    We're editing a couple of music video in FCP 6.0.1.
    we shot with an HMC150 so the clips are being uploaded from an SDHC in an AVCHD folder via log and transfer. the first video went relatively fine barring several problems with log and transfer (files not matching thumbnails, files corrupting, FCP crashing) the problems seem to be random and inconsistent, as issues like a misplaced thumbnail or corrupted import could be reopened and fixed so there was no way to tell exactly why each thing was happening. eventually it all subsided and work went smoothly.
    went on to finish video number two and after several imports the log and transfer feature has decided to be the death of the project. Choosing log and transfer inevitably leads to an almost instant crash of FCP unless all drives it's reading from are disconnected. reinserting any drive means an instant crash. the drives are not corrupt and function just fine with any and all other programs, even imovie.
    why in the world can't i get FCP to stay alive when i open the log and transfer? please help.

    Right - I've solved this one. It turned out that I'd recorded some 1080p50 footage. The mere presence of this on the card freaked Log & Transfer. The camera doesn't make it easy by hiding that footage when you're looking at 1080i25 (or whatever "normal" mode is).

  • Log and Transfer Crashing FCP

    Not sure what is going on. Been using Log and Transfer for 8 months to capture video from P2 Cards in Panasonic HVX200 recorded in 720p60. Haven't had a problem before. Today, went to capture new footage (only about 15 minutes worth) and the first time I briefly saw the dialog window before FCP crashed, but since then, after restarting, closing the open files, creating a new project, making sure software was up to date, etc, it keeps crashing before even showing the window. I just get the 'spinning beachball of death' for about 5 seconds before the crash.
    I also tried just transferring the files to the local drive first than running the log and transfer, but that didn't work either.
    I don't have FCP tricked out with any plug-ins, with the exception of Flip for Mac, but that has been running fine for all 8 months.
    Any ideas?

    Shane's Stock Answer #44: FCP acting weird or unusual. Just not like is normally should
    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 Preference Manager from Digital Rebellion: http://www.digitalrebellion.com/pref_man.htm
    http://www.kenstone.net/fcphomepage/trashing_fcpprefs.html
    2) Open the Disk Utility and Repair Permissions.
    3) Shut down for 10 min. Go for a quick walk around the block and get SOME exercise today. Come back, turn on the computer and see how things are.
    4) (optional) Do the Hokey Pokey and turn your self about. Results may vary.
    Shane

  • Log and Transfer Crash FCP 6.06, from Canon Vixia HF20

    I am having a strange problem in logging and transferring from FCP 6.06. I have been logging and transferring from my Canon Vixia HF20 without any problems for monthes. Then I have been granted access to a Sony HXR-NX5U NXCAM from work, I logged and Transferred from the flash memory unit HXR-FMU128, without any problems. But ever since I logged and Transfered from the sony flash unit, in attempting to log an transfer from my Canon Vixia has caused FCP to crash every single time. I then log and transfer again from the Sony Flash unit without any problems, after having dealt with the Canon transfer crashes.
    Currently log and transfer from Song Flash unit always works, from Canon Vixia never works in FCO 6.06.....boooOOO!
    Anyone else experience a problem like this?

    Hi Eugene
    Seems like maybe your FCP's preferences have taken a turn for the worse ... at least I haven't heard of this being a widespread issue so I would recommend you start by using a free app like Digital Rebellion's Preference Manager to make a backup copy of your current FCP user preferences, then use the same Preference Manager app to "trash" those existing prefs. Now restart FCP and see if the problem still persists .. hopefully not. If the problem is still there then you can use Preference Manager (again) to restore your previous prefs from the backup copy you made ... and you are back where you started.
    Post back
    Andy

  • AVCHD Crashes FCP on Log and Transfer *SURPRISE*

    OK after days of scouring the net I've not been able to come up with a solution...
    I'm running FCP v7 on a quad core Intel mac with 8Gb's RAM
    Whenever I open the Log and Transfer window to attempt to import my AVCHD footage I get the beach-ball of death and a crash.
    iMovie crashes as well if I attempt an import.
    The files are .mts from the new Sony Pov cam
    And yes, I've disabled Perian
    Failing a solution I'm about to ditch Final Cut and go with Premier Pro which now seems to be streets ahead of FCP!
    Any help would be much appreciated

    Sounds like Premiere is indeed the best option, if it's working for you now, and there's a deadline ahead.
    Best of luck with it.

Maybe you are looking for

  • ITunes won't stay authorized...

    Not sure when this started but everytime now I open iTunes and try to play a song, watch a movie or listen to an audiobook, I get the "This computer is not authorized" message. I put in my username and password and then I get "You have authorized 3 o

  • I have given up on BB & Mac

    When I got my Curve last May I was told that it was 100% compatible with Macs. Wrong, wrong, wrong. I have tried PocketMac and basically just given up. They have tried to help me and RIM has tried to help me but have been unable to fix the problem. I

  • Photo Order in iCloud Sharing

    How can I keep my photos in the same order as they are in the album, once I upload to iCloud Photo Sharing?

  • Recording sound with Soundbooth

    I managed to record sound with the system 'sound recorder', but when I try to record sound in soundbooth with the same mic (simple cheap mic) there is nothing showing on the meter and nothing records. Can somebody please explain to me what is the pro

  • Text Reflow

    I am loading a UILoader in AS3 and am dropping it on top of two Dynamic Text fields. I need the text to reflow around the picture if it loads and to remain where it is if there is no picture loading. I do not see any method in the UILoader class to a