Closed GoogleCodeExporter closed 9 years ago
Thanks for notifying this. I do not have Snow Leopard currently, but probably
will soon. This might be related to
the fact that the driver still carries PowerPC code.
I'll update the front page about this and will try to update the driver as soon
as I get Snow Leopard.
Original comment by perso...@francoisferland.com
on 14 Sep 2009 at 2:02
[deleted comment]
I am happy to report that I have been using it with no issue under Snow Leopard
10.6.1 and a Celviano ap-500.
Here is the content of my root 'Midi Drivers' folder:
ls /Library/Audio/MIDI\ Drivers/
CasioUSBMIDIDriver.plugin
EmagicUSBMIDIDriver.plugin
Thanks for your great work!
Original comment by Pierrick...@gmail.com
on 20 Sep 2009 at 1:23
I have a Casio CTK-720 and OS X 10.6.1. Alas, no luck with this driver, but I
have my fingers crossed for an
update soon!
Original comment by melvin.h...@gmail.com
on 11 Oct 2009 at 6:47
I have uploaded a new version of the driver, the installation procedure is the
same. I tested it on an original
MacBook Pro (1.83GHz) with 10.6.1. Please tell me if it works.
Original comment by ferland....@gmail.com
on 17 Oct 2009 at 5:09
Hi Ferland i have a macbook pro 2.26 with snow leopard 10.6 and i cant see my
casio ctk-720.. I copy and paste
the files to both midi driver folders the one in mac hd and the other in the
user folder and i cant make it work,
thanks for your time. hopefully you can answer this! THANKS AGAIN
Original comment by pcros...@gmail.com
on 20 Oct 2009 at 8:16
Do you see the interface the Audio & MIDI Setup ? It should be grayed out if
the keyboard isn't working. If it isn't,
could you go into your Console and search for message with "casio" in them and
report it here ?
Thanks,
Original comment by perso...@francoisferland.com
on 20 Oct 2009 at 8:27
hi, im new using mac os and i can open audio & midi setup but there doesnt seem
to appear nothing but iac
driver and network. and could you be so kind to tell me how to open the console
please.
Original comment by pcros...@gmail.com
on 20 Oct 2009 at 8:37
o here it is the console log:
20/10/09 14:18:07 Safari[205] LSOpenFromURLSpec() returned -10814 for
application (null) path
/Users/diegoherreramurguia/Downloads/CasioUSBMIDIDriver.plugin.
20/10/09 14:18:07 Safari[205] LSOpenFromURLSpec() returned -10814 for
application (null) path
/Users/diegoherreramurguia/Downloads/CasioUSBMIDIDriver.plugin.
20/10/09 14:39:18 Dock[135]
LSOpenFromURLSpec(file://localhost/Users/diegoherreramurguia/Downloads/CasioUSBM
IDIDriver.plugin/)
failed with -10814
20/10/09 14:42:11 MIDIServer[212] PlugIn CasioUSBMIDIDriver.plugin --
/Library/Audio/MIDI Drivers/
does not contain a supported architecture.
20/10/09 14:42:11 MIDIServer[212] CasioUSBMIDIDriver.plugin --
/Users/diegoherreramurguia//Library/Audio/MIDI Drivers/ not loaded because of
UUID conflict
20/10/09 14:42:11 MIDIServer[212] Failed to create instance for
CasioUSBMIDIDriver.plugin --
/Library/Audio/MIDI Drivers/
20/10/09 14:42:23 MIDIServer[219] PlugIn CasioUSBMIDIDriver.plugin --
/Library/Audio/MIDI Drivers/
does not contain a supported architecture.
20/10/09 14:42:23 MIDIServer[219] CasioUSBMIDIDriver.plugin --
/Users/diegoherreramurguia//Library/Audio/MIDI Drivers/ not loaded because of
UUID conflict
20/10/09 14:42:23 MIDIServer[219] Failed to create instance for
CasioUSBMIDIDriver.plugin --
/Library/Audio/MIDI Drivers/
20/10/09 14:53:11 MIDIServer[320] PlugIn CasioUSBMIDIDriver.plugin --
/Library/Audio/MIDI Drivers/
does not contain a supported architecture.
20/10/09 14:53:11 MIDIServer[320] CasioUSBMIDIDriver.plugin --
/Users/diegoherreramurguia//Library/Audio/MIDI Drivers/ not loaded because of
UUID conflict
20/10/09 14:53:11 MIDIServer[320] Failed to create instance for
CasioUSBMIDIDriver.plugin --
/Library/Audio/MIDI Drivers/
20/10/09 15:01:32 MIDIServer[348] PlugIn CasioUSBMIDIDriver-.plugin --
/Library/Audio/MIDI Drivers/
does not contain a supported architecture.
20/10/09 15:01:32 MIDIServer[348] CasioUSBMIDIDriver.plugin --
/Users/diegoherreramurguia//Library/Audio/MIDI Drivers/ not loaded because of
UUID conflict
20/10/09 15:01:32 MIDIServer[348] Failed to create instance for
CasioUSBMIDIDriver-.plugin --
/Library/Audio/MIDI Drivers/
20/10/09 15:07:17 MIDIServer[179] PlugIn CasioUSBMIDIDriver-.plugin --
/Library/Audio/MIDI Drivers/
does not contain a supported architecture.
20/10/09 15:07:18 MIDIServer[179] CasioUSBMIDIDriver.plugin --
/Users/diegoherreramurguia//Library/Audio/MIDI Drivers/ not loaded because of
UUID conflict
20/10/09 15:07:18 MIDIServer[179] Failed to create instance for
CasioUSBMIDIDriver-.plugin --
/Library/Audio/MIDI Drivers/
20/10/09 15:10:26 Safari[192] LSOpenFromURLSpec() returned -10814 for
application (null) path
/Users/diegoherreramurguia/Downloads/CasioUSBMIDIDriver.plugin.
20/10/09 15:10:26 Safari[192] LSOpenFromURLSpec() returned -10814 for
application (null) path
/Users/diegoherreramurguia/.Trash/CasioUSBMIDIDriver 14-56-49.plugin.
20/10/09 15:12:24 MIDIServer[206] PlugIn CasioUSBMIDIDriver-.plugin --
/Library/Audio/MIDI Drivers/
does not contain a supported architecture.
20/10/09 15:12:24 MIDIServer[206] CasioUSBMIDIDriver.plugin --
/Library/Audio/MIDI Drivers/ not
loaded because of UUID conflict
20/10/09 15:12:24 MIDIServer[206] CasioUSBMIDIDriver.plugin --
/Users/diegoherreramurguia//Library/Audio/MIDI Drivers/ not loaded because of
UUID conflict
20/10/09 15:12:25 MIDIServer[206] Failed to create instance for
CasioUSBMIDIDriver-.plugin --
/Library/Audio/MIDI Drivers/
20/10/09 15:20:04 MIDIServer[191] PlugIn CasioUSBMIDIDriver.plugin --
/Library/Audio/MIDI Drivers/
does not contain a supported architecture.
20/10/09 15:20:04 MIDIServer[191] CasioUSBMIDIDriver.plugin --
/Users/diegoherreramurguia//Library/Audio/MIDI Drivers/ not loaded because of
UUID conflict
20/10/09 15:20:04 MIDIServer[191] Failed to create instance for
CasioUSBMIDIDriver.plugin --
/Library/Audio/MIDI Drivers/
Original comment by pcros...@gmail.com
on 20 Oct 2009 at 8:41
Works for me.
It took me a while (since I'm new to OSX) to figure out that the keyboard
belongs in the MIDI Studio window and
not Audio Devices. And since GarageBand has a MIDI-In I figured that it would
also have a MIDI-Out (it doesn't)
which caused me quite a bit of headache. In any case, both work when using IN
and OUT supporting
sequencers.
Thanks a whole bunch.
Original comment by hord...@gmail.com
on 20 Oct 2009 at 9:45
pcros333,
Thanks for the log. You can remove one of the two copies of the plugin - it
should remove the errors about
the UUID conflict.
The error about the architecture might indicate a 32/64-bit issue. The plugin
is currently built for Intel 32-bit
architectures only, since PowerPCs are unsupported with 10.6 anyway. My goal
was to provide a 32 and 64-
bit version of the plugin, but right now I only have a 32-bit Intel Core Duo,
so I can't test it. I should be able
to build an hybrid version anyway, and I'll try soon.
Original comment by perso...@francoisferland.com
on 20 Oct 2009 at 9:53
hi, francois, thanks for the reply!! if you want I can test the future files to
achieve a 64 bit version of this file.
many thanks again for the effort of doing this, if theres anything i can do to
help please tell me. thankyou
Original comment by pcros...@gmail.com
on 21 Oct 2009 at 3:26
I can confirm that it works in 64-bit mode. Both input and output. I do,
however, get the same error as
pcros333 (posted below) so I'm not sure that it's the cause of his problems.
The error:
10/21/09 7:18:56 PM MIDIServer[1083] PlugIn CasioUSBMIDIDriver.plugin --
/Library/Audio/MIDI Drivers/
does not contain a supported architecture.
I'm still a bit confused. Is the keyboard supposed to show up under *both*
MIDI Studio and Audio Devices?
Because it only shows up under MIDI Studio on my system.
Original comment by hord...@gmail.com
on 21 Oct 2009 at 7:46
hordurp, Thanks for the precision about 64-bit. No, it shouldn't show up in
Audio Devices, I just called the
application by its (loosely translated from French) full name. Sorry for the
confusion.
While I do have access to a few 64-bit systems, they're either Mac Pros and I
can't really move my Casio
keyboard, or laptops that haven't been upgraded yet. I should resolve this soon
enough, though.
Original comment by perso...@francoisferland.com
on 21 Oct 2009 at 7:52
I can confirm that it worked well, I deleted the driver in the user's folder
and then i restarted, and it showed up
in the midi menu, it appeared as "myproductname", it works pretty well right
now, thanks so much francois.!!!
Original comment by pcros...@gmail.com
on 22 Oct 2009 at 2:54
It's not working for me with Snow Leopard 10.6.2 on a MacBook Pro (2009) and my
Casio
PX-320. Here's the console log:
11/14/09 10:00:11 PM MIDIServer[295] PlugIn CasioUSBMIDIDriver.plugin --
/Library/Audio/MIDI Drivers/ does not contain a supported architecture.
11/14/09 10:00:11 PM MIDIServer[295] CasioUSBMIDIDriver.plugin --
/Users/henrykim//Library/Audio/MIDI Drivers/ not loaded because of UUID conflict
11/14/09 10:00:11 PM MIDIServer[295] Failed to create instance for
CasioUSBMIDIDriver.plugin -- /Library/Audio/MIDI Drivers/
I've got one copy of the plugin saved in the system Library/Audio/MIDI Drivers/
folder. I've restarted several times. Not recognized in Logic Pro 9. Any help
would
be appreciated!
Original comment by Henr...@gmail.com
on 15 Nov 2009 at 6:43
Hi there
Running OSX 10.6.1 on a Macbook 2.4, installed the latest snow leopard plugin
per instructions and restarted
and tried connecting my Casio WK-3300. I do not see anything "Casio" listed in
Audio Midi setup. Any ideas?
Original comment by inhouse...@gmail.com
on 16 Nov 2009 at 12:25
oh here is comment log
11/15/09 4:23:57 PM MIDIServer[376] PlugIn CasioUSBMIDIDriver.plugin --
/Library/Audio/MIDI Drivers/ does
not contain a supported architecture.
11/15/09 7:14:47 PM MIDIServer[239] PlugIn CasioUSBMIDIDriver.plugin --
/Library/Audio/MIDI Drivers/ does
not contain a supported architecture.
Original comment by inhouse...@gmail.com
on 16 Nov 2009 at 12:32
I just downloaded your newest version 10.6 to a new Macbook Pro running Snow
Leopard. Works great. I did not
see a "Casio" device listed in the MIDI setup, but there was a new "generic"
device listed (sorry I did not write
down what it said.) I changed the device name to my model - Privia PX-320, and
selected this for input and
output.
This works better than two different MIDI interfaces I tried to use - a
MIDIsport UNO, and a MIDIsport 2x2, both
USB to midi devices. Each of them worked with some programs and not others.
This driver appears to work with
everything. THANK YOU!
Original comment by vze24...@gmail.com
on 3 Dec 2009 at 3:53
[deleted comment]
I am trying to use the new driver with Casio WK-3800 connected to M-Audio Fast
Track Pro interface, and have
been unable to connect to my Macbook Pro running OS X 10.6.2. The Midi utility
is not recognizing the driver.
I connect to GarageBand and I cannot see any sound transferring over. I tried
various things, with no luck. Any
suggestions? Thank you.
Original comment by dunk...@gmail.com
on 21 Dec 2009 at 12:53
I am having the same exact problem as dunkele... I have a midi1x1 tab E-MU and
garage band sees it but
there no input coming through. Any ideas? I have the driver on the correct
folder:
abarcenas-5:MIDI Drivers root# pwd
/Library/Audio/MIDI Drivers
abarcenas-5:MIDI Drivers root# ls -la
total 16
drwxrwxr-x 5 root admin 170 Dec 23 18:08 .
drwxrwxr-x 10 root admin 340 Aug 31 17:55 ..
-rw-r--r--@ 1 abarcenas admin 6148 Dec 23 18:07 .DS_Store
drwxr-xr-x@ 3 abarcenas staff 102 Oct 17 13:00 CasioUSBMIDIDriver.plugin
drwxrwxr-x 3 root admin 102 Dec 5 2007 EmagicUSBMIDIDriver.plugin
Original comment by andrebar...@gmail.com
on 24 Dec 2009 at 2:44
I'm sorry that I can't investigate this issue further through. Once I have
access to a 64-bit Mac with SL and that I
can plug my keyboard in I'll update the driver.
Original comment by perso...@francoisferland.com
on 24 Dec 2009 at 12:11
Thank you for your help. I also have a 64bit =o( and it doesn't work. Is Midi
studio
in Garage Band? I dont see it in either GB or on the HD. Maybe its an older
version.
Original comment by tj.chamb...@gmail.com
on 13 Jan 2010 at 7:40
A Casio CTK-710 is working fine on SnowLeopard 10.6.2 64x. In MIDI Setup it
doesn't appear but Logic 9,
Garage Band and other apps can recognize it and works full.
THANKS A LOT!!!!
Original comment by xepar...@gmail.com
on 18 Jan 2010 at 7:58
I have an iMac 2009 (old version) 2.66 Ghz Intel Core 2 Duo with Mac OS X
10.5.6 and the driver is working
perfectly on my CASIO WK-110.
Thank you very much!
Original comment by RudyCo...@gmail.com
on 23 Jan 2010 at 8:14
My Casio WK-3800 worked fine with 10.5.6, but once I upgraded to Snow Leopard,
it stopped working. I am
debating whether to sell the Casio and get a keyboard that works with Mac.
Original comment by dunk...@gmail.com
on 24 Jan 2010 at 4:57
Hi everyone,
I have a new, experimental version of this driver for Snow Leopard and 64-bit
CPUs. As I said before, I cannot
test it on a 64-bit Mac, but this universal x86_64/i386 build works on 10.6 and
32-bit CPUs (Core Duo 1.83
here) and I would like to get feedback on it with more recent machines.
Here's the link:
http://code.google.com/p/casiousbmididriver/downloads/detail?
name=CasioUSBMIDIDriver.plugin.zip&can=2&q=
Original comment by ferland....@gmail.com
on 24 Jan 2010 at 5:14
You can also get the driver in the download section under
"CasioUSBMIDIDriver.r15"
Original comment by ferland....@gmail.com
on 24 Jan 2010 at 5:16
I need help... I have an LK-90tv, trying to connect to Macbook V. 10.4.11...
what file should i download?
much appreciated, thank you
Original comment by dkj...@optonline.net
on 6 Mar 2010 at 4:20
looks like i figured it out!!!! so happy!!! thank you for your efforts and
plugin
very nice
Original comment by dkj...@optonline.net
on 6 Mar 2010 at 4:34
Hi, Francois!
Can you help me to get working the WK-3300 on my 10.6.5 (10H542) x64? I tried a
r15, a special driver for Snow Leopard, and nothing... In console I got wrong
UUID and problems with architecture... Here the exact console messages:
MIDIServer[292] MIDIServer [292] starting; arch=x86_64
MIDIServer[292] PlugIn CasioUSBMIDIDriver.plugin -- /Library/Audio/MIDI
Drivers/ does not contain a supported architecture.
MIDIServer[292] MIDIServer relaunching because a 32-bit driver was found
MIDIServer[292] MIDIServer [292] starting; arch=i386
MIDIServer[292] CasioUSBMIDIDriver.plugin -- /Users/Nemo//Library/Audio/MIDI
Drivers/ not loaded because of UUID conflict
MIDIServer[292] Cannot find factory 0AF61C91-A75F-4CDC-A91A-9A76B179F7DE
MIDIServer[292] Failed to create instance for CasioUSBMIDIDriver.plugin --
/Library/Audio/MIDI Drivers/
Original comment by Nemo1...@gmail.com
on 24 Oct 2010 at 1:13
I'm typing this from my phone but check if you don't have multiple copies of
the driver plugin in all your MIDI drivers folders, the second error (UUID
conflict) might imply that. Only keep the latest one.
Original comment by perso...@francoisferland.com
on 24 Oct 2010 at 2:07
So.. Thanks for you answer, Francois! Now I got suggested wrong UUIDs... I have
not got it in console... But I'am still not seeing any MIDI device in MIDI
Configuration application... And Garage Band doesn't see it too... Que ce que
je peux faire en moment? Je pense, que je pourrais parlais français =)
Here are the exact console messages that I got with CasioUSBMIDIDriver.plugin
for Snow Leopard special:
MIDIServer[309] MIDIServer [309] starting; arch=x86_64
MIDIServer[309] PlugIn CasioUSBMIDIDriver.plugin -- /Library/Audio/MIDI
Drivers/ does not contain a supported architecture.
MIDIServer[309] MIDIServer relaunching because a 32-bit driver was found
MIDIServer[309] MIDIServer [309] starting; arch=i386
And that is all... How I can see there is not any problems with architecture,
but everything is so sunny... What can I do now?
Original comment by Nemo1...@gmail.com
on 24 Oct 2010 at 4:46
Damn... Wrong proposition...
*"...everything is not so sunny..."
Original comment by Nemo1...@gmail.com
on 24 Oct 2010 at 4:51
I can't look into the details right now (I'm traveling in Tokyo, coming back
from a conference) but I'll look into it once I'm back home next week.
Your French is good!
Original comment by perso...@francoisferland.com
on 25 Oct 2010 at 1:36
Merci pour a compliment, mais ce moi qui étais un imbécile... Par ce que je
n'avais pas un USB joint fonctionnaire... Zut!
Now, when I have understood the reason I fixed it and I got that keyboard
working... Thanks a lot for your driver! It works perfectly...
Original comment by Nemo1...@gmail.com
on 25 Oct 2010 at 10:05
Original comment by ferland....@gmail.com
on 24 Mar 2011 at 8:50
Original issue reported on code.google.com by
de...@hotmail.com
on 13 Sep 2009 at 5:47