Re: [PD] vstplugin~ v0.1.0 - NOTE for Windows users

[Lucas Cordiviola]

Thanks!

Confirmed, Deken versions dated "2019-03-15" are working Ok :


vstplugin~[v0.1.0](Windows-i386-32).dek
     Uploaded by spacechild1 @ 2019-03-15 14:04:09


vstplugin~[v0.1.0](Windows-amd64-32).dek
     Uploaded by spacechild1 @ 2019-03-15 14:03:10


:)

Mensaje telepatico asistido por maquinas.

On 3/15/2019 10:11 AM, Christof Ressi wrote:
> in the end, I just had to modify the build system. since there are no changes 
> in the actual source code, I just uploaded the new binaries to Deken (will be 
> available tomorrow). I've tested with Lucas, who reported the problem, and 
> the problem is resolved. I won't touch v0.1.0 from now on.
>
> Christof
>
>> Gesendet: Freitag, 15. März 2019 um 05:18 Uhr
>> Von: "Christof Ressi" 
>> An: Pd-List 
>> Betreff: [PD] vstplugin~ v0.1.0 - NOTE for Windows users
>>
>> due to an oversight by me, opening VST plugins won't work if you don't have 
>> Pd in your PATH (probe.exe will crash)! also, make sure to open Pd from 
>> pd.exe and not by double clicking a patch file.
>>
>> I will fix this as soon as possible and make a bugfix release! (the fix is 
>> trivial but I can't do it right now.)
>>
>>> Gesendet: Freitag, 15. März 2019 um 01:59 Uhr
>>> Von: "Christof Ressi" 
>>> An: pd-l...@iem.at
>>> Betreff: Re: [PD] [PD-announce] vstplugin~ v0.1.0 released!
>>>
>>> if possible, please report any bugs on the issue tracker: 
>>> https://git.iem.at/pd/vstplugin/issues (needs a GitHub or Gmail account)
>>>
 Gesendet: Freitag, 15. März 2019 um 01:30 Uhr
 Von: "Christof Ressi" 
 An: pd-annou...@lists.iem.at
 Betreff: [PD] [PD-announce] vstplugin~ v0.1.0 released!

 I'm happy to announce the first stable release of vstplugin~! Binaries are 
 already available on Deken.

 Source code: https://git.iem.at/pd/vstplugin/tree/master

 The repository also includes a version for Supercollider called VSTPlugin 
 (which works very differently but achieves the same thing).

 The overall design and functionality of vstplugin~ v0.1.0 is the same as 
 in vstplugin~ v0.1-alpha, but there are some breaking changes and new 
 features! Have a look at the change log in 
 https://git.iem.at/pd/vstplugin/releases

 Have fun!

 Christof





 ___
 Pd-announce mailing list
 pd-annou...@lists.iem.at
 https://lists.puredata.info/listinfo/pd-announce
 ___
 Pd-list@lists.iem.at mailing list
 UNSUBSCRIBE and account-management -> 
 https://lists.puredata.info/listinfo/pd-list

>>>
>>>
>>> ___
>>> Pd-list@lists.iem.at mailing list
>>> UNSUBSCRIBE and account-management -> 
>>> https://lists.puredata.info/listinfo/pd-list
>>>
>>
>>
>> ___
>> Pd-list@lists.iem.at mailing list
>> UNSUBSCRIBE and account-management -> 
>> https://lists.puredata.info/listinfo/pd-list
>>
>
>
> ___
> Pd-list@lists.iem.at mailing list
> UNSUBSCRIBE and account-management -> 
> https://lists.puredata.info/listinfo/pd-list
___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
https://lists.puredata.info/listinfo/pd-list

Re: [PD] added libs on deken

[Lucas Cordiviola]

Cool,

They are up on Deken.

:)

Mensaje telepatico asistido por maquinas.

