Forum Replies Created
-
Posts
-
Steinberg wants to drop VST2 by October 2018 in favor of VST3 and will disallow distributing software that include VST2 SDK unless you got a signed license from them.
// LICENSE
// (c) 2017, Steinberg Media Technologies GmbH, All Rights Reserved
//—————————————————————————–
// This Software Development Kit may not be distributed in parts or its entirety
// without prior written agreement by Steinberg Media Technologies GmbH.
// This SDK must not be used to re-engineer or manipulate any technology used
// in any Steinberg or Third-party application or software module,
// unless permitted by law.The sysex file you are trying to send, has only one F0 and one F7 (one single block of data) or has several blocks? According to these links, it’s made of several blocks.
http://www.korgforums.com/forum/phpBB2/viewtopic.php?t=7550
https://www.soundonsound.com/techniques/korg-wavestation-tips-techniquesIf that’s the case, you need to send them individually with a timer to allow a delay between them.
I’ve had this problem before, but only with long lines.
I’ve sent you a message, let me know if you can solve the issue.
Yes, he is registered. I’ve created a password (that he could change after login) for him and sent it to his email account. Let me know if it worked.
This is not caused by Ctrlr or the panel. The panel was made with a Virus Snow that lacks a keyboard and also lacks Local parameter, so the panel can’t change it.
It could be that once you connect the USB cable, the Virus change to Local Off. Look at these posts:
https://www.virus.info/forum/index.php/Thread/6165-How-can-I-save-Local-on-off-to-off-permantly/
https://www.virus.info/forum/index.php/Thread/5577-Virus-TI-using-MIDI-only-over-USB/This plugin has no list, but you can write 2 or 3 letters of the member name and get a result.
When a new PM is received, you’ll see it in the main menu. The old plugin is there just to have access to old messages.
I’ve added a new private messages plugin, as I can’t find the reason the old one isn’t working. It is located in the main menu. The previous one is still active to have access to the old messages.
I’ve created another account and can’t send pm with it, too. Still looking what’s going on.
Poss, can you read your old PMs?
Can someone else confirm this? It’s not happening to me, I can send PM as usual.Private messages in this site are managed with an old wordpress plugin that is no updated anymore, but I don’t see anything wrong with the settings. I could install a more recent plugin, but we would loose old private messages.
To my knowledge when you talk about the plugin version of Ctrlr it does not matter if you have a multiclient capable midi interface. The DAW and the Ctrlr plugin won’t ever be able to use both the same port.
As I have no multi client midi interface I can’t test it by myself, but this contradicts this post:
Windows XP/ Ableton 8.1
Midiman midisport 2X2: supports multiclient (selecting the midi out in ableton preferences as in the plugin)
RME Fireface midi: does not support multiclient. (selecting the CTRLR midi out will cause an error openDevice hardware failed if it is also selcted in ableton midi preferences))
It’s not a Windows port sharing problem. I definitely CAN share ports inside Cubase. I am only using one ‘app’ – Cubase. It’s just that Ctrlr (as a plug-in – I’m not running it separately) cannot access any port that is referenced in Cubase’s MIDI Device Manager. If I remove the reference then Ctrlr accesses the port just fine. Removing the port in Cubase isn’t an option anyway – I then wouldn’t be able to play the instrument in Cubase.
If I’m not mistaken, you’re sharing ports INSIDE the same app (Cubase). Of course this is possible without multi client drivers. But Ctrlr, even as a plugin, has to manage his own ports, independent of the host, so consider it as another app, just as when you use Ctrlr as a stand alone app.
Can you use Cubase and Ctrlr standalone at the same time using the same ports?Yes, it is a Windows sharing thing. You are answering your question.
It’s just that Ctrlr cannot access any port that is referenced in Cubase’s MIDI Device Manager. If I remove the reference then Ctrlr accesses the port just fine.
Ctrlr needs it’s own ports, so you have two apps trying to access the same port, Cubase and Ctrlr. If the ports were multi client, you could use the same port with Cubase and Ctrlr.
I can’t help you with Cubase, but have you tried to use “input from plugin host” and “output to plugin host” and not selecting any midi in/out device?
Only Atom can fix this, as the links are outside the WordPress site.
On Windows you can’t share the same port with different apps if your MIDI interface drivers aren’t multi client. Your options are:
Change the MIDI interface to one with multi client capabilities.
Use virtual midi ports.
Disable in Cubase the MIDI port used with Ctrlr.
