Since i changed my Midisport to another device can't use CTRL

[casiowaves]

“There is not enough memory available for this task”
If i close my DAW then i can work with ctrl, but not both, this didn’t happened to me with my last midi card, midisport4/4 until it stopped working suddenly.

[dasfaker]

That’s probably because your new interface is not bi-directional. If that’s the case, you can’t share the same port in more than one application. You should close the midi port in your daw to use it with Ctrlr.

• This reply was modified 6 years, 2 months ago by dasfaker.

[casiowaves]

very bad news.. how i can know this before buying another device? you people at ctrl recommend some? i need 20 midi or more.

[dasfaker]

As far as I know, one of the few bi-directional midi interfaces for Windows was ESI. Don’t know about recent interfaces like Iconnectivity.

[Possemo]

E.g. the MOTU interfaces are all multi-client capable. The thing is that the built-in MIDI drivers of Windows aren’t mulit-client but many manufacturers provide their own drivers – lots of them are multi-client capable. The iConnectivity seem to be great interfaces. They are class-compliant, so they will work with the built-in drivers of Windows and Mac, but additionally they provide their own drivers which are multi-client.

What type is your interface? Maybe they provide mulit-client drivers.

[casiowaves]

MIDITECH MIDIFACE 4/4
http://miditech.de/en-239-produkte-midiface-4×4

Doesn’t come with any driver i think.

• This reply was modified 6 years, 2 months ago by casiowaves.

[Possemo]

indeed it looks like they don’t provide proprietary drivers. There is one option left – when you use the Ctrlr VSTi plugin with a DAW like Reaper which allows full integration of the Ctrlr plugin. I haven’t seen any other DAW that will do this. Oh well, there is another option – on Mac OsX the built-in drivers are multi-client capable.

• This reply was modified 6 years, 2 months ago by Possemo.

[Author]

Posts