Pd-list June 2021

pd-list@lists.iem.at

29 participants
43 discussions

Re [cyclone/MouseState] not working with the Kiosk Plugin on Linux
by Jean-Yves Gratius 04 Jun '21

04 Jun '21

@Ingo Did you try iemguts/receivecanvas ? > Subject: > [PD] [cyclone/MouseState] not working with the Kiosk Plugin on Linux > From: > "Ingo" <ingo(a)miamiwave.com> > Date: > 02/06/2021 Ã 19:11 > > To: > "'Pd list'" <pd-list(a)lists.iem.at> > > > I was wondering if anybody else is having trouble with > [cyclone/MouseState] when the kiosk plugin is running. > > It's not working anymore here with Debian. > > I have made myself an alternative with [hid] but it's not 100% reliable. > > [MouseState] was the only left mouse button recognition that always > worked with absolutely every mouse and touch screen. > > Especially with multiple devices like a mouse and a touch screen at > the same time - there was never a problem. > > With [hid] the mouse is recognized 90-95% of the time but not always. > After unplugging and reconnecting it works. > > When I'm having two devices at the same time chances that one of them > doesn't work after starting up increases. > > I'm monitoring /dev/input/ and see if mouse0 or mouse1 is present and > if yes I check for the hid ID which works perfectly. > > But [hid] sometimes simply doesn't open the mouse. [hid] only works > with the numbers like [open 7(. > > [open mouse( or [open mouse1( or [open mouse 1( does not do anything. > > Does anyone know how to get [cyclone/MouseState] to work with the > kisok plugin? > > Alternatively, is there a button that registers momentary mouse > pressing and releasing with a "1" and "0 "? > > This means not a switch like [toggle] that needs clicking twice for on > / off (1 / 0 )! > > I couldn't find anything. > > I have buttons that change their function when being pressed briefly > or being held for 2 seconds. > > Thanks! > > Ingo >

3 3

Re: [PD] UDP server with Pd
by Dan Wilcox 04 Jun '21

04 Jun '21

You could try a longer connection timeout via the [timeout f( message. The default is 10 seconds, I believe, but maybe it might need more time if hosts take forever to resolve. > On Jun 3, 2021, at 6:00 PM, pd-list-request(a)lists.iem.at wrote: > > Message: 3 > Date: Thu, 03 Jun 2021 14:52:07 +0200 > From: Roman Haefeli <reduzent(a)gmail.com <mailto:reduzent@gmail.com>> > To: pd-list(a)lists.iem.at <mailto:pd-list@lists.iem.at> > Subject: Re: [PD] UDP server with Pd > Message-ID: <d588131641f4e973e59201abc884fc5191cb0e6c.camel(a)gmail.com <mailto:d588131641f4e973e59201abc884fc5191cb0e6c.camel@gmail.com>> > Content-Type: text/plain; charset="utf-8" > > On Tue, 2021-06-01 at 15:27 -0700, Miller Puckette via Pd-list wrote: >> One solution (which the conniption server/client and quacktrip both >> use in somewhat different ways) is for a "netreceive" object to wait >> for an incoming connection and then, once one arrives, immediately to >> close >> its own listening port and for a "nestsend" in the same patch to open >> a connection to the IP and port that the "netreceive" reported (via >> its >> second outlet). It's a bit complicated but gets the job done. > > > Turns out this works for light loads only. For the loads I'm interested > in, the clients get "disconnected". Probably the server is sending an > ICMP notification that the destination port is not ready or something > like that and [netsend -u -b] on the client side terminates the > "connection" (outlet turns zero). > > Roman -------- Dan Wilcox @danomatika <http://twitter.com/danomatika> danomatika.com <http://danomatika.com/> robotcowboy.com <http://robotcowboy.com/>

2 1

Can't compile pyext for Python3, Python.h no such file or directory (was: Re: [PD-announce] Deep Learning Models in Pure Data with pyext for Python 3)
by Alexandros 04 Jun '21

04 Jun '21

I initially replied to Koray's mail under [PD-announce], thought this fits the main mailing list better. I'm trying to build everything as instructed here https://github.com/SopiMlab/DeepLearningWithAudio/blob/master/utilities/pye… Everything is ok until I try to setup pyext. If I type `python build.py` I get this: install: cannot stat 'pd-linux/debug-multi/py.pd_linux': No such file or directory If I go to pyext-setup/py and type `make CPPFLAGS="-I ../flext/source"` I get this: source/pyprefix.h:22:10: fatal error: Python.h: No such file or directory The thing is I have both Python3.8 and Python3.9 header files installed in my system in `/usr/include/python3.8/Python.h` and `/usr/include/python3.9/Python.h` respectively. I'm trying to build the whole deep learning project with Python3.8. How can I solve this issue? I'm on UbuntuStudio 21.04. Thanks

1 0

[cyclone/MouseState] not working with the Kiosk Plugin on Linux
by Ingo 03 Jun '21

03 Jun '21

I was wondering if anybody else is having trouble with [cyclone/MouseState] when the kiosk plugin is running. It's not working anymore here with Debian. I have made myself an alternative with [hid] but it's not 100% reliable. [MouseState] was the only left mouse button recognition that always worked with absolutely every mouse and touch screen. Especially with multiple devices like a mouse and a touch screen at the same time - there was never a problem. With [hid] the mouse is recognized 90-95% of the time but not always. After unplugging and reconnecting it works. When I'm having two devices at the same time chances that one of them doesn't work after starting up increases. I'm monitoring /dev/input/ and see if mouse0 or mouse1 is present and if yes I check for the hid ID which works perfectly. But [hid] sometimes simply doesn't open the mouse. [hid] only works with the numbers like [open 7(. [open mouse( or [open mouse1( or [open mouse 1( does not do anything. Does anyone know how to get [cyclone/MouseState] to work with the kisok plugin? Alternatively, is there a button that registers momentary mouse pressing and releasing with a "1" and "0 "? This means not a switch like [toggle] that needs clicking twice for on / off (1 / 0 )! I couldn't find anything. I have buttons that change their function when being pressed briefly or being held for 2 seconds. Thanks! Ingo

2 5

Re: [PD] pyext for Python3 (was: Re: [PD-announce] Deep Learning Models in Pure Data with pyext for Python 3
by Koray Tahiroğlu 03 Jun '21

03 Jun '21

Hi IOhannes, It has been long time, I was hoping to see you this July during AIMC, but that will be another remote conference this year. Yes it is the proper way to do, contributing to the Thomas’s original repository directly, when we were preparing the Deep Learning with Audio course materials, it was necessary to fork the main models and setup dependencies, just not to deal with last minute things during the course and to make sure all the exercises will work. Pyext was one of them, same as DDSP, Magenta and others. We also create conda environment to make all the necessary setup, build and installations, the announcement is just to make this work available if anyone needs pyext for Python 3. I have discussed earlier with Thomas before we started working on this, about the Python 3 version, bu now, if possible, it would be great to keep everything under the original pyext. best, Koray ------------------------------------- M.Koray Tahiroğlu Department of Media, Aalto University School of Arts, Design and Architecture http://sopi.aalto.fi/ http://dmi.aalto.fi/ https://sopi.aalto.fi/koraytahiroglu/ > > > Date: Thu, 03 Jun 2021 11:01:00 +0200 > From: IOhannes m zm?lnig <zmoelnig(a)iem.at> > To: pd-list(a)lists.iem.at > Subject: [PD] pyext for Python3 (was: Re: [PD-announce] Deep Learning > Models in Pure Data with pyext for Python 3) > Message-ID: <EB677F63-7FC4-4A2B-BCC6-EB308AF5726F(a)iem.at> > Content-Type: text/plain; charset="utf-8" > > Hi Koray, > > good to hear you are still alive and kicking. > > > Am 3. Juni 2021 05:42:00 MESZ schrieb "Koray Tahiro?lu" <koray.tahiroglu(a)gmail.com>: >> >> We have also developed the pyext external to support Python 3, > > that is fantastic. > >> >> Here it is the link to the SOPI fork of pyext. >> >> https://github.com/SopiMlab/py >> >> > > but i'm sorely missing the pull-request against https://github.com/grrrr/py > > my understanding is, that thomas is happily accepting PRs for py3 support, so i dont understand the need to announce a separate fork. > > mfg.ezf.xhe > IOhannes > -- > Diese Nachricht wurde von meinem Android-Ger?t mit K-9 Mail gesendet. >

1 0

UDP server with Pd
by Roman Haefeli 03 Jun '21

03 Jun '21

Hey all I would like to open a datagram listening socket and be able to send back to clients from which I received messages. It seems both [netsend -u] and (obviously) [netreceive -u] actually can open a listening socket. However, [netreceive -u] can't send anything back. While [netsend -u] can send messages back, it doesn't show the source address of the incoming packets. And using [netreceive -u] for receiving and [netsend -u] for sending back doesn't work, because for the packets to arrive at the client, they need to be sent from the same port that is already occupied by [netreceive]. Yet, as long as I used TCP and iemnet, this was possible. However, as far as I can tell, it's not possible with UDP, neither with iemnet nor with Pd's built-in classes. Is that something worth to make a feature request for? While we're at it, it seems [netreceive] (in TCP mode) can only send back to all connected clients, but not to a specific one. Roman

4 6

Re: [PD] UDP server with Pd
by Roman Haefeli 03 Jun '21

03 Jun '21

(replying to list as - I believe - you intended to) On Wed, 2021-06-02 at 09:34 -0400, Martin Peach wrote: > On Wed, Jun 2, 2021 at 3:31 AM Roman Haefeli <reduzent(a)gmail.com> > wrote: > > On Tue, 2021-06-01 at 19:19 -0400, Martin Peach wrote: > > > A [udpsend] normally has a different port number to the one it > > > sends > > > to, but a [udpreceive] in the same Pd process can still receive > > > on > > > that port. > > > > My understanding is that a client won't accept messages with a > > different source port than it has sent to. Also, such packets > > wouldn't > > be able to traverse NAT firewalls. > > > > A udp packet almost always has a different source port from its > destination. It's not the same as TCP as there is no real > "connection" > established or maintained, it's just fire and forget. I modified the > udp objects in response to a request to do just that: send back to > the > same port. You're absolutely right. I think my wording was not clear. Sorry for that. When a client with bind port 52333 sends a packet to the server listening on port 5000, it won't accept response packets from the server with (matching) destination port 52333 and (different) source port 5001. [udpsend] on the server side cannot use bind_port=5000, because it is already used by [udpreceive]. And from what I see in the documentation, [udpsend] doesn't support setting a bind port, it seems to pick a random one (which is the normal thing to do when acting as a client, but not sufficient for a server response to a client request). So, I believe my goal can (so far) only be achieved with [netsend -u]/[netreice -u] as Miller suggested. Mission accomplished. Roman

3 5

Re: [PD] Pd FLOSS Manual, what to do with it?
by ol＠ogeem.be 02 Jun '21

02 Jun '21

hello, concerning the french version : I was part of it back in 2011, and still have access, the organisation that manage the french FLOSS manuals and actively organized booksprints to write them is still active also ( https://activdesign.eu/ ) at the time, given the context and potential public for the book (which is also available on paper) we did a complete rewrite of the manual, including context history and explanation of use case so newcomers in the "creative interactive media creation" could jump in. the french manual while proposing (at the time) to install pd-extended for beginners, does not make a hard choice and is focusing on the basis of the tool, talking about the different libraries independently of the way it has been installed (namely GEM, PDP, Pduino, OSC) in a progressive manner (compared to the english one which is more a technical reference) as we also took into account the fact that each object has a help patch. (which should be translated somewhere ... ?) it is indeed outdated for the installation parts (and it's mention of pd-extended that should be replaced by an article about deken) but still mostly relevant for the most part (I still use it to teach the basics) Like for the articles on Wikipedia, I'm not sure there need to have 1/1 correspondence between languages ... but maybe the english one could take inspiration on the french one for it's structure this is quite a job to make a revision and translate it, not sure when I could put time on it, but it's indeed time we look at it again collectively ;) best, Olm-e > > there's also yet another link here which seems to refer to the same > content > of the new incarnation of the manual > http://write.flossmanuals.net/pure-data/introduction2/ > > why? dear god, why? > > Em seg., 31 de mai. de 2021 ?s 18:07, Alexandre Torres Porres < > porres(a)gmail.com> escreveu: > >> Em seg., 31 de mai. de 2021 ?s 07:35, Dan Wilcox >> <danomatika(a)gmail.com> >> escreveu: >> >>> I agree. I think the current Pd-extended focused manual could be >>> moved to >>> a Pd-extended location for historical reasons. >>> >> >> what's a "pd-extended location" and where is it? >> >> >>> The "main" Pd FLOSS manual should be Vanilla + links or sections to >>> active forks including the original Pd-extended manual. The current >>> manual >>> could then be refactored/updated and existing links would not be >>> *terribly* >>> broken. >>> >> >> It has now come to my attention that we have different versions of >> this >> manual. There's an archived version => >> http://archive.flossmanuals.net/pure-data/ >> >> And a new version created two months ago by 'mickfuzz' which is >> actually >> the same! https://en.flossmanuals.net/pure-data - The Pd Vanila html >> manual references to this link, by the way, and also to a french >> version >> here: https://fr.flossmanuals.net/puredata/introduction/ >> >> Note that the french version is considerably different, so yeah, we >> have >> quite some chaos... there are two versions somehow, different and >> independent unofficial takes on what a Pd manual is and should be and >> depending on what language you speak you get a different idea and >> information? :) >> >> Well, I'd love to help sort things out, but I don't know where to >> start, >> it's all decentralized in a very messy way. >> >> We need to coordinate the efforts if anything is to be done. I speak >> no >> french, for instance >> >> Where are the floss manuals people anyway? Who is 'mickfuzz'? Who's >> working on the french version? >> >> How could I get involved in the english one? >> >> Thanks >>

4 4

Re: [PD] UDP server with Pd
by Philip Stone 02 Jun '21

02 Jun '21

I hope I’m not butting in where I have no business, but I’d like to mention that Ross Bencina’s ‘OSCGroups’ (http://www.rossbencina.com/code/oscgroups) does an excellent job of handling group formation, broadcast and NAT tunneling. Our group has been using it for over fifteen years, and it’s as solid as a rock. It may not be Pd-native, but it does the job extremely well. Best, Phil Stone Davis, CA From: Christof Ressi <info(a)christofressi.com> To: Pd-List <pd-list(a)lists.iem.at> Subject: Re: [PD] UDP server with Pd Message-ID: <06b68c67-a27e-81d8-4b6e-5b60db9436c5(a)christofressi.com> Content-Type: text/plain; charset="utf-8"; Format="flowed" If you want the server to reply only to the current client, [iemnet/udpserver] actually works fine (despite the error message in the console): the list method will send the packet to the source address of the most recently received packet. However, if you need to send packets to several/all registered clients, e.g. like a game server, this doesn't work (yet). Christof On 02.06.2021 08:54, Roman Haefeli wrote: > On Tue, 2021-06-01 at 15:27 -0700, Miller Puckette via Pd-list wrote: >> One solution (which the conniption server/client and quacktrip both >> use in somewhat different ways) is for a "netreceive" object to wait >> for an incoming connection and then, once one arrives, immediately to >> close >> its own listening port and for a "nestsend" in the same patch to open >> a connection to the IP and port that the "netreceive" reported (via >> its >> second outlet). It's a bit complicated but gets the job done. > That absolutely works. And since that can be done in zero logical time, > [netsend] doesn't claim any packets coming in on the port "shared" > with [netreceive]. Cheers to Pd's determinism! > > That opens up an a lot of new things to explore for me. Thanks! > > Roman > > _______________________________________________ > Pd-list(a)lists.iem.at mailing list > UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list

1 0

Re: [PD] Binaural w32?
by Dan Wilcox 02 Jun '21

02 Jun '21

I updated the earplug~ external to build using pd-lin-builder, so it should be easy to build on Windows: https://github.com/pd-externals/earplug/tree/main <https://github.com/pd-externals/earplug/tree/main> It's not the best but we use it for a project at work. It can use some additional optimizations and the dataset is for 44.1k so you are in luck. For our project, we are likely to introduce resampling for other sample rates so it's more accurate beyond 44.1k... > On Jun 2, 2021, at 12:06 AM, pd-list-request(a)lists.iem.at wrote: > > Message: 2 > Date: Tue, 1 Jun 2021 14:12:23 +0100 > From: Jo?o Pais <jmmmpais(a)gmail.com <mailto:jmmmpais@gmail.com>> > To: PD-List <pd-list(a)lists.iem.at <mailto:pd-list@lists.iem.at>> > Subject: [PD] Binaural w32? > Message-ID: <ef02d682-c394-1622-2787-a7de210f1d75(a)gmail.com <mailto:ef02d682-c394-1622-2787-a7de210f1d75@gmail.com>> > Content-Type: text/plain; charset=utf-8; format=flowed > > Hi list, > > what is the current state of the art in binaural externals? I see in the > archives that there are several around, each with advantages/disadvantages. > > I would need it to: > > - windows 32b > > - record the output of an already existing patch with x-y > coordinates/trajectories into binaural audio > > - sample rate fixed at 44.1KHz > > - there are around 500 samples with an individual player, so each will > need its own enconder. They don't play necessarily all together, though. > > Best, > > Joao -------- Dan Wilcox @danomatika <http://twitter.com/danomatika> danomatika.com <http://danomatika.com/> robotcowboy.com <http://robotcowboy.com/>

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

Pd-list June 2021