Author |
Topic: None of the demos send midi after diverting SOLVED (Read 3272 times) |
|
Soul-Burn
New Member
MIDI-OX Rules!
Posts: 2
|
 |
None of the demos send midi after diverting SOLVED
« on: May 14th, 2013, 7:28pm » |
 Quote  Modify
|
I have tried running the demos at C:\Program Files (x86)\MIDIOX\WSH including:
MOXScriptDemo.vbs
MOXScriptPoll.vbs
MOXPythonDemo.py
In all of them, when selecting "divert midi", no data sent from the controller is propagated onwards (unlike when just midi-ox, without a script, is running). The data is received in the script (added prints for debugging), but the OutputMidiMsg function fails to do anything.
This is my mapping (if relevant)
Inputs:
Midi controller 1
Midi controller 2
teMidiloop return
Outputs:
teMidiloop 1
teMidiloop 2
teMidiloop both
Mapping:
teMidiloop 1
- Midi controller 1
teMidiloop 2
- Midi controller 2
teMidiloop both
- Midi controller 1
- Midi controller 2
-- SOLUTION --
I didn't add the Midi-OX events to the channels, causing the generated events to go nowhere.
|
| « Last Edit: May 15th, 2013, 2:20am by Soul-Burn » |
 IP Logged |
|
|
|
Soul-Burn
New Member
MIDI-OX Rules!
Posts: 2
|
|
Re: None of the demos send midi after diverting
« Reply #1 on: May 15th, 2013, 2:12am » |
Quote Modify
|
Ok so regardless of diverting, the call "mox.OutputMidiMsg(-1, status, data1, data2)" does not seem to send the data back to midi-ox.
Other calls seems to work (GetInPortID etc) and return usable values.
The output monitor screen stays empty until diversion is over.
The input monitor screen shows the input, but seems to stutter quite a bit.
|
|
IP Logged |
|
|
|
|
User Forum ::
Powered by YaBB
Home 
Help 
Search 
Members 
Login 
Register
Reply
Notify of replies
Send Topic
Print