Home › Forums › General › General MIDI discussion › Short question about Sysex "parameter value"
- This topic has 10 replies, 5 voices, and was last updated 13 years ago by atom.
-
AuthorPosts
-
April 6, 2011 at 11:27 pm #314
It’s a long time ago that I created some SysEx messages – I almost forgot everything. So it would be nice if someone could help.
I want to create in Ctrlr v5 a slider/pot which sends a Sysex message to my Virus. For example I want to control "LFO3 rate" which has values from 0-127. I did type in Ctrlr this hex code: F0 00 20 33 01 00 71 00 07 7F F7
"07" is the parameter number (LFO3 rate) and "7F" is the parameter value (127). So far so good. Now if I turn the pot in v5 the Virus receives the message… and LFO3 is set to value 127.
The question is: How do I control the full value range (0-127) of LFO3? What do I have to type in the "parameter value field"? For now I’m only able to send one single value which is in many cases not enough.One quick question more: how do I have to setup v5 to display values from -64 to +63 i.g. for pan values (negative and positive)? I’ve tried it with "Minimum value/Maximum value" in the v5 GUI, but the result wasn’t useful.
April 7, 2011 at 12:05 am #2514put xx in the byte where the value of the slider should be put in F0 00 20 33 01 00 71 00 07 xx F7 and that will give you the full range.
April 7, 2011 at 1:04 am #2515"minimalist":2v7n6pwe wrote:how do I have to setup v5 to display values from -64 to +63 i.g. for pan values (negative and positive)? I’ve tried it with "Minimum value/Maximum value" in the v5 GUI, but the result wasn’t useful.[/quote:2v7n6pwe]I was wondering the same thing for the Tetr4 and Mopho Mod amounts. I have been controlling these values on the Tetra with "Multi" message. The minimum and maximum values are listed in the manuals as 0-254. What am hoping is possible is to have the displayed range from -127 to 127 like you see on the instruments LCD display. Is this possible? Thanks.
April 7, 2011 at 9:17 am #2516yes it’s possible, at the moment it can be done in two ways
using lua and the luaHookModulatorChanged
or using the FixedSlider UI Component (you can create a map of values for the FixedSlider, Combo, Button components)
just type in the values you want displayed followed by the actual value you want sent, like so in the content property:
Value One=13
Value Two=14
Value Three=15
Value Four=127April 7, 2011 at 10:25 am #2517Thanks atom, Sysex works! From day to day I love v5 more and more. Hope that I can host and automate my Ctrlr projects without crashes soon.
April 7, 2011 at 10:43 am #2518pretty soon i think yes ” title=”Smile” />
April 7, 2011 at 12:53 pm #2519” title=”Razz” /> !
April 7, 2011 at 2:43 pm #2520"atom":29kbfv19 wrote:using lua and the luaHookModulatorChanged
[/quote:29kbfv19]
a small example or links to a guide for the LUA?April 7, 2011 at 3:02 pm #2521yeah i know ” title=”Smile” /> i need more time to reach a point where i know i won’t be changing anything that might impact your LUA code. a bit more patience please.
April 13, 2011 at 5:32 am #2522I started making template for DSI Mono Evolver, just want to make sure if I am doing it correctly to avoid fixing all those knobs in the end.
After trial and error I got knobs to communicate with the synth. First I watched midi monitor, which shows:
[quote:19viqm91][MidiIn][0:40:31:362.000]: [MIDI IN][8pre MIDI Port][f0 01 20 01 01 10 06 06 f7]
[MidiIn][0:40:31:392.000]: [MIDI IN][8pre MIDI Port][f0 01 20 01 01 10 07 06 f7][/quote:19viqm91]And I did Sysex knob with: [quote:19viqm91][f0] [01] [20] [01] [01] [10] [LSB 4bit] [MSB 4bit] [f7][/quote:19viqm91]
I just copy that knob and change part before LSB (10 to 16, etc) for another parameter (+ fix maximum value).
Knobs do work but CTRLR frequently freezes for few seconds when moving knobs from the synth.Osx 10.6.7, latest Ctrlr beta Stand-alone.
edit. OK, freezing is gone.. had to reboot. This starts to look quite promising. If someone could still confirm does my aproach look aproriate?
April 13, 2011 at 9:23 am #2523i have the evo and all sysex are the same and you are on the right track [f0] [01] [20] [01] [01] [10] [ls] [ms] [f7] i think the midi channel or the device ID might be one of the bytes too so you can add that but this will work i verified that at home.
-
AuthorPosts
- The forum ‘General MIDI discussion’ is closed to new topics and replies.