Log and Transfer Clips are in order from name, not actual time of recording
When I first installed my Final Cut Express HD and went to Log and Transfer, the clips were organized properly (#1 #2 #3 etc.), but one time I accidentally hit the "Name" column at the top, which then put all the clips in order by name (#1 #10 #11). This makes things a lot harder for me when I only need to select certain clips. I've tried re-installing the program, but to no avail. Can someone please help me get this back to the order in which the clips were first recorded?
I found out the problem. The controls do not work if the AVCHD footage is in SD. They do appear if footage is in HD.
Similar Messages
-
I cannot log and transfer clips that are longer than 5 minutes.
Hello,
I am trying to log and transfer several clips from my Canon Vixia HF S11 camcorder. When I attempt to transfer a clip into Final Cut Express that is longer than 5 minutes, it stops right when it is about to finishe and says, "Unknown Error." Due to the volume of my HD footage, I am working on an external hard drive with ample space. Could this be the problem? Should I attempt to transfer these longer clips onto my MacBook hard drive? Thank you very much for you help.
-SamanthaUse Disk Utility (in your Applications>Utilities folder) to erase the drive and reformat as Mac OS Extended. There are differing opinions regarding whether or not you should select journaling. With media drives, I tend not to. (This process will, of course, erase what's on the drive presently.)
-
Log and transfer clip setting over clip #100 +
When I selected all clips on log and transfer, they stop at Clip #99. It could not transfer more than #100. I had to rename to a, b, c, etc. Is there any preferance settings to accept over #100? I want to keep them in order.
All cards start with #1? I don't see "#1" anywhere.
I see the clip names, like 0001MS, 0002Z8 and so on. And VOLUME NAME is the name of the card or name of the folder you put the card in. The second card MIGHT start again with 0001, but have another code, like "0001GU, 0002B2" and so on. Because that it the first one on that card. IF a shot spanned from one card to the next, the number scheme would continue, like you are seeing. 0057HW, 0058J9, something to that effect.
This is the way P2 names clips, and there is nothing you can do to change this. Import them, and then rename them...fine.
Are you saying that it can't go beyond shot 100? 0100YU, but no 0101IK? P2 can go to 999.
Shane -
Log and Transfer - Clip Sorting Issue
Hello. I have been using an AVCHD camera for some time now, and when I would use the Log And Transfer the clips would show up in the order they were recorded. I accidentally pressed a tab at the top to sort a different way, and now I can't get back to how it was. See http://dcdl.info/20100212171440.png for a screenshot. I know it has to do with how the clips are automatically named.
If anyone can help me with this, I'd really appreciate it. Thanks!Just a thought!
Right-click on the "Name" field and check "Date Created" in the drop-down list. If you now sort using the Date Created column, will this reorder the clips as you want them? If not, are there any other options in the list that might?
Frank -
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 -
Missing Log and Transfer Clip Browsing window
Help!!!
I was using log and transfer to import videos. My daughter came along and clicked somewhere in the log and transfer window. Now all I see is the right handside pane of a particular clip. I lost the left hand side where I see the list of clips from my media. How do I get it back?
ThanksHi -
Did she accidentally swipe it to the side?
There is a pane size bar in the middle of the window, if that gets dragged to the right the preview window will be hidden:
!http://www.spotsbeforeyoureyes.com/L%26TPreWindow2.jpg!
Grab it with your cursor and pull it back to the center
!http://www.spotsbeforeyoureyes.com/L%26TPreWindow1.jpg!
Hope this helps. -
I have my boyfriends number (iPhone 4) connected to my account with my iPhone 4S and iPad 2 when he texts me after he updated his phone last night it now sends us both the message sent every time so the conversation is now on two different conversations on the phone. Please help
Settings > Messages > Send and Received > Uncheck any number/email that does not belong to the device
Note: The little blue (>) will give you an option to remove the number/email from the device
Note: Check this setting on any device(s) using the same Apple ID -
Cant import using Log and Transfer to FCE 4.0.1 from Panasonic DMC-TZ10
Does anyone know if/how I can import into FCE 4.0.1 using Log and Transfer? I use Log and Transfer with my Sony HDR XR200VE Video Camera but when I try this with the Panasonic DMC-TZ10 I can play the clips in the Log and Transfer Clip viewer however they don't import after I add them to the queue. It just gives me an ! icon and gives up.
I guess I need to know if there is a combination of camera settings and Codecs I can choose that will allow me to successfully import into FCE 4.0.1 using Log and Transfer.
The settings I can choose on the DMC-TZ10 camera are the Rec Mode (Either AVCHD Lite (GPS Rec), AVCHD Lite, or Motion JPEG) and the Rec Quality SH, H or L).
iPhoto 09 and iMovie 09 will automatically import video from this camera if I choose Motion JPEG and H on the DMC-TZ10Log and transfer only supports AVCHD. It does not support AVCHD Lite, nor will it work with Motion JPEG media. You could use third party software to convert it, or iMovie and then export a QuickTime movie from there in the correct codec and format.
-
Log and Transfer - Mystery Clips Appear?
Whenever I go to import P2 media using the Log and Transfer mode in Final Cut Pro 7, I'm getting these mystery clips labled "Clip #1, Clip #2.. all they way up to Clip #344 and it indicates they reside on my external media drive. Most of the clips have no related media, that is, nothing appears in the thumbnail or name block-- its just black. Now, there are a few that do have thumbnails representing video clips but when try to view any related media, nothing shows. It seems they could be from a non-P2 import from a long time ago, yet the media no longer exists. I can click on one of the clips and eject, which makes them all disappear, but I also get the message "This volume cannot be unmounted because it is being used for importing." Which is strange as I never import from this volume. Rather, I either import from an internal drive or from a network drive.
If I do a Find (command + F) in Finder and type in Clip #1, it cannot find anything on the external media drive or anywhere else. I'm wondering if it has something to do with some legacy Prefs but I've dumped those and restarted and still get these mystery clips. And this is EVERY time I go to Log and Transfer. I can exit Log and Transfer and, in the same session, go back and there are those mystery clips! Again.
Anybody have any ideas? Thanks!Maybe I wasn't clear: I have no trouble loading or viewing my P2 card media (which is already off-loaded onto an archive drive and then transcoded-- via Log and Transfer-- to my media drive.) Its that every time I open Log and Transfer, these mystery clips appear. If I eject them, I get the error message mentioned. If I don't, I can still load my P2 media and the mystery clips are listed below the actual P2 media I am looking to use.
And I have dumped my prefs repeatedly and still the mystery clips survive.
I think my issue resides in the Log and Transfer Import Preferences. If I could only clean those up, as I see one of my options is MPEG2 Consumer Cameras (??), maybe that would help.
Thanks! -
Log and transfer crashes when converting to 422 from avchd from sony fs700
trying to import AVChd files shot on a Sony FS700.
the files are on average one hour or more.
Need to import as 422 HQ
log and transfer sees the files but FCP 7 crashes every time
I've tried using PavTube to convert but files over 10 minutes are segmented in chunks ranging from 10 minutes to 11 minutes when the source file is long. Also the media slips out of sync over time.
I have had success with short files in FCP 7 via log and transfer but anything long results in the crash.
is this just a limitation? IS there a fix for this?
thanks
here is the crash report -
Process: Final Cut Pro [13445]
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 [459]
Date/Time: 2013-07-12 16:53:44.169 -0700
OS Version: Mac OS X 10.6.8 (10K549)
Report Version: 6
Interval Since Last Report: 1220259 sec
Crashes Since Last Report: 2
Per-App Interval Since Last Report: 969553 sec
Per-App Crashes Since Last Report: 2
Anonymous UUID: 05E60465-B8BC-47A2-A3DF-C5BD1E5C8ABF
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 (22063)'
*** Call stack at first throw:
0 CoreFoundation 0x9976c6ca __raiseError + 410
1 libobjc.A.dylib 0x94a725a9 objc_exception_throw + 56
2 CoreFoundation 0x9976c3f8 +[NSException raise:format:arguments:] + 136
3 CoreFoundation 0x9976c36a +[NSException raise:format:] + 58
4 Foundation 0x95b0f169 _NSMutableDataGrowBytes + 1154
5 Foundation 0x95b0ec77 -[NSConcreteMutableData appendBytes:length:] + 75
6 AVCHD 0x6e5b0cd1 0x0 + 1851460817
7 AVCHD 0x6e5aadb3 0x0 + 1851436467
8 MIO 0x010772cb TundraPluginCallbackProc + 355
9 Tundra 0x5b574d98 TundraUnitHALInputEntry + 12756
10 Tundra 0x5b50d38d 0x0 + 1532023693
11 Tundra 0x5b5416df TundraUnitMPEG2DemuxEntry + 22037
12 Tundra 0x5b57c63a TundraUnitVDIGInputEntry + 13711
13 Tundra 0x5b591553 TundraUnitMPEG2MuxEntry + 11138
14 Tundra 0x5b50d38d 0x0 + 1532023693
15 Tundra 0x5b5416df TundraUnitMPEG2DemuxEntry + 22037
16 Tundra 0x5b57c63a TundraUnitVDIGInputEntry + 13711
17 Tundra 0x5b592fbe TundraUnitMPEG2MuxEntry + 17901
18 Tundra 0x5b50d38d 0x0 + 1532023693
19 Tundra 0x5b5416df TundraUnitMPEG2DemuxEntry + 22037
20 Tundra 0x5b57c63a TundraUnitVDIGInputEntry + 13711
21 Tundra 0x5b592fbe TundraUnitMPEG2MuxEntry + 17901
22 Tundra 0x5b50d38d 0x0 + 1532023693
23 Tundra 0x5b5416df TundraUnitMPEG2DemuxEntry + 22037
24 Tundra 0x5b57c63a TundraUnitVDIGInputEntry + 13711
25 Tundra 0x5b592fbe TundraUnitMPEG2MuxEntry + 17901
26 Tundra 0x5b50d38d 0x0 + 1532023693
27 Tundra 0x5b5416df TundraUnitMPEG2DemuxEntry + 22037
28 Tundra 0x5b57c63a TundraUnitVDIGInputEntry + 13711
29 Tundra 0x5b59f67e TundraUnitAudioOutputEntry + 18972
30 Tundra 0x5b50d38d 0x0 + 1532023693
31 Tundra 0x5b59ef2c TundraUnitAudioOutputEntry + 17098
32 Tundra 0x5b59eed2 TundraUnitAudioOutputEntry + 17008
33 Tundra 0x5b5b654d TundraUnitBFrameFileOutputEntry + 25068
34 CarbonCore 0x92fd051f CallComponentDispatch + 29
35 CoreMediaIOServicesPrivate 0x0111b5de TundraOutputUnitComponentCallRender + 49
36 CoreMediaIOServicesPrivate 0x0110080e _ZN8MIOGraph15PullOutputUnitsEbRbS0_S0_ + 348
37 CoreMediaIOServicesPrivate 0x01101548 _ZN8MIOGraph25PullAndProcessThreadEntryEv + 632
38 CoreMediaIOServicesPrivate 0x0110264f _ZN8MIOGraph21_PullAndProcessThreadEP13MIOThreadPriv + 495
39 CoreMediaIOServicesPrivate 0x0110e3a1 start_thread + 61
40 libSystem.B.dylib 0x917b8259 _pthread_start + 345
41 libSystem.B.dylib 0x917b80de thread_start + 34
Thread 0: Dispatch queue: com.apple.main-thread
0 libSystem.B.dylib 0x9178aafa mach_msg_trap + 10
1 libSystem.B.dylib 0x9178b267 mach_msg + 68
2 com.apple.CoreFoundation 0x996d530f __CFRunLoopRun + 2079
3 com.apple.CoreFoundation 0x996d43f4 CFRunLoopRunSpecific + 452
4 com.apple.CoreFoundation 0x996d4221 CFRunLoopRunInMode + 97
5 com.apple.HIToolbox 0x920e1e04 RunCurrentEventLoopInMode + 392
6 com.apple.HIToolbox 0x920e1bb9 ReceiveNextEventCommon + 354
7 com.apple.HIToolbox 0x9226a084 _AcquireNextEvent + 54
8 com.apple.HIToolbox 0x9225fd40 RunApplicationEventLoop + 228
9 com.apple.FinalCutPro 0x001539d1 KGMainEvent(void*) + 51
10 com.apple.FinalCutPro 0x002c1278 main + 54
11 com.apple.FinalCutPro 0x00002d5b _start + 209
12 com.apple.FinalCutPro 0x00002c89 start + 41
Thread 1: Dispatch queue: com.apple.libdispatch-manager
0 libSystem.B.dylib 0x917b1382 kevent + 10
1 libSystem.B.dylib 0x917b1a9c _dispatch_mgr_invoke + 215
2 libSystem.B.dylib 0x917b0f59 _dispatch_queue_invoke + 163
3 libSystem.B.dylib 0x917b0cfe _dispatch_worker_thread2 + 240
4 libSystem.B.dylib 0x917b0781 _pthread_wqthread + 390
5 libSystem.B.dylib 0x917b05c6 start_wqthread + 30
Thread 2: com.apple.CFSocket.private
0 libSystem.B.dylib 0x917a9ac6 select$DARWIN_EXTSN + 10
1 com.apple.CoreFoundation 0x99714c83 __CFSocketManager + 1091
2 libSystem.B.dylib 0x917b8259 _pthread_start + 345
3 libSystem.B.dylib 0x917b80de thread_start + 34
Thread 3:
0 libSystem.B.dylib 0x9178ab42 semaphore_wait_signal_trap + 10
1 libSystem.B.dylib 0x917b86f8 _pthread_cond_wait + 1089
2 libSystem.B.dylib 0x9180105f pthread_cond_wait + 48
3 com.apple.FinalCutPro 0x0043f42b Synchronizable::Wait() + 53
4 com.apple.FinalCutPro 0x0042911f DisplayQueue::Run() + 681
5 com.apple.FinalCutPro 0x0046b49a Thread::RunHelper(void*) + 20
6 libSystem.B.dylib 0x917b8259 _pthread_start + 345
7 libSystem.B.dylib 0x917b80de thread_start + 34
Thread 4:
0 libSystem.B.dylib 0x9178ab42 semaphore_wait_signal_trap + 10
1 libSystem.B.dylib 0x917b86f8 _pthread_cond_wait + 1089
2 libSystem.B.dylib 0x9180105f pthread_cond_wait + 48
3 com.apple.FinalCutPro 0x0043f42b Synchronizable::Wait() + 53
4 com.apple.FinalCutPro 0x004e67c3 WorkUnitPerformer::Run() + 55
5 com.apple.FinalCutPro 0x0046b49a Thread::RunHelper(void*) + 20
6 libSystem.B.dylib 0x917b8259 _pthread_start + 345
7 libSystem.B.dylib 0x917b80de thread_start + 34
Thread 5:
0 libSystem.B.dylib 0x9178ab42 semaphore_wait_signal_trap + 10
1 libSystem.B.dylib 0x917b86f8 _pthread_cond_wait + 1089
2 libSystem.B.dylib 0x9180105f pthread_cond_wait + 48
3 com.apple.FinalCutPro 0x0043f42b Synchronizable::Wait() + 53
4 com.apple.FinalCutPro 0x004e67c3 WorkUnitPerformer::Run() + 55
5 com.apple.FinalCutPro 0x0046b49a Thread::RunHelper(void*) + 20
6 libSystem.B.dylib 0x917b8259 _pthread_start + 345
7 libSystem.B.dylib 0x917b80de thread_start + 34
Thread 6:
0 libSystem.B.dylib 0x9178ab42 semaphore_wait_signal_trap + 10
1 libSystem.B.dylib 0x917b86f8 _pthread_cond_wait + 1089
2 libSystem.B.dylib 0x9180105f pthread_cond_wait + 48
3 com.apple.FinalCutPro 0x0043f42b Synchronizable::Wait() + 53
4 com.apple.FinalCutPro 0x004e67c3 WorkUnitPerformer::Run() + 55
5 com.apple.FinalCutPro 0x0046b49a Thread::RunHelper(void*) + 20
6 libSystem.B.dylib 0x917b8259 _pthread_start + 345
7 libSystem.B.dylib 0x917b80de thread_start + 34
Thread 7:
0 libSystem.B.dylib 0x9178ab42 semaphore_wait_signal_trap + 10
1 libSystem.B.dylib 0x917b86f8 _pthread_cond_wait + 1089
2 libSystem.B.dylib 0x9180105f pthread_cond_wait + 48
3 com.apple.FinalCutPro 0x0043f42b Synchronizable::Wait() + 53
4 com.apple.FinalCutPro 0x004e67c3 WorkUnitPerformer::Run() + 55
5 com.apple.FinalCutPro 0x0046b49a Thread::RunHelper(void*) + 20
6 libSystem.B.dylib 0x917b8259 _pthread_start + 345
7 libSystem.B.dylib 0x917b80de thread_start + 34
Thread 8:
0 libSystem.B.dylib 0x9178ab42 semaphore_wait_signal_trap + 10
1 libSystem.B.dylib 0x917b86f8 _pthread_cond_wait + 1089
2 libSystem.B.dylib 0x9180105f pthread_cond_wait + 48
3 com.apple.FinalCutPro 0x0043f42b Synchronizable::Wait() + 53
4 com.apple.FinalCutPro 0x004e67c3 WorkUnitPerformer::Run() + 55
5 com.apple.FinalCutPro 0x0046b49a Thread::RunHelper(void*) + 20
6 libSystem.B.dylib 0x917b8259 _pthread_start + 345
7 libSystem.B.dylib 0x917b80de thread_start + 34
Thread 9:
0 libSystem.B.dylib 0x9178ab42 semaphore_wait_signal_trap + 10
1 libSystem.B.dylib 0x917b86f8 _pthread_cond_wait + 1089
2 libSystem.B.dylib 0x9180105f pthread_cond_wait + 48
3 com.apple.FinalCutPro 0x0043f42b Synchronizable::Wait() + 53
4 com.apple.FinalCutPro 0x004e67c3 WorkUnitPerformer::Run() + 55
5 com.apple.FinalCutPro 0x0046b49a Thread::RunHelper(void*) + 20
6 libSystem.B.dylib 0x917b8259 _pthread_start + 345
7 libSystem.B.dylib 0x917b80de thread_start + 34
Thread 10:
0 libSystem.B.dylib 0x9178ab42 semaphore_wait_signal_trap + 10
1 libSystem.B.dylib 0x917b86f8 _pthread_cond_wait + 1089
2 libSystem.B.dylib 0x9180105f pthread_cond_wait + 48
3 com.apple.FinalCutPro 0x0043f42b Synchronizable::Wait() + 53
4 com.apple.FinalCutPro 0x004e67c3 WorkUnitPerformer::Run() + 55
5 com.apple.FinalCutPro 0x0046b49a Thread::RunHelper(void*) + 20
6 libSystem.B.dylib 0x917b8259 _pthread_start + 345
7 libSystem.B.dylib 0x917b80de thread_start + 34
Thread 11:
0 libSystem.B.dylib 0x9178ab42 semaphore_wait_signal_trap + 10
1 libSystem.B.dylib 0x917b86f8 _pthread_cond_wait + 1089
2 libSystem.B.dylib 0x9180105f pthread_cond_wait + 48
3 com.apple.FinalCutPro 0x0043f42b Synchronizable::Wait() + 53
4 com.apple.FinalCutPro 0x004e67c3 WorkUnitPerformer::Run() + 55
5 com.apple.FinalCutPro 0x0046b49a Thread::RunHelper(void*) + 20
6 libSystem.B.dylib 0x917b8259 _pthread_start + 345
7 libSystem.B.dylib 0x917b80de thread_start + 34
Thread 12:
0 libSystem.B.dylib 0x9178ab42 semaphore_wait_signal_trap + 10
1 libSystem.B.dylib 0x917b86f8 _pthread_cond_wait + 1089
2 libSystem.B.dylib 0x9180105f pthread_cond_wait + 48
3 com.apple.FinalCutPro 0x0043f42b Synchronizable::Wait() + 53
4 com.apple.FinalCutPro 0x004e67c3 WorkUnitPerformer::Run() + 55
5 com.apple.FinalCutPro 0x0046b49a Thread::RunHelper(void*) + 20
6 libSystem.B.dylib 0x917b8259 _pthread_start + 345
7 libSystem.B.dylib 0x917b80de thread_start + 34
Thread 13:
0 libSystem.B.dylib 0x9178ab42 semaphore_wait_signal_trap + 10
1 libSystem.B.dylib 0x917b86f8 _pthread_cond_wait + 1089
2 libSystem.B.dylib 0x9180105f pthread_cond_wait + 48
3 com.apple.FinalCutPro 0x0043f42b Synchronizable::Wait() + 53
4 com.apple.FinalCutPro 0x004e67c3 WorkUnitPerformer::Run() + 55
5 com.apple.FinalCutPro 0x0046b49a Thread::RunHelper(void*) + 20
6 libSystem.B.dylib 0x917b8259 _pthread_start + 345
7 libSystem.B.dylib 0x917b80de thread_start + 34
Thread 14:
0 libSystem.B.dylib 0x9178ab42 semaphore_wait_signal_trap + 10
1 libSystem.B.dylib 0x917b86f8 _pthread_cond_wait + 1089
2 libSystem.B.dylib 0x9180105f pthread_cond_wait + 48
3 com.apple.FinalCutPro 0x0043f42b Synchronizable::Wait() + 53
4 com.apple.FinalCutPro 0x004e67c3 WorkUnitPerformer::Run() + 55
5 com.apple.FinalCutPro 0x0046b49a Thread::RunHelper(void*) + 20
6 libSystem.B.dylib 0x917b8259 _pthread_start + 345
7 libSystem.B.dylib 0x917b80de thread_start + 34
Thread 15:
0 libSystem.B.dylib 0x9178aafa mach_msg_trap + 10
1 libSystem.B.dylib 0x9178b267 mach_msg + 68
2 com.apple.CoreFoundation 0x996d530f __CFRunLoopRun + 2079
3 com.apple.CoreFoundation 0x996d43f4 CFRunLoopRunSpecific + 452
4 com.apple.CoreFoundation 0x996da334 CFRunLoopRun + 84
5 com.apple.DVCPROHDMuxer 0x3898d98f AVS::DestroyAVCDeviceController(AVS::AVCDeviceController*) + 317
6 libSystem.B.dylib 0x917b8259 _pthread_start + 345
7 libSystem.B.dylib 0x917b80de thread_start + 34
Thread 16:
0 libSystem.B.dylib 0x9178aafa mach_msg_trap + 10
1 libSystem.B.dylib 0x9178b267 mach_msg + 68
2 com.apple.CoreFoundation 0x996d530f __CFRunLoopRun + 2079
3 com.apple.CoreFoundation 0x996d43f4 CFRunLoopRunSpecific + 452
4 com.apple.CoreFoundation 0x996d4221 CFRunLoopRunInMode + 97
5 ....CoreMediaIOServicesPrivate 0x010fc9ab MIO::DAL::RunLoop::OwnThread(void*) + 157
6 ....CoreMediaIOServicesPrivate 0x010fe81c CAPThread::Entry(CAPThread*) + 96
7 libSystem.B.dylib 0x917b8259 _pthread_start + 345
8 libSystem.B.dylib 0x917b80de thread_start + 34
Thread 17:
0 libSystem.B.dylib 0x9178aafa mach_msg_trap + 10
1 libSystem.B.dylib 0x9178b267 mach_msg + 68
2 com.apple.CoreFoundation 0x996d530f __CFRunLoopRun + 2079
3 com.apple.CoreFoundation 0x996d43f4 CFRunLoopRunSpecific + 452
4 com.apple.CoreFoundation 0x996da334 CFRunLoopRun + 84
5 com.apple.qmaster.do 0x51e8b460 swamp::CRAdReceiver2::ReceivingThread::runOnce() + 234
6 com.apple.AECore 0x426a6022 aecore::CThread::runThread() + 34
7 com.apple.AECore 0x426a3fb9 threadProc(void*) + 17
8 libSystem.B.dylib 0x917b8259 _pthread_start + 345
9 libSystem.B.dylib 0x917b80de thread_start + 34
Thread 18:
0 libSystem.B.dylib 0x917a9ac6 select$DARWIN_EXTSN + 10
1 com.apple.AECore 0x426a6067 aecore::CThread::runThread() + 103
2 com.apple.AECore 0x426a3fb9 threadProc(void*) + 17
3 libSystem.B.dylib 0x917b8259 _pthread_start + 345
4 libSystem.B.dylib 0x917b80de thread_start + 34
Thread 19:
0 libSystem.B.dylib 0x9178ab5a semaphore_timedwait_signal_trap + 10
1 libSystem.B.dylib 0x917b86e1 _pthread_cond_wait + 1066
2 libSystem.B.dylib 0x917e75a8 pthread_cond_timedwait_relative_np + 47
3 ...ple.CoreServices.CarbonCore 0x92fafb90 TSWaitOnConditionTimedRelative + 242
4 ...ple.CoreServices.CarbonCore 0x92faf8ce TSWaitOnSemaphoreCommon + 511
5 ...ickTimeComponents.component 0x93f58e35 ReadSchedulerThreadEntryPoint + 4698
6 libSystem.B.dylib 0x917b8259 _pthread_start + 345
7 libSystem.B.dylib 0x917b80de thread_start + 34
Thread 20:
0 libSystem.B.dylib 0x9178ab36 semaphore_wait_trap + 10
1 com.apple.TundraComponent 0x5b5e4aaa TundraUnitVideoSynchronizerEntry + 28798
2 com.apple.TundraComponent 0x5b5b98a8 TundraUnitNativeFileOutputEntry + 9152
3 com.apple.TundraComponent 0x5b5b9cd6 TundraUnitNativeFileOutputEntry + 10222
4 com.apple.TundraComponent 0x5b5e490f TundraUnitVideoSynchronizerEntry + 28387
5 libSystem.B.dylib 0x917b8259 _pthread_start + 345
6 libSystem.B.dylib 0x917b80de thread_start + 34
Thread 21:
0 libSystem.B.dylib 0x9178ab36 semaphore_wait_trap + 10
1 com.apple.AVCHDPlugin 0x6e60a788 0x6e5a0000 + 436104
2 com.apple.AVCHDPlugin 0x6e688156 0x6e5a0000 + 950614
3 com.apple.AVCHDPlugin 0x6e60ac11 0x6e5a0000 + 437265
4 libSystem.B.dylib 0x91880a6a _pthread_body + 27
Thread 22:
0 libSystem.B.dylib 0x9178ab42 semaphore_wait_signal_trap + 10
1 libSystem.B.dylib 0x917b86f8 _pthread_cond_wait + 1089
2 libSystem.B.dylib 0x9180105f pthread_cond_wait + 48
3 com.apple.AVCHDPlugin 0x6e76074f 0x6e5a0000 + 1836879
4 com.apple.AVCHDPlugin 0x6e78dd2a 0x6e5a0000 + 2022698
5 com.apple.AVCHDPlugin 0x6e7603ee 0x6e5a0000 + 1836014
6 com.apple.AVCHDPlugin 0x6e60ac11 0x6e5a0000 + 437265
7 libSystem.B.dylib 0x91880a6a _pthread_body + 27
Thread 23:
0 libSystem.B.dylib 0x9178ab36 semaphore_wait_trap + 10
1 com.apple.AVCHDPlugin 0x6e60a788 0x6e5a0000 + 436104
2 com.apple.AVCHDPlugin 0x6e688156 0x6e5a0000 + 950614
3 com.apple.AVCHDPlugin 0x6e60d238 0x6e5a0000 + 447032
4 com.apple.AVCHDPlugin 0x6e60ac11 0x6e5a0000 + 437265
5 libSystem.B.dylib 0x91880a6a _pthread_body + 27
Thread 24:
0 libSystem.B.dylib 0x9178aafa mach_msg_trap + 10
1 libSystem.B.dylib 0x9178b267 mach_msg + 68
2 com.apple.CoreFoundation 0x996d530f __CFRunLoopRun + 2079
3 com.apple.CoreFoundation 0x996d43f4 CFRunLoopRunSpecific + 452
4 com.apple.CoreFoundation 0x996da334 CFRunLoopRun + 84
5 com.apple.DiscRecording 0x91244dcf DRWorkLoop::WorkLoop() + 271
6 com.apple.DiscRecording 0x91244cad DRWorkLoop::WorkLoopEntry(DRWorkLoop*) + 17
7 com.apple.DiscRecording 0x91244a19 DRThreadObject::StartRoutine(DRThreadObject*) + 151
8 libSystem.B.dylib 0x917b8259 _pthread_start + 345
9 libSystem.B.dylib 0x917b80de thread_start + 34
Thread 25:
0 libSystem.B.dylib 0x9178ab5a semaphore_timedwait_signal_trap + 10
1 libSystem.B.dylib 0x917b86e1 _pthread_cond_wait + 1066
2 libSystem.B.dylib 0x917e75a8 pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x95b3195c -[NSCondition waitUntilDate:] + 453
4 com.apple.Foundation 0x95aea451 -[NSConditionLock lockWhenCondition:beforeDate:] + 279
5 com.apple.Foundation 0x95aea334 -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proapps.MIO 0x01066043 -[PluginLockPair scanPaths] + 729
7 com.apple.Foundation 0x95af5564 -[NSThread main] + 45
8 com.apple.Foundation 0x95af5514 __NSThread__main__ + 1499
9 libSystem.B.dylib 0x917b8259 _pthread_start + 345
10 libSystem.B.dylib 0x917b80de thread_start + 34
Thread 26:
0 libSystem.B.dylib 0x9178ab5a semaphore_timedwait_signal_trap + 10
1 libSystem.B.dylib 0x917b86e1 _pthread_cond_wait + 1066
2 libSystem.B.dylib 0x917e75a8 pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x95b3195c -[NSCondition waitUntilDate:] + 453
4 com.apple.Foundation 0x95aea451 -[NSConditionLock lockWhenCondition:beforeDate:] + 279
5 com.apple.Foundation 0x95aea334 -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proapps.MIO 0x01066043 -[PluginLockPair scanPaths] + 729
7 com.apple.Foundation 0x95af5564 -[NSThread main] + 45
8 com.apple.Foundation 0x95af5514 __NSThread__main__ + 1499
9 libSystem.B.dylib 0x917b8259 _pthread_start + 345
10 libSystem.B.dylib 0x917b80de thread_start + 34
Thread 27:
0 libSystem.B.dylib 0x9178ab5a semaphore_timedwait_signal_trap + 10
1 libSystem.B.dylib 0x917b86e1 _pthread_cond_wait + 1066
2 libSystem.B.dylib 0x917e75a8 pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x95b3195c -[NSCondition waitUntilDate:] + 453
4 com.apple.Foundation 0x95aea451 -[NSConditionLock lockWhenCondition:beforeDate:] + 279
5 com.apple.Foundation 0x95aea334 -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proapps.MIO 0x01066043 -[PluginLockPair scanPaths] + 729
7 com.apple.Foundation 0x95af5564 -[NSThread main] + 45
8 com.apple.Foundation 0x95af5514 __NSThread__main__ + 1499
9 libSystem.B.dylib 0x917b8259 _pthread_start + 345
10 libSystem.B.dylib 0x917b80de thread_start + 34
Thread 28:
0 libSystem.B.dylib 0x9178ab5a semaphore_timedwait_signal_trap + 10
1 libSystem.B.dylib 0x917b86e1 _pthread_cond_wait + 1066
2 libSystem.B.dylib 0x917e75a8 pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x95b3195c -[NSCondition waitUntilDate:] + 453
4 com.apple.Foundation 0x95aea451 -[NSConditionLock lockWhenCondition:beforeDate:] + 279
5 com.apple.Foundation 0x95aea334 -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proapps.MIO 0x01066043 -[PluginLockPair scanPaths] + 729
7 com.apple.Foundation 0x95af5564 -[NSThread main] + 45
8 com.apple.Foundation 0x95af5514 __NSThread__main__ + 1499
9 libSystem.B.dylib 0x917b8259 _pthread_start + 345
10 libSystem.B.dylib 0x917b80de thread_start + 34
Thread 29:
0 libSystem.B.dylib 0x9178ab5a semaphore_timedwait_signal_trap + 10
1 libSystem.B.dylib 0x917b86e1 _pthread_cond_wait + 1066
2 libSystem.B.dylib 0x917e75a8 pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x95b3195c -[NSCondition waitUntilDate:] + 453
4 com.apple.Foundation 0x95aea451 -[NSConditionLock lockWhenCondition:beforeDate:] + 279
5 com.apple.Foundation 0x95aea334 -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.proapps.MIO 0x01066043 -[PluginLockPair scanPaths] + 729
7 com.apple.Foundation 0x95af5564 -[NSThread main] + 45
8 com.apple.Foundation 0x95af5514 __NSThread__main__ + 1499
9 libSystem.B.dylib 0x917b8259 _pthread_start + 345
10 libSystem.B.dylib 0x917b80de thread_start + 34
Thread 30:
0 libSystem.B.dylib 0x917b8aa2 __semwait_signal + 10
1 libSystem.B.dylib 0x917b875e _pthread_cond_wait + 1191
2 libSystem.B.dylib 0x917ba3f8 pthread_cond_wait$UNIX2003 + 73
3 com.apple.vImage 0x979736ec vImageQueue_DequeueJob + 44
4 com.apple.vImage 0x979737ec vImageWorkerThreadFunc + 124
5 libSystem.B.dylib 0x917b8259 _pthread_start + 345
6 libSystem.B.dylib 0x917b80de thread_start + 34
Thread 31:
0 libSystem.B.dylib 0x917b8aa2 __semwait_signal + 10
1 libSystem.B.dylib 0x917b875e _pthread_cond_wait + 1191
2 libSystem.B.dylib 0x917ba3f8 pthread_cond_wait$UNIX2003 + 73
3 com.apple.vImage 0x979736ec vImageQueue_DequeueJob + 44
4 com.apple.vImage 0x979737ec vImageWorkerThreadFunc + 124
5 libSystem.B.dylib 0x917b8259 _pthread_start + 345
6 libSystem.B.dylib 0x917b80de thread_start + 34
Thread 32:
0 libSystem.B.dylib 0x917b8aa2 __semwait_signal + 10
1 libSystem.B.dylib 0x917b875e _pthread_cond_wait + 1191
2 libSystem.B.dylib 0x917ba3f8 pthread_cond_wait$UNIX2003 + 73
3 com.apple.vImage 0x979736ec vImageQueue_DequeueJob + 44
4 com.apple.vImage 0x979737ec vImageWorkerThreadFunc + 124
5 libSystem.B.dylib 0x917b8259 _pthread_start + 345
6 libSystem.B.dylib 0x917b80de thread_start + 34
Thread 33:
0 libSystem.B.dylib 0x917b8aa2 __semwait_signal + 10
1 libSystem.B.dylib 0x917b875e _pthread_cond_wait + 1191
2 libSystem.B.dylib 0x917ba3f8 pthread_cond_wait$UNIX2003 + 73
3 com.apple.vImage 0x979736ec vImageQueue_DequeueJob + 44
4 com.apple.vImage 0x979737ec vImageWorkerThreadFunc + 124
5 libSystem.B.dylib 0x917b8259 _pthread_start + 345
6 libSystem.B.dylib 0x917b80de thread_start + 34
Thread 34:
0 libSystem.B.dylib 0x917b8aa2 __semwait_signal + 10
1 libSystem.B.dylib 0x917b875e _pthread_cond_wait + 1191
2 libSystem.B.dylib 0x917ba3f8 pthread_cond_wait$UNIX2003 + 73
3 com.apple.vImage 0x979736ec vImageQueue_DequeueJob + 44
4 com.apple.vImage 0x979737ec vImageWorkerThreadFunc + 124
5 libSystem.B.dylib 0x917b8259 _pthread_start + 345
6 libSystem.B.dylib 0x917b80de thread_start + 34
Thread 35:
0 libSystem.B.dylib 0x917b8aa2 __semwait_signal + 10
1 libSystem.B.dylib 0x917b875e _pthread_cond_wait + 1191
2 libSystem.B.dylib 0x917ba3f8 pthread_cond_wait$UNIX2003 + 73
3 com.apple.vImage 0x979736ec vImageQueue_DequeueJob + 44
4 com.apple.vImage 0x979737ec vImageWorkerThreadFunc + 124
5 libSystem.B.dylib 0x917b8259 _pthread_start + 345
6 libSystem.B.dylib 0x917b80de thread_start + 34
Thread 36:
0 libSystem.B.dylib 0x917b8aa2 __semwait_signal + 10
1 libSystem.B.dylib 0x917b875e _pthread_cond_wait + 1191
2 libSystem.B.dylib 0x917ba3f8 pthread_cond_wait$UNIX2003 + 73
3 com.apple.vImage 0x979736ec vImageQueue_DequeueJob + 44
4 com.apple.vImage 0x979737ec vImageWorkerThreadFunc + 124
5 libSystem.B.dylib 0x917b8259 _pthread_start + 345
6 libSystem.B.dylib 0x917b80de thread_start + 34
Thread 37:
0 libSystem.B.dylib 0x917b8aa2 __semwait_signal + 10
1 libSystem.B.dylib 0x917b875e _pthread_cond_wait + 1191
2 libSystem.B.dylib 0x917ba3f8 pthread_cond_wait$UNIX2003 + 73
3 com.apple.vImage 0x979736ec vImageQueue_DequeueJob + 44
4 com.apple.vImage 0x979737ec vImageWorkerThreadFunc + 124
5 libSystem.B.dylib 0x917b8259 _pthread_start + 345
6 libSystem.B.dylib 0x917b80de thread_start + 34
Thread 38:
0 libSystem.B.dylib 0x917b8aa2 __semwait_signal + 10
1 libSystem.B.dylib 0x917b875e _pthread_cond_wait + 1191
2 libSystem.B.dylib 0x917ba3f8 pthread_cond_wait$UNIX2003 + 73
3 com.apple.vImage 0x979736ec vImageQueue_DequeueJob + 44
4 com.apple.vImage 0x979737ec vImageWorkerThreadFunc + 124
5 libSystem.B.dylib 0x917b8259 _pthread_start + 345
6 libSystem.B.dylib 0x917b80de thread_start + 34
Thread 39:
0 libSystem.B.dylib 0x917b8aa2 __semwait_signal + 10
1 libSystem.B.dylib 0x917b875e _pthread_cond_wait + 1191
2 libSystem.B.dylib 0x917ba3f8 pthread_cond_wait$UNIX2003 + 73
3 com.apple.vImage 0x979736ec vImageQueue_DequeueJob + 44
4 com.apple.vImage 0x979737ec vImageWorkerThreadFunc + 124
5 libSystem.B.dylib 0x917b8259 _pthread_start + 345
6 libSystem.B.dylib 0x917b80de thread_start + 34
Thread 40:
0 libSystem.B.dylib 0x917b8aa2 __semwait_signal + 10
1 libSystem.B.dylib 0x917b875e _pthread_cond_wait + 1191
2 libSystem.B.dylib 0x917ba3f8 pthread_cond_wait$UNIX2003 + 73
3 com.apple.vImage 0x979736ec vImageQueue_DequeueJob + 44
4 com.apple.vImage 0x979737ec vImageWorkerThreadFunc + 124
5 libSystem.B.dylib 0x917b8259 _pthread_start + 345
6 libSystem.B.dylib 0x917b80de thread_start + 34
Thread 41:
0 libSystem.B.dylib 0x9178ab36 semaphore_wait_trap + 10
1 com.apple.AVCHDPlugin 0x6e60a788 0x6e5a0000 + 436104
2 com.apple.AVCHDPlugin 0x6e688156 0x6e5a0000 + 950614
3 com.apple.AVCHDPlugin 0x6e60ac11 0x6e5a0000 + 437265
4 libSystem.B.dylib 0x91880a6a _pthread_body + 27
Thread 42:
0 libSystem.B.dylib 0x917b8aa2 __semwait_signal + 10
1 libSystem.B.dylib 0x917b875e _pthread_cond_wait + 1191
2 libSystem.B.dylib 0x917ba3f8 pthread_cond_wait$UNIX2003 + 73
3 com.apple.AVCHDPlugin 0x6ebdb708 0x6e5a0000 + 6534920
4 com.apple.AVCHDPlugin 0x6ebdd924 0x6e5a0000 + 6543652
5 libSystem.B.dylib 0x917b8259 _pthread_start + 345
6 libSystem.B.dylib 0x917b80de thread_start + 34
Thread 43:
0 libSystem.B.dylib 0x9178ab36 semaphore_wait_trap + 10
1 com.apple.TundraComponent 0x5b5e4aaa TundraUnitVideoSynchronizerEntry + 28798
2 com.apple.TundraComponent 0x5b54acee TundraUnitMPEG2DemuxEntry + 60452
3 com.apple.TundraComponent 0x5b5e490f TundraUnitVideoSynchronizerEntry + 28387
4 libSystem.B.dylib 0x917b8259 _pthread_start + 345
5 libSystem.B.dylib 0x917b80de thread_start + 34
Thread 44 Crashed:
0 com.apple.CoreFoundation 0x997b7a37 ___TERMINATING_DUE_TO_UNCAUGHT_EXCEPTION___ + 7
1 libobjc.A.dylib 0x94a725a9 objc_exception_throw + 56
2 com.apple.CoreFoundation 0x9976c3f8 +[NSException raise:format:arguments:] + 136
3 com.apple.CoreFoundation 0x9976c36a +[NSException raise:format:] + 58
4 com.apple.Foundation 0x95b0f169 _NSMutableDataGrowBytes + 1154
5 com.apple.Foundation 0x95b0ec77 -[NSConcreteMutableData appendBytes:length:] + 75
6 com.apple.AVCHDPlugin 0x6e5b0cd1 0x6e5a0000 + 68817
7 com.apple.AVCHDPlugin 0x6e5aadb3 0x6e5a0000 + 44467
8 com.apple.proapps.MIO 0x010772cb TundraPluginCallbackProc + 355
9 com.apple.TundraComponent 0x5b574d98 TundraUnitHALInputEntry + 12756
10 com.apple.TundraComponent 0x5b50d38d 0x5b500000 + 54157
11 com.apple.TundraComponent 0x5b5416df TundraUnitMPEG2DemuxEntry + 22037
12 com.apple.TundraComponent 0x5b57c63a TundraUnitVDIGInputEntry + 13711
13 com.apple.TundraComponent 0x5b591553 TundraUnitMPEG2MuxEntry + 11138
14 com.apple.TundraComponent 0x5b50d38d 0x5b500000 + 54157
15 com.apple.TundraComponent 0x5b5416df TundraUnitMPEG2DemuxEntry + 22037
16 com.apple.TundraComponent 0x5b57c63a TundraUnitVDIGInputEntry + 13711
17 com.apple.TundraComponent 0x5b592fbe TundraUnitMPEG2MuxEntry + 17901
18 com.apple.TundraComponent 0x5b50d38d 0x5b500000 + 54157
19 com.apple.TundraComponent 0x5b5416df TundraUnitMPEG2DemuxEntry + 22037
20 com.apple.TundraComponent 0x5b57c63a TundraUnitVDIGInputEntry + 13711
21 com.apple.TundraComponent 0x5b592fbe TundraUnitMPEG2MuxEntry + 17901
22 com.apple.TundraComponent 0x5b50d38d 0x5b500000 + 54157
23 com.apple.TundraComponent 0x5b5416df TundraUnitMPEG2DemuxEntry + 22037
24 com.apple.TundraComponent 0x5b57c63a TundraUnitVDIGInputEntry + 13711
25 com.apple.TundraComponent 0x5b592fbe TundraUnitMPEG2MuxEntry + 17901
26 com.apple.TundraComponent 0x5b50d38d 0x5b500000 + 54157
27 com.apple.TundraComponent 0x5b5416df TundraUnitMPEG2DemuxEntry + 22037
28 com.apple.TundraComponent 0x5b57c63a TundraUnitVDIGInputEntry + 13711
29 com.apple.TundraComponent 0x5b59f67e TundraUnitAudioOutputEntry + 18972
30 com.apple.TundraComponent 0x5b50d38d 0x5b500000 + 54157
31 com.apple.TundraComponent 0x5b59ef2c TundraUnitAudioOutputEntry + 17098
32 com.apple.TundraComponent 0x5b59eed2 TundraUnitAudioOutputEntry + 17008
33 com.apple.TundraComponent 0x5b5b654d TundraUnitBFrameFileOutputEntry + 25068
34 ...ple.CoreServices.CarbonCore 0x92fd051f CallComponentDispatch + 29
35 ....CoreMediaIOServicesPrivate 0x0111b5de TundraOutputUnitComponentCallRender + 49
36 ....CoreMediaIOServicesPrivate 0x0110080e MIOGraph::PullOutputUnits(bool, bool&, bool&, bool&) + 348
37 ....CoreMediaIOServicesPrivate 0x01101548 MIOGraph::PullAndProcessThreadEntry() + 632
38 ....CoreMediaIOServicesPrivate 0x0110264f MIOGraph::_PullAndProcessThread(MIOThreadPriv*) + 495
39 ....CoreMediaIOServicesPrivate 0x0110e3a1 start_thread + 61
40 libSystem.B.dylib 0x917b8259 _pthread_start + 345
41 libSystem.B.dylib 0x917b80de thread_start + 34
Thread 45:
0 libSystem.B.dylib 0x9178ab36 semaphore_wait_trap + 10
1 com.apple.TundraComponent 0x5b5e4aaa TundraUnitVideoSynchronizerEntry + 28798
2 com.apple.TundraComponent 0x5b5a928e TundraUnitAudioFileOutputEntry + 18915
3 com.apple.TundraComponent 0x5b5a9929 TundraUnitAudioFileOutputEntry + 20606
4 com.apple.TundraComponent 0x5b5e490f TundraUnitVideoSynchronizerEntry + 28387
5 libSystem.B.dylib 0x917b8259 _pthread_start + 345
6 libSystem.B.dylib 0x917b80de thread_start + 34
Thread 46:
0 libSystem.B.dylib 0x9178ab36 semaphore_wait_trap + 10
1 com.apple.TundraComponent 0x5b5e4aaa TundraUnitVideoSynchronizerEntry + 28798
2 com.apple.TundraComponent 0x5b51a74d TundraUnitVideoCompressorEntry + 22204
3 com.apple.TundraComponent 0x5b51b156 TundraUnitVideoCompressorEntry + 24773
4 com.apple.TundraComponent 0x5b5e490f TundraUnitVideoSynchronizerEntry + 28387
5 libSystem.B.dylib 0x917b8259 _pthread_start + 345
6 libSystem.B.dylib 0x917b80de thread_start + 34
Thread 47:
0 libSystem.B.dylib 0x9178ab36 semaphore_wait_trap + 10
1 QuickTimeH264.scalar 0x372fd1eb JVTCompEncodeFrame + 3038234
2 QuickTimeH264.scalar 0x3733db8f JVTCompEncodeFrame + 3302846
3 libSystem.B.dylib 0x917b8259 _pthread_start + 345
4 libSystem.B.dylib 0x917b80de thread_start + 34
Thread 48:
0 libSystem.B.dylib 0x9178ab36 semaphore_wait_trap + 10
1 QuickTimeH264.scalar 0x372fd1eb JVTCompEncodeFrame + 3038234
2 QuickTimeH264.scalar 0x3733db8f JVTCompEncodeFrame + 3302846
3 libSystem.B.dylib 0x917b8259 _pthread_start + 345
4 libSystem.B.dylib 0x917b80de thread_start + 34
Thread 49:
0 QuickTimeH264.scalar 0x371e3e13 JVTCompEncodeFrame + 1886274
1 QuickTimeH264.scalar 0x3724d187 JVTCompEncodeFrame + 2317238
2 QuickTimeH264.scalar 0x37320b01 JVTCompEncodeFrame + 3183920
3 QuickTimeH264.scalar 0x3733e129 JVTCompEncodeFrame + 3304280
Thread 50:
0 libSystem.B.dylib 0x9178ab36 semaphore_wait_trap + 10
1 QuickTimeH264.scalar 0x372fd1eb JVTCompEncodeFrame + 3038234
2 QuickTimeH264.scalar 0x3733db8f JVTCompEncodeFrame + 3302846
3 libSystem.B.dylib 0x917b8259 _pthread_start + 345
4 libSystem.B.dylib 0x917b80de thread_start + 34
Thread 51:
0 libSystem.B.dylib 0x9178ab36 semaphore_wait_trap + 10
1 QuickTimeH264.scalar 0x372fd1eb JVTCompEncodeFrame + 3038234
2 QuickTimeH264.scalar 0x3733db8f JVTCompEncodeFrame + 3302846
3 libSystem.B.dylib 0x917b8259 _pthread_start + 345
4 libSystem.B.dylib 0x917b80de thread_start + 34
Thread 52:
0 libSystem.B.dylib 0x9178ab36 semaphore_wait_trap + 10
1 QuickTimeH264.scalar 0x372fd1eb JVTCompEncodeFrame + 3038234
2 QuickTimeH264.scalar 0x3733db8f JVTCompEncodeFrame + 3302846
3 libSystem.B.dylib 0x917b8259 _pthread_start + 345
4 libSystem.B.dylib 0x917b80de thread_start + 34
Thread 53:
0 libSystem.B.dylib 0x9178ab36 semaphore_wait_trap + 10
1 QuickTimeH264.scalar 0x372fd1eb JVTCompEncodeFrame + 3038234
2 QuickTimeH264.scalar 0x3733db8f JVTCompEncodeFrame + 3302846
3 libSystem.B.dylib 0x917b8259 _pthread_start + 345
4 libSystem.B.dylib 0x917b80de thread_start + 34
Thread 54:
0 libSystem.B.dylib 0x9178ab36 semaphore_wait_trap + 10
1 QuickTimeH264.scalar 0x372fd1eb JVTCompEncodeFrame + 3038234
2 QuickTimeH264.scalar 0x3733db8f JVTCompEncodeFrame + 3302846
3 libSystem.B.dylib 0x917b8259 _pthread_start + 345
4 libSystem.B.dylib 0x917b80de thread_start + 34
Thread 55:
0 libSystem.B.dylib 0x9178ab36 semaphore_wait_trap + 10
1 QuickTimeH264.scalar 0x372fd1eb JVTCompEncodeFrame + 3038234
2 QuickTimeH264.scalarhttp://mac-video-compatibility.over-blog.com/sony-nex-fs700-60p-avchd-importing- workflow-in-final-cut-pro-x-7-6
seems like some formats that the camera shoots are not compatible. Not sure if this applies to your footage, but you might want to try clipwrap to do the conversion.
http://www.divergentmedia.com/clipwrap
It's not very expensive and there's a free trial to test the workflow.
Don't think there are any updates for fcp that will help this, but you might try doing a software update and see if there's anything that looks likely. -
Spanned Clip will not log and transfer
The editor:
Mac Pro 10.4.11
FCP 6.0.2.
Quicktime Version 7.4.1 (14)
30 minutes of video shot to a P2 card on an HVX200 is unable to log and transfer. Plays fine in the browser and on camera.
Workflow tried:
Write protect P2 and connect HVX200 to Mac via firewire.
Set scratch disk, then log and transfer (clip says spanned).
Error (red caution sign, tried retry, same error).
Tried P2CMS to ingest footage on a firewire drive, then log and transfer, same error.
Any suggestions?
Message was edited by: bpistoneOne word for ya: Raylight.
I had the same problem. I tried P2CMS, renaming, and any trick I could think of. Raylight to the rescue. It creates a "pointer" MOV file to the actual P2 media and then you simply import the Raylighted MOV files into FCP. No data loss, and way quicker than a P2 transfer.
Well worth the money.
http://www.dvfilm.com/raylight/
Cheers. -
Working with AVCHD: Log and Transfer FAQs
Disclaimer: Apple does not necessarily endorse any suggestions, solutions, or third-party software products that may be mentioned in the topic below. Apple encourages you to first seek a solution at Apple Support. The following links are provided as is, with no guarantee of the effectiveness or reliability of the information. Apple does not guarantee that these links will be maintained or functional at any given time. Use the information below at your own discretion.
Working with AVCHD: Log and Transfer FAQs
Log and Transfer was introduced to the product chain in Final Cut Express 4, and is the program's process for ingesting files in the AVCHD format utilizing MPEG-4 AVC/H.264 video coding and either Dolby AC-3 or uncompressed linear PCM audio coding. The most frequently observed problems relating to the Log and Transfer process are generally quite easily addressed.
What should I know before attempting to ingest my footage?
The following facts regarding the Log and Transfer process were adapted from the [Apple Knowledge Base article|http://support.apple.com/kb/TA24840?viewlocale=en_US] on transferring AVCHD in Final Cut Pro 6.0.1 but still hold true for the current version of FCE:
AVCHD support is available only on Intel-based Macintosh computers.
AVCHD camcorders typically connect to computers via USB 2.0, not FireWire.
DVD-based AVCHD camcorders are not supported in Mac OS X 10.4 or earlier.
Standard definition video recorded with AVCHD camcorders cannot be accessed in the Log and Transfer window. SD and HD clips should not be mixed on the same HDD.
Preview of AVCHD video in the Log and Transfer window is limited to 1x forward playback. Scrubbing the playhead does not update the video in the Preview area until you stop scrubbing.
When you choose to transfer AVCHD audio in the Logging area, audio is automatically mixed down to stereo.
AVCHD footage is not ingested natively but is transcoded to the Apple Intermediate Codec.
Apple Intermediate Codec files are significantly larger than the original AVCHD files. FCE does not estimate the size of a transcoded AVCHD file before ingesting, so it is possible to exceed the available space on your capture disk during transfer. Before ingesting, keep in mind that the disk space required is about ten times greater than the size of the native AVCHD file.
Which specific formats can be ingested by Log and Transfer?
Only AVCHD footage can be ingested through the Log and Transfer process. Other formats and variants such as AVCHD Lite are not supported. All video should be recorded in a frame size of either 1440x1080 or 1920x1080 and a frame rate of 25 or 29.97 frames per second. Audio recorded on AVCHD camcorders is generally at a rate of 48kHz. If your camera shoots in a format that does not comply with one of these setups then it is most likely not supported by the application and is not guaranteed to work correctly.
Which Easy Setup preset should I select before ingesting my footage?
It is extremely important to select the preset that matches your media before you attempt to ingest via Log and Transfer. There is only one Easy Setup preset that matches the frame size and rate of your footage. If you intend to ingest AVCHD clips through Log and Transfer you will first need to select one of the following presets:
AVCHD-Apple Intermediate Codec 1440x1080i50
AVCHD-Apple Intermediate Codec 1440x1080i60
AVCHD-Apple Intermediate Codec 1920x1080i50
AVCHD-Apple Intermediate Codec 1920x1080i60
If these four options do not appear under your Easy Setup list then you probably need to run Software Update and update to FCE 4.0.1. DO NOT cycle through the available presets until you find one that works - there is only one preset that matches your media and it should be evident which one to choose by the way it is named. Select the AVCHD preset that mentions your frame size and frame rate (i50 presets support both 50i and 25p frame rates; similarly, i60 presets support both 60i and 29.97p frame rates). If you do cycle through many options in the hope of selecting the correct one through guess-and-check you will probably have corrupted your preference file and need to [trash your preferences|http://support.apple.com/kb/TS2611] before continuing.
Why don't my clips appear when I open the Log and Transfer window?
Make sure your camcorder records AVCHD in a format supported by FCE4. It should be connected to one of your computer's USB ports (never connect it to an external hard drive or other external device such as your keyboard or a USB hub), powered on, and set to video playback mode.
If the camcorder +does not+ mount on your Desktop your USB port or cable may be malfunctioning. Try plugging it in to another port or using a different USB cable to see if it makes a difference.
If the camcorder does mount on your Desktop but the clips do not appear in the Log and Transfer window you will need to point the program to the directory that contains your media.
First, click the Add Folder button in the upper left of the Log and Transfer window. The button looks like this:
Then, you will need to navigate to the root directory in which your media is stored. Most camcorders call this folder "PRIVATE" or "AVCHD" and it should be located at the very top level of the camcorder when mounted. If your camcorder records to a valid AVCHD directory structure then your clips should load after the Add Folder process is completed.
I would like to keep a working backup of my original clips so that I can delete them off the camcorder's internal memory. How should I do this?
There are two main ways to keep a backup of your clips. The first is to ingest every clip on your camcorder through the Log and Transfer process, and store the Apple Intermediate Codec files the application creates in an easily accessible place such as an external FireWire drive. The advantage of this method is that you have the ability to open back up old editing projects, reconnect the media as necessary, and keep going as if you'd never left. However, due to the large amount of space AIC takes up (usually somewhere in the vicinity of 41-50GB an hour when transcoded from AVCHD), this is not always feasible.
Another often preferable approach is to copy over the root directory in which your clips are stored (usually named "PRIVATE" or "AVCHD") from the camcorder to your computer or an external drive. As long as you maintain the original file structure, you will be able to ingest your clips again at a later date using the "Add Folder" process detailed above to navigate to their new location.
My clips appear, but when I attempt to ingest a red exclamation point appears and the window displays the message "Error: No Data"
This is one of the most common problems that users experience when trying to ingest their media through the Log and Transfer process. Luckily, it also has one of the easiest solutions.
In the Log and Transfer window, click on the gear icon in the top right and select "Preferences" in the contextual menu that appears.
Make sure the video is set to transcode to the Apple Intermediate Codec and the audio is set to Plain Stereo.
After doing so, hit OK and try to ingest again.
I am experiencing a problem that is not covered in this tip or the solutions here do not work.
The best thing to do at this point would be to trash your preferences and start a new topic in the [FCE Forum|http://discussions.apple.com/forum.jspa?forumID=936&start=0] with a detailed description of your problem. Check out the user tip on [Basic Troubleshooting in Final Cut Express|http://discussions.apple.com/thread.jspa?threadID=2662419] for more information.
This is the 1st version of this tip. It was submitted on December 03, 2010 by skalicki`.
Do you want to provide feedback on this User Contributed Tip or contribute your own? If you have achieved Level 2 status, visit the User Tips Library Contributions forum for more information.Disclaimer: Apple does not necessarily endorse any suggestions, solutions, or third-party software products that may be mentioned in the topic below. Apple encourages you to first seek a solution at Apple Support. The following links are provided as is, with no guarantee of the effectiveness or reliability of the information. Apple does not guarantee that these links will be maintained or functional at any given time. Use the information below at your own discretion.
Working with AVCHD: Log and Transfer FAQs
Log and Transfer was introduced to the product chain in Final Cut Express 4, and is the program's process for ingesting files in the AVCHD format utilizing MPEG-4 AVC/H.264 video coding and either Dolby AC-3 or uncompressed linear PCM audio coding. The most frequently observed problems relating to the Log and Transfer process are generally quite easily addressed.
What should I know before attempting to ingest my footage?
The following facts regarding the Log and Transfer process were adapted from the [Apple Knowledge Base article|http://support.apple.com/kb/TA24840?viewlocale=en_US] on transferring AVCHD in Final Cut Pro 6.0.1 but still hold true for the current version of FCE:
AVCHD support is available only on Intel-based Macintosh computers.
AVCHD camcorders typically connect to computers via USB 2.0, not FireWire.
DVD-based AVCHD camcorders are not supported in Mac OS X 10.4 or earlier.
Standard definition video recorded with AVCHD camcorders cannot be accessed in the Log and Transfer window. SD and HD clips should not be mixed on the same HDD.
Preview of AVCHD video in the Log and Transfer window is limited to 1x forward playback. Scrubbing the playhead does not update the video in the Preview area until you stop scrubbing.
When you choose to transfer AVCHD audio in the Logging area, audio is automatically mixed down to stereo.
AVCHD footage is not ingested natively but is transcoded to the Apple Intermediate Codec.
Apple Intermediate Codec files are significantly larger than the original AVCHD files. FCE does not estimate the size of a transcoded AVCHD file before ingesting, so it is possible to exceed the available space on your capture disk during transfer. Before ingesting, keep in mind that the disk space required is about ten times greater than the size of the native AVCHD file.
Which specific formats can be ingested by Log and Transfer?
Only AVCHD footage can be ingested through the Log and Transfer process. Other formats and variants such as AVCHD Lite are not supported. All video should be recorded in a frame size of either 1440x1080 or 1920x1080 and a frame rate of 25 or 29.97 frames per second. Audio recorded on AVCHD camcorders is generally at a rate of 48kHz. If your camera shoots in a format that does not comply with one of these setups then it is most likely not supported by the application and is not guaranteed to work correctly.
Which Easy Setup preset should I select before ingesting my footage?
It is extremely important to select the preset that matches your media before you attempt to ingest via Log and Transfer. There is only one Easy Setup preset that matches the frame size and rate of your footage. If you intend to ingest AVCHD clips through Log and Transfer you will first need to select one of the following presets:
AVCHD-Apple Intermediate Codec 1440x1080i50
AVCHD-Apple Intermediate Codec 1440x1080i60
AVCHD-Apple Intermediate Codec 1920x1080i50
AVCHD-Apple Intermediate Codec 1920x1080i60
If these four options do not appear under your Easy Setup list then you probably need to run Software Update and update to FCE 4.0.1. DO NOT cycle through the available presets until you find one that works - there is only one preset that matches your media and it should be evident which one to choose by the way it is named. Select the AVCHD preset that mentions your frame size and frame rate (i50 presets support both 50i and 25p frame rates; similarly, i60 presets support both 60i and 29.97p frame rates). If you do cycle through many options in the hope of selecting the correct one through guess-and-check you will probably have corrupted your preference file and need to [trash your preferences|http://support.apple.com/kb/TS2611] before continuing.
Why don't my clips appear when I open the Log and Transfer window?
Make sure your camcorder records AVCHD in a format supported by FCE4. It should be connected to one of your computer's USB ports (never connect it to an external hard drive or other external device such as your keyboard or a USB hub), powered on, and set to video playback mode.
If the camcorder +does not+ mount on your Desktop your USB port or cable may be malfunctioning. Try plugging it in to another port or using a different USB cable to see if it makes a difference.
If the camcorder does mount on your Desktop but the clips do not appear in the Log and Transfer window you will need to point the program to the directory that contains your media.
First, click the Add Folder button in the upper left of the Log and Transfer window. The button looks like this:
Then, you will need to navigate to the root directory in which your media is stored. Most camcorders call this folder "PRIVATE" or "AVCHD" and it should be located at the very top level of the camcorder when mounted. If your camcorder records to a valid AVCHD directory structure then your clips should load after the Add Folder process is completed.
I would like to keep a working backup of my original clips so that I can delete them off the camcorder's internal memory. How should I do this?
There are two main ways to keep a backup of your clips. The first is to ingest every clip on your camcorder through the Log and Transfer process, and store the Apple Intermediate Codec files the application creates in an easily accessible place such as an external FireWire drive. The advantage of this method is that you have the ability to open back up old editing projects, reconnect the media as necessary, and keep going as if you'd never left. However, due to the large amount of space AIC takes up (usually somewhere in the vicinity of 41-50GB an hour when transcoded from AVCHD), this is not always feasible.
Another often preferable approach is to copy over the root directory in which your clips are stored (usually named "PRIVATE" or "AVCHD") from the camcorder to your computer or an external drive. As long as you maintain the original file structure, you will be able to ingest your clips again at a later date using the "Add Folder" process detailed above to navigate to their new location.
My clips appear, but when I attempt to ingest a red exclamation point appears and the window displays the message "Error: No Data"
This is one of the most common problems that users experience when trying to ingest their media through the Log and Transfer process. Luckily, it also has one of the easiest solutions.
In the Log and Transfer window, click on the gear icon in the top right and select "Preferences" in the contextual menu that appears.
Make sure the video is set to transcode to the Apple Intermediate Codec and the audio is set to Plain Stereo.
After doing so, hit OK and try to ingest again.
I am experiencing a problem that is not covered in this tip or the solutions here do not work.
The best thing to do at this point would be to trash your preferences and start a new topic in the [FCE Forum|http://discussions.apple.com/forum.jspa?forumID=936&start=0] with a detailed description of your problem. Check out the user tip on [Basic Troubleshooting in Final Cut Express|http://discussions.apple.com/thread.jspa?threadID=2662419] for more information.
This is the 1st version of this tip. It was submitted on December 03, 2010 by skalicki`.
Do you want to provide feedback on this User Contributed Tip or contribute your own? If you have achieved Level 2 status, visit the User Tips Library Contributions forum for more information. -
I have a 2GHz Mac Book Pro with 2 GB or ram. I use this quite a lot when shooting and editing with my Panasonic P2 (HPX2000). Usually, I log and transfer DV, DVC Pro and DVC Pro 50 files with no issues. The other day, I shot a concert in 720P and when trying to log and transfer a 40 minute video, it would not finish. It would show the file transferring, but show the exclamation point at next to it, alerting me that it had problems. I was able to transfer over small chunks and edit them together in FCP, but I wonder if this is a ram issue or something like that. Any thoughts?
#36 - One or More P2 files failed to import.
Shane's Stock Answer #36 - "One or more clips failed to import..."
Very often in the field with this camera the camera operator will delete clips from the P2 card that they just don't like. That is the beauty of this camera. But, the still for that video file (located in the CLIP folder in the CONTENTS folder)...the still that you see when you are in the P2 Import window...is not deleted. So you will see the image, and the name, but the video file would have been deleted.
What you can do it compare the file names in the VIDEO folder and CLIP folder and see if anything is missing. If something is, then you know what the problem is. You can then just import the rest a few at time, skipping that one.
ALSO...in the P2 Import window...in the P2 Browser, there is a little sprocket drop down menu. Click on that and choose PREFERENCES. Uncheck REMOVE PULLDOWN and then try importing again.
ALSO...make sure your file names aren't too long. Try shortening them and see if that works.
ALSO make sure that the folders that contain the CONTENTS folder doesn't have any odd characters like /!@#$%^&*()?. -
Very very slow import using LOG and Transfer
I am using a CANON VIXAIA HF10.and the clips are importing very very slow. The max time on each clip is only 5 min or so. Is there a way to speed this up? Thanks.
Log and transfer only supports AVCHD. It does not support AVCHD Lite, nor will it work with Motion JPEG media. You could use third party software to convert it, or iMovie and then export a QuickTime movie from there in the correct codec and format.
-
Log and transfer progressive files
Hi,
When I try to log and transfer clips shot in progressive HD (AVCD) there is no image in the log and transfer screen - it is all green, although I can hear the sound of the clip, when I play it.
It also gets transferred, but as I can't see the clip before transferring it, I can't make in and out points.
Very frustrating!I believe the HMC151 is an AVCCAM and the PH mode you are shooting is not directly compatible with FCE. My understanding is that currently only FCPro can capture progressive from these cameras. There may be a workaround for FCE and perhaps Tom Wolsky will see your post here and can contribute an answer.
In the meantime, try shooting some 1080i50 in HA or HG mode and see if you can import that successfully using the AVCHD 1080i50 Easy Setup.
Maybe you are looking for
-
PE11 crashes when animating layers in Save for Web?
After months of saving GIFs just fine, Elements 11 has stopped working properly. I've tried uninstalling, resetting preferences, and reducing the file size, but when trying to save a GIF, all I get is a frozen screen that says "Export: Save for Web a
-
Windows 8.1 UI in boot camp faster than Yosemite UI
I'm slowly beginning to think I'm going to bin my late 2010 17in Macbook Pro. Since moving up to yosemite the UI responsiveness and smoothness had dropped significantly. The only way to speed things up slightly is to reduce transparency and enable hi
-
What is the main advantage in EJB Transactions.
My question is i can have a stateless bean to accept the client requests and will set the Autocommit of database to false and which will invoke the java bean component based up on transaction code and passes the database connection object . the java
-
Error in Item Category Determination
Hai, When I am trying to define the Item category determination for the quotation type I get the following error message "only quotation items can be assigned to package transaction types" Can you please let me know the reason for the error Thanks, V
-
Couple of tech questions about the flash drives in the new MBA. First, SSD's only have a limited number of rewrite cycles, so what is the benchmark with the MBA drives..? Second, what is the issue with TRIM..? I don't think OS X supports the TRIM com