Log and Transfer_FCP6/HELP!

Please help me out
I read all the messages regarding this  topic on the forum and I tried everything__still doesn't work.
here's my situation: I have a iMac 10.5.4, FCP6.0, VIXIA HF10 Canon and I can't log and transfer.
a) I connected the power adaptor to the camera and the usb cable.
b) Selected PC/print in the camcorder. Then the icon (orangeHD) come up on the desktop. Then, I opened FCP6.
c) My setting in  are  Format: AIC   Using: HDV-AIC 1080i60 Capture: HDV-AIC Control(?) Sony HDfirewire( I don't know what to select-there isn't usb as an option)
d) Then I clicked on capture and transfer-then play in the window - nothing-
PLEASE HELP ME OUT"""" I have been working on this for days.

I'll assume you area actually selecting "Log and Transfer" since there isn't a menu option for "capture and transfer" (as you state in your message). You don't need to worry about the sequence settings, as those can be automatically adjusted upon inserting your first clip onto the timeline. FCP will ask if you want to match the sequence setting to the clip parameters, but in any event it is unimportant to the task of ingesting AVCHD footage.
I use a different AVCHD camcorder (Sony HDR-CX7) but the workflow should be the same. You insert your media or otherwise mount your media drive (in your case by attaching the USB cable). Then open FCP and select the "Log and Transfer" menu item. After opening, you might need to select the folder icon in the upper left corner and select your camcorder media drive, then give the app a little time to find the clips and display them with thumbnails. After that you can import them in batch or singly. There are a few settings you can change to suit your timeline specifics, such as the default format (Apple ProRes or AIC) and also the audio format. Log and Transfer actually converts the AVCHD clips into something editable by FCP (one of the aforementioned formats) and places a Quicktime movie of the clips into the capture scratch disk.
It can be a bit quirky at times, but ingesting AVCHD seems to work quite well and on my system the clips are converted very quickly.
Good Luck and Happy Editing!

Similar Messages

  • Media offline after log and capture HELP!!!!

    hi,
    i am capturing media from my camera from dv tape into FCP,
    i log and capture the footage and all seems fine, i've done this hundreds of times before.
    today however when i log and capture the file comes up as media offline (file logo with red line through it) in the browser window, i need to get this file done asap!! HELP!!
    Message was edited by: Modern Video

    i have a deck and i've tried coming from the deck, but its giving me fallout due to deck issues i have, so i'm coming from the camera. when i log and cap i get the file with the red line.
    when i try to reconnect it to a file all i have in the capture scratch folder is the bad file from the deck.
    so i cant reconnect the media from what i have captured already.
    so essentially my problem is that from my camera, i log and capture and get a file that does not go into capture scratch and yet still comes up as an unconnected media file in the browser!!??

  • Random Kernel attacks ... can you have a look at the log and maybe help me out?

    Hello,
    i have an old macbookpro since 2006 and i am getting random kernel attacks during booting up. Here is a copy of the log that i dont understand at all. Can someone have a look at it so that if a peripheral is responsible i could remove it etc? Thank you very much in advance...
    Interval Since Last Panic Report:  1014086 sec
    Panics Since Last Report:          1
    Anonymous UUID:                    715B81C9-84E0-46BE-BAA4-7B9F69D717E2
    Thu Mar 13 19:41:46 2014
    panic(cpu 1 caller 0x30c210): "vnode_rele_ext: vp 0xadda940 usecount -ve : -1.  v_tag = 16, v_type = 1, v_flag = 84800."@/SourceCache/xnu/xnu-1699.32.7/bsd/vfs/vfs_subr.c:1711
    Backtrace (CPU 1), Frame : Return Address (4 potential args on stack)
    0x48a43908 : 0x2203de (0x6b08cc 0x48a43928 0x229fb0 0x0)
    0x48a43938 : 0x30c210 (0x6c33e0 0xadda940 0xffffffff 0x10)
    0x48a43968 : 0x30e109 (0xadda940 0x0 0x0 0x0)
    0x48a43988 : 0x48a5237b (0xadda940 0x1 0x29794f74 0x15f)
    0x48a439a8 : 0x48a531a8 (0x8b15000 0x6d51330 0x20 0x48a54aa8)
    0x48a43b98 : 0x48a5426e (0xadda940 0x7e48b54 0x6002f04 0x2)
    0x48a43bb8 : 0x54d297 (0x6002f04 0x0 0x2 0x7e48b54)
    0x48a43be8 : 0x30863e (0x6110a04 0x6002f04 0x2 0x7e48b54)
    0x48a43c28 : 0x322aa8 (0xadda940 0x48a43e50 0x8001 0x7e48b54)
    0x48a43c88 : 0x31aea0 (0x48a43d20 0x48a43ce8 0x48a43e80 0x7e48b54)
    0x48a43cf8 : 0x31b4ad (0x7e48b54 0x48a43d20 0x8000 0x48a43e80)
    0x48a43f78 : 0x5f3c2a (0x6441918 0x867bad4 0x7e48a98 0x0)
    0x48a43fc8 : 0x2e60a7 (0x867bad0 0x0 0x10 0x867bad0)
          Kernel Extensions in backtrace:
             com.sophos.kext.sav(8.0.14)[9C551297-42E6-4D0D-8221-F4456D0099D5]@0x48a51000->0 x48a56fff
    BSD process name corresponding to current thread: notifyd
    Mac OS version:
    11G63
    Kernel version:
    Darwin Kernel Version 11.4.2: Thu Aug 23 16:26:45 PDT 2012; root:xnu-1699.32.7~1/RELEASE_I386
    Kernel UUID: 859B45FB-14BB-35ED-B823-08393C63E13B
    System model name: MacBookPro2,2 (Mac-F42187C8)
    System uptime in nanoseconds: 908326037068
    last loaded kext at 291712925725: com.lacie.driver.LaCie_RemoteComms          1.0.1 (addr 0xd15000, size 12288)
    last unloaded kext at 355433688452: com.lacie.driver.LaCie_RemoteComms          1.0.1 (addr 0xd15000, size 12288)
    loaded kexts:
    com.sophos.kext.sav          8.0.14
    com.intego.kext.AppBarrierKPI          2.2
    com.splashtop.driver.SRXFrameBufferConnector          1.6
    com.intego.kext.NetBarrierKPI          10.5.4
    com.splashtop.driver.SRXDisplayCard          1.6
    com.Cycling74.driver.Soundflower          1.6.6
    com.markspace.driver.Android.RNDIS          1.2
    com.plantronics.driver.PlantronicsDriverShield          4.3
    com.Logitech.Control Center.HID Driver          3.9.0
    com.seagate.driver.PowSecLeafDriver_10_5          5.0.1
    com.oxsemi.driver.OxsemiDeviceType00          1.28.13
    com.seagate.driver.PowSecDriverCore          5.0.1
    net.osx86.kexts.GenericUSBXHCI          1.2.7
    com.rim.driver.BlackBerryUSBDriverInt          0.0.67
    com.apple.driver.AppleHWSensor          1.9.5d0
    com.apple.driver.AppleHDA          2.2.5a5
    com.apple.driver.AppleUpstreamUserClient          3.5.9
    com.apple.driver.AudioAUUC          1.59
    com.apple.kext.ATIFramebuffer          7.3.2
    com.apple.driver.SMCMotionSensor          3.0.2d6
    com.apple.filesystems.autofs          3.0
    com.apple.driver.AppleSMCPDRC          5.0.0d8
    com.apple.driver.AppleSMCLMU          2.0.1d2
    com.apple.iokit.IOUserEthernet          1.0.0d1
    com.apple.iokit.IOBluetoothSerialManager          4.0.8f17
    com.apple.driver.AirPort.Atheros21          431.14.10
    com.apple.Dont_Steal_Mac_OS_X          7.0.0
    com.apple.driver.AudioIPCDriver          1.2.3
    com.apple.driver.ApplePolicyControl          3.1.33
    com.apple.driver.ACPI_SMC_PlatformPlugin          5.0.0d8
    com.apple.driver.AppleLPC          1.6.0
    com.apple.driver.AppleBacklight          170.2.2
    com.apple.driver.AppleMCCSControl          1.0.33
    com.apple.ATIRadeonX1000          7.0.4
    com.apple.driver.CSRUSBBluetoothHCIController          4.0.8f17
    com.apple.driver.AppleUSBTrackpad          227.6
    com.apple.driver.AppleIRController          312
    com.apple.driver.AppleUSBTCKeyEventDriver          227.6
    com.apple.driver.AppleUSBTCKeyboard          227.6
    com.apple.AppleFSCompression.AppleFSCompressionTypeDataless          1.0.0d1
    com.apple.AppleFSCompression.AppleFSCompressionTypeZlib          1.0.0d1
    com.apple.BootCache          33
    com.apple.driver.XsanFilter          404
    com.apple.iokit.IOAHCIBlockStorage          2.1.0
    com.apple.driver.AppleUSBHub          5.1.0
    com.apple.iokit.AppleYukon2          3.2.2b1
    com.apple.driver.AppleAHCIPort          2.3.1
    com.apple.driver.AppleIntelPIIXATA          2.5.1
    com.apple.driver.AppleFWOHCI          4.9.0
    com.apple.driver.AppleSmartBatteryManager          161.0.0
    com.apple.driver.AppleUSBEHCI          5.1.0
    com.apple.driver.AppleUSBUHCI          5.1.0
    com.apple.driver.AppleEFINVRAM          1.6.1
    com.apple.driver.AppleRTC          1.5
    com.apple.driver.AppleHPET          1.7
    com.apple.driver.AppleACPIButtons          1.5
    com.apple.driver.AppleSMBIOS          1.9
    com.apple.driver.AppleACPIEC          1.5
    com.apple.driver.AppleAPIC          1.6
    com.apple.driver.AppleIntelCPUPowerManagementClient          195.0.0
    com.apple.nke.applicationfirewall          3.2.30
    com.apple.security.quarantine          1.4
    com.apple.security.TMSafetyNet          8
    com.apple.driver.AppleIntelCPUPowerManagement          195.0.0
    com.apple.driver.DspFuncLib          2.2.5a5
    com.apple.kext.triggers          1.0
    com.apple.iokit.IOFireWireIP          2.2.5
    com.apple.iokit.IOSurface          80.0.2
    com.apple.iokit.IOSerialFamily          10.0.5
    com.apple.iokit.IO80211Family          420.3
    com.apple.driver.AppleHDAController          2.2.5a5
    com.apple.iokit.IOHDAFamily          2.2.5a5
    com.apple.iokit.IOAudioFamily          1.8.6fc18
    com.apple.kext.OSvKernDSPLib          1.3
    com.apple.driver.AppleSMC          3.1.3d10
    com.apple.driver.IOPlatformPluginLegacy          5.0.0d8
    com.apple.driver.IOPlatformPluginFamily          5.1.1d6
    com.apple.driver.AppleGraphicsControl          3.1.33
    com.apple.driver.AppleBacklightExpert          1.0.4
    com.apple.driver.AppleSMBusController          1.0.10d0
    com.apple.iokit.IONDRVSupport          2.3.4
    com.apple.kext.ATI1600Controller          7.3.2
    com.apple.kext.ATISupport          7.3.2
    com.apple.iokit.IOGraphicsFamily          2.3.4
    com.apple.driver.AppleUSBBluetoothHCIController          4.0.8f17
    com.apple.driver.IOBluetoothHIDDriver          4.0.8f17
    com.apple.iokit.IOBluetoothFamily          4.0.8f17
    com.apple.iokit.IOUSBHIDDriver          5.0.0
    com.apple.driver.AppleUSBMergeNub          5.1.0
    com.apple.iokit.IOFireWireSerialBusProtocolTransport          2.1.0
    com.apple.iokit.IOFireWireSBP2          4.2.0
    com.apple.iokit.IOATABlockStorage          3.0.1
    com.apple.iokit.IOUSBUserClient          5.0.0
    com.apple.iokit.IONetworkingFamily          2.1
    com.apple.iokit.IOAHCIFamily          2.0.8
    com.apple.iokit.IOATAFamily          2.5.1
    com.apple.iokit.IOFireWireFamily          4.4.8
    com.apple.driver.AppleEFIRuntime          1.6.1
    com.apple.iokit.IOHIDFamily          1.7.1
    com.apple.iokit.IOSMBusFamily          1.1
    com.apple.security.sandbox          177.11
    com.apple.kext.AppleMatch          1.0.0d1
    com.apple.driver.DiskImages          331.7
    com.apple.driver.AppleKeyStore          28.18
    com.apple.iokit.IOUSBMassStorageClass          3.0.3
    com.apple.driver.AppleUSBComposite          5.0.0
    com.apple.iokit.IOSCSIBlockCommandsDevice          3.2.1
    com.apple.iokit.IOStorageFamily          1.7.2
    com.apple.iokit.IOSCSIArchitectureModelFamily          3.2.1
    com.apple.iokit.IOUSBFamily          5.1.0
    com.apple.driver.AppleACPIPlatform          1.5
    com.apple.iokit.IOPCIFamily          2.7
    com.apple.iokit.IOACPIFamily          1.4
    Model: MacBookPro2,2, BootROM MBP22.00A5.B07, 2 processors, Intel Core 2 Duo, 2.33 GHz, 3 GB, SMC 1.12f5
    Graphics: ATI Radeon X1600, ATY,RadeonX1600, PCIe, 256 MB
    Memory Module: BANK 0/DIMM0, 2 GB, DDR2 SDRAM, 667 MHz, 0x7F98000000000000, 0x202020202020202020202020202020202020
    Memory Module: BANK 1/DIMM1, 1 GB, DDR2 SDRAM, 667 MHz, 0x7F7F7F0B00000000, 0x4E5431475436345538484230424E2D334320
    AirPort: spairport_wireless_card_type_airport_extreme, Atheros 5416: 2.1.14.9
    Bluetooth: Version 4.0.8f17, 2 service, 11 devices, 2 incoming serial ports
    Network Service: AirPort, AirPort, en1
    PCI Card: sppci_expresscard_name, ExpressCard
    Serial ATA Device: KINGSTON SV300S37A240G, 240.06 GB
    Parallel ATA Device: WDC WD7500BPKT-00PK4T0, 750.16 GB
    USB Device: Built-in iSight, apple_vendor_id, 0x8501, 0xfd400000 / 5
    USB Device: USB2.0 Hub, 0x05e3  (Genesys Logic, Inc.), 0x0608, 0xfd300000 / 2
    USB Device: USB Receiver, 0x046d  (Logitech Inc.), 0xc50c, 0xfd340000 / 3
    USB Device: USB Receiver, 0x046d  (Logitech Inc.), 0xc51a, 0xfd330000 / 4
    USB Device: Apple Internal Keyboard / Trackpad, apple_vendor_id, 0x021b, 0x1d200000 / 2
    USB Device: IR Receiver, apple_vendor_id, 0x8240, 0x5d200000 / 2
    USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x8205, 0x7d100000 / 2
    FireWire Device: FA GoFlex Desk, Seagate, 800mbit_speed

    Remove the Sophos product by following the instructions on this page. If you have a different version, the procedure may be different.
    Remove the Intego product by following the instructions on this page. Again, if you have a different version of the product, the procedure may be different.
    Back up all data before making any changes.

  • Huge errors.log daemons.log and everything.log [SOLVED]

    Ok people i have i big problem since my last update, wich happened yesterday.
    errors.log, daemons.log and everything.log are extremly huge over 1.3G per file.
    I tried this to make them smaller with this:
    >errors.log
    >daemons.log
    >everything.log
    and this helps for about 5 mins, but after that 5 mins, those three files are growing large again.
    logrotate is in my /etc/cron.daily. Should i put it in /etc/cron.hourly. Is this gonna help me with my problem or is it something else that causes it.
    This is the message that is written over and over in errors.log:
    Jul  6 13:06:44 myhost famd[2151]: fd 4 message length 1347375956 bytes exceeds max of 4136.
    This one is from daemon.log:
    Jul  6 13:08:09 myhost famd[2151]: fd 4 message length 1347375956 bytes exceeds max of 4136.
    And this one is fron everything.log:
    Jul  6 13:09:03 myhost famd[2151]: fd 4 message length 1347375956 bytes exceeds max of 4136.
    As you can see this is the same message in all three files.
    This is the outputos ps -ax command:
      PID TTY      STAT   TIME COMMAND                                           
        1 ?        Ss     0:00 ini                                               
        2 ?        S<     0:00 [kthreadd]                                         
        3 ?        S<     0:00 [migration/0]                                     
        4 ?        S<     0:00 [ksoftirqd/0]                                     
        5 ?        S<     0:00 [watchdog/0]                                       
        6 ?        S<     0:00 [migration/1]                                     
        7 ?        R<     0:00 [ksoftirqd/1]                                     
        8 ?        S<     0:00 [watchdog/1]                                       
        9 ?        S<     0:00 [events/0]                                         
       10 ?        S<     0:00 [events/1]                                         
       11 ?        S<     0:00 [khelper]                                         
       12 ?        S<     0:00 [async/mgr]                                       
       13 ?        S<     0:00 [kblockd/0]                                       
       14 ?        S<     0:00 [kblockd/1]                                       
       15 ?        S<     0:00 [kacpid]                                           
       16 ?        S<     0:00 [kacpi_notify]                                     
       17 ?        S<     0:00 [kseriod]                                         
       18 ?        S      0:00 [khungtaskd]                                       
       19 ?        S      0:00 [pdflush]                                         
       20 ?        S      0:01 [pdflush]                                         
       21 ?        S<     0:00 [kswapd0]                                         
       22 ?        S<     0:00 [aio/0]                                           
       23 ?        S<     0:00 [aio/1]                                           
       24 ?        S<     0:00 [crypto/0]                                         
       25 ?        S<     0:00 [crypto/1]                                         
       38 ?        S<     0:00 [ata/0]                                           
       39 ?        S<     0:00 [ata/1]                                           
       40 ?        S<     0:00 [ata_aux]                                         
       44 ?        S<     0:00 [scsi_eh_0]                                       
       45 ?        S<     0:00 [scsi_eh_1]                                       
       48 ?        S<     0:00 [scsi_eh_2]                                       
       49 ?        S<     0:00 [scsi_eh_3]                                       
      309 ?        S<     0:00 [ksuspend_usbd]                                   
      331 ?        S<     0:00 [khubd]                                           
      539 ?        S<     0:00 [usbhid_resumer]                                   
      585 ?        S<     0:00 [kjournald]                                       
      609 ?        S<s    0:00 /sbin/udevd --daemon                               
      674 ?        S<     0:00 [hd-audio0]                                       
    1456 ?        S<     0:00 [kpsmoused]                                       
    1923 ?        S      0:00 supervising syslog-ng                             
    1924 ?        Ss    17:00 /usr/sbin/syslog-ng                               
    1954 ?        Ss     0:00 /sbin/dhcpcd -q eth0                               
    1970 ?        S      0:00 /usr/sbin/crond                                   
    1985 ?        Ss     0:00 /usr/bin/dbus-daemon --system                     
    1988 ?        Ss     0:00 /usr/sbin/hald                                     
    1991 ?        Ssl    0:00 /usr/sbin/console-kit-daemon                       
    1992 ?        S      0:00 hald-runner                                       
    2082 ?        S      0:00 hald-addon-input: Listening on /dev/input/event1 /dev/input/event5 /dev/input/event4
    2122 ?        S      0:00 hald-addon-storage: polling /dev/sr0 (every 16 sec)                                 
    2138 ?        S      0:00 hald-addon-acpi: listening on acpi kernel interface /proc/acpi/event               
    2143 ?        Ss     0:00 /usr/bin/rpcbind                                                                   
    2151 ?        Ss     9:37 /usr/sbin/famd -T 0 -c /etc/fam/fam.conf                                           
    2166 ?        S      0:02 /usr/bin/timidity -iAD                                                             
    2200 tty1     Ss     0:00 /bin/login --                                                                       
    2201 tty2     Ss+    0:00 /sbin/agetty -8 38400 vc/2 linux                                                   
    2202 tty3     Ss+    0:00 /sbin/agetty -8 38400 vc/3 linux                                                   
    2203 tty4     Ss+    0:00 /sbin/agetty -8 38400 vc/4 linux                                                   
    2204 tty5     Ss+    0:00 /sbin/agetty -8 38400 vc/5 linux                                                   
    2205 tty6     Ss+    0:00 /sbin/agetty -8 38400 vc/6 linux                                                   
    2206 ?        Ss     0:00 /opt/ibm/db2/V9.5/bin/db2fmcd                                                       
    2207 tty1     S      0:00 -bash                                                                               
    2210 tty1     S+     0:00 /bin/sh /usr/bin/startx                                                             
    2226 tty1     S+     0:00 xinit /home/radovan/.xinitrc -- /etc/X11/xinit/xserverrc :0 -auth /home/radovan/.serverauth.2210
    2227 tty7     S<s+   1:07 /usr/bin/X -nolisten tcp                                                                       
    2235 tty1     S      0:00 /bin/sh /usr/bin/startkde                                                                       
    2262 tty1     S      0:00 dbus-launch --sh-syntax --exit-with-session
    2263 ?        Ss     0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
    2269 ?        Ss     0:00 kdeinit4: kdeinit4 Running...
    2270 ?        S      0:00 klauncher
    2272 ?        S      0:00 kded4
    2283 tty1     S      0:00 kwrapper4 ksmserver
    2284 ?        Sl     0:00 ksmserver
    2286 ?        S      0:47 kwin -session 10e0ed686f000124296811100000033390000_1243359004_612398
    2287 ?        S      0:00 /usr/bin/kwrited
    2290 ?        Sl     0:00 /usr/bin/knotify4
    2291 ?        Sl     0:35 /usr/bin/plasma
    2294 ?        Sl     0:00 /usr/bin/nepomukserver
    2296 ?        S      0:00 /usr/bin/kaccess
    2298 ?        S      0:02 /usr/bin/nepomukservicestub nepomukstorage
    2307 ?        S      0:01 /usr/bin/krunner
    2309 ?        S      0:00 /usr/bin/nepomukservicestub nepomukfilewatch
    2310 ?        S      0:00 /usr/bin/nepomukservicestub nepomukontologyloader
    2311 ?        S      0:00 /usr/bin/nepomukservicestub nepomukqueryservice
    2317 ?        S      0:00 kmix -session 10e0ed686f000124296811600000033390010_1243359004_602182
    2319 ?        R     26:01 python /usr/bin/printer-applet
    2321 ?        S      0:00 /usr/bin/klipper
    2328 ?        S      0:00 kdeinit4: kio_file [kdeinit] file local:
    2365 ?        Sl     0:00 /home/dasusr1/das/adm/db2dasrrm
    2385 ?        S      0:00 /opt/ibm/db2/V9.5/das/bin/db2fmd -i dasusr1 -m /opt/ibm/db2/V9.5/das/lib/libdb2dasgcf.so.1
    2553 ?        S      0:00 kdeinit4: kio_http [kdeinit] http local:
    2896 ?        Sl     0:00 /usr/bin/yaspd
    2897 ?        S      0:00 ksysguardd
    2931 ?        Sl     1:23 /usr/bin/firefox
    2936 ?        S      0:00 /usr/lib/GConf/gconfd-2
    3997 ?        S      0:08 /usr/bin/dolphin -icon system-file-manager -caption Dolphin /home/radovan
    4189 ?        Rl     0:03 /usr/bin/konsole
    4191 pts/1    Ss     0:00 /bin/bash
    4192 pts/1    S      0:00 su
    4193 pts/1    S      0:00 bash
    4467 pts/1    S      0:00 su radovan
    4468 pts/1    S      0:00 bash
    4490 pts/1    S      0:00 su
    4491 pts/1    S      0:01 bash
    5260 pts/1    R+     0:00 ps -ax
    Sorry for my Tarzan English. I hope someone can help me.
    Edit:Ok i have killed famd daemon and those three log files are now normal. Was it ok for me to kill it, i mean is it safe?
    Last edited by pivonroll (2009-07-06 11:59:09)

    OK i did what you suggested. It works!
    Thx man

  • 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

  • I used to be able to download files from the Harddrive of my Sony Handycam, but now it won't let me import them while going through "log and transfer."  I have tried to update my settings, but this doesn't seem to work.  Any help would be much appreciated

    I used to be able to download files from the Harddrive of my Sony Handycam, but now it won't let me import them while going through "log and transfer."  I have tried to update my settings, but this doesn't seem to work.  Any help would be much appreciated

    Hard Drive:  The Hard Drive is on my camera (Sony Handycam)
    Just needed some info on what is going on with your particular system.
    Knowing the exact camera model will also assist us.
    If this camera is standard AVCHD you should be able to connect with USB to Mac with FCE open and use Log and Transfer without all the fiddling around converting etc.
    What FCE does during ingest is convert files to AIC. (Apple Intermediate Codec)
    FCE cannot read the individual files in the BDMV folder, that's why all the converting is required when you use that method.
    BTW: regards formatting drives/cards/memory on cameras; it is wise to use the actual device to format rather than a computer. This is a prime cause of read/write goof ups with solid state media. This applies to still or video cameras.
    Keeping the COMPLETE card/memory structure in tact is vital for successful transfers.
    Try here for some trouble shooting tips:
    https://discussions.apple.com/message/12682263#12682263
    Al

  • Hey, I have Final Cut Express 4.0.1 and a JVC everio camera, whenever i try to import my files to FCE via "Log and transfer", it just doesn't do anything, as if FCE doesn't know the camera is there, please help !

    Hey,
    I have Final Cut Express 4.0.1 and a JVC everio camera.
    Whenever i try to import my files to FCE via "Log and transfer", it just doesn't do anything, as if FCE doesn't know the camera is there,
    please help !

    FCE 4.0.1 can only capture DV/HDV which is produced by cameras using Mini-DV TAPES and cameras shooting AVCHD which is a high definition format.
    If your camera shoots standard definition on Memory Cards, DVDs or Hard Drives it will not work in FCE.
    What is your camera's exact model name and number?

  • Help In keithley 2400 VI!!(Problem with the data logging and graph plotting)

    Hi,need help badly=(.
    My program works fine when i run it,and tested it out with a simple diode.The expected start current steps up nicely to the stop current.The only problem is when it ends,i cannot get the data log and the graph,though i already have write code for it.Can someone help me see what's wrong with the code?I've attached the necessary file below,and i'm working with Labview 7.1.
    Thanks in advance!!!
    Attachments:
    24xx Swp-I Meas-V gpib.llb ‏687 KB

    Good morning,
    Without the instrument it might be hard for others to help
    troubleshoot the problem.  Was there a
    specific LabVIEW programming question you had, are you having problems with the
    instrument communication, are there errors? 
    I’d like to help, but could you provide some more specific information
    on what problems you are encountering, and maybe accompany that with a simple
    example which demonstrates the behavior? 
    In general we don’t we will be unable to open specific code and debug,
    but I’d be happy to help with specific questions. 
    I did notice, though, that in your logging VI you have at
    least one section of code which appears to not do anything.  It could be that a small section of code, or
    a wire was removed and the data is not being updated correctly (see pic below).  Is your file being opened properly?  Is the data being passed to the file
    properly?  What are some of the things
    you have examined so far?
    Sorry I could not provide the ‘fix’, but I’m confident that
    we can help.  Thanks for posting, and
    have a great day-
    Message Edited by Travis M. on 07-11-2006 08:51 AM
    Travis M
    LabVIEW R&D
    National Instruments
    Attachments:
    untitled.JPG ‏88 KB

  • [Help Request] Log and Transfer with Sony HDR-SR10

    Hello Everyone,
    I am very new to Final Cut Express and I am trying to import the clips from my camera (Sony HDR-SR10) to Final Cut. Here are the settings that I have for FCE and the camera:
    *Easy Setup*
    Format: Apple Intermediate Codec
    Rate: (all rates)
    Use: AVCHD-Apple Intermediate Codec 1440x1080i60
    +settings found in this thread (http://discussions.apple.com/message.jspa?messageID=9162394)+
    *Camera Settings*
    HD FH (AVC HD 16M (FH)
    Then I mount the camera on the desktop. Then File > Log and Transfer. However, no clips appear in the viewer. I have tried adding a folder to the Log and Transfer window, but no clips show up. I have about 30gb of footage on my camera, so it's not like the camera is blank or something.
    Any help would be greatly appreciated. Thanks in advance.
    Sincerely,
    Jon

    Jonathan,
    In addition to Tom's advice...
    I have an SR-11 which I believe is nearly identical to your's. Do you have any SD video on your camera? If you do you may have to erase these clips. When I first started using FCE, I had to get rid of any SD footage I had before FCE would display my HD clips in the Log and Transfer window. Fortunately I only had a couple of test clips in SD, so erasing them wasn't a big deal. I don't know why this happens, but since I only shoot in HD mode I never looked into in further.
    Additionally insure your playback mode is set for HD and not SD (I don't have my camera with me right now, but if I remember correctly there is a selection in one of the menus for this).
    Hope this helps a bit.
    Marc

  • Log and transfer does not recognize footage. Please Help

    When i open the log and transfer window in FCP on my macbook it no longer recognizes the files from the Contents folder of a P2 card or the RED ONE files from the folder on my hard drive. last week however, everything was working fine.
    does this have something to do with the project settings or the RED plugins? any help is greatly appreciated. thanks.

    Have you changed your set up or software, or computer in any manner since last week?
    And did you trash your preferences and try that?

  • When I do log and transfer in final cut pro 7 from external hard it will not responding, and i will force quit from final cut, plz help!!

    When I do log and transfer in final cut pro 7 from external hard it will not responding,
    and i will do force quit from final cut, plz help!!
    i have alot work to do plllllllllz help

    Hi. Your FCP7 question should be posted in this  forum.  https://discussions.apple.com/community/professional_applications/final_cut_stud io
    Good luck.
    Russ

  • 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

  • Will upgrading GPU help log and transfer of 7D footage to ProRes

    I have a 1.1 MacPro with 2.6 quad and ATI X1800.. Will upgrading my GPU to a ati 4870 5770 help with my log and trasnfer speeds..
    Does Compressor or FCP use GPU during transcodes or log and transfers for either encode or decode?

    Will upgrading my GPU to a ati 4870 5770 help with my log and trasnfer speeds..
    No. Only processor speed.
    Does Compressor or FCP use GPU during transcodes or log and transfers for either encode or decode?
    No. Only Motion and Color, and a few plugins (FXPlug) in FCP utilize the GPU. Compressor, FCP log and transfer...that's processor power.
    Shane

  • My mac froze in an application so I shut it down by powering off with button, now when I try to turn it on I have a grey screen with Apple loge and the timer swirling but it doesn't get past this, please help!

    I Shut down my Mac by holding in the power button after my iMac froze and now when I try to turn it back it on all I get is the grey screen with Apple loge and the timer and doesn't get any further.  I have tried the diagnostic test but nothing was found.

    Take each of these steps that you haven't already tried. Stop when the problem is resolved.
    To restart an unresponsive computer, press and hold the power button for a few seconds until the power shuts off, then release, wait a few more seconds, and press it again briefly.
    Step 1
    The first step in dealing with a startup failure is to secure the data. If you want to preserve the contents of the startup drive, and you don't already have at least one current backup, you must try to back up now, before you do anything else. It may or may not be possible. If you don't care about the data that has changed since the last backup, you can skip this step.
    There are several ways to back up a Mac that is unable to start. You need an external hard drive to hold the backup data.
    a. Start up from the Recovery partition, or from a local Time Machine backup volume (option key at startup.) When the OS X Utilities screen appears, launch Disk Utility and follow the instructions in this support article, under “Instructions for backing up to an external hard disk via Disk Utility.” The article refers to starting up from a DVD, but the procedure in Recovery mode is the same. You don't need a DVD if you're running OS X 10.7 or later.
    b. If Step 1a fails because of disk errors, and no other Mac is available, then you may be able to salvage some of your files by copying them in the Finder. If you already have an external drive with OS X installed, start up from it. Otherwise, if you have Internet access, follow the instructions on this page to prepare the external drive and install OS X on it. You'll use the Recovery installer, rather than downloading it from the App Store.
    c. If you have access to a working Mac, and both it and the non-working Mac have FireWire or Thunderbolt ports, start the non-working Mac in target disk mode. Use the working Mac to copy the data to another drive. This technique won't work with USB, Ethernet, Wi-Fi, or Bluetooth.
    d. If the internal drive of the non-working Mac is user-replaceable, remove it and mount it in an external enclosure or drive dock. Use another Mac to copy the data.
    Step 2
    If the startup process stops at a blank gray screen with no Apple logo or spinning "daisy wheel," then the startup volume may be full. If you had previously seen warnings of low disk space, this is almost certainly the case. You might be able to start up in safe mode even though you can't start up normally. Otherwise, start up from an external drive, or else use the technique in Step 1b, 1c, or 1d to mount the internal drive and delete some files. According to Apple documentation, you need at least 9 GB of available space on the startup volume (as shown in the Finder Info window) for normal operation.
    Step 3
    Sometimes a startup failure can be resolved by resetting the NVRAM.
    Step 4
    If a desktop Mac hangs at a plain gray screen with a movable cursor, the keyboard may not be recognized. Press and hold the button on the side of an Apple wireless keyboard to make it discoverable. If need be, replace or recharge the batteries. If you're using a USB keyboard connected to a hub, connect it to a built-in port.
    Step 5
    If there's a built-in optical drive, a disc may be stuck in it. Follow these instructions to eject it.
    Step 6
    Press and hold the power button until the power shuts off. Disconnect all wired peripherals except those needed to start up, and remove all aftermarket expansion cards. Use a different keyboard and/or mouse, if those devices are wired. If you can start up now, one of the devices you disconnected, or a combination of them, is causing the problem. Finding out which one is a process of elimination.
    Step 7
    If you've started from an external storage device, make sure that the internal startup volume is selected in the Startup Disk pane of System Preferences.
    Start up in safe mode. Note: If FileVault is enabled in OS X 10.9 or earlier, or if a firmware password is set, or if the startup volume is a software RAID, you can’t do this. Post for further instructions.
    Safe mode is much slower to start and run than normal, and some things won’t work at all, including wireless networking on certain Macs.
    The login screen appears even if you usually log in automatically. You must know the login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
    When you start up in safe mode, it's normal to see a dark gray progress bar on a light gray background. If the progress bar gets stuck for more than a few minutes, or if the system shuts down automatically while the progress bar is displayed, the startup volume is corrupt and the drive is probably malfunctioning. In that case, go to Step 11. If you ever have another problem with the drive, replace it immediately.
    If you can start and log in in safe mode, empty the Trash, and then open the Finder Info window on the startup volume ("Macintosh HD," unless you gave it a different name.) Check that you have at least 9 GB of available space, as shown in the window. If you don't, copy as many files as necessary to another volume (not another folder on the same volume) and delete the originals. Deletion isn't complete until you empty the Trash again. Do this until the available space is more than 9 GB. Then restart as usual (i.e., not in safe mode.)
    If the startup process hangs again, the problem is likely caused by a third-party system modification that you installed. Post for further instructions.
    Step 8
    Launch Disk Utility in Recovery mode (see Step 1.) Select the startup volume, then run Repair Disk. If any problems are found, repeat until clear. If Disk Utility reports that the volume can't be repaired, the drive has malfunctioned and should be replaced. You might choose to tolerate one such malfunction in the life of the drive. In that case, erase the volume and restore from a backup. If the same thing ever happens again, replace the drive immediately.
    This is one of the rare situations in which you should also run Repair Permissions, ignoring the false warnings it may produce. Look for the line "Permissions repair complete" at the end of the output. Then restart as usual.
    Step 9
    If the startup device is an aftermarket SSD, it may need a firmware update and/or a forced "garbage collection." Instructions for doing this with a Crucial-branded SSD were posted here. Some of those instructions may apply to other brands of SSD, but you should check with the vendor's tech support.  
    Step 10
    Reinstall the OS. If the Mac was upgraded from an older version of OS X, you’ll need the Apple ID and password you used to upgrade.
    Step 11
    Do as in Step 9, but this time erase the startup volume in Disk Utility before installing. The system should automatically restart into the Setup Assistant. Follow the prompts to transfer the data from a Time Machine or other backup.
    Step 12
    This step applies only to models that have a logic-board ("PRAM") battery: all Mac Pro's and some others (not current models.) Both desktop and portable Macs used to have such a battery. The logic-board battery, if there is one, is separate from the main battery of a portable. A dead logic-board battery can cause a startup failure. Typically the failure will be preceded by loss of the settings for the startup disk and system clock. See the user manual for replacement instructions. You may have to take the machine to a service provider to have the battery replaced.
    Step 13
    If you get this far, you're probably dealing with a hardware fault. Make a "Genius" appointment at an Apple Store, or go to another authorized service provider.

  • Need help with our "log and transfer" workflow...

    All,
    Again, it's our first tapeless project so please keep having patience with us.
    What should the workflow be for our project?
    I bring in the Firestore and dump raw files to a hard drive. Should I then transfer all footage to QT files? OR should my editor start looking at footage and carving it up as he transfers those files to QT?
    Our issue is that we have a lot of footage coming in and the new tower is slow when transferring footage from raw files to QT. It's driving us crazy.
    Aside from buying a more powerful tower, is there a way for us to review and log the footage and transfer at a real time pace (for example, is there a way to log the footage and do a transfer to QT files at the end of session?).
    Thanks.

    David, thanks for the questions.
    Yes, it's FS-100. And yes, we are shooting on a HVX200.
    The settings we were given by our editing guru create MXF files rather than QT. If so, we should dump onto a hard drive and then bring into FCP, correct?
    Is there a way to log a number of clips and then transfer them en masse? Or do I have log and transfer them one at a time?
    Our issue is that the computer grinds to a virtual halt while transferring.
    Thanks again. We look forward to your thoughts.

Maybe you are looking for