XDCam woes

Question

Level 1

9 points

XDCam woes

This applies to XDCam HD and XDCam EX footage: Crashing every two minutes. Jerky playback. Solution is to re-launch the app, or trash prefs and relaunch the app about every three minutes. I have to save after every single edit. I'm not kidding. This is horrible.

FCP works GREAT with ProRes footage. I've re-installed FCP.

I can't afford to be transcoding all my footage every time I get an XDCam project. I just started one with three hours of source footage, or about 250 G of XDCam HD footage. Some people tell me they don't have problems with XDCam, but it's been nothing short of a nightmare since the first frame I imported.

The crash log ALWAYS says "MPEG2 Component" in the first ten lines or so.

Am I alone? Is transcoding my only option?

Can I reinstall Quicktime? If so, how?

Mac Pro 3,1, Mac OS X (10.6.3)

Posted on Mar 24, 2011 11:45 AM

Reply

Answer 1

Shane Ross

Level 8

43,110 points

Mar 24, 2011 12:10 PM in response to Jim Curtis

Edit the footage in a ProRes sequence...see what that does for you.

Shane

Reply

Answer 2

Jim Curtis Author

Level 1

9 points

Mar 24, 2011 12:30 PM in response to Shane Ross

OK, I gave that a try, and it crashed a few minutes later.

For academic purposes, look at this crash log: 16 crashes since the last report today. Look at lines 9 & 10. That's what all the crash logs say. I'm no engineer, but I'm convinced the problem is the codec.

Date/Time: 2011-03-24 14:27:07.469 -0500
OS Version: Mac OS X 10.6.3 (10D578)
Report Version: 6

Interval Since Last Report: 761667 sec
Crashes Since Last Report: 16
Per-App Interval Since Last Report: 213280 sec
Per-App Crashes Since Last Report: 15
Anonymous UUID: 0B4A7EC5-05D6-43FB-8D02-F664E2973306

Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Application Specific Information:
abort() called

Thread 0 Crashed: Dispatch queue: com.apple.main-thread
0 libSystem.B.dylib 0x946f6132 __kill + 10
1 libSystem.B.dylib 0x946f6124 kill$UNIX2003 + 32
2 libSystem.B.dylib 0x947888e5 raise + 26
3 libSystem.B.dylib 0x9479e99c abort + 93
4 libstdc++.6.dylib 0x96ff5fda _gnu_cxx::__verbose_terminatehandler() + 433
5 libstdc++.6.dylib 0x96ff417a _cxxabiv1::_terminate(void (*)()) + 10
6 libstdc++.6.dylib 0x96ff41ba _cxxabiv1::_unexpected(void (*)()) + 0
7 libstdc++.6.dylib 0x96ff42b8 _gxx_exception_cleanup(_Unwind_ReasonCode, UnwindException*) + 0
8 libstdc++.6.dylib 0x96ff4658 operator new(unsigned long) + 101
9 com.apple.AppleHDVCodec 0x0fe98569 MPEG2CompressorComponentDispatch + 422041
10 com.apple.AppleHDVCodec 0x0fe90a73 MPEG2CompressorComponentDispatch + 390563

Reply

Answer 3

Shane Ross

Level 8

43,110 points

Mar 24, 2011 12:37 PM in response to Jim Curtis

YOu didn't post enough of the crash log. A bit more please.

Shane

Reply

Answer 4

Jim Curtis Author

Level 1

9 points

Mar 24, 2011 12:41 PM in response to Shane Ross

OK. All I had to do was keep working, and it crashed again.

Is this long enough?

BTW, thanks for your interest in my issue, Shane.

Date/Time: 2011-03-24 14:39:59.715 -0500
OS Version: Mac OS X 10.6.3 (10D578)
Report Version: 6

Interval Since Last Report: 762436 sec
Crashes Since Last Report: 17
Per-App Interval Since Last Report: 213999 sec
Per-App Crashes Since Last Report: 16
Anonymous UUID: 0B4A7EC5-05D6-43FB-8D02-F664E2973306

Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Application Specific Information:
abort() called