On 3/15/2019 5:34 AM, cyrille henry wrote:
> hello Lucas,
>
> thanks for the commpilation,
> yes, please, you can put then on deken.
>
> cheers
>
>
> Le 14/03/2019 à 21:37, Lucas Cordiviola a écrit :
>> Hi Cyrille,
>>
>> Thanks for the libs!
>>
>> I have compiled them for Windows-64-bits. It was very straight-forward
>> using pd-lib-builder + msys2 + MinGW64.
>>
>> Here's a preview (sources included):
>>
>> http://lucarda.com.ar/x/pre-deken-chenry-w64-libs.zip
>>
>> Most are tested and working. I even tried the pmpd examples with
>> "Gem/0.94~pre1 (deken-archive for Windows 64bit)" and they are 
>> working. :)
>>
>> Is it OK if I upload them to Deken?
>>
>>
>> Mensaje telepatico asistido por maquinas.
>>
>> On 3/13/2019 6:54 AM, cyrille henry wrote:
>>> Hello everyone,
>>>
>>> I'm sorry not to be active anymore on this list, I'm still using pd
>>> very regularly, but I don't have time anymore to interact with other
>>> pd user.
>>> Anyway, I finally manage to have a few spare time to upload my library
>>> to deken. (should be searchable in 24h according to deken log)
>>>
>>> this libs are :
>>> - pmpd : one of the 1st (maybe the 1st) open source, generic,
>>> particular based, physical modelling library. It was developed more
>>> than 15 years ago, major update was made 10 years ago. Nowadays,
>>> development is mostly inactive, not because this lib is abandoned, but
>>> because it do everything I want it to do. It is efficient, stable and
>>> well documented.
>>>
>>> - shmem : an object and abstractions allowing to share data (table)
>>> between multiple pd instances. This is very useful to share large data
>>> between pd and pd~. It can also be used to share audio faster than
>>> using a dac~ in the pd~ instance.
>>>
>>> - nusmuk-audio : a collection of various audio abstraction and
>>> externals I made over the years : band limited oscillators, filters
>>> with audio coefficient, audio table reader with better interpolation,
>>> etc.
>>>
>>> - nusmuk-utils : various abstractions that I use regularly, nothing
>>> very interesting except for the line3 object. [line3] is just like
>>> [line] but the output allow continuity of the derivative. You can
>>> replace [line] with [line3] to have a less robotic and more natural 
>>> fell.
>>>
>>> - puremapping (it was already uploaded by Antoine so I did not added
>>> it) : is a collection of object dedicated to mapping data values.
>>>
>>> This is nothing new for old pd users, but others may have missed this
>>> libs.
>>>
>>> cheers,
>>> Cyrille
>>>
>>>
>>>
>>> ___
>>> Pd-list@lists.iem.at mailing list
>>> UNSUBSCRIBE and account-management ->
>>> https://lists.puredata.info/listinfo/pd-list
>> ___
>> Pd-list@lists.iem.at mailing list
>> UNSUBSCRIBE and account-management -> 
>> https://lists.puredata.info/listinfo/pd-list
>>
>
>
>
> ___
> Pd-list@lists.iem.at mailing list
> UNSUBSCRIBE and account-management -> 
> https://lists.puredata.info/listinfo/pd-list
___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
https://lists.puredata.info/listinfo/pd-list

[PD] PdParty and externals like Cyclone

[Alexandre Torres Porres]

Em sex, 22 de fev de 2019 às 07:03, Dan Wilcox 
escreveu:

> Congrats!
>
> Cyclone is an important library and it's great to see its continuation.
> This has been a learning experience for all but it is now success story of
> the post-extended "deken model." If/when I'm teaching Pd in the future, I
> will most likely be piggy-backing off of this work as Cyclone and your new
> tutorials are a great entry point for both beginners and people coming from
> Max.
>

Thanks Dan! That'd be an honor ;)

I've been meaning to ask you. Now that we seem to be able to compile
cyclone for libpd, could we use it with "PdParty". I don't own a smartphone
so I'm pretty clueless on this deal, but I'm curious and would like to know
what's up with that

Cheers
___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
https://lists.puredata.info/listinfo/pd-list

[PD] [PD-announce] jmmmp library Version 0.52

[João Pais]

Hello everyone,

The jmmmp library of abstractions has been updated.

A small bug in Granulator, a Pure Data port of Robert Henke's Granulator,
has been fixed. (Also some aesthetic details in the mat~ object collection)

You can download it soon through deken, or follow the link below.

For more informations and a tarball file, visit http://bit.ly/jmmmp_052

