Hello. I am using a Casio px-s1100 keyboard with the bluetooth WU-BT10 adaptor. I want to record midi with my keyboard via bluetooth but can’t get it to work. I followed some instructions on google and cubase does recognize the device as an ASIO device so I can output audio to my keyboard but I can’t see the device in my midi port setup so I cant select it as a midi device.
It says on google:
3.Cubase Configuration:
Open Cubase and go to “Studio” > “Studio Setup”.
Navigate to “MIDI Port Setup”.
Locate the WU-BT10 in the list of available MIDI ports.
Check the box next to “In All MIDI” to enable it.
I would like to follow these instructions but the problem is that the device DOES NOT APPEAR in the list at all. What am I doing wrong?
First of all, as you are using WU-BT10 device, you will not see Casio as the device, but the WU-BT10 instead. As this is MIDI-BT device (I expect), you will not see it as an ASIO driver. You can see it only as a MIDI Device in the Studio > Studio Setup > MIDI Ports Setup.
Thank you for your reply. here are two screenshots. The midi port set-up page and studio set-up page. I am able to select the WU-BT10 as a device in the studio set-up page but not as a midi device in the midi port set-up page. I would like to record midi with my casio keyboard using the WU-BT10 device. How can I do this?
I got it to show in Cubase now so thank you for helping
I had to use the Audio Midi Setup app on my mac and it is now recognized by Cubase but when I play the Casio, no midi is coming through… whats the next step to trouble shoot this?
does the Audio System also need to use the Casio for it to work because right now it is only recognized in Midi Port setup but I have used another device in the Audio System dialogue box.
You may want to Dock your Audio/Midi app. You may have to continually reconnect it after disconnect so that it loads back into Mac’s midi devices collection and is active.
I’ve tried a couple of different BT MIDI keyboards and they refused to automatically reconnect as midi devices though the actual BT connection was automatic. Not sure why, but it became more of a pain than my personal threshold allowed for. Hopefully that won’t happen to you, but just something to keep in mind.
I would expect the Visibility, State, Monitor and Usage columns in the MIDI Port Setup. Then you can show the MIDI Monitor on the given Input. But you don’t have itavailable.
If you play the MIDI keyboard, can you see the MIDI Inpu activity meters on the Transport Panel?
it shows the casio bluetooth adaptor and the IAC driver
But I am not sure why in Cubase there are two “in” ports and two “out” ports as you can see in the screenshot above. Can you explain this to me? Is it because the midi goes from the CASIO to the IAC into Cubase? If so, why does Cubase show both ports in the Midi port setup page?
You just enabled the IAC driver - that’s why it’s showing up. It’s a virtual midi device that allows you to connect apps together via a common virtual midi driver.
Since it’s a “midi” component, and you enabled it, it’s showing up in Cubase. I don’t think that has anything to do with your setup.
I think it would be really valuable for you to watch some videos on how Apple midi devices work in general so that you can get a better foundation of the components involved here. None of this has anything to do with Cubase per se, and I think it would help for you to get more general information.
Thanks. I am learning about it as you can see but in all honesty, I have had several midi keyboards and never had to open this app before. Things have always showed up in Cubase as they should have in the past. Well thanks for your help anyway.
Well, this is a BT wireless MIDI and it has more dependancies. I wasn’t trying to be disparaging or critical, I was just trying to increase your scope a bit. All of your midi devices are in the Midi Studio window of the Audio MIDI Setup app as well.
And things ARE showing up as they should in Cubase. I’m just suggesting you learn a bit more about the components since none of what you’re asking here is “a Cubase issue.” That’s all I was saying. But I’ll leave you to it. Good luck out there!