Page 1 of 1
monitoring data from secondary source
Posted: 04 Apr 2015 06:06
by auralsculpture
I suspect this is more simple than I'm making it, but I'm very much a newbie
I'm modifying the Absynth Faders +XY template. This allows you to map a cc to each of the faders and xys etc. I simply want to put a monitor or a label next to each fader so I can see what it is set to - but I'm stuck - I've missed something.
If someone can post a fix I'll populate and re-upload
Colin
Re: monitoring data from secondary source
Posted: 04 Apr 2015 08:19
by Softcore
Here's the problem......WHAT units will the monitors show?
MIDI values? Thats easy!
The "mapped" parameter? How does Lemur know what is actually being mapped - since, in one preset the fader might be mapped to a filter cut off, next preset the same fader migh tbe mapped to a dry-wet knob or something. How is Lemur supposed to know, and consequently how do we know WHAT to display on that monitor?
Re: monitoring data from secondary source
Posted: 04 Apr 2015 08:20
by Softcore
...or are you simply wanting to display the mapped CC and its value (in MIDI)?
Re: monitoring data from secondary source
Posted: 04 Apr 2015 08:24
by Softcore
Oooooops my board attachment quota has been reached?????
Re: monitoring data from secondary source
Posted: 04 Apr 2015 08:28
by Softcore
Re: monitoring data from secondary source
Posted: 04 Apr 2015 09:33
by auralsculpture
Yes it's just to see what cc# value the fader is sending. The file you uploaded is good for 1 fader, but if I duplicate it for the second fader, how does it kink?
Monitor for the value is Fader1.x*127 (this one I understand, it looks at the x value of the fader and all I have to do is change Fader1 to Fader2
but this one, Monitor MCC1 x=CC[0] I dont understand where the value is coming from because if I make a MCC2 with the same string it fails
Thanks
Colin
Re: monitoring data from secondary source
Posted: 04 Apr 2015 10:09
by Softcore
Ah see in order to get this you have to ask yourself....How are the configurations (fader mappings) for each fader saved/stored - recalled in the first place.
Now look at the custom expression (array) CC.....it consists of numbers and each number is the 'saved' configuration for each fader.
So , CC[0] is Fader1's CC, CC[1] is Fader2's and so on and so on.
Re: monitoring data from secondary source
Posted: 04 Apr 2015 10:11
by Softcore
...the same could apply to the Midi channels for each fader....Guess what you would have to type in a monitor to also display the midi channel of each fader....
Ch[0], Ch[1] and so on!
Re: monitoring data from secondary source
Posted: 04 Apr 2015 10:54
by auralsculpture
aha, I get it, its not looking at the fader, but the custom array
thanks so much
Colin