I've found that sometimes I need to launch Audio MIDI Setup and hit the "Rescan MIDI" button for the devices to update (in ChucK and in other programs).  Plus, that's a good way to see whether CoreMIDI recognizes your device.  Just a thought.

Andrew

On Tue, Jan 27, 2009 at 1:15 AM, Robert Poor <rdpoor@gmail.com> wrote:
Hi Rogan:

The M-Audio web site:
       http://www.m-audio.com/index.php?do=support.drivers&f=656
claims that "This device is class compliant and does not require driver support for OS X. "

I think the deeper issue is that USB != MIDI, and the ChucK system is really expecting a MIDI device.  I think there needs to be some patching mechanism to associate the USB device with a MIDI device, but I don't know how to make that happen.

- rdp


On 26 Jan 2009, at 19:19, Rogan Carr wrote:

I think I used one of these once, but I had to use some special driver
from M-Audio.  Have you searched for a driver?

Rogan

On Mon, Jan 26, 2009 at 8:24 PM, Robert Poor <rdpoor@gmail.com> wrote:
[insert gratuitous ravingly happy chuck comment here]

I'm a brand new user, so this may be a simple cockpit error.

I've plugged in a midiman "oxygen 8" clavier keyboard into my Mac Powerbook
G4.  The Mac recognizes the clavier keyboard in System Profiler...
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Vendor-Specific Device:
Product ID:   0x1014
Vendor ID:    0x0763  (M-Audio)
Version:      0.01
Speed:        Up to 12 Mb/sec
Location ID:  0x1b100000
Current Available (mA):       500
Current Required (mA):        Unknown (Device has not been configured)
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
... but chuck --probe does not:
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
[poorbook15-5:chuck-1.2.1.2-exe/examples/midi] r% chuck --probe
[chuck]: found 1 device(s) ...
[chuck]: ------( chuck -- dac1 )---------------
[chuck]: device name = "Apple: Built-in Audio"
[chuck]: probe [success] ...
[chuck]: # output channels = 2
[chuck]: # input channels  = 2
[chuck]: # duplex Channels = 2
[chuck]: default device = YES
[chuck]: natively supported data formats:
[chuck]:    8-bit int
[chuck]:   16-bit int
[chuck]:   24-bit int
[chuck]:   32-bit int
[chuck]:   32-bit float
[chuck]:   64-bit float
[chuck]: supported sample rates:
[chuck]:   32000 Hz
[chuck]:   44100 Hz
[chuck]:   48000 Hz
[chuck]:
[chuck]: ------( chuck -- 0 MIDI inputs )------
[chuck]:
[chuck]: ------( chuck -- 0 MIDI outputs )-----
[chuck]:
[poorbook15-5:chuck-1.2.1.2-exe/examples/midi] r%
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Any ideas what's required to get Chuck to honor the USB / Midi keyboard?

Thanks.

- Rob
_______________________________________________
chuck-users mailing list
chuck-users@lists.cs.princeton.edu
https://lists.cs.princeton.edu/mailman/listinfo/chuck-users

_______________________________________________
chuck-users mailing list
chuck-users@lists.cs.princeton.edu
https://lists.cs.princeton.edu/mailman/listinfo/chuck-users

_______________________________________________
chuck-users mailing list
chuck-users@lists.cs.princeton.edu
https://lists.cs.princeton.edu/mailman/listinfo/chuck-users