Thread 0 Crashed: Dispatch queue: com.apple.main-thread
0 libSystem.B.dylib 0x946f6132 __kill + 10
1 libSystem.B.dylib 0x946f6124 kill$UNIX2003 + 32
2 libSystem.B.dylib 0x947888e5 raise + 26
3 libSystem.B.dylib 0x9479e99c abort + 93
4 libstdc++.6.dylib 0x96ff5fda _gnu_cxx::__verbose_terminatehandler() + 433
5 libstdc++.6.dylib 0x96ff417a _cxxabiv1::_terminate(void (*)()) + 10
6 libstdc++.6.dylib 0x96ff41ba _cxxabiv1::_unexpected(void (*)()) + 0
7 libstdc++.6.dylib 0x96ff42b8 _gxx_exception_cleanup(_Unwind_ReasonCode, UnwindException*) + 0
8 libstdc++.6.dylib 0x96ff4658 operator new(unsigned long) + 101
9 com.apple.AppleHDVCodec 0x20a5d569 MPEG2CompressorComponentDispatch + 422041
10 com.apple.AppleHDVCodec 0x20a55a73 MPEG2CompressorComponentDispatch + 390563

Thread 1: Dispatch queue: com.apple.libdispatch-manager
0 libSystem.B.dylib 0x946bbb42 kevent + 10
1 libSystem.B.dylib 0x946bc25c dispatch_mgrinvoke + 215
2 libSystem.B.dylib 0x946bb719 dispatch_queueinvoke + 163
3 libSystem.B.dylib 0x946bb4be dispatch_workerthread2 + 240
4 libSystem.B.dylib 0x946baf41 pthreadwqthread + 390
5 libSystem.B.dylib 0x946bad86 start_wqthread + 30

Thread 2:
0 libSystem.B.dylib 0x946b4286 select$DARWIN_EXTSN + 10
1 com.apple.CoreFoundation 0x91ab482d __CFSocketManager + 1085
2 libSystem.B.dylib 0x946c2a19 pthreadstart + 345
3 libSystem.B.dylib 0x946c289e thread_start + 34

Thread 3:
0 libSystem.B.dylib 0x94695342 semaphore wait_signaltrap + 10
1 libSystem.B.dylib 0x946c2eb8 pthread_condwait + 1089
2 libSystem.B.dylib 0x9470b42f pthread condwait + 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 0x946c2a19 pthreadstart + 345
7 libSystem.B.dylib 0x946c289e thread_start + 34

Thread 4:
0 libSystem.B.dylib 0x94695342 semaphore wait_signaltrap + 10
1 libSystem.B.dylib 0x946c2eb8 pthread_condwait + 1089
2 libSystem.B.dylib 0x9470b42f pthread condwait + 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 0x946c2a19 pthreadstart + 345
7 libSystem.B.dylib 0x946c289e thread_start + 34

Reply

Answer 5

Shane Ross

Level 8

43,110 points

Mar 24, 2011 1:08 PM in response to Jim Curtis

Says something you already know...

MPEG Media

This crash appears to have been caused by MPEG media (or MPEG-derived media such as XDCAM, HDV or H.264) in the timeline. MPEG-based media is not recommended for editing in Final Cut Pro.
Suggested Actions

Set the codec of your sequence to ProRes in Sequence Settings.
Alternatively, and for best results, transcode any HDV, MPEG-2, XDCAM, AVCHD, H.264 or other long-GOP media into an editing-friendly format such as ProRes or Apple Intermediate Codec (AIC).
Relevant Line

9 ÃÂ ÃÂ com.apple.AppleHDVCodec ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ 0x20a5d569 MPEG2CompressorComponentDispatch + 422041

Shane

Reply

Answer 6

Mar 24, 2011 1:14 PM in response to Jim Curtis

Hi there,
whilst Shane checks out the crash log, I've found (with many projects involving xdcam) that mixing it with other formats is the big no no. Now this may sound odd but Ive found that if you have to work with with xdcam and cant go prores (definitely my preference!) then doing the following has helped enormously with the type of crashing you are seeing

