Alas, my problem of disconnections are still there. Not sure what is going on, but the keyboard keeps reverting the DAW to Live, and disconnects from Cubase. At that time it seems that MIDIIN2/OUT2 are no longer available to reconnect. I can’t find what is triggering this, but it does seem to happen when I’m not playing. Not sure if something is still timing out.
The keyboard continues to work, but the transport buttons and all the other DAW stuff stops working. I have to change the DAW to Cubase on the Keylab and restart Cubase to get it back.
Yes, this is how I set it to do, to have Live as the selected DAW, so please keep it this way. Note that this has nothing to do with the disconnections. Think of it as what set of MIDI messages I chose the Keylab to send. This decision was mainly based upon the pads assignments which I needed to be the same from installation to installation.
This has to be the known issue discussed in some threads concerning the midi remote.
Here’s one of them:
This issue from what I read is resolved in CB 13.0.41, but at the same time I see users still mentioning that the issue is still there.
What I don’t understand is that I’ve played with my Keylab, a Novation and a Komplete Kontrol and never ever experienced these disconnections. BUT at the same time, I always keep my devices powered on and connected to Cubase while I’m working in it. What I do recall at some point, was that I had a fault USB cable for my Komplete Kontrol causing strange things. But then, I really don’t know, it’s a frustrating thing.
Trying something else here… the keyboard came with this dongle that allows to separate sources for power and USB functionality. I’m trying the keyboard powered with an external USB power adapter (its an old phone one, but it seems to have enough power to power the keyboard on its own), and also USB to the computer. If it is a USB power issue, this might solve it. We’ll see! FWIW, I am running Cubase Pro 13.0.41.
Thanks for the advice about it using Live as the DAW. I thought it was randomly changing the DAW from Cubase to Live, but I guess not.
Yeah, it does seem weird, but hey it’s a Dell. Anything could be! I can’t say I’ve had it with this computer up to this point, but my previous Dell desktop had some odd USB behaviour so it could be the culprit. I will report back either way when I’ve given it some time to break. So far so good!
By the way, I recall in the thread I shared, that a user suggested adding to our project, a midi track (a dummy one) connected to the port of the midi remote (in our case the DAW port of the Keylab). He found out that the disconnections vanished. Maybe you should give this tip a try as well.
Adding power didn’t help (though it did take longer to tap out). I’ll try the dummy midi track thing - do you mean the MIDI channel output connected to MIDIOUT2 or < MIDI channel input connected to MIDIIN2? Or both?
Might also find a free USB sniffer. I’m convinced something is interrupting either the data flow or the power.
After yet more disconnects today, I did another search. It was only after this, that I realized that the problem is not the Keylab. It’s Cubase. Since I was mad at Arturia, I naturally assumed the problem was with the Keylab. I also found that the culprit might be using DirectMIDI as your device. I didn’t realize the significance of this, or even that I could change it - I’ve always assumed it was just some kind of driver. Anyway, it seems that unchecking “Use Device ‘DirectMusic’” (Studio> MIDI Port Setup) changes the MIDI port device to Windows MIDI (which is what I see in m.c’s screenshot). A re-start of my machine, and Cubase, and everything connects up the way it should. I’ve now been hours without a disconnection. Fingers crossed this was it!
DirectMusic is an old story of Microsoft, I’m not even sure if the checkbox is checked by default in Cubase, perhaps it is. And then WinRT is another area that though promising, needs refinements. But, both of these are Microsoft’s, so I don’t know whether I could put the blame on Steinberg
DirectMusic was checked by default on mine. Could have been from a previous version I guess, but my computer isn’t THAT old, and I think v.12 was the first version on it. I wouldn’t have checked it. I’ve had no need to delve into that stuff up to this point. I never bothered to try to set up my old Novation keyboard on it, and only used it for keys alone. Anyway, so far so good on this.
I think I’m finally ready to get on with stuff! I’m sorry for being so mad at Arturia. I still think they should have done what you have done for the keyboard (as I said elsewhere - I paid full price for it, and its still listed as a current model), but it does seem a lot of the problems are with Steinberg, not Arturia.
The thing is that they could actually implement some more functions even by using the MCU standard, since their implementation was based on this. Same goes for other manufacturers using this standard. However I can only recall Nektar Technology, diving deep with their Panorama P-series (this was actually one of my first keyboards after a long period of absence). As said in the thread you’re referring to, their point of view is most probably that the “targeted” user would be happy enough with volume/pan/transports. But yeah, this is not what one can call “deep integration” I suppose.
I somehow feel that it’s more a Microsoft’s thing to be honest As far as I know these disconnections do not appear on Macs.
Hi again, Wonder if you can help re your script? I started Cubase and although the Arturia - Keylab MK2 MC Custom is showing up in the midi remote tab it is grayed out. When I click on the midi remote manager it gives me some info including the status, which tells me it’s ‘Disconnected’. Is there an easy way to connect it. I have been looking and trying things out but so far I haven’t been able to figure it out? Many Thanks
In the Midi remote manager, click on the Script tab to view the script name. Click on it. On the sub-window below, there should be info on the script, and a “button” saying “Enable Controller Script”. Click on it and that should do it. Or maybe I did not understand your problem. In which case a screen picture would help…
Not sure if this would be of help, but both In ports of the Keylab should be set to “visible”. What I want and is described in my short pdf file, is to uncheck the In ‘All MIDI’ for the MIDIIN2 port. The reason for this, is not hear unwanted sounds when using our keyboard’s controls, since some of them are using notes instead of ccs.
Thanks, So as in the screenshot in the previous message do I make visible the top two ports or just the top one? It did work when I first loaded it in with the top two ports disabled but when I shut down and reload Cubase I get no connection.
I have another device/script installed (see screenshot) and when Cubase loads the one created by ‘Carillion’ connects by default and I have to select your script after loading. Nothing happens however when I select your script. Perhaps it has to connect when loading up Cubase? I don’t know how to delete the ‘Carillion’ device to see if this is the problem. Thanks
Ah, two remotes. You have to delete one of these or at least disable it. I would go for just disabling, just in case later you want to use the other one.
Open Studio→MIDI Remote Manager, click on the Scripts tab, find the one with its Device named as Keylab 88 MK 2, and select it. In the pane at the bottom of the window, you’ll see a Disable Controller Script button. Click it and you’re done.
