Hi Chris - thanks for the quick and helpful reply, the exhibit is using
a matrox dualhead2go box and was selecting a non standard color profile
although it was rgb (see the following screenshot)
https://skitch.com/sheridan/8uhue/contributeright
I unchecked the "show profiles for this display only box" and selected
the generic rgb profile
https://skitch.com/sheridan/8uhux/contributeright-genericcolorprofile
And it seems to have fixed the problem (although I didn't check
thoroughly as I'm not at the museum and had to screen share in didn't
want to reboot the machine in case there are patrons in the space
watching the exhibit)
Thanks again - James
On 18/04/12 11:45 AM, Christopher Wright wrote:
Does anyone have any insight into whats causing the below crash?
Its from a quartz builder (1.4) application so maybe this is the
wrong place to ask but after searching through the mailing list
archives it seems its a reasonably common problem.
The colorspace needs to be RGB (as opposed to a single-channel space,
or something inappropriate for OpenGL like CMYK or YUV), and it needs
to not be DeviceRGB. I'm going to guess it's the last part of the
assertion that fails (really that assertion should be split into 2
pieces so that the caller knows which piece is breaking) - perhaps the
driver or display is set to a profile that happens to match deviceRGB?
QuartzBuilder should probably sanitize its inputs before initializing
the renderer to ensure that it won't trigger this exception.
Does changing the display profile help?
--
Christopher Wright
christopher_wri...@apple.com <mailto:christopher_wri...@apple.com>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Quartzcomposer-dev mailing list (Quartzcomposer-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/quartzcomposer-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
