What is QuickTime error -1856

Question

Level 6

18,941 points

What is QuickTime error -1856

Over the weekend, iDVD5 crashed on my system and since then a number of QuickTime based apps aren't working quite right, including iTunes and WireTap Pro.

QuickTime Player itself (7.0) gives this message on startup -

QuickTime cannot open the file: "trampoline.mov"
an unknown error occurred (-1856)

Any ideas what this means? (Other than that trampoline.mov is missing ...)

iMacG5/2.0GHz/2GB/1.6TB, Mac OS X (10.4.2), eMac/1.25GHz/1GB/160GB, MacBookPro/2GHz/1GB/100GB, Too much other gear.

Posted on May 7, 2007 5:04 PM

Reply

Answer 1

Best reply

AeroQ

Level 2

210 points

May 11, 2007 10:46 AM in response to MartinR

Hi,

According to Apple developer documents, this error is a Carbon Apple Event error:

handlerNotFoundErr = -1856, /* handler not found */

This description doesn't tell much.
From the symptoms that you describe, I would re-install QuickTime from scratch and pray.

Regards, BJ

Reply

Answer 2

MartinR Author

Level 6

18,941 points

May 13, 2007 10:48 AM in response to AeroQ

Well, this is exactly the kind of scenario for which I made a complete backup image of my HD when I first installed everything last year. I wiped the HD and reinstalled the image and I'm back up & running.

Reply

Answer 3

May 13, 2007 11:00 AM in response to MartinR

You could have solved it by turning off the "Show Content Guide" in the QuickTime Player preferences.
The "trampoline.mov" just bounces (get it) to the download for the content guide.
QuickTime error messages start at -2000

Reply

Answer 4

MartinR Author

Level 6

18,941 points

May 14, 2007 11:50 AM in response to QuickTimeKirk

No, I was aware of that trick, but there was much more that was awry. All of the QuickTime-based apps on my system were affected, and some wouldn't even run anymore. The iTunes UI was corrupted, iDVD had no sound, WireTap showed weird audio settings and failed to capture, Final Cut wouldn't even start ...

Reimaging the HD was the right thing to do, and everything is working fine again.

Reply