Yes, I have noted that as well.
The not-so-good part about this is that these new DAW ports-at first glance, at least, are far less accessible to the user. So they’re not as easily monitored, or to troubleshoot-at least for me-as is a standard MIDI Port.
What is sure is that both Arturia and NI setup their controllers to be compatible with their own VST ecosystems, you’re correct on this. But I can’t blame them, I would have done the same 
To my eyes, since I own and used here a Keylab Mk2, a Komplete Kontrol MK2, a Novation SL MK3, and a Korg Keystage, is that they all have their advantages, disadvantages, I think a user should really get behind the marketing lines, and check for themselves the keyboards, their keybed, the number/quality of controls, displays if it helps their workflow. I scripted for all of them, and I don’t have a real favourite, I slightly tend to the SL MK3.
Well, they don’t, that’s true. This didn’t stop me from scripting the SL MK3 to handle VstPresets, which was a big plus in my workflow: https://www.youtube.com/watch?v=ODWAGtXOhJQ
Currently I don’t use any of them, because I moved to a hardware synth, I scripted for it as well, but the workflow changed to the degree that after recording my songs in Cubase I can happily use the mouse most of the time, for the advanced things Cubase offers to me
I agree, which is why I’ve already scripted for many, many Arturia and Akai VSTs onto my ReMote SL/Zero, but have done literally zero of that for my Keylab Mk3. Novation’s way of doing things makes scripting for these VSTs infinitely more inviting for me than on the Arturia.
Yes, but on the other hand, it allows the use of Note messages (and others) to be used for DAW control without affecting the playing of notes in virtual instruments.
I find it easy enough to slap a MIDI monitor on the DAW port to find out what it’s sending. But on the hardware receiving side, such “reverse engineering” can get a lot more tricky without documentation.
Yes-exactly. This is really what I’m talking about. These new DAW ports feel like highways that only the manufactures can use. They are far less accessible to a user seeking more ways to send messages to their controller. It can be frustrating to see that whole port, and to know that it’s not for you to touch. Especially when you have a good reason for wanting to separate certain channels of information.
Note that Novation did an excellent job on this. They provide openly a MIDI specification for the SL MK3 which was of tremendous help to me to directly dive into scripting for it, while you can find here a programmer’s guide for the LaunchKey Mini MK4 as well:
Just scroll down at the bottom of the manuals’ section.
Other companies have been more cryptic with their DAW ports. I don’t blame them, it’s just that it made me more difficult, had to spent some hours to properly understand what and when these devices send and receive in these ports.
That is a very clever way you’ve come up with using what is definitely one of my all-time FAVORITE functions in Cubase: MediaBay.
It took me a minute to figure out how you were using it. I’m wondering: did you write the script in hopes of your SL Mk3 screen completely replacing the need to use your computer screen to navigate around MB? Or: is it simply augmenting the feedback you’re getting from the computer screen?
Again: I LOVE MediaBay! MediaBay is the single reason why, for the past year, I have basically ignored my MPC Live II. Even with the new-and much improved-MPC 3.0 beta (complete with it’s newly re-designed, DAW-inspired Arranger Section), I just can’t come up with a reason why I would make music on my MPC, when I have Cubase around, because doing it on Cubase is just so much easier, and because whatever the MPC can do, Cubase can do, and much more, because it is just so, so much more powerful than the average DAW in a Box.
And: MediaBay is just so, so much better at organizing assets. I don’t even mind the hours that I spend tagging assets because I know that this will pay off in the end, by giving me the ability to direct myself to just the assets I’m needing in the moment.
Cool! I’m taking a look at this right now!
It was not just a hope, I’ve done it It’s a complete rewrite, using an external app I’ve made. I get access to mediaBay’s db and proceed on my own, until the final stage of actually putting the preset in the instrument slot, where I have to use the track presets window by robot-typing the preset name in its search field and so on.
Hi M.C. I was wondering if you had any luck getting your hands on a LaunchKey Mini 37 Mk4?
Hello my friend, no, because I was wrong! My friend has an M-Audio Mini controller, I’m sorry, I really forgot to update here! Then, I didn’t go into coding, because as I’ve said it could potentially be a torture for both you and me (perhaps even more for you as the tester), in the debugging stage
Hmmm. I’m trying to figure out a way to get you one. That would help you, right?
Don’t bother, the expenses would be greater than the price of the keyboard itself. I’ll have a look at the script these days, or perhaps build one from scratch so you can give it a try Just tell me what functionality you’re looking for.
Functionality? Well, I just really want for the DAW Mode section to work. I’d like for the Pad/Button lights to not go away, and I’d like for the DAW functions to not go away from some projects. I just want it to be stable and reliable: I use it in an educational situation, and I need to ensure that the functions I rely on for that teaching situation are there when I need them, and that I don’t have to take precious time out from the lesson to troubleshoot.
Do you think I could communicate with Novation what they need to know in order for them to fix it? And if the answer is yes, then how do you think I should phrase my communications with them, to maximize their chances of success?
That doesn’t sound much to ask for I was wondering whether you may be have some sort of deflected USB cable?
It depends. If we’re talking only about the initialization step, then, yes, there are recommendations. But for the middle of a session, I don’t see there’s much to be done, disconnections have been reported, and I find it a complicated problem unfortunately, since it involves every part of the connection, DAW, OS, Keyboard.
Are you talking about my disconnections, as in reported to you, by me, or are you speaking from a knowledge of having heard about this issue before, from others as well as me?
Exactly. There are other threads as well concerning disconnections.
Well, honestly, where I’m at is this:
I don’t know your locale, but it it were in such a reasonable distance that I could pay to ship my own unit to and from you then I think I’m right about willing to contemplate that.
If there are some others out there who are having similar issues then maybe you want to get in touch with me, and we can all chip in to provide M.C. with his own LK-getting it at my reduced price, of course-happy in the knowledge that he’d be doing some good work for all of us, and in a way that would benefit the whole Cubase/LaunchKey community.
Wouldn’t it be more appropriate if simply Novation send me one?
Anyway, here’s what we can do. I’ll buy one, and check how it’s behaving. If I notice similar things as the ones you describe, I’ll get into re-scripting the unit. Is it OK?
I think if M.C. were to do this work for all of us, then providing him with a LaunchKey is the least we who benefit could do.
That’s my take on it.