1. sequence same as source (ie xdcam) and dont set to render in prores ( I know this goes against common advice, but creating prores render files seems to create the mixed format timeline which causes crashes in the first place!)
2. thumbnails off (critical this)
3. only keep 1 or 2 sequences open in the timeline

As I said my preference is to work in prores but as we all know, sometimes this is just not possible
best of luck
Andy

Reply

Answer 7

Jim Curtis Author

Level 1

9 points

Mar 24, 2011 1:21 PM in response to Shane Ross

Well Shane, that's not surprising, but I'm glad to see the confirmation of my suspicion. It's curious that you say, "MPEG-based media is not recommended for editing in Final Cut Pro" when XDCam (and other long-GOP MPEG) is specifically endorsed by Apple and used as a selling point for using FCP (link from the apple FCS site):

http://www.apple.com/finalcutstudio/finalcutpro/broad-format-support.html

They say you can mix it in the timeline with other formats, suggesting that we can use it with abandon willy nilly to our heart's content.

I realize I can transcode all my footage to ProRes before editing, but that's a tough call to make. I have to weigh the time it takes to transcode against the time lost due to crashes and lost work, and decide which is the path of least resistance.

Anyway... thanks so much for confirming my suspicion, Shane. It appears that FCP just isn't ready for MPEG editing. Maybe (fingers crossed), it'll work better under the next "awesome" release.

Regards,
Jim Curtis

PS. I'm going to tag this as "question answered" but the issue is far from resolved, as far as I'm concerned.

Reply

Answer 8

Shane Ross

Level 8

43,110 points

Mar 24, 2011 1:27 PM in response to Jim Curtis

Marketting people don't have real world experience. FCP is designed to work with it...and it does. But it will crash if the loads are too heavy, if you mix in other formats...any number of things. They might test a couple things and go "yup, it works." But then in the real world we do all sorts of things they didn't take into consideration, like editing on projects longer than 10 min.

Shane

Reply

Answer 9

Jim Curtis Author

Level 1

9 points

Mar 24, 2011 1:29 PM in response to Jim Curtis

Hi Andy,

Two things:

1. How do I turn of Thumbnails? I set my User Preferences > Timeline > Thumbnail Display on Names, but the Thumbnails persist.

2. It's not realistic for me to work with just a couple of Sequences open. I organize my footage by sequences, and my rough process is to switch between sequences, cutting from one and pasting into a master Sequence. I suppose I could create one huge sequence with all my selects on it. But dang it, the app is supposed to accommodate me, not the other way around. But, I'm used to employing workarounds with buggy software. I'll give it a try. I'm desperate. I'll try anything!!

Thanks much,
Jim

Reply

Answer 10

Mar 24, 2011 1:37 PM in response to Jim Curtis

Hi Jim

turn off thumbs by highlighting your current sequence in the browser then
sequence>settings>timeline options.
what you did affects new sequences not old.
I know its a pain with the sequences, but try it and see if it helps for a bit
good luck
Andy

Reply

Answer 11

Jim Curtis Author

Level 1

9 points

Mar 24, 2011 3:22 PM in response to andy chastney

Andy,

Thanks to you, I just discovered that you can select all the clips in an active sequence, and then follow your instructions, and the Thumbnails will disable.

I will give this a try. I'm going to take a break from editing for a while. I'll let you know later if your tips helped.

Thanks again,
Jim

Reply

Answer 12

Jim Curtis Author

Level 1

9 points

Mar 25, 2011 8:37 AM in response to Jim Curtis

Reporting back. I'm sorry to say that disabling thumbnails and just working with two Sequences has failed to stop the crashing.

I get crashes most often when shuttling quickly through a timeline - moving the CTI quickly left or right.

And other times, I get crashes simply switching from one Sequence to another.

Reply

Answer 13

Mar 25, 2011 9:10 AM in response to Jim Curtis

