jordan-umbrace / casiousbmididriver

Automatically exported from code.google.com/p/casiousbmididriver
0 stars 0 forks source link

PX 200 on iMac with OS 10.5.8 not connecting #5

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?

I followed your instructions, downloaded the plugin, unpacked it, copied to
the midi-folder (actually in both folders, the general and the one in my
user profile) and also tried to reboot several times, but still the driver
doesn't show in the audio-midi-setup

What is the expected output? What do you see instead?

In the Audio-Midi-Setup i only see the two Standard "IAC-Driver" and "Network"

What version of the product are you using? On what operating system?

I'm using a Casio Privia PX-200 on an iMac(late 2009) with Intel Core 2 Duo
2.66 Ghz and 4 Gb's Memory, OS 10.5.8

Please provide any additional information below.

Since you gave the advice to run USBProber, here are the results

Full Speed device @ 6 (0x24340000):
.............................................   Vendor-specific device from
Casio Computer Co., Ltd.
    Device Descriptor   
        Descriptor Version Number:   0x0200
        Device Class:   255   (Vendor-specific)
        Device Subclass:   0   (Vendor-specific)
        Device Protocol:   255
        Device MaxPacketSize:   8
        Device VendorID/ProductID:   0x07CF/0x6802   (Casio Computer Co., Ltd.)
        Device Version Number:   0x0100
        Number of Configurations:   1
        Manufacturer String:   0 (none)
        Product String:   0 (none)
        Serial Number String:   0 (none)
    Configuration Descriptor   
        Length (and contents):   69
            Raw Descriptor (hex)    0000: 09 02 45 00 01 01 00 C0  00 09 04
00 00 02 FF 00  
            Raw Descriptor (hex)    0010: FF 00 07 24 01 00 01 33  00 06 24
02 01 00 01 09  
            Raw Descriptor (hex)    0020: 24 03 01 00 01 00 00 02  06 24 02
01 04 03 09 24  
            Raw Descriptor (hex)    0030: 03 01 04 01 00 00 04 07  05 01 02
40 00 00 07 05  
            Raw Descriptor (hex)    0040: 82 02 40 00 01 
        Number of Interfaces:   1
        Configuration Value:   1
        Attributes:   0xC0 (self-powered)
        MaxPower:   0 ma
        Interface #0 - Vendor-specific   
            Alternate Setting   0
            Number of Endpoints   2
            Interface Class:   255   (Vendor-specific)
            Interface Subclass;   0   (Vendor-specific)
            Interface Protocol:   255
        Raw Descriptor (hex)   0000: 07 24 01 00 01 33 00 
        Raw Descriptor (hex)   0000: 06 24 02 01 00 01 
        Raw Descriptor (hex)   0000: 09 24 03 01 00 01 00 00  02 
        Raw Descriptor (hex)   0000: 06 24 02 01 04 03 
        Raw Descriptor (hex)   0000: 09 24 03 01 04 01 00 00  04 
            Endpoint 0x01 - Bulk Output   
            Endpoint 0x82 - Bulk Input   

Thank you for your help!

Original issue reported on code.google.com by johannes...@gmail.com on 20 May 2010 at 6:04

GoogleCodeExporter commented 8 years ago
Thanks for the USB Prober output - according to the IDs (0x07CF/0x6802), it 
should 
work. Which driver did you download ? Is it the beta ? I actually never tested 
it 
below 10.6.1.

Original comment by perso...@francoisferland.com on 20 May 2010 at 6:26

GoogleCodeExporter commented 8 years ago
I downloaded both, the binary and the beta...and copied both to the midi
drivers-folder...nevertheless it still doesn't work :-(
no entry in the audio-midi-setup

Original comment by johannes...@gmail.com on 20 May 2010 at 8:41

GoogleCodeExporter commented 8 years ago
You can try leaving only one driver in each folder (start with the non-beta 
one.) You 
have two different drivers trying to register for the same device. 

You can also look at the Console to see if you have error messages regarding 
this 
driver.

Original comment by perso...@francoisferland.com on 21 May 2010 at 2:40

GoogleCodeExporter commented 8 years ago
thanks for the advice,,,I tried it...i deleted the beta one, so in the folder i 
find
now CasioUSBMIDIDriver.r9.plugin, and there already were two others:
RDUSB0033Midi.plugin and EmagicUSBMIDIDriver.plugin
do I have to delete them as well?

Sorry about the console...i'm not used to it...never tried...

So far no change, still the keyboard doesn't show up and in the 
audio-midi-setup only
the two old symbols (network and iac)

Original comment by johannes...@gmail.com on 21 May 2010 at 10:37

GoogleCodeExporter commented 8 years ago
PS: in the console i went to see the log ~/Library/Logs/Audiofile: 
audio-unit-manager
and it's empty

Original comment by johannes...@gmail.com on 21 May 2010 at 10:41

GoogleCodeExporter commented 8 years ago
Look for anything suspicious in system.log (from the Console) when the keyboard 
is plugged-in and powered 
up.

Original comment by perso...@francoisferland.com on 26 May 2010 at 1:00

GoogleCodeExporter commented 8 years ago

Original comment by ferland....@gmail.com on 24 Mar 2011 at 8:51