|
|||||||
![]() |
|
|
LinkBack | Thread Tools |
|
|
#1 |
|
DriverHeaven Junior Member
Join Date: Nov 2003
Posts: 95
Rep Power: 0 ![]() |
MIDI IN-to-kX Control
As we all know - Asynth has a simple drop-down list of all MIDI Inputs.
So, is it possible for someone, familiar with coding, to make a simple "plugin" which can act as bridge between those MIDI Inputs AND kX Control? Thus way we will be able to control all DSP plugins through MIDI without need of external software. I hope to see such drop-down list in the next druiver release, but probably Eugene has more important stuff to add there. |
|
|
|
|
|
#2 |
|
DriverHeaven Junior Member
Join Date: Dec 2004
Posts: 88
Rep Power: 0 ![]() |
|
|
|
|
|
|
#3 |
|
Tail Razer
Join Date: Jun 2005
Location: Bernyurass, AZ - USA
Posts: 4,027
Rep Power: 36 ![]() ![]() |
well midiyoke - is just a 'virtual midi' driver that allows midi ox to act as the bridge. (or thats how it seems to me)
Thus - it sorta is using 2x the 'resource' than say - the KX driver acting as the bridge...or even if it were an addon to KX - but Id think youd still need midiyoke driver installed UNLESS KX control was made as a 'sharable' driver (do those even exists?) that would act as a 'midi merge'. But I could be wrong and would like to be corrected if so... |
|
|
|
|
|
#4 | ||
|
DH Senior Member
Join Date: Jan 2003
Location: The Netherlands
Posts: 1,879
Rep Power: 48 ![]() ![]() ![]() ![]() |
Quote:
Although all kX MIDI ports are multi-client, the OS (Windows) does not allow to open any MIDI port more then once by the same application (which makes sense). Since kX-plugins run as dll extension 'in' kxmixer.exe they can not open kX-Control port since it is already opened (in use) by that same kxmixer.exe. It is however possible and not hard to write a standalone app which routes any MIDI-IN port to kX-control but that is the same as using MIDI-OX. I wrote Asynth not to use kx-control at all but that is mainly because the kx-control port is to slow for busy and tight MIDI playback. Quote:
want to be able to send midi data between MIDI applications. MIDI-OX itself is 'just' a MIDI Port router. That is; if you only want to route physical MIDI IN port data to, let's say kX-Control port, you don't have to have midiyoke driver installed at all. Visa versa; if you only want to route midi data from one MIDI App to another, you have to have midiyoke driver installed, but you don't necesarily need MIDI-OX. HTH. Cheers, /Lex. |
||
|
|
|
|
|
#5 |
|
Tail Razer
Join Date: Jun 2005
Location: Bernyurass, AZ - USA
Posts: 4,027
Rep Power: 36 ![]() ![]() |
|
|
|
|
|
|
#6 |
|
Tail Razer
Join Date: Jun 2005
Location: Bernyurass, AZ - USA
Posts: 4,027
Rep Power: 36 ![]() ![]() |
In case anyone is interested...
vMidiMixer |
|
|
|
![]() |
| Bookmarks |
| Thread Tools | |
|
|