AVCHD Log and Transfer Crashes FCP
We've got one machine in our facility that flat refuses to transfer AVCHD clips from the SD card.
We've tried all the usual fixes (Removing Perian which wasn't even on the machine, but I did install it then uninstall it to see if that might help!) Know about the FX Factory update but it's not on the system. I've tried different settings in the L&T prefs such as removing duplicate frames, different capture codecs etc. Nothing works.
So the symptoms are, you can see all the clips no problem, but as soon as you add one to the queue, you get a brief period of nothing, then the beach ball for about 5 seconds then a 'poof' crash of FCP. Tried capturing from 2 card reader, direct from the camera...zilch, crashes everytime without fail...sorry, with fail!
Machine spec:
FCP 6.0.5 (Can't update to 6.0.6 because of my RAID and server config)
Mac Pro Intel Dual Core Xeon 3GHz
4 MB RAM
Black Magic Extreme HD SDI card
Mac OSX 10.5.5 (again cannot update because of my XSAN config)
Help appreciated...
Hi DevRona, welcome to the Apple Discussions forum for FCP
buzz online is that perian the add on for quicktime has something to do with it. but i cannot even find it on my system!
Perian is a 3rd party component and is not installed unless you installed it yourself
...mine crashes after that balloon thing appears...
If you want apt advice then you need to be clear and concise in your description of your problem
what am i doing wrong
Start a new thread, don't piggyback someone else's. List all your pertinent hardware and software specs. Take your time to clearly describe the problem as best you can ... remember that none of us are there and can see what you may or may not be doing wrong. If you do that then there is a good chance that folks here will do their level best to help you.
Best
Andy
Similar Messages
-
SONY XDCAM LOG and TRANSFER CRASHING FCP
I am trying to log and transfer xd cam footage. every time i open the log and transfer window, FCP crashes. What is the cleanest way to get rid of the xdcam plugin.
the error message reads:
The application Final Cut Pro quit unexpectedly after it was relaunched. The problem may have been caused by the SonyXDCAM plug-in.
I have tried to get rid of it and obviously failed because i keep getting that message which tells me it's still there.
Can someone give me a step by step on how to get rid of it?
Model Name: Mac Pro
Model Identifier: MacPro3,1
Processor Name: Quad-Core Intel Xeon
Processor Speed: 3.2 GHz
Number Of Processors: 2
Total Number Of Cores: 8
L2 Cache (per processor): 12 MB
Memory: 8 GB
Bus Speed: 1.6 GHzShane's Stock Answer #44: FCP acting weird or unusual. Just not like is normally should
If the program was working fine, and now isn't, or just isn't working the way it should, the first things to do are:
1) Trash your FCP preferences. Download the Preference Manager from Digital Rebellion: http://www.digitalrebellion.com/pref_man.htm
http://www.kenstone.net/fcphomepage/trashing_fcpprefs.html
2) Open the Disk Utility and Repair Permissions.
3) Shut down for 10 min. Go for a quick walk around the block and get SOME exercise today. Come back, turn on the computer and see how things are.
4) (optional) Do the Hokey Pokey and turn your self about. Results may vary.
Shane -
Not sure what is going on. Been using Log and Transfer for 8 months to capture video from P2 Cards in Panasonic HVX200 recorded in 720p60. Haven't had a problem before. Today, went to capture new footage (only about 15 minutes worth) and the first time I briefly saw the dialog window before FCP crashed, but since then, after restarting, closing the open files, creating a new project, making sure software was up to date, etc, it keeps crashing before even showing the window. I just get the 'spinning beachball of death' for about 5 seconds before the crash.
I also tried just transferring the files to the local drive first than running the log and transfer, but that didn't work either.
I don't have FCP tricked out with any plug-ins, with the exception of Flip for Mac, but that has been running fine for all 8 months.
Any ideas?Shane's Stock Answer #44: FCP acting weird or unusual. Just not like is normally should
If the program was working fine, and now isn't, or just isn't working the way it should, the first things to do are:
1) Trash your FCP preferences. Download the Preference Manager from Digital Rebellion: http://www.digitalrebellion.com/pref_man.htm
http://www.kenstone.net/fcphomepage/trashing_fcpprefs.html
2) Open the Disk Utility and Repair Permissions.
3) Shut down for 10 min. Go for a quick walk around the block and get SOME exercise today. Come back, turn on the computer and see how things are.
4) (optional) Do the Hokey Pokey and turn your self about. Results may vary.
Shane -
Log and Transfer Crash FCP 6.06, from Canon Vixia HF20
I am having a strange problem in logging and transferring from FCP 6.06. I have been logging and transferring from my Canon Vixia HF20 without any problems for monthes. Then I have been granted access to a Sony HXR-NX5U NXCAM from work, I logged and Transferred from the flash memory unit HXR-FMU128, without any problems. But ever since I logged and Transfered from the sony flash unit, in attempting to log an transfer from my Canon Vixia has caused FCP to crash every single time. I then log and transfer again from the Sony Flash unit without any problems, after having dealt with the Canon transfer crashes.
Currently log and transfer from Song Flash unit always works, from Canon Vixia never works in FCO 6.06.....boooOOO!
Anyone else experience a problem like this?Hi Eugene
Seems like maybe your FCP's preferences have taken a turn for the worse ... at least I haven't heard of this being a widespread issue so I would recommend you start by using a free app like Digital Rebellion's Preference Manager to make a backup copy of your current FCP user preferences, then use the same Preference Manager app to "trash" those existing prefs. Now restart FCP and see if the problem still persists .. hopefully not. If the problem is still there then you can use Preference Manager (again) to restore your previous prefs from the backup copy you made ... and you are back where you started.
Post back
Andy -
Mavericks and Final Cut Pro 7 - Log and Transfer crashes
Hi all. I (perhaps unintelligently) upgraded to OSX Mavericks on my Mac Pro while working on a project in Final Cut Pro 7. What is good news is that FCP 7 still works for the most part. The bad news is that Log and Transfer crashes.
I have a Panasonic P2 camera and I dump video via FireWire 800. When I first click on the Log and Transfer button, nothing happens. When I click on it again, the Log and Transfer window opens, but then FCP 7 crashes.
Is there any way to get video from my P2 card into the project without Log and Transfer?
Also, would any of these options work?
Trash preferences (working to figure out how to do that on Mavericks)
Worst case, re-format and re-install Lion (Don't have much time to do that)
Please let me know if you have a work around or a fix for this. I need to have this solved TODAY.
I appreciate your help in advance.I am having the same issue on my iMac that was udated to Mavericks a while back and apparently I haven't tried to log and transfer anything since.
The error comes up everytime I have a my Sandisk High Speed Card in my lexar Fire Wire 800 card reader. The Log and Transfer screen pops up and it starts adding the clips and instead of populating the screen, it crashes. Mine also says FCP quit while using the canonIHL plug in, here's a screen shot of the indication.
I agree, this needs to be resolved ASAP. I'm dead in the water. The only thing I can do is transfer the raw files into a folder somewhere, then import the clips, but then to have them as ProRes files I guess I would have to use compressor before hand. I've done it before, but it never runs as smoothly without it being natively imported. -
Refresher for log and transfer in FCP 7
Hi,
I need a bit of a refresher to using log and transfer in FCP 7 what setting do I use for XDCAM ? Do I set it to AVCHD?
Please help
Thank you
JeffHave you loaded the xdcam plug in?
https://discussions.apple.com/docs/DOC-2721
Otherwise, I think you have the choice of keeping it as xdcam or converting to prores when you log and transfer. xdcam are smaller file sizes, while prores is generally less taking on the system. -
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. -
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. -
Log and transfer causes FCP to crash with long clips
Hi. I am trying to import a few 2 hour+ clips using Log and Transfer from my Sony NX5. Once the destination clip has reached approx 60GB, FCP crashes every time. There is plenty of disk space left.
I have tried trashing preferences and also changing scratch disks. I am turned off time machine. I am really worried that I wont be able to get this footage onto my machine.
Any ideas?
ThanksIn the end Clipwrap saved the day on this project.
This did happen to me again though on yet another project, where the files were around an hour long this time. In the end I got it to work, not sure the solution but tried the following:
- Selected a different easy setup (choose PAL) - this fixed the problem for a colleague of mine, even though it doesn't seem logical
- Used my internal drive as a scratch disk instead of my firewire drive (normally this is not a problem)
I haven't tried this with the really long clips, as Clipwrap saved me.
Many thanks for suggestions. -
FCP Log and Transfer Crashes on new imac
Hey Guys,
I just purchased a new intel imac. I'm running FCP 6.0.6. Every time i try to open log and transfer it immediately crashes Final Cut. i already tried deleting and reinstalling FCP with no luck. I read some of the forums and tried to disable perian, no luck. it constantly crashes every time i try to open log and transfer. is there anything i can do to fix this issue? please help!You need to use FCS Remover to completely uninstall FCS. You should never use Migration Assistant with any pro apps that call on system resources; actually you probably shouldn't use it for anything except docs and email. You will need to completely reinstall FCS from the discs.
-
Prokit 7 makes Log and Transfer Crash
I've stayed on Prokit 5.1 for a while now, since it does not create any problems, but I recently tried to upgrade to 7. FCP opens, but when opening log and transfer, it crashes again. I have downgraded back to 5.1 for now, but then I can't use aperture. Anyone else facing this problem and have a workaround?
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 -
Sony CX-160 camcorder compatible in Log and Transfer in FCP X?
Looking at Apple FCP X compatibility list and it is not on there. I know this list is not anywhere accurate. Camera is AVCHD .mts file format.
Anyone have this camcorder to confirm this first hand either way?
Thanks in advance. Do not have the FCP X yet. Just seeing what I am getting myself into.+Have you updated to the latest version of FCP?+
No, I'm currently running 6.0 with QT 7.2 on OS 10.4.10. In searching the tech forums I'm finding a lot of people having problems with P2 and FCP 6.0.2 and QT 7.3 (which requires OS 10.4.11) so I've steered clear.
+How have you copied the p2 volumes?+
Yes. The P2 volumes have been copied to hard drives. I'm not anywhere near the P2 cards at this point.
+Where are they located?+
LaCie 500 drives
+Did you write protect to the p2 card before copying?+
You mean on the original P2 cards? I don't know, but the files have already successfully been copied to the current hard drives. I can convert them to QT's using Log and Transfer without any trouble. What I can't do is see them in the Log and Transfer viewer before I import. I'd like to be able to do that so I can break them down into more manageable QT files on transfer.
Martin -
AVCHD log and transfer jerky jumpy during playback
I've been given some files from a Sony HDR-CX12 to export to dvd. The files playback fine in the log and transfer window but stutter / jump in the viewer window and also when added to the sequence.
The files provided are
a AVCHD folder
a AVF_INFO folder
a DCIM folder
and two locked Unix executable files.
Final Cut Easy Set Up
Format - HD
Rate - 29.97
Use - 1080p30 FireWire Basic
Log and Transfer
Transcode to Apple ProRes 422
Final Cut Pro version 6.0.5
System
Os 10.5.6
processor 2 x 2.8 GHz quad-core Intel Zeon
Memory 14 gb
Hard drive containing files is internal.
side note - i did migrate the system from a PowerPC but have since updated the lastest FCP update.
If anyone has any help or tips to get these files playing back properly I'd really appreciate hearing from you.Do you have Perian installed? I had the same problem, but when I disabled Perian in the System Preferences panel and re-transfered the footage, everything looked fine. Once your footage has been re-transfered, you can re-enable Perian.
-
AVCHD Log and Transfer Woes. Please advise.
Folks, I am using the latest version of FInal Cut (7.02) to log and transfer AVCHD content from a Panasonic Lumix GH1. Many clips get imported but many stop with errors ( a stream error as note by a exclamation mark in a red alert icon in the status column) even though they play back in the log and transfer window, VLC, Toast 10.
I've had to resort to using Toast 10 to transcode which is disheartening that it can and FCP can't. Plus it's slow. Another strange thing is that in FCP the number of clips that are successfully transcoded outnumber the number of clips for the same reel in Log and Transfer.
Per some other message board to troubleshoot, I've updated my FxFactory plugin app, uninstalled Perian, deactivated the pulldown feature in Log and Transfer, and changed the AVCHD audio settings to plain stereo. None of these efforts has changed the stream errors I am getting.
I could use some advice on this.L&T and Lumix GH1 footage needs the file structure in the 'PRIVATE' folder intact.
So don't delete a single thing in there from the computer - if you want to remove clips you must do it from the camera. And when doing back-ups to a harddrive, copy the entire PRIVATE folder and again, don't change anything in there once it's on the harddrive. Then L&T can still access the clips, you don't have to do it from the SDHC card.
And don't include photo captures. -
Every time I open my Log and Transfer window FCE crashes right away. I don't even have a camcorder attached. Any ideas?
Processor Name: Intel Core 2 Duo
Processor Speed: 2.4 GHz
Number Of Processors: 1
Memory: 1 GBI am getting what might be the same problem.
The log and transfer window just hangs and I get the spinning beachball.
I am trying to transfer from SD5 AVCHD and the problem only happens with one SD card. Doesn't seem to be corrupt though as it works on the camera.
Seems to Crash iMovie 08 too!
Any help would be much appreciated!
Message was edited by: Eye Doc
Maybe you are looking for
-
I have a apple component AV TV out cable (red, green,blue + red,white) and have had this connected to TV for about 6 months working fine. I moved the TV disconnected cables to move now I can only get video and no sound back on TV. Any suggestions ?
-
Have problem with Fax in AS5400HPX Voice Gateway
I've problem in my system.AS5400 Voicegateway.when I send fax from my system,it's ok.But when i receive fax from another number in out system,data in fax loss.about 1/2 data in paper loss. -from my system to outside :ok -from outside to my system: no
-
Payment Card Vs Procurement Card
Hi Experts, I know that 'Procurement card' can be given as a payment method in External requirement / Purchase order in SRM. The same can be cnfigured under SPRO-->Supplier Relationship Management --> SRM server --> Procurement Card. However, I am no
-
Changing from classic withholding tax to extendend withholding tax
Hi all the client is using clasic withholding tax. now they want extendend withholding tax can you give clarification on this . what are the changes i need to modify? this is very urgent Thanks Krishna
-
Storage location not found in MIGO for 101 movement type
Hi all, While posting goods receipt in MIGO for purchase order using 101 movement type,i am not getting the storage location field..Though goods is getting posted in migo transaction,it is not getting updated in the stock while seeing it in mmbe... c