Best,

João Pais
___
Pd-announce mailing list
pd-annou...@lists.iem.at
https://lists.puredata.info/listinfo/pd-announce
___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
https://lists.puredata.info/listinfo/pd-list

Re: [PD] vstplugin~ v0.1.0 - NOTE for Windows users

[Christof Ressi]

in the end, I just had to modify the build system. since there are no changes 
in the actual source code, I just uploaded the new binaries to Deken (will be 
available tomorrow). I've tested with Lucas, who reported the problem, and the 
problem is resolved. I won't touch v0.1.0 from now on.

Christof

> Gesendet: Freitag, 15. März 2019 um 05:18 Uhr
> Von: "Christof Ressi" 
> An: Pd-List 
> Betreff: [PD] vstplugin~ v0.1.0 - NOTE for Windows users
>
> due to an oversight by me, opening VST plugins won't work if you don't have 
> Pd in your PATH (probe.exe will crash)! also, make sure to open Pd from 
> pd.exe and not by double clicking a patch file. 
> 
> I will fix this as soon as possible and make a bugfix release! (the fix is 
> trivial but I can't do it right now.)
> 
> > Gesendet: Freitag, 15. März 2019 um 01:59 Uhr
> > Von: "Christof Ressi" 
> > An: pd-l...@iem.at
> > Betreff: Re: [PD] [PD-announce] vstplugin~ v0.1.0 released!
> >
> > if possible, please report any bugs on the issue tracker: 
> > https://git.iem.at/pd/vstplugin/issues (needs a GitHub or Gmail account)
> > 
> > > Gesendet: Freitag, 15. März 2019 um 01:30 Uhr
> > > Von: "Christof Ressi" 
> > > An: pd-annou...@lists.iem.at
> > > Betreff: [PD] [PD-announce] vstplugin~ v0.1.0 released!
> > >
> > > I'm happy to announce the first stable release of vstplugin~! Binaries 
> > > are already available on Deken.
> > > 
> > > Source code: https://git.iem.at/pd/vstplugin/tree/master
> > > 
> > > The repository also includes a version for Supercollider called VSTPlugin 
> > > (which works very differently but achieves the same thing).
> > > 
> > > The overall design and functionality of vstplugin~ v0.1.0 is the same as 
> > > in vstplugin~ v0.1-alpha, but there are some breaking changes and new 
> > > features! Have a look at the change log in 
> > > https://git.iem.at/pd/vstplugin/releases
> > > 
> > > Have fun!
> > > 
> > > Christof
> > > 
> > > 
> > > 
> > > 
> > > 
> > > ___
> > > Pd-announce mailing list
> > > pd-annou...@lists.iem.at
> > > https://lists.puredata.info/listinfo/pd-announce
> > > ___
> > > Pd-list@lists.iem.at mailing list
> > > UNSUBSCRIBE and account-management -> 
> > > https://lists.puredata.info/listinfo/pd-list
> > >
> > 
> > 
> > 
> > ___
> > Pd-list@lists.iem.at mailing list
> > UNSUBSCRIBE and account-management -> 
> > https://lists.puredata.info/listinfo/pd-list
> >
> 
> 
> 
> ___
> Pd-list@lists.iem.at mailing list
> UNSUBSCRIBE and account-management -> 
> https://lists.puredata.info/listinfo/pd-list
>



___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
https://lists.puredata.info/listinfo/pd-list

Re: [PD] In 2019 is there a way to detect mouse down/up?

[Dan Wilcox]

I would use #mouse to match the internal send names like #notein, etc. :)

Actually, you can receive messages to [notein] using [r #notein] so I could 
imagine a similar set of mouse objects which work in the same manner ala 
[mouseup], [mousedown], [mousemove], & possibly [mousedrag]. We can look into 
the code on those objects and replicate how they work to avoid the missing 
receiver name.

Honestly, this should be something built in however I would first make sure 
there isn't any sort of major performance penalty (probably not). Chris's 
comment about "in 2019" is spot on...

> On Mar 15, 2019, at 11:06 AM, pd-list-requ...@lists.iem.at wrote:
> 
> From: Jean-Yves Gratius mailto:j...@gumo.fr>>
> To: pd-list@lists.iem.at 
> Subject: Re: [PD] In 2019 is there a way to detect mouse down/up?
> Message-ID:  >
> Content-Type: text/plain; charset="utf-8"; Format="flowed"
> 
> Not sure it can be considered as a vanilla solution, but you should edit 
> tcl/pdtk_canvas.tcl file and add one line in the proc 
> pdtk_canvas_mouseup (line 216) :
> 
> proc pdtk_canvas_mouseup {tkcanvas x y b} {
> set mytoplevel [winfo toplevel $tkcanvas]
> pdsend "$mytoplevel mouseup [$tkcanvas canvasx $x] [$tkcanvas 
> canvasy $y] $b"
> pdsend "MOUSE mouseup [$tkcanvas canvasx $x] [$tkcanvas canvasy $y] $b"
> }
> (see attachment)
> 
> Then you'll always need to have a receiver (named "MOUSE") in your 
> patch, else you will receive error messages in pd console.
> If you click on a bang object in your patch, you can then listen to the 
> MOUSE receiver and wait for the message "mouseup"


Dan Wilcox
@danomatika 
danomatika.com 
robotcowboy.com 



___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
https://lists.puredata.info/listinfo/pd-list

Re: [PD] In 2019 is there a way to detect mouse down/up?

[Christof Ressi]

It's the pointer value printed as hex, so it will change (most likely :-)

> Gesendet: Freitag, 15. März 2019 um 10:49 Uhr
> Von: "Peter P." 
> An: pd-list@lists.iem.at
> Betreff: Re: [PD] In 2019 is there a way to detect mouse down/up?
>
> * Liam Goodacre  [2019-03-15 10:45]:
> > You can receive mouse and mouseup information in Vanilla by using [receive 
> > .x55dca8289140], where ".x55dca8289140" is a hexadecimal ID unique to the 
> > given canvas. However, the only way I know of retrieving that ID is using 
> > [hcs/canvasname], which is back to using externals.
> Good information, thanks Liam! Does the Canvas ID change when re-opening
> the patch or will it remain the same "forever"?
> 
> 
> 
> ___
> Pd-list@lists.iem.at mailing list
> UNSUBSCRIBE and account-management -> 
> https://lists.puredata.info/listinfo/pd-list
>



___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
https://lists.puredata.info/listinfo/pd-list

Re: [PD] In 2019 is there a way to detect mouse down/up?

[Jean-Yves Gratius]

Not sure it can be considered as a vanilla solution, but you should edit 
tcl/pdtk_canvas.tcl file and add one line in the proc 
pdtk_canvas_mouseup (line 216) :


proc pdtk_canvas_mouseup {tkcanvas x y b} {
    set mytoplevel [winfo toplevel $tkcanvas]
    pdsend "$mytoplevel mouseup [$tkcanvas canvasx $x] [$tkcanvas 
canvasy $y] $b"

    pdsend "MOUSE mouseup [$tkcanvas canvasx $x] [$tkcanvas canvasy $y] $b"
}
(see attachment)

