Re: [PD] Patch2Svg exports controlled in a pd patch

[IOhannes m zmölnig]

On 6/7/21 15:38, boscomac wrote:

Hi List,

I recently discovered this Patch2Svg add-on. It works perfectly (mac os mojave, 
Pd 0.50-2).

Working with data structures, I generate many serial drawings that I export to 
Svg.
Basically, I export my Pd-data sub-patch which contains the graphical display 
only.

I would like to know if there is a way to control and serialize this export 
operation directly in the Pd patch?
Something like [write $1.svg( message, as it can be done with an array, audio 
recording, txt file, etc.


in the patch2svg-plugin folder you find an "autoexport.pd" abstraction, 
that will export all currently open canvases as an SVG - and then quit 
Pd (the idea was to use this in a script).


the filenames are created automatically based on the canvas title and 
the window-id. (this is somehow tweakable - but not very much).


it's hard to provide anything more sophisticated without also writing an 
accompanying external (which needs to be compiled for all the archs) - i 
don't think this is worth it.


fmsard
IOhannes


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

Re: [PD] UDP server with Pd

[Roman Haefeli]

On Mon, 2021-06-07 at 16:57 -0400, Martin Peach wrote:
> So I changed it to use sendto and it works a lot better. It receives
> from multiple clients while sending to any one.
> I added a [to ( message to set the destination, and removed the
> [connect( and [disconnect{ methods.
> Thanks Christof for the critique!.

Seems to work as advertised! I find the interface with a 'to' method
makes sense.

I will do some more extensive test with some more load.

Great! Thanks for your effort!

Roman



signature.asc
Description: This is a digitally signed message part
___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
https://lists.puredata.info/listinfo/pd-list

Re: [PD] UDP server with Pd

[Christof Ressi]

Great to hear!

On 07.06.2021 22:57, Martin Peach wrote:

So I changed it to use sendto and it works a lot better. It receives
from multiple clients while sending to any one.
I added a [to ( message to set the destination, and removed the
[connect( and [disconnect{ methods.
Thanks Christof for the critique!.

Martin

On Mon, Jun 7, 2021 at 4:02 PM Christof Ressi  wrote:

The only problem I see with it is that while the socket is connected
for a send, it won't receive anything.

Why is that? This shouldn't happen.

BTW, you don't actually have to call connect(), instead you could just
save the sockaddr and use sendto(). Consequently you could also rename
the [connect( method to something else, e.g. [set  ( or
[client  (, etc. After all, a server doesn't *connect* to a
client...

Christof

On 07.06.2021 21:34, Martin Peach wrote:

OK, I have implemented something that might work: [udpsrvr] can listen
on a port and send to an address using the same or a different port.
The only problem I see with it is that while the socket is connected
for a send, it won't receive anything. I overcome this partly by
sending the connect/send/disconnect sequence in one comma-delimited
message.
The code is at
https://sourceforge.net/p/pure-data/svn/HEAD/tree/trunk/externals/mrpeach/net/udpsrvr.c

Martin

On Mon, Jun 7, 2021 at 3:48 AM Roman Haefeli  wrote:

On Sun, 2021-06-06 at 20:26 -0400, Martin Peach wrote:

If you have a [udpreceive 9898] as your 'server' it will receive from
anywhere on port 9898. So you can take the sender's ip and port from
the latest incoming message (route 'from' at the second outlet) and
use them to set the address and port of a single [udpsend] for the
reply.
There is no connection in udp so you need to add metadata in your
datagrams for routing and so forth.

Again, this does not work. The socket on the client side will only
accept packets originating from the port it has sent packets to, but
[udpsend] on the server cannot use this port as bind port, because it
is already occupied by [udpreceive]. To put this into telephone
analogy: When you call someone, you expect a third party to be
prohibited from shouting into your call, and you expect to hear only
the party you called.

The only solution to this is to use the same socket for both sending
and receiving, as Christof already suggested.

Roman
___
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] UDP server with Pd

[Martin Peach]

So I changed it to use sendto and it works a lot better. It receives
from multiple clients while sending to any one.
I added a [to ( message to set the destination, and removed the
[connect( and [disconnect{ methods.
Thanks Christof for the critique!.

Martin

On Mon, Jun 7, 2021 at 4:02 PM Christof Ressi  wrote:
>
> > The only problem I see with it is that while the socket is connected
> > for a send, it won't receive anything.
> Why is that? This shouldn't happen.
>
> BTW, you don't actually have to call connect(), instead you could just
> save the sockaddr and use sendto(). Consequently you could also rename
> the [connect( method to something else, e.g. [set  ( or
> [client  (, etc. After all, a server doesn't *connect* to a
> client...
>
> Christof
>
> On 07.06.2021 21:34, Martin Peach wrote:
> > OK, I have implemented something that might work: [udpsrvr] can listen
> > on a port and send to an address using the same or a different port.
> > The only problem I see with it is that while the socket is connected
> > for a send, it won't receive anything. I overcome this partly by
> > sending the connect/send/disconnect sequence in one comma-delimited
> > message.
> > The code is at
> > https://sourceforge.net/p/pure-data/svn/HEAD/tree/trunk/externals/mrpeach/net/udpsrvr.c
> >
> > Martin
> >
> > On Mon, Jun 7, 2021 at 3:48 AM Roman Haefeli  wrote:
> >> On Sun, 2021-06-06 at 20:26 -0400, Martin Peach wrote:
> >>>
> >>> If you have a [udpreceive 9898] as your 'server' it will receive from
> >>> anywhere on port 9898. So you can take the sender's ip and port from
> >>> the latest incoming message (route 'from' at the second outlet) and
> >>> use them to set the address and port of a single [udpsend] for the
> >>> reply.
> >>> There is no connection in udp so you need to add metadata in your
> >>> datagrams for routing and so forth.
> >>
> >> Again, this does not work. The socket on the client side will only
> >> accept packets originating from the port it has sent packets to, but
> >> [udpsend] on the server cannot use this port as bind port, because it
> >> is already occupied by [udpreceive]. To put this into telephone
> >> analogy: When you call someone, you expect a third party to be
> >> prohibited from shouting into your call, and you expect to hear only
> >> the party you called.
> >>
> >> The only solution to this is to use the same socket for both sending
> >> and receiving, as Christof already suggested.
> >>
> >> Roman
> >> ___
> >> 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] UDP server with Pd

[Martin Peach]

On Mon, Jun 7, 2021 at 4:02 PM Christof Ressi  wrote:
>
> > The only problem I see with it is that while the socket is connected
> > for a send, it won't receive anything.
> Why is that? This shouldn't happen.
>
I don't know why, that's what happens when I try it here on linux.
I will see if sendto() works any better. Thanks for the tip.

Martin


> BTW, you don't actually have to call connect(), instead you could just
> save the sockaddr and use sendto(). Consequently you could also rename
> the [connect( method to something else, e.g. [set  ( or
> [client  (, etc. After all, a server doesn't *connect* to a
> client...
>
> Christof
>
> On 07.06.2021 21:34, Martin Peach wrote:
> > OK, I have implemented something that might work: [udpsrvr] can listen
> > on a port and send to an address using the same or a different port.
> > The only problem I see with it is that while the socket is connected
> > for a send, it won't receive anything. I overcome this partly by
> > sending the connect/send/disconnect sequence in one comma-delimited
> > message.
> > The code is at
> > https://sourceforge.net/p/pure-data/svn/HEAD/tree/trunk/externals/mrpeach/net/udpsrvr.c
> >
> > Martin
> >
> > On Mon, Jun 7, 2021 at 3:48 AM Roman Haefeli  wrote:
> >> On Sun, 2021-06-06 at 20:26 -0400, Martin Peach wrote:
> >>>
> >>> If you have a [udpreceive 9898] as your 'server' it will receive from
> >>> anywhere on port 9898. So you can take the sender's ip and port from
> >>> the latest incoming message (route 'from' at the second outlet) and
> >>> use them to set the address and port of a single [udpsend] for the
> >>> reply.
> >>> There is no connection in udp so you need to add metadata in your
> >>> datagrams for routing and so forth.
> >>
> >> Again, this does not work. The socket on the client side will only
> >> accept packets originating from the port it has sent packets to, but
> >> [udpsend] on the server cannot use this port as bind port, because it
> >> is already occupied by [udpreceive]. To put this into telephone
> >> analogy: When you call someone, you expect a third party to be
> >> prohibited from shouting into your call, and you expect to hear only
> >> the party you called.
> >>
> >> The only solution to this is to use the same socket for both sending
> >> and receiving, as Christof already suggested.
> >>
> >> Roman
> >> ___
> >> 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] UDP server with Pd

[Christof Ressi]

The only problem I see with it is that while the socket is connected
for a send, it won't receive anything.

Why is that? This shouldn't happen.

BTW, you don't actually have to call connect(), instead you could just 
save the sockaddr and use sendto(). Consequently you could also rename 
the [connect( method to something else, e.g. [set  ( or 
[client  (, etc. After all, a server doesn't *connect* to a 
client...


Christof

On 07.06.2021 21:34, Martin Peach wrote:

OK, I have implemented something that might work: [udpsrvr] can listen
on a port and send to an address using the same or a different port.
The only problem I see with it is that while the socket is connected
for a send, it won't receive anything. I overcome this partly by
sending the connect/send/disconnect sequence in one comma-delimited
message.
The code is at
https://sourceforge.net/p/pure-data/svn/HEAD/tree/trunk/externals/mrpeach/net/udpsrvr.c

Martin

On Mon, Jun 7, 2021 at 3:48 AM Roman Haefeli  wrote:

On Sun, 2021-06-06 at 20:26 -0400, Martin Peach wrote:


If you have a [udpreceive 9898] as your 'server' it will receive from
anywhere on port 9898. So you can take the sender's ip and port from
the latest incoming message (route 'from' at the second outlet) and
use them to set the address and port of a single [udpsend] for the
reply.
There is no connection in udp so you need to add metadata in your
datagrams for routing and so forth.


Again, this does not work. The socket on the client side will only
accept packets originating from the port it has sent packets to, but
[udpsend] on the server cannot use this port as bind port, because it
is already occupied by [udpreceive]. To put this into telephone
analogy: When you call someone, you expect a third party to be
prohibited from shouting into your call, and you expect to hear only
the party you called.

The only solution to this is to use the same socket for both sending
and receiving, as Christof already suggested.

Roman
___
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] UDP server with Pd

[Martin Peach]

OK, I have implemented something that might work: [udpsrvr] can listen
on a port and send to an address using the same or a different port.
The only problem I see with it is that while the socket is connected
for a send, it won't receive anything. I overcome this partly by
sending the connect/send/disconnect sequence in one comma-delimited
message.
The code is at
https://sourceforge.net/p/pure-data/svn/HEAD/tree/trunk/externals/mrpeach/net/udpsrvr.c

Martin

On Mon, Jun 7, 2021 at 3:48 AM Roman Haefeli  wrote:
>
> On Sun, 2021-06-06 at 20:26 -0400, Martin Peach wrote:
> >
> >
> > If you have a [udpreceive 9898] as your 'server' it will receive from
> > anywhere on port 9898. So you can take the sender's ip and port from
> > the latest incoming message (route 'from' at the second outlet) and
> > use them to set the address and port of a single [udpsend] for the
> > reply.
> > There is no connection in udp so you need to add metadata in your
> > datagrams for routing and so forth.
>
>
> Again, this does not work. The socket on the client side will only
> accept packets originating from the port it has sent packets to, but
> [udpsend] on the server cannot use this port as bind port, because it
> is already occupied by [udpreceive]. To put this into telephone
> analogy: When you call someone, you expect a third party to be
> prohibited from shouting into your call, and you expect to hear only
> the party you called.
>
> The only solution to this is to use the same socket for both sending
> and receiving, as Christof already suggested.
>
> Roman
> ___
> 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] Binaural w32?

[Dan Wilcox]

earplug-0.3.0-macos-universal-64-arm-intel.zip 


> On Jun 7, 2021, at 8:03 PM, João Pais  wrote:
> 
> 
>>> I see that the version in deken is for all OSs except Mac, is that correct? 
>>> Is a mac (64+32b) binary available, or it's already there, only deken 
>>> doesn't know about it?
>> 
>> Lucas made a build for Linux and Windows. There isn't a build for macOS yet 
>> and we just need someone to upload one.
> 
> if the only difference is the darwin file, would it be possible to send it 
> here? (someone I know wanted to try it, but he can't learn how to install/try 
> out externals)
> 


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] Binaural w32?

[João Pais]

I see that the version in deken is for all OSs except Mac, is that 
correct? Is a mac (64+32b) binary available, or it's already there, 
only deken doesn't know about it?


Lucas made a build for Linux and Windows. There isn't a build for 
macOS yet and we just need someone to upload one.


if the only difference is the darwin file, would it be possible to send 
it here? (someone I know wanted to try it, but he can't learn how to 
install/try out externals)





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

[PD] Patch2Svg exports controlled in a pd patch

[boscomac]

Hi List,

I recently discovered this Patch2Svg add-on. It works perfectly (mac os mojave, 
Pd 0.50-2). 

Working with data structures, I generate many serial drawings that I export to 
Svg. 
Basically, I export my Pd-data sub-patch which contains the graphical display 
only. 

I would like to know if there is a way to control and serialize this export 
operation directly in the Pd patch? 
Something like [write $1.svg( message, as it can be done with an array, audio 
recording, txt file, etc.

Thank you in advance.

Boscomac


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

[PD] osx - PD network allowance issues

[oliver]

hi, dear mac users

recently i installed PD-0.51-4 on an old macbook (10.9.x) and even 
though everything works fine, i always get an alert at startup, asking 
me if i want to allow network connections for this application. i set 
"allow" everytime plus i also set the firewall exceptions for the PD 
package (the one in the applications folder) in the security preferences 
but OSX doesn't seem to care ;-) - i still get this alert on every PD 
startup ...


does somebody here on this list have some experiences in this matter ?

thanks for any help

oliver



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

Re: [PD] Binaural w32?

[Dan Wilcox]

> On Jun 7, 2021, at 9:33 AM, João Pais  wrote:
> 
> Great, thanks. A first tryout seems to work with no issues (and sounds better 
> than the previous version which was highly filtered).

Cool.

> I see that the version in deken is for all OSs except Mac, is that correct? 
> Is a mac (64+32b) binary available, or it's already there, only deken doesn't 
> know about it?

Lucas made a build for Linux and Windows. There isn't a build for macOS yet and 
we just need someone to upload one.

> Also to confirm: if for some reason the current earplug_data.txt file isn't 
> packed with earplug~, the default values within the object match the ones in 
> the txt file, correct?

Yes. The default behavior is to compile in the default dataset which can be 
overridden when an earplug_data.txt fiel is found and loaded. For those that 
compile the external themselves, there is an option to disable compiling in the 
data which makes the binary smaller but then requires the txt file.


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] UDP server with Pd

[Roman Haefeli]

On Sun, 2021-06-06 at 20:26 -0400, Martin Peach wrote:
> 
> 
> If you have a [udpreceive 9898] as your 'server' it will receive from
> anywhere on port 9898. So you can take the sender's ip and port from
> the latest incoming message (route 'from' at the second outlet) and
> use them to set the address and port of a single [udpsend] for the
> reply.
> There is no connection in udp so you need to add metadata in your
> datagrams for routing and so forth.


Again, this does not work. The socket on the client side will only
accept packets originating from the port it has sent packets to, but
[udpsend] on the server cannot use this port as bind port, because it
is already occupied by [udpreceive]. To put this into telephone
analogy: When you call someone, you expect a third party to be
prohibited from shouting into your call, and you expect to hear only
the party you called.

The only solution to this is to use the same socket for both sending
and receiving, as Christof already suggested. 

Roman


signature.asc
Description: This is a digitally signed message part
___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
https://lists.puredata.info/listinfo/pd-list

Re: [PD] Binaural w32?

[João Pais]

Great, thanks. A first tryout seems to work with no issues (and sounds 
better than the previous version which was highly filtered).


I see that the version in deken is for all OSs except Mac, is that 
correct? Is a mac (64+32b) binary available, or it's already there, only 
deken doesn't know about it?


Also to confirm: if for some reason the current earplug_data.txt file 
isn't packed with earplug~, the default values within the object match 
the ones in the txt file, correct?



Ok, earplug~ 0.3.0 is ready:

https://github.com/pd-externals/earplug

Lucas (or any Windows dev), if you have time, could you make Windows 
builds for deken? Then Joao can give it a try...


Done. Its up on Deken :

~~~
earplug~[v0.3.0](Linux-amd64-32)(Linux-i386-32)(Windows-amd64-32)(Windows-i386-32).dek 


    Uploaded by lucarda @ 2021-06-06 18:45:39
~~~

:)




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