Csound Csound-dev Csound-tekno Search About

[Csnd] MPE aftouch opcode

Date2017-12-08 08:31
Fromalexmitchellmus
Subject[Csnd] MPE aftouch opcode
I am interested in using aftouch opcode in Csound for MPE controllers such as
the Roli Seaboard.

Current behavior of aftouch is to init as FL(127) (for both channel pressure
& plyphonic aftertouch).

Would changing the aftouch init value to FL(0.0) be considered a break in
compatibility?

This is also a discussion at Cabbage Audio forum:
http://forum.cabbageaudio.com/t/roli-seaboard-mpe-with-cabbage/839/42

Cheers,
Alex



--
Sent from: http://csound.1045644.n5.nabble.com/Csound-General-f1093014.html

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2017-12-08 22:37
FromSteven Yi
SubjectRe: [Csnd] MPE aftouch opcode
Hi Alex,

I think it would be considered a break.  I see this in InOut/midirecv.c:

    /* reset aftertouch to max value - added by Istvan Varga, May 2002 */
    chn->aftouch = FL(127.0);
    for (i = 0; i < 128; i++)
      chn->polyaft[i] = FL(127.0);

I suppose this was done for a reason. I tried searching online for
MIDI specification info about what defaults there should be, if any,
for channel and polyphonic aftertouch.

You could always file an issue on Csound's issue tracker; perhaps
someone can implement some way to make the default user-settable,
which would keep the backwards compatibility if it defaulted to 127
like before.

steven


On Fri, Dec 8, 2017 at 3:31 AM, alexmitchellmus
 wrote:
> I am interested in using aftouch opcode in Csound for MPE controllers such as
> the Roli Seaboard.
>
> Current behavior of aftouch is to init as FL(127) (for both channel pressure
> & plyphonic aftertouch).
>
> Would changing the aftouch init value to FL(0.0) be considered a break in
> compatibility?
>
> This is also a discussion at Cabbage Audio forum:
> http://forum.cabbageaudio.com/t/roli-seaboard-mpe-with-cabbage/839/42
>
> Cheers,
> Alex
>
>
>
> --
> Sent from: http://csound.1045644.n5.nabble.com/Csound-General-f1093014.html
>
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>         https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2017-12-09 04:21
Fromalexmitchellmus
SubjectRe: [Csnd] MPE aftouch opcode
Hey Steven,

Yes the user option sounds like a great idea! I think I will post a note on
the issue tracker.

So the value could be set among the global variables like sr, ksmps etc..?
Or are you suggesting a CsOptions approach?

Cheers,
Alex



--
Sent from: http://csound.1045644.n5.nabble.com/Csound-General-f1093014.html

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2017-12-09 14:22
FromSteven Yi
SubjectRe: [Csnd] MPE aftouch opcode

I think adding new global variables would be a bit burdensome to maintain. An opcode or command line flag seems more appropriate.


On Fri, Dec 8, 2017, 23:21 alexmitchellmus <alex.w.mitchell@gmail.com> wrote:
Hey Steven,

Yes the user option sounds like a great idea! I think I will post a note on
the issue tracker.

So the value could be set among the global variables like sr, ksmps etc..?
Or are you suggesting a CsOptions approach?

Cheers,
Alex



--
Sent from: http://csound.1045644.n5.nabble.com/Csound-General-f1093014.html

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date2017-12-09 14:46
FromVictor Lazzarini
SubjectRe: [Csnd] MPE aftouch opcode
couldn’t we solve this with a new optional argument for the opcode?

Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy
Maynooth University
Ireland

On 9 Dec 2017, at 14:23, Steven Yi <stevenyi@GMAIL.COM> wrote:

I think adding new global variables would be a bit burdensome to maintain. An opcode or command line flag seems more appropriate.


On Fri, Dec 8, 2017, 23:21 alexmitchellmus <alex.w.mitchell@gmail.com> wrote:
Hey Steven,

Yes the user option sounds like a great idea! I think I will post a note on
the issue tracker.

So the value could be set among the global variables like sr, ksmps etc..?
Or are you suggesting a CsOptions approach?

Cheers,
Alex



--
Sent from: http://csound.1045644.n5.nabble.com/Csound-General-f1093014.html

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date2017-12-09 14:57
FromJohn ff
SubjectRe: [Csnd] MPE aftouch opcode
That was my thought too.

⁣Sent from TypeApp ​