Then you'll always need to have a receiver (named "MOUSE") in your 
patch, else you will receive error messages in pd console.
If you click on a bang object in your patch, you can then listen to the 
MOUSE receiver and wait for the message "mouseup"


On 14/03/2019 13:32, Fede Camara Halac wrote:

Not the best solution, but you may be able to monitor a slider for value 
changes to emulate a click-down, click-up situation... so you'd be tricking a 
click-drag :)


fdch.github.io


On Mar 14, 2019, at 11:02 AM, IOhannes m zmoelnig  wrote:


On 14.03.19 10:42, Chris McCormick wrote:


keep in mind that it is not touch sensitive.

What do you mean by this? It only responds to mouse events and not touch
events?

no. that's not what i meant.

it was a(n admittedly stupid) joke on the discrepancy between a
mouse-based interface (where you only get a boolean value of whether a
button is clicked or not) and the expectation of a (musical) "hardware
keyboard" that typically gives you "touch sensitive" data in the form of
'velocity'.

fgamsdr
IOhannes


___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
https://lists.puredata.info/listinfo/pd-list







package provide pdtk_canvas 0.1

package require pd_bindings

namespace eval ::pdtk_canvas:: {
namespace export pdtk_canvas_popup
namespace export pdtk_canvas_editmode
namespace export pdtk_canvas_getscroll
namespace export pdtk_canvas_setparents
namespace export pdtk_canvas_reflecttitle
namespace export pdtk_canvas_menuclose
}

