Okay, can you delete the "visual=" attribute from the first display mode and try again? There is no valid reason I can think of why it's dying there when the only thing I changed was the specific codes I'm sending... Especially one that would only happen in DC mode. But if you don't set a visual attribute, it won't try to send those codes, and I can see if it's really related to that or not. Still doesn't tell me where to look, but it at least gets rid of the possible red herring.

It also would be helpful if you can bump up the debug level of emphatic by running it with the following:

/usr/local/bin/emphatic --debug 5

and send me the output right around the time it crashes.

Are any other apps running at the time, by the way?