Re: Filtering on ctl values & intervals

From: Jarl Nilsson <jarl.nilsson_at_gmail.com>
Date: Sun Jan 17 2016 - 16:08:55 CET
Hello Raphael,

Yes, that's one aspect for notes and CCs while the other is that there's no
possibility to specify the actual value or value interval of a ctl, just
the ctl number (much like the note number). There seem to be no modifiers
available that reach down to the value level in a similar fashion that the
velocity adjustment for the notes do. From a technical and logical point of
view the constraint for ctl values could most likely be that "... the set
must contain ranges of the same size *or size one*".

Greetings,
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
This
email has been sent from a virus-free computer protected by Avast.
www.avast.com
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
<#DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Sun, Jan 17, 2016 at 2:21 PM, Rapha√ęl Mouneyres <rmouneyres@gmail.com>
wrote:

> hello,
>
> rereading the revelant section of user manual (
> http://www.midish.org/manual.html#section_6_1 )
> a note says "The source and destination event sets must be of the same
> type and must contain ranges of the same size"
> So what you're asking looks like it is not doable as you source range is
> bigger than the destination range.
>
> Rapha√ęl
>
> Le 12 janv. 2016 à 02:50, Jarl Nilsson <jarl.nilsson@gmail.com> a écrit :
>
> > My situation is that I receive a CC value to be interpreted into three
> distinct levels where I'd need to map the three levels into two other CC
> events with different values from what I received. Something
> > along the line of the below if you can follow:
> >
> >  fmap {ctl in 3:0..63} {ctl out 4:127} # All values in interval 0...63
> from ctl 3 would yield a 127 on ctl4,
> >  fmap {ctl in 3:0..63} {ctl out 5:1} # along with a 1 on ctl 5.
> >
> > This far I haven't seen any way to do this. Have I missed something?
>
>
Received on Sun, 17 Jan 2016 16:08:55 +0100

This archive was generated by hypermail 2.1.8 : Wed Nov 08 2017 - 16:32:28 CET