February 2008 - chuck-dev - lists.cs.princeton.edu

64-bit ChucK (once more unto the breach)
by Drake Wilson 15 Feb '08

15 Feb '08

Hum. So, searching the mailing list archives, I find several people reporting that compiling ChucK on any 64-bit platform segfaults immediately on startup due to assumptions about type widths. This is also my experience. This should be unsurprising to me by now, but apparently I can still be toppled over backwards by this sort of stuff, so pardon me if I flame somewhat. I'm not going to ask for a fix date or anything like that. I'd love to fix it myself, ideally, though I have no idea whether I'll have a chance to do that. What I will ask, however, is _why_? I see no response to this in any of the earlier threads (possibly because nobody asked), only vague rumblings about "it doesn't work on 64-bit machines yet; we're still working on it". Which assumptions is ChucK making about type widths, and why is it making them? A cursory inspection of the source seems to indicate that someone decided long must be four bytes on every machine and happily hardcoded it everywhere, thus making it almost impossible to dig the all-the-world's-an-i386 syndrome out now that it's sunk so deep into the VM and such. Is that what it is, or is it something else? Are there other similar nonportable assumptions (aside from the stuff that's actually demarcated as platform-specific)? What compels people to not use mechanisms like sizeof for this sort of thing? I don't see anything doing fancy enough tricks to legitimately depend on assumptions like that. I'm honestly stunned. I decided to try ChucK instead of SuperCollider because SuperCollider stupidly assumes it can stuff a void * into an int, which makes it not compile on my machine, so I immediately gave up on it. I was getting my hopes up because ChucK at least compiled, but now I find that a similar form of bogosity will probably destroy any reasonable chance at that too. At any rate, it would be nice to check at compilation-configuration time, or even at process initialization time, that all the sizes fit whatever constraints they're required to fit, and then bomb in a well-defined manner if they don't. There being no obvious compilation-configuration stage seems to make the former possibility into more of a mess than it should be, of course, so meh. ---> Drake Wilson

1 0

Wacom tablet configuration failure
by Alexey Kondratiev 10 Feb '08

10 Feb '08

Hi, I cannot use the Wacom tablet on OSX because it fails to be configured in Chuck. The problem seems to be happening while opening the HID interface with this line in "util_hid.cpp": result = (*interface)->open( interface, 0 ); it returns the negative result(-536870203). This is what Chuck reports: mouse 'PTZ-431W' ready [chuck]:(5:INFORM): hid: starting PTZ-431W [chuck]:(5:INFORM): | hid: configuring PTZ-431W [chuck]:(3:SEVERE): | hid: error configuring PTZ-431W I'm not an expert in device drivers, perhaps someone can figure out why it happens. Alexey

1 0

About features ChucK/miniAudicle
by lucas samaruga 05 Feb '08

05 Feb '08

Hello I'm fascinating whit ChucK, and I become an assiduous user-composer. I have some questions about the language and his derivates projects, if somebody have time to answer. There is some place were the dll interface is explained? It's ready to use? There is possible to do (whit that interface) Qt widgets that can be called from ChucK like the MAUI widgets on miniAudicle? I can't use MAUI because I don't use mac (and I can't compile whit it on linux). Related to the second question: I think that Qt framework is good portable option to implement the miniAudicle IDE. I think that an IDE that integrate your own interface whit elements controlled by the ChucK language, can be a powerfull tool to develop music composition or rt performances, because the UI can be self programmable. That in addition to the greater innovative proposals of Chuck. Maybe if the (mini)audicle was full implemented this questions can be inadequates. Thanks Lucas

1 0

openGL + ChucK
by Jeremy Hunt 04 Feb '08

04 Feb '08

Hi all, I have heard of an openGL implementation planned for chuck, is someone out there actively working on one? Please let me know. My coding talents are meager but I would love to help. I could do tedious grunt coding that doesn't take skill :D Best, Jeremy

2 1