qtKitErrorCatchAll (-43) error

Question

Level 2

462 points

qtKitErrorCatchAll (-43) error

I've noticed this one for a while and has finally irritated me to the point of coming on here and seeing if anyone else has seen this.

Basically, I used to be able to export video or audio from quicktime to an Xsan volume without a problem, but more and more recently (until now where its about 90% of the time), exporting anything to a Xsan volume from QT produces: qtKitErrorCatchAll (-43)

Any idea what this error is?

(2) dual 2.5 g5, Mac OS X (10.4.2)

Posted on Jan 7, 2008 3:17 PM

Reply

Answer 1

Jan 18, 2008 7:44 PM in response to Alex Geis

Same here exactly the same error, I just recently seen this issue just this january, i did nothing to update anything, exporting to local drives is successful, but exporting in xsan error qtKitErrorCatchAll (-43), rebooting the system does not help at all. Where is the logs of the Quicktime, Tried it on an xserve xsan client the exporting will finished but macpros it will not.

Reply

Answer 2

Alex Geis Author

Level 2

462 points

Feb 5, 2008 1:06 AM in response to Alex Geis

I've been able to get rid of the error finally.. I've found that it's somehow related to file name length, although don't know the specifics yet. It seems to affect both the name of the original file that's being exported via QT and/or the name of the file it's being exported to.

All I know so far is that reducing the filename length has allowed me to export without a problem, each and every time.

Reply

Answer 3

Feb 5, 2008 5:06 PM in response to Alex Geis

IS this related to the Intel Mac QuickTime export bug? Are you on Mac Intel hardware? Running 10.4.10 or earlier? Supposed to be fixed with 10.4.11. It threw our workflow for a loop. Hmm.. Can't export to QuickTime. Ya, who needs to do that 😉

Reply

Answer 4

Alex Geis Author

Level 2

462 points

Feb 5, 2008 6:51 PM in response to Mathieu Mauser

verrrrrrrrrry curious. Yeah, this is on my MacPro with 10.4.10.
Time for an update, MANY thanks for the note... I was getting rather sick of exporting 100+GB clips to our HFS+ and then copying over to our xsan.

Reply

Answer 5

Feb 6, 2008 12:54 PM in response to Alex Geis

It was odd/even number of characters bug... I reported on it here in back in July. When I started running into it on our new Mac Pros. A Shake artist in Europe put the pieces together first, and started decoding the problem as a file length (path to file name length) issue. Strange. And ugly. Since our workflow was all Shake tool derived, exporting to QuickTime broke with Xsan, and no one was happy.

Reply

Answer 6

Feb 6, 2008 12:57 PM in response to Alex Geis

Here's my post in July which explains the problem:

http://discussions.apple.com/message.jspa?messageID=5038064#5038064

Reply

Answer 7

cat7cat

Level 1

0 points

Mar 30, 2008 9:25 AM in response to Alex Geis

Im getting this error every time I try to export a 2.52.18 long movie to iPod using Quicktime.

Any idea why this is happening? Ive read that I might have some huge temporary files located SOMEWHERE...

Reply

Answer 8

Apr 14, 2008 3:35 PM in response to Alex Geis

I'm getting this error on a standalone MacBook (Santa Rosa). Everything's up to date, I don't understand. Converting a 30-40 minute .MOV clip from Animation codec to DV-PAL... Any ideas? I've tried changing the file name several times, took all the spaces out - right now I'm encoding it just as 1.mov... maybe that will work...

Reply