On Dec 9, 2017, 14:46, at 14:46, Victor Lazzarini  wrote:
>couldn’t we solve this with a new optional argument for the opcode?
>
>Victor Lazzarini
>Dean of Arts, Celtic Studies, and Philosophy
>Maynooth University
>Ireland
>
>On 9 Dec 2017, at 14:23, Steven Yi
>> wrote:
>
>
>I think adding new global variables would be a bit burdensome to
>maintain. An opcode or command line flag seems more appropriate.
>
>On Fri, Dec 8, 2017, 23:21 alexmitchellmus
>> wrote:
>Hey Steven,
>
>Yes the user option sounds like a great idea! I think I will post a
>note on
>the issue tracker.
>
>So the value could be set among the global variables like sr, ksmps
>etc..?
>Or are you suggesting a CsOptions approach?
>
>Cheers,
>Alex
>
>
>
>--
>Sent from:
>http://csound.1045644.n5.nabble.com/Csound-General-f1093014.html
>
>Csound mailing list
>Csound@listserv.heanet.ie
>https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>Send bugs reports to
>        https://github.com/csound/csound/issues
>Discussions of bugs and features can be posted here
>Csound mailing list
>Csound@listserv.heanet.ie
>https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>https://github.com/csound/csound/issues Discussions of bugs and
>features can be posted here
>
>Csound mailing list
>Csound@listserv.heanet.ie
>https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>Send bugs reports to
>        https://github.com/csound/csound/issues
>Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2017-12-09 17:12
FromSteven Yi
SubjectRe: [Csnd] MPE aftouch opcode
I don't think so. If you look at my message, the code in question is
in InOut/midirecv.c.  So it is there that sets the aftertouch values
to 127.  Imagine too that there could be multiple aftouch opcodes with
different ranges being used, but they'll all be reading the same input
values.  So the reader opcodes here are decoupled from the input and
we would need to modify the input.

On Sat, Dec 9, 2017 at 9:57 AM, John ff  wrote:
> That was my thought too.
>
> ⁣Sent from TypeApp
>
> On Dec 9, 2017, 14:46, at 14:46, Victor Lazzarini  wrote:
>>couldn’t we solve this with a new optional argument for the opcode?
>>
>>Victor Lazzarini
>>Dean of Arts, Celtic Studies, and Philosophy
>>Maynooth University
>>Ireland
>>
>>On 9 Dec 2017, at 14:23, Steven Yi
>>> wrote:
>>
>>
>>I think adding new global variables would be a bit burdensome to
>>maintain. An opcode or command line flag seems more appropriate.
>>
>>On Fri, Dec 8, 2017, 23:21 alexmitchellmus
>>> wrote:
>>Hey Steven,
>>
>>Yes the user option sounds like a great idea! I think I will post a
>>note on
>>the issue tracker.
>>
>>So the value could be set among the global variables like sr, ksmps
>>etc..?
>>Or are you suggesting a CsOptions approach?
>>
>>Cheers,
>>Alex
>>
>>
>>
>>--
>>Sent from:
>>http://csound.1045644.n5.nabble.com/Csound-General-f1093014.html
>>
>>Csound mailing list
>>Csound@listserv.heanet.ie
>>https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>Send bugs reports to
>>        https://github.com/csound/csound/issues
>>Discussions of bugs and features can be posted here
>>Csound mailing list
>>Csound@listserv.heanet.ie
>>https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>>https://github.com/csound/csound/issues Discussions of bugs and
>>features can be posted here
>>
>>Csound mailing list
>>Csound@listserv.heanet.ie
>>https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>Send bugs reports to
>>        https://github.com/csound/csound/issues
>>Discussions of bugs and features can be posted here
>
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>         https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2017-12-09 23:12
FromJohn ff
SubjectRe: [Csnd] MPE aftouch opcode
Looking at the code I think the option (command line and CsOption) is the way to go.  But I know little about MIDI so not sure of usecase.

Sent from Blue
On 9 Dec 2017, at 17:12, Steven Yi <stevenyi@GMAIL.COM> wrote:
I don't think so. If you look at my message, the code in question is
in InOut/midirecv.c. So it is there that sets the aftertouch values
to 127. Imagine too that there could be multiple aftouch opcodes with
different ranges being used, but they'll all be reading the same input
values. So the reader opcodes here are decoupled from the input and
we would need to modify the input.

On Sat, Dec 9, 2017 at 9:57 AM, John ff <jpff@codemist.co.uk> wrote:
That was my thought too.

