Forums > Jitter

check failed: egetfn (setport): corrupt object

March 25, 2006 | 12:56 am

Hello list,

Anyone knows what:

> check failed: egetfn (setport): corrupt object



March 26, 2006 | 11:29 am

Bad news: Save open documents, preferably under new names, quit Max,
relaunch the program.

It’s not always a compete disaster, but usually the harbinger of evil
tidings, a bad omen.

————– ————-
Peter Castine +–> Litter Power & Litter Bundle for Jitter

iCE: Sequencing, Recording & |home | chez nous|
Interface Building for |bei uns | i nostri|
Max/MSP Extremely cool

April 5, 2006 | 2:48 am

I think this is also the root of some of my troubles here.
Somebody have a clue on the meaning of:

check failed: egetfn (setport): corrupt object

appearing in the Max print window

Running Mac OS 10.4.6, Max/MSP 4.5.7, Jitter 1.5.2


April 20, 2006 | 2:18 pm

thought I’d try again here…

I’m using the "hi" object to track a USB device (info. comes across
as mouse data). The "hi" object loses the device from time to time,
and in many cases it requires a reboot of Max to get it back (rarely
hitting "hi" with the device I.D. again fixes it). The device
manages to maintain control over the mouse cursor despite being lost
by Max.

I haven’t ruled out my device entirely as the problem, but I’m still
puzzled by the: "check failed: egetfn (setport): corrupt object" …
and wondering if anyone knows its cause, and if it could be tied to
this sporadic issue.


April 20, 2006 | 3:25 pm

i had this problem (losing devices) too with HI so i choose to use
junxtion from
very nice and stable. but it’s an outside app.

Viewing 5 posts - 1 through 5 (of 5 total)

Forums > Jitter