# store the filename associated with this window,
# so we can use it during menuclose
array set ::pdtk_canvaswindow_fullname {}

# One thing that is tricky to understand is the difference between a Tk
# 'canvas' and a 'canvas' in terms of Pd's implementation.  They are similar,
# but not the same thing.  In Pd code, a 'canvas' is basically a patch, while
# the Tk 'canvas' is the backdrop for drawing everything that is in a patch.
# The Tk 'canvas' is contained in a 'toplevel' window. That window has a Tk
# class of 'PatchWindow'.

# TODO figure out weird frameless window when you open a graph


#TODO: http://wiki.tcl.tk/11502
# MS Windows
#wm geometry . returns contentswidthxcontentsheight+decorationTop+decorationLeftEdge.
#and
#winfo rooty . returns contentsTop
#winfo rootx . returns contentsLeftEdge

if {$::tcl_version < 8.5 || \
($::tcl_version == 8.5 && \
 [tk windowingsystem] eq "aqua" && \
 [lindex [split [info patchlevel] "."] 2] < 13) } {
# fit the geometry onto screen for Tk 8.4,
# also check for Tk Cocoa backend on macOS which is only stable in 8.5.13+;
# newer versions of Tk can handle multiple monitors so allow negative pos
proc pdtk_canvas_wrap_window {x y w h} {
set width [lindex [wm maxsize .] 0]
set height [lindex [wm maxsize .] 1]

if {$w > $width} {
set w $width
set x 0
}
if {$h > $height} {
# 30 for window framing
set h [expr $height - $::menubarsize - $::windowframey]
set y $::menubarsize
}

set x [ expr $x % $width]
set y [ expr $y % $height]
if {$x < 0} {set x 0}
if {$y < 0} {set y 0}

return [list ${x} ${y} ${w} ${h}]
}
} {
proc pdtk_canvas_wrap_window {x y w h} {
return [list ${x} ${y} ${w} ${h}]
}
}

# this proc is split out on its own to make it easy to override. This makes it
# easy for people to customize these calculations based on their Window
# Manager, desires, etc.
proc pdtk_canvas_place_window {width height geometry} {
::pdwindow::configure_window_offset

# read back the current geometry +posx+posy into variables
scan $geometry {%[+]%d%[+]%d} - x - y
set xywh [pdtk_canvas_wrap_window \
[expr $x - $::windowframex] [expr $y - $::windowframey] $width $height]
set x [lindex $xywh 0]
set y [lindex $xywh 1]
set w [lindex $xywh 2]
set h [lindex $xywh 3]
return [list ${w} ${h} ${w}x${h}+${x}+${y}]
}


#--#
# canvas new/saveas

proc pdtk_canvas_new {mytoplevel width height geometry editable} {
set l [pdtk_canvas_place_window $width $height $geometry]
set width [lindex $l 0]
set height [lindex $l 1]
set geometry [lindex $l 2]
set ::undo_actions($mytoplevel) no
set ::redo_actions($mytoplevel) no

# release the window grab here so that the 

Re: [PD] In 2019 is there a way to detect mouse down/up?

[Peter P.]

* Liam Goodacre  [2019-03-15 10:45]:
> You can receive mouse and mouseup information in Vanilla by using [receive 
> .x55dca8289140], where ".x55dca8289140" is a hexadecimal ID unique to the 
> given canvas. However, the only way I know of retrieving that ID is using 
> [hcs/canvasname], which is back to using externals.
Good information, thanks Liam! Does the Canvas ID change when re-opening
the patch or will it remain the same "forever"?



___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
https://lists.puredata.info/listinfo/pd-list

Re: [PD] In 2019 is there a way to detect mouse down/up?

[Liam Goodacre]

You can receive mouse and mouseup information in Vanilla by using [receive 
.x55dca8289140], where ".x55dca8289140" is a hexadecimal ID unique to the given 
canvas. However, the only way I know of retrieving that ID is using 
[hcs/canvasname], which is back to using externals.

If you accept externals then [iemguts/receivecanvas] is definitely the best way 
to go.

From: Pd-list  on behalf of Jos? de Abreu 

Sent: 14 March 2019 12:38
To: Fede Camara Halac
Cc: pd-list@lists.iem.at
Subject: Re: [PD] In 2019 is there a way to detect mouse down/up?

hid can receive mouse information? isn't a vanilla solution, but i'm curious

Em Qui, 14 de mar de 2019 09:33, Fede Camara Halac 
mailto:camaraf...@gmail.com>> escreveu:
Not the best solution, but you may be able to monitor a slider for value 
changes to emulate a click-down, click-up situation... so you'd be tricking a 
click-drag :)