⁣Sent from TypeApp

On Dec 9, 2017, 14:46, at 14:46, Victor Lazzarini <Victor.Lazzarini@MU.IE> wrote:
couldn’t we solve this with a new optional argument for the opcode?

Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy
Maynooth University
Ireland

On 9 Dec 2017, at 14:23, Steven Yi
<stevenyi@GMAIL.COM<mailto:stevenyi@GMAIL.COM>> wrote:


I think adding new global variables would be a bit burdensome to
maintain. An opcode or command line flag seems more appropriate.

On Fri, Dec 8, 2017, 23:21 alexmitchellmus
<alex.w.mitchell@gmail.com<mailto:alex.w.mitchell@gmail.com>> wrote:
Hey Steven,

Yes the user option sounds like a great idea! I think I will post a
note on
the issue tracker.

So the value could be set among the global variables like sr, ksmps
etc..?
Or are you suggesting a CsOptions approach?

Cheers,
Alex



--
Sent from:
http://csound.1045644.n5.nabble.com/Csound-General-f1093014.html

Csound mailing list
Csound@listserv.heanet.ie<mailto:Csound@listserv.heanet.ie>
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
Csound mailing list
Csound@listserv.heanet.ie<mailto:Csound@listserv.heanet.ie>
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
https://github.com/csound/csound/issues Discussions of bugs and
features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2017-12-10 01:51
Fromalexmitchellmus
SubjectRe: [Csnd] MPE aftouch opcode
What CsOption name would be most suitable?

This setting is for changing the init value of after-touch, so:

initat

initaft

Also would it be better to simply have a flag by itself to change init to 0,
as opposed to entering in a value? Eg: initat=0

If so aftzero makes more sense- or aft0

As an aftertouch user I can't see any benefit to having selectable range, as
I mentioned before- this value becomes 0 after first note-on event anyway.



--
Sent from: http://csound.1045644.n5.nabble.com/Csound-General-f1093014.html

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2017-12-10 11:55
Fromalexmitchellmus
SubjectRe: [Csnd] MPE aftouch opcode
Hey, I was able to get this working using:

csound->oparms

Is that an accepted Csound way?

I can push this onto GitHub, currently I am using the flag: --aft_zero but
if it needs to be something else let me know, and if we need to have a short
form as well?

Cheers,
Alex



--
Sent from: http://csound.1045644.n5.nabble.com/Csound-General-f1093014.html

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2017-12-10 13:36
FromJohn ff
SubjectRe: [Csnd] MPE aftouch opcode
I would have used a new field in CSOUND.  Question is do we rush this into 6.10 at this late stage?  Clearly easy to code, and to document.

⁣Sent from TypeApp ​

On Dec 10, 2017, 11:56, at 11:56, alexmitchellmus  wrote:
>Hey, I was able to get this working using:
>
>csound->oparms
>
>Is that an accepted Csound way?
>
>I can push this onto GitHub, currently I am using the flag: --aft_zero
>but
>if it needs to be something else let me know, and if we need to have a
>short
>form as well?
>
>Cheers,
>Alex
>
>
>
>--
>Sent from:
>http://csound.1045644.n5.nabble.com/Csound-General-f1093014.html
>
>Csound mailing list
>Csound@listserv.heanet.ie
>https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>Send bugs reports to
>        https://github.com/csound/csound/issues
>Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2017-12-10 14:23
Fromalexmitchellmus
SubjectRe: [Csnd] MPE aftouch opcode
Well here is my github fork:

https://github.com/alcomposer/csound

As I'm new to Csound development I am not quite sure how it works with
documentation. Is this mainly in the github Csound/Manual? or within
Csound/Csound? 

Obviously it was a great learning experience looking into Csound regardless.

Cheers,
Alex



--
Sent from: http://csound.1045644.n5.nabble.com/Csound-General-f1093014.html

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2017-12-10 18:56
From"Dr. Richard Boulanger"
SubjectRe: [Csnd] MPE aftouch opcode
I would really like to see an MPE aftouch opcode for use with devices such as the ROLI controller.  Iain M.  should have some insights into this as he just shared some examples?  Thoughts about fully supporting expressive Controllers, such as the ROLI, in Csound?

Sent from my iPhone