Hi Jim sorry theres no improvement. the symptoms you are showing are identical to what I had.
As a final try before going down a transcode route, you have only xdcam in your project right? no jpegs etc.
try throwing out all your renders using render manager and re rendering using same as codec, and also throw out your thumbnail cache (documents>fcp documents>thumbnail cache files), reboot and it will rebuild it. If you can stand the pain, you could try repeating this setting renders to be in pro res as is normally recommended, but as I said before this did not work for me.
out of interest, are you using an aja or blackmagic breakout box? and how much ram have you got? how big is the project file? and are other apps open?
cheers
Andy

Andy

Reply

Answer 14

Jim Curtis Author

Level 1

9 points

Mar 25, 2011 3:10 PM in response to andy chastney

Hi Andy,

My project was just getting underway, so all the footage is XDCam HD 422 50Mbit. I have 32GB RAM; a crazy fast RAID (>1GBs reads; >700MBs writes). I do in fact have an AJA Kona LHi, and it is suspected in many of my crashes. But before I wrote my OP here, I uninstalled my AJA CP software to remove it from the equation; and I had Video Preview off. I know that Video Preview through the AJA is asking for trouble, but with it off, I still have it.

Project file is about 6Mb now. I always have other apps running. Like Mail, Safari, After Effects, Activity Monitor, and often Open Office to refer to my script, and Excel to keep track of my time (because I charge by the hour).

And as I mentioned, I have this situation most of the time, and with ProRes footage, have few problems.

I did trash my render files; I didn't have many as I was just starting my rough cut. All my footage is MOS. I've taken the project to After Effects to show client a sample, and won't be editing again until next week.

Thanks,
Jim

Reply

Answer 15

May 25, 2011 9:44 AM in response to Jim Curtis

Hi Jim,

Do you have any updates on your issues?

It makes me sad to see so many people struggling with Long-GOP MPEG-2 in Final Cut Pro. Issues like these have been the story of my life for well over a year now, and I am starting to get really tired of it. I have tried all the suggested tips and tricks, without any luck. Transcoding to ProRes obviously helps, but for a lot of people transcoding to an intermediate codec is not really an option. It might work fine if you only have a single edit suite to support, but with a large number of FCP systems the storage requirements are quite the challenge.

XDCAM discs are very affordable, and the Sony broadcast cameras, and recently the prosumer XF series, are really quite nice. I-frame based HD MPEG-2 from the NANOFlash seems to be more stable in FCP, but it comes at a cost - You need to at least double or triple your storage capacity. Storage requirements for XDCAM HD422 with a constant bitrate of 50Mbit is a big selling point for a lot of people and organizations. If only editing these Long-GOP MPEG-2 based formats was a little more stable in Final Cut Pro... as you would expect when Apple advertise that they support it.

Any form of HD Long-GOP MPEG-2 is decoded by the AppleHDVCodec.component (located in /Library/QuickTime). The codec is obviously the problem here, as working with other i-frame based media works fine most of the time. XDCAM EX is quite unstable too. After an editing session with HD Long-GOP MPEG-2 based media, you will most likely also see a lot of memory allocation errors (malloc) in the system.log in /Applications/Utilities/Console. This makes me think there are some memory leak problems going on when decoding Long-GOP MPEG-2. As you have most likely already experienced, the worst you can do is mixing other codecs together with Long-GOP MPEG-2 in the same sequence.

XDCAM HD422 support was introduced with Final Cut Pro 6.0.3, in Apple HDV Codec 1.4.

Apple HDV Codec 1.4

This release of Apple HDV Codec provides XDCAM HD422 support in Final Cut Pro.

Pro Applications Update 2008‑01 Release Notes

I do not have any experience with XDCAM HD422 projects from back then, but it seems like some XDCAM HD422 projects have become more unstable after Apple HDV Codec 1.6 was introduced with Final Cut Pro 7.0.3. You might want to try reverting to Apple HDV Codec 1.5 (you can extract it from the AppleHDVCodec.pkg on the Installer DVD using Pacifist). I have seen some projects become more stable after doing that.

Btw. you can analyze your own FCP crash logs, just like Shane Ross did, using Jon Chappel's (Digital Rebellion's) Crash Analyzer, which is part of the FCS Maintenance Pack 🙂

Reply