fdch.github.io

> On Mar 14, 2019, at 11:02 AM, IOhannes m zmoelnig 
> mailto:zmoel...@iem.at>> wrote:
>
>> On 14.03.19 10:42, Chris McCormick wrote:
>>
>>> keep in mind that it is not touch sensitive.
>>
>> What do you mean by this? It only responds to mouse events and not touch
>> events?
>
> no. that's not what i meant.
>
> it was a(n admittedly stupid) joke on the discrepancy between a
> mouse-based interface (where you only get a boolean value of whether a
> button is clicked or not) and the expectation of a (musical) "hardware
> keyboard" that typically gives you "touch sensitive" data in the form of
> 'velocity'.
>
> fgamsdr
> IOhannes
>
>
> ___
> Pd-list@lists.iem.at mailing list
> UNSUBSCRIBE and account-management -> 
> https://lists.puredata.info/listinfo/pd-list



___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
https://lists.puredata.info/listinfo/pd-list
___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
https://lists.puredata.info/listinfo/pd-list

Re: [PD] added libs on deken

[cyrille henry]

hello Lucas,

thanks for the commpilation,
yes, please, you can put then on deken.

cheers


Le 14/03/2019 à 21:37, Lucas Cordiviola a écrit :

Hi Cyrille,

Thanks for the libs!

I have compiled them for Windows-64-bits. It was very straight-forward
using pd-lib-builder + msys2 + MinGW64.

Here's a preview (sources included):

http://lucarda.com.ar/x/pre-deken-chenry-w64-libs.zip

Most are tested and working. I even tried the pmpd examples with
"Gem/0.94~pre1 (deken-archive for Windows 64bit)" and they are working. :)

Is it OK if I upload them to Deken?


Mensaje telepatico asistido por maquinas.

On 3/13/2019 6:54 AM, cyrille henry wrote:

Hello everyone,

I'm sorry not to be active anymore on this list, I'm still using pd
very regularly, but I don't have time anymore to interact with other
pd user.
Anyway, I finally manage to have a few spare time to upload my library
to deken. (should be searchable in 24h according to deken log)

this libs are :
- pmpd : one of the 1st (maybe the 1st) open source, generic,
particular based, physical modelling library. It was developed more
than 15 years ago, major update was made 10 years ago. Nowadays,
development is mostly inactive, not because this lib is abandoned, but
because it do everything I want it to do. It is efficient, stable and
well documented.

- shmem : an object and abstractions allowing to share data (table)
between multiple pd instances. This is very useful to share large data
between pd and pd~. It can also be used to share audio faster than
using a dac~ in the pd~ instance.

- nusmuk-audio : a collection of various audio abstraction and
externals I made over the years : band limited oscillators, filters
with audio coefficient, audio table reader with better interpolation,
etc.

- nusmuk-utils : various abstractions that I use regularly, nothing
very interesting except for the line3 object. [line3] is just like
[line] but the output allow continuity of the derivative. You can
replace [line] with [line3] to have a less robotic and more natural fell.

- puremapping (it was already uploaded by Antoine so I did not added
it) : is a collection of object dedicated to mapping data values.

This is nothing new for old pd users, but others may have missed this
libs.

cheers,
Cyrille



___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management ->
https://lists.puredata.info/listinfo/pd-list

___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
https://lists.puredata.info/listinfo/pd-list





___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
https://lists.puredata.info/listinfo/pd-list