> On Dec 10, 2017, at 9:23 AM, alexmitchellmus  wrote:
> 
> Well here is my github fork:
> 
> https://github.com/alcomposer/csound
> 
> As I'm new to Csound development I am not quite sure how it works with
> documentation. Is this mainly in the github Csound/Manual? or within
> Csound/Csound? 
> 
> Obviously it was a great learning experience looking into Csound regardless.
> 
> Cheers,
> Alex
> 
> 
> 
> --
> Sent from: http://csound.1045644.n5.nabble.com/Csound-General-f1093014.html
> 
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>        https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2017-12-10 19:13
FromIain McCurdy
SubjectRe: [Csnd] MPE aftouch opcode

What Csound already has - aftouch, pchbend and midic7 - all work well with the way MPE devices work. These opcodes all read on the MIDI channel on which the note was triggered and this aligns with the way MPE data is channelised and sent. Csound can then be directed to send notes on all channels to a single instrument using massign but the MIDI channel information is still available to the instrument. The only limitation I encountered so far is that sustain pedal operations won't work as they come in on a single channel (typically channel 1) and not on the channel of notes that are begin played. Csound's built-in mechansim needs the sustain data (CC#64) to be on the same channel as the note. One solution, of course, is to disable Csound's built-in MIDI note scheduling mechanism and build the whole system with Csound code but perhaps there is scope for being able to fine tuning Csound's built-in mechanism with a header opcode along the lines of massign. For example:

susassign 0, 1

could direct all sustain instructions to instrument 1.




From: A discussion list for users of Csound <CSOUND@LISTSERV.HEANET.IE> on behalf of Dr. Richard Boulanger <rboulanger@BERKLEE.EDU>
Sent: 10 December 2017 18:56
To: CSOUND@LISTSERV.HEANET.IE
Subject: Re: [Csnd] MPE aftouch opcode
 
I would really like to see an MPE aftouch opcode for use with devices such as the ROLI controller.  Iain M.  should have some insights into this as he just shared some examples?  Thoughts about fully supporting expressive Controllers, such as the ROLI, in Csound?

Sent from my iPhone

> On Dec 10, 2017, at 9:23 AM, alexmitchellmus <alex.w.mitchell@GMAIL.COM> wrote:
>
> Well here is my github fork:
>
> https://github.com/alcomposer/csound
>
> As I'm new to Csound development I am not quite sure how it works with
> documentation. Is this mainly in the github Csound/Manual? or within
> Csound/Csound?
>
> Obviously it was a great learning experience looking into Csound regardless.
>
> Cheers,
> Alex
>
>
>
> --
> Sent from: http://csound.1045644.n5.nabble.com/Csound-General-f1093014.html


>
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND


> Send bugs reports to
>        https://github.com/csound/csound/issues


> Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND


Send bugs reports to
        https://github.com/csound/csound/issues


Discussions of bugs and features can be posted here

Date2017-12-10 20:02
From"Dr. Richard Boulanger"
SubjectRe: [Csnd] MPE aftouch opcode
I like the susassign idea very much.

And good to know that we have most of what we need already in place.

Sent from my iPhone

On Dec 10, 2017, at 2:13 PM, Iain McCurdy <i_mccurdy@HOTMAIL.COM> wrote:

What Csound already has - aftouch, pchbend and midic7 - all work well with the way MPE devices work. These opcodes all read on the MIDI channel on which the note was triggered and this aligns with the way MPE data is channelised and sent. Csound can then be directed to send notes on all channels to a single instrument using massign but the MIDI channel information is still available to the instrument. The only limitation I encountered so far is that sustain pedal operations won't work as they come in on a single channel (typically channel 1) and not on the channel of notes that are begin played. Csound's built-in mechansim needs the sustain data (CC#64) to be on the same channel as the note. One solution, of course, is to disable Csound's built-in MIDI note scheduling mechanism and build the whole system with Csound code but perhaps there is scope for being able to fine tuning Csound's built-in mechanism with a header opcode along the lines of massign. For example:

susassign 0, 1

could direct all sustain instructions to instrument 1.




From: A discussion list for users of Csound <CSOUND@LISTSERV.HEANET.IE> on behalf of Dr. Richard Boulanger <rboulanger@BERKLEE.EDU>
Sent: 10 December 2017 18:56
To: CSOUND@LISTSERV.HEANET.IE
Subject: Re: [Csnd] MPE aftouch opcode
 
I would really like to see an MPE aftouch opcode for use with devices such as the ROLI controller.  Iain M.  should have some insights into this as he just shared some examples?  Thoughts about fully supporting expressive Controllers, such as the ROLI, in Csound?

Sent from my iPhone

> On Dec 10, 2017, at 9:23 AM, alexmitchellmus <alex.w.mitchell@GMAIL.COM> wrote:
>
> Well here is my github fork:
>
> https://github.com/alcomposer/csound
>
> As I'm new to Csound development I am not quite sure how it works with
> documentation. Is this mainly in the github Csound/Manual? or within
> Csound/Csound?
>
> Obviously it was a great learning experience looking into Csound regardless.
>
> Cheers,
> Alex
>
>
>
> --
> Sent from: http://csound.1045644.n5.nabble.com/Csound-General-f1093014.html


>
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> Send bugs reports to
>        https://github.com/csound/csound/issues


> Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

Send bugs reports to
        https://github.com/csound/csound/issues


Discussions of bugs and features can be posted here
Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date2017-12-11 06:03
Fromalexmitchellmus
SubjectRe: [Csnd] MPE aftouch opcode
Roli also have the Blocks system, which is a 'magnetically snapped together'
controller system:

* Seaboard Block
* Lightpad Block (v1 & v2)
* Live, Loop, Touch Block

The Lightpad Block is very interesting as it can be programmed (currently
with Blocks Dashboard & Max/MSP)

I believe that there is a Juce class for sending SysEx to the Lightpad
Blocks.  These messages can configure its behaviour- and program custom
behaviour.

It may be really cool in the future to have a Csound Opcode that allows
control of the Lightpad, enabling custom layouts to be generated from within
Csound.

At this point I think that the communication is part of the MPE Class in the
Juce Framework: https://juce.com/doc/classBlock

Further to this it may be exciting to have a Roli Blocks Csound Opcode that
is able to communicate with all the connected Blocks in a Blocks system.



--
Sent from: http://csound.1045644.n5.nabble.com/Csound-General-f1093014.html

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2017-12-11 10:44
FromIain McCurdy
SubjectRe: [Csnd] MPE aftouch opcode

In general, I think opcodes that are hardware-specific are better as UDOs. This way, if the hardware becomes obsolete, Csound doesn't need to bear the bloat. However, if there is some functionality that is standard and likely to receive continued support then an opcode is certainly worth considering.



From: A discussion list for users of Csound <CSOUND@LISTSERV.HEANET.IE> on behalf of alexmitchellmus <alex.w.mitchell@GMAIL.COM>
Sent: 11 December 2017 06:03
To: CSOUND@LISTSERV.HEANET.IE
Subject: Re: [Csnd] MPE aftouch opcode
 
Roli also have the Blocks system, which is a 'magnetically snapped together'
controller system:

* Seaboard Block
* Lightpad Block (v1 & v2)
* Live, Loop, Touch Block

The Lightpad Block is very interesting as it can be programmed (currently
with Blocks Dashboard & Max/MSP)

I believe that there is a Juce class for sending SysEx to the Lightpad
Blocks.  These messages can configure its behaviour- and program custom
behaviour.

It may be really cool in the future to have a Csound Opcode that allows
control of the Lightpad, enabling custom layouts to be generated from within
Csound.

At this point I think that the communication is part of the MPE Class in the
Juce Framework: https://juce.com/doc/classBlock



Further to this it may be exciting to have a Roli Blocks Csound Opcode that
is able to communicate with all the connected Blocks in a Blocks system.



--
Sent from: http://csound.1045644.n5.nabble.com/Csound-General-f1093014.html



Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2017-12-11 11:22
Fromalexmitchellmus
SubjectRe: [Csnd] MPE aftouch opcode
Yes, I do agree, and was pained to suggest this. I think that apart from MPE
the SysEx would be far from specific.



--
Sent from: http://csound.1045644.n5.nabble.com/Csound-General-f1093014.html

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2017-12-12 01:45
Fromalexmitchellmus
SubjectRe: [Csnd] MPE aftouch opcode
Thanks for fixing up --aft-zero as a field jpff!!! --aft-zero is now a thing!



--
Sent from: http://csound.1045644.n5.nabble.com/Csound-General-f1093014.html

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2017-12-12 03:42
From"Dr. Richard Boulanger"
SubjectRe: [Csnd] MPE aftouch opcode

A collection of UDOS would be excellent.  Maybe Iain has already made them?

I am just thinking the MPE is becoming a new standard for more "expressive" controller hardware 
(the Linnstrument is awesome, as are the ROLI controllers)

Maybe the MPE class in Juce might enlighten us as to what is missing from Csound's current MIDI opcodes

There is also support for MPE in Max/MSP that could be considered as well.

Here are some links










_____________________________________________
Dr. Richard Boulanger
Professor of Electronic Production and Design
Professional Writing and Music Technology Division
Berklee College of Music
______________________________________________
President of Boulanger Labs - http://boulangerlabs.com
Author & Editor of The Csound Book - http://mitpress.mit.edu/books/csound-book
Author & Editor of The Audio Programming Book - http://mitpress.mit.edu/books/audio-programming-book
______________________________________________
about: 
http://www.boulangerlabs.com/#about
about: http://www.csounds.com/community/developers/dr-richard-boulanger/
music: http://www.csounds.com/community/developers/dr-richard-boulanger/dr-richard-boulanger-music/

______________________________________________
email: rboulanger@berklee.edu
facebook: https://www.facebook.com/richard.boulanger.58

On Mon, Dec 11, 2017 at 1:03 AM, alexmitchellmus <alex.w.mitchell@gmail.com> wrote:
Roli also have the Blocks system, which is a 'magnetically snapped together'
controller system:

* Seaboard Block
* Lightpad Block (v1 & v2)
* Live, Loop, Touch Block

The Lightpad Block is very interesting as it can be programmed (currently
with Blocks Dashboard & Max/MSP)

I believe that there is a Juce class for sending SysEx to the Lightpad
Blocks.  These messages can configure its behaviour- and program custom
behaviour.

It may be really cool in the future to have a Csound Opcode that allows
control of the Lightpad, enabling custom layouts to be generated from within
Csound.

At this point I think that the communication is part of the MPE Class in the
Juce Framework: https://juce.com/doc/classBlock

Further to this it may be exciting to have a Roli Blocks Csound Opcode that
is able to communicate with all the connected Blocks in a Blocks system.



--
Sent from: http://csound.1045644.n5.nabble.com/Csound-General-f1093014.html

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Date2017-12-12 12:32
Fromalexmitchellmus
SubjectRe: [Csnd] MPE aftouch opcode
Just thought that it may be great if there was a way to use massign for a
range of midi channels.
Currently, my understanding is that massign is one channel- per instrument
number:

massign 1, 1

With MPE- we get 15 midi channels, (2-16) so it would be great to either add
the ability to allow massign to process a range of values, or an MPE assign
opcode (one that would include the ability to assign a channel as the master
control channel).

massign 2..16, 1

as opposed to:

massign 2, 1
massign 3, 1
...
massign 16, 1

However I believe this would not be good Csound convention, as this would
limit its use. Maybe it would be good to have a new massign2, or mpeassign?

mpeassign ichnl1, ichnl2, isnum[, ireset]

In which ichnl1 is lower midi channel, and ichnl2 is upper midi channel.

Possibly this could just be mmassign (multi-midi-assign)





--
Sent from: http://csound.1045644.n5.nabble.com/Csound-General-f1093014.html

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Date2017-12-12 14:33
From"Dr. Richard Boulanger"
SubjectRe: [Csnd] MPE aftouch opcode
I like the  mpeassign idea. 
- one needs to define a master channel

But also???

Could instr 1.1, 1.2, 1.3, 1.4 play some role?

Sent from my iPhone

> On Dec 12, 2017, at 7:32 AM, alexmitchellmus  wrote:
> 
> Just thought that it may be great if there was a way to use massign for a
> range of midi channels.
> Currently, my understanding is that massign is one channel- per instrument
> number:
> 
> massign 1, 1
> 
> With MPE- we get 15 midi channels, (2-16) so it would be great to either add
> the ability to allow massign to process a range of values, or an MPE assign
> opcode (one that would include the ability to assign a channel as the master
> control channel).
> 
> massign 2..16, 1
> 
> as opposed to:
> 
> massign 2, 1
> massign 3, 1
> ...
> massign 16, 1
> 
> However I believe this would not be good Csound convention, as this would
> limit its use. Maybe it would be good to have a new massign2, or mpeassign?
> 
> mpeassign ichnl1, ichnl2, isnum[, ireset]
> 
> In which ichnl1 is lower midi channel, and ichnl2 is upper midi channel.
> 
> Possibly this could just be mmassign (multi-midi-assign)
> 
> 
> 
> 
> 
> --
> Sent from: http://csound.1045644.n5.nabble.com/Csound-General-f1093014.html
> 
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>        https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here