Re: [Csnd-dev] [EXTERNAL] [Csnd-dev] Opcode Request: k-time versions of notnum and veloc
vlz <[email protected]> Fri, 17 Jul 2026 11:51:37 +0100
| Newsgroups | gmane.comp.audio.csound.devel |
|---|---|
| Message-ID | <[email protected]> |
--Apple-Mail-885C7DE4-722E-4864-9CD3-B46FF7219109 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Isn't that what midiin is for? An UDO would do the trick. notnum and veloc are i-time because they tap into the midi event starting th= e instrument. On the other hand, midiin listens to incoming midi traffic and= reads from it. Internally, it is a different source. If we were to do a per= f pass notnum etc, it would be basically a wrap over midiin. An UDO seems ju= st as appropriate. best Prof. Victor Lazzarini Maynooth University Ireland > On 16 Jul 2026, at 15:31, Arthur Hunkins <000001e1d761dea2-dmarc-request@l= istserv.heanet.ie> wrote: > =EF=BB=BF > Use case: >=20 > For notnum: When pressing a note (via MIDI key, button or pad), an always o= n instrument receives that message and instantiates an event in another inst= rument. >=20 > For veloc: ability to eliminate the above routing when veloc =3D 0. (Other= uses also possible.) >=20 > For both cases, the need for midiin is avoided and coding simplified. >=20 > Rationale: we've long had the k-time flexibility of ctrl7 for pots and sli= ders. We need the same flexibility for buttons, keys and pads. >=20 > Art Hunkins >=20 > [email protected] > http://www.arthunkins.com --Apple-Mail-885C7DE4-722E-4864-9CD3-B46FF7219109 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable <html class=3D"apple-mail-supports-explicit-dark-mode"><head><meta http-equi= v=3D"content-type" content=3D"text/html; charset=3Dutf-8"></head><body dir=3D= "auto"><div dir=3D"ltr"><br class=3D"webkit-block-placeholder"></div><div di= r=3D"ltr">Isn't that what midiin is for? An UDO would do the trick.<div><br>= </div><div>notnum and veloc are i-time because they tap into the midi event s= tarting the instrument. On the other hand, midiin listens to incoming midi t= raffic and reads from it. Internally, it is a different source. If we were t= o do a perf pass notnum etc, it would be basically a wrap over midiin. An UD= O seems just as appropriate.</div><div><div><br></div><div>best<br id=3D"lin= eBreakAtBeginningOfSignature"><div dir=3D"ltr">Prof. Victor Lazzarini<div>Ma= ynooth University</div><div>Ireland</div></div><div dir=3D"ltr"><br><blockqu= ote type=3D"cite">On 16 Jul 2026, at 15:31, Arthur Hunkins <000001e1d761d= [email protected]> wrote:<br><br></blockquote></div><b= lockquote type=3D"cite"><div dir=3D"ltr">=EF=BB=BF <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-1= "> <div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFon= t, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; col= or: rgb(0, 0, 0);"> Use case:</div> <div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFon= t, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; col= or: rgb(0, 0, 0);"> <br> </div> <div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFon= t, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; col= or: rgb(0, 0, 0);"> For notnum: When pressing a note (via MIDI key, button or pad), an always on= instrument receives that message and instantiates an event in another instr= ument.</div> <div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFon= t, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; col= or: rgb(0, 0, 0);"> <br> </div> <div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFon= t, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; col= or: rgb(0, 0, 0);"> For veloc: ability to eliminate the above routing when veloc =3D 0. (Other u= ses also possible.)</div> <div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFon= t, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; col= or: rgb(0, 0, 0);"> <br> </div> <div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFon= t, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; col= or: rgb(0, 0, 0);"> For both cases, the need for midiin is avoided and coding simplified.</div> <div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFon= t, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; col= or: rgb(0, 0, 0);"> <br> </div> <div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFon= t, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; col= or: rgb(0, 0, 0);"> Rationale: we've long had the k-time flexibility of ctrl7 for pots and slide= rs. We need the same flexibility for buttons, keys and pads.</div> <div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFon= t, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; col= or: rgb(0, 0, 0);"> <br> </div> <div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFon= t, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; col= or: rgb(0, 0, 0);"> Art Hunkins</div> <div id=3D"Signature" class=3D"elementToProof"> <div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFon= t, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; col= or: rgb(0, 0, 0);"> <br> </div> <div class=3D"elementToProof" style=3D"font-family: Calibri, Arial, Helvetic= a, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> [email protected]</div> <div class=3D"elementToProof" style=3D"font-family: Calibri, Arial, Helvetic= a, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> http://www.arthunkins.com</div> </div> </div></blockquote></div></div></div></body></html>= --Apple-Mail-885C7DE4-722E-4864-9CD3-B46FF7219109--