Author |
Topic: Problems with #CC to Sysex. (Read 2665 times) |
|
synthpelle
New Member
MIDI-OX Rules!
Posts: 5
|
 |
Problems with #CC to Sysex.
« on: Apr 15th, 2009, 8:56am » |
 Quote  Modify
|
I wan´t to control my Roland Mks-80 with Access Virus KC.
I´m sending #CC messages to Mks-80 and it answers but the value dosen´t change. If I set the value to another number the Mks-80 only turns to that value when I turn the knobs on KC. The value I change is the two last zeros at the sysex. How can I do to make the knobs on the KC to change the value on my Mks-80?
This is the Data Mapping:
Input: Channel-Any, EventType-Ctrl, Min-18, Max-18, Min-0, Max-127.
Output: EventType-Sysex, F0 41 36 00 20 20 01 00 00 F7.
Thank you for a great program.
|
|
 IP Logged |
|
|
|
synthpelle
New Member
MIDI-OX Rules!
Posts: 5
|
|
Re: Problems with #CC to Sysex.
« Reply #1 on: Apr 16th, 2009, 5:57am » |
Quote Modify
|
Someone maybe know how to help me??
I get contact with my mks-80 but the value dosen´t change when I turn the knobs.
|
|
IP Logged |
|
|
|
Breath
Administrator
Gender: 
Posts: 1030
|
|
Re: Problems with #CC to Sysex.
« Reply #2 on: Apr 25th, 2009, 11:43pm » |
Quote Modify
|
Hi,
just so we are on the same page... your sysex
F0 41 36 00 20 20 01 00 00 F7 just puts out
F0 41 36 00 20 20 01 00 00 F7
F0 41 36 00 20 20 01 00 00 F7
F0 41 36 00 20 20 01 00 00 F7
for every incoming CC message
According to the online manual this is the upper tone, LFO Rate
F0 41 36 00 20 20 01(upper tone) 00(LFO rate) val F7
where val = 0 to 100
What you want is the val to be a value of 0 to 100 so you put out the message
...
F0 41 36 00 20 20 01 00 06 F7
F0 41 36 00 20 20 01 00 07 F7
F0 41 36 00 20 20 01 00 08 F7
....
for (mod wheel, channel 1)
B0 01 06
B0 01 07
B0 01 08
As far as I know you can't get the CC value (Value2) into the sysex message.
I tried changing the sysex line F0 41 36 00 20 20 01 00 00 F7
into F0 41 36 00 20 20 01 00 < F7 (the txm file style)
or F0 41 36 00 20 20 01 00 -1 F7, but no good.
They are seen as illegal numbers and the sysex line is truncated
If no one else knows how to do this in MidiOx - excluding scripting - you might be better off with Bome's translator
www.bome.com
Royce
|
|
IP Logged |
|
|
|
synthpelle
New Member
MIDI-OX Rules!
Posts: 5
|
|
Re: Problems with #CC to Sysex.
« Reply #3 on: May 2nd, 2009, 5:19am » |
Quote Modify
|
on Apr 25th, 2009, 11:43pm, Breath wrote:Hi,
just so we are on the same page... your sysex
F0 41 36 00 20 20 01 00 00 F7 just puts out
F0 41 36 00 20 20 01 00 00 F7
F0 41 36 00 20 20 01 00 00 F7
F0 41 36 00 20 20 01 00 00 F7
for every incoming CC message
According to the online manual this is the upper tone, LFO Rate
F0 41 36 00 20 20 01(upper tone) 00(LFO rate) val F7
where val = 0 to 100
What you want is the val to be a value of 0 to 100 so you put out the message
...
F0 41 36 00 20 20 01 00 06 F7
F0 41 36 00 20 20 01 00 07 F7
F0 41 36 00 20 20 01 00 08 F7
....
for (mod wheel, channel 1)
B0 01 06
B0 01 07
B0 01 08
As far as I know you can't get the CC value (Value2) into the sysex message.
I tried changing the sysex line F0 41 36 00 20 20 01 00 00 F7
into F0 41 36 00 20 20 01 00 < F7 (the txm file style)
or F0 41 36 00 20 20 01 00 -1 F7, but no good.
They are seen as illegal numbers and the sysex line is truncated
If no one else knows how to do this in MidiOx - excluding scripting - you might be better off with Bome's translator
www.bome.com
Royce |
|
Thanks.
I will give www.bome.com a try. See if that working better.
|
|
IP Logged |
|
|
|
Jamie OConnell
Administrator
Gender:
Posts: 2027
|
|
Re: Problems with #CC to Sysex.
« Reply #4 on: Jun 11th, 2009, 3:03am » |
Quote Modify
|
From the help file (try it!):
SysEx Mapping
You can map normal MIDI messages and NRPNs to System Exclusive strings. When you choose SysEx as the Output Event Type, the edit interface changes to allow entry of a SysEx string. Actually, any string may be entered here (for instance multiple normal MIDI messages), but any string will be sent via the low-level Windows midiOutLongMessage() API function. This function call sends a buffer instead of a single MIDI message. MIDI-OX SysEx string mappings are limited to 1022 MIDI bytes or less. They should be entered as hexadecimal bytes (example: "F0 7F 00 02 01 F7").
There are three special substitution characters you can use within SysEx strings: FC, FA, and FB. In a mapping, they are replaced by values from the MIDI messages which triggers SysEx. They each result in 8 bits of data (a byte). They have the following meanings:
Code Replaced by Notes
FC Channel Values: 0 - 15, taken from the MIDI Message Status Byte
FA Data1 Values: 0 - 127, the first MIDI Message Data Byte
FB Data2 Values: 0 - 127, the second MIDI Message Data Byte
Example of SysEx Substitution:
Sysex String F0 00 00 13 FC FA 10 00 FC 00 FB 00 F7
MIDI Message 92 3F 48
Result F0 00 00 13 02 3F 10 00 02 00 48 00 F7
|
| « Last Edit: Jun 11th, 2009, 3:04am by Jamie OConnell » |
IP Logged |
--Jamie
Music is its own reward.
|
|
|
|
User Forum ::
Powered by YaBB
Home 
Help 
Search 
Members 
Login 
Register
Reply
Notify of replies
Send Topic
Print