[sergeeo]

Yep that’s the point, you can’t use that ports from the plug-in because they’re still visible to your Cubase project! First you have to set those ports as “non-visible”, and then you access them through the plug-in. You don’t need the MIDI DEVICE MANAGER for anything.

I’ve added a screenshot to let you see what you should unmark (my version is in Spanish, but you’ll recognize the menu).

Lemme know if this works for you.

PS: If you’ve installed your device using the MIDI DEVICE MANAGER, my advice is to uninstall it and use your device the way I’ve explained.

PS2: Sorry, I’ve read the whole thread n_n If you don’t want to keep a dedicated port to that synth, I guess this isn’t useful for you.

• This reply was modified 6 years ago by sergeeo.
• This reply was modified 6 years ago by sergeeo.

Attachments:

You must be logged in to view attached files.

[sergeeo]

Hey!

I’ve had a similar problem with other panel. AFAIK the multiclient MIDI ports are the problem in Windows. I’ve even tried multiclient drivers for my midi interface and… they just didn’t work.

I’ve found two different solutions:

1. Installing a virtual midi device such as LoopBe and using the panel in standalone mode. You can route your midi channels in Cubase to LoopBe input, and in your panel, route the LoopBe out as your input device. This solution is a bit “clumsy” as I’ve noticed a bit extra latency.

2. Deactivate the MIDI ports where your device is connected in Cubase. Just go to MIDI PORT SETUP menu and set those input/output ports as non visible. Then load your plug-in and let it connect directly to your device. This has been my favourite solution. You have to do this before trying to connect the plug-in 🙂

Hope this helps

• This reply was modified 6 years ago by sergeeo.
• This reply was modified 6 years ago by sergeeo.

[sergeeo]

THIS would be awesome. +1 for this project.

[Author]

Posts