I misspoke, I wasn't running as admin, I was running as a user (but with full privileges). It is strange about the sound card, I agree.. I figured if anything it would be a much better solution than my on-board audio. Perhaps I'll try to figure it out over the Summer when I've got a little time to spare. :) I still get some strange output using ChucK -v --loop in Windows but it all seems to resolve itself and it works, considerably better than it did on my previous installation. I don't know why, but as I'm sure many of you know, sometimes the best route is to start from scratch with a fresh install. BTW, as far as Linux is concerned, ChucK utilizing JACK built from source is AWESOME. Works amazingly well, and the Linux environs just feel better when working in a terminal, although I don't use Mac so I can't compare the two. Now, if only someone would port Cinder to Linux I wouldn't have to use ChucK on Windows at all...:)
________________________________
From: Kassen
Well, I have the problem fixed (sort of). The new sound card seems to have been the culprit. For whatever reason, ChucK did not like my sound card. I did a fresh install of Linux while I was at it and had the same issues as I was having in Windows (never had a problem with ChucK in Linux before..I had purchased the sound card to try to resolve Windows issues!). All audio, aside from ChucK audio, was working fine. I took the sound card out and ChucK is working better than ever in both Windows and Linux. Go figure.
Great! The state of Linux drivers has generally been improving in the past few years, I think largely thanks to standardised devices, but that's not much help if you want it on Windows :-). It's still odd that the one card wouldn't work. You mentioned running as Admin, is that because you like to or is that needed? If it is needed that should probably be in the docs. Personally I don't think that is a very good sollution, but at least it is a sollution. Congratulations, Kas.