Re: [PD] raspberry pi window position problem

Thanks again for this helpful thread, sdf On 23 March 2016 at 15:33, oliver wrote: > IOhannes m zmoelnig wrote: > >> On 2016-03-23 10:47, oliver wrote: >> >>> for whatever reason, my recently "apt-get installed" puredata was >>> version 0.43 (how so ?) >>> >> >>

Re: [PD] Print a big patch

I think patch2svg-plugin.tcl may help you with that ( https://github.com/iem-projects/patch2svg-plugin ) 2016-03-25 2:44 GMT+01:00 Jack : > Salut Olivier, > > I guess you work with linux. > I think is doable with 'xvfb' (with which you can create a virtual > screen of any size)

Re: [PD] Print a big patch

Thank you Jack, I've tried xvfb + imagemagick but I failed to open the patch's window in fullscreen... So, it's with a lot of pleasure that I've discovered the message of Tim this morning. :-) Thank you. It works fine. I've got some error messages

Re: [PD] Edit Pd file to change coordinates. pdlua or other language?

> that sounds good. But I think you sent me the same file as before? > They are exactly alike. Just checked, and I did send a newer version, I even added a 0.2 version number in the header. Here it is version 0.3. On 2016-03-25 01:53 AM, João Pais wrote: Hi, I tinkered around with tcl,

[PD] can signal inlets that aren't the main inlet have float or message methods?

Howdy, for main inlets (left inlet), you can add whatever kind of method to whatever kind of type, being it a signal, a symbol, a list... but not sure if you can do this with non-main inlets (the documentation pd-externals how to put up my IOhannes seems to confirm this). anyway, i kinda needed a

Re: [PD] strange result with netsend/netreceive

pd represent 101 with 1e+06. it's the same representation than 100 ... c Le 25/03/2016 23:00, Jack a écrit : Hello, when i send a float '101' with 'netsend', 'netreceine' get '100'. Is it a normal behavior ? Configuration : Pd 0.46.5 Ubuntu 15.10 ++ Jack PS : i find a

Re: [PD] can signal inlets that aren't the main inlet have float or message methods?

There's a way to do it.  Search the mailing list for "proxy inlet". However, as a general rule this is a bad idea.  (Unless of course you are trying to be compatible with a Max/MSP object that does it that way.) -Jonathan On Friday, March 25, 2016 5:33 PM, Derek Kwan

Re: [PD] Automatic Sample Separator / possible bug in some Pd versions

Hi Christopher: You can do arrays bigger than 90 sec, see [soundfiler] help, flags for reading: -resize and -maxsize. It is safe to use soundfiles shorter than 16777216 samples (around 6 min @44.1khz), this is the maximum possible integer for a 3 byte number, this is also the biggest number

[PD] strange result with netsend/netreceive

Hello, when i send a float '101' with 'netsend', 'netreceine' get '100'. Is it a normal behavior ? Configuration : Pd 0.46.5 Ubuntu 15.10 ++ Jack PS : i find a workaround by sending the number as symbol. signature.asc Description: OpenPGP digital signature

Re: [PD] strange result with netsend/netreceive

Le 25/03/2016 23:52, Jack a écrit : What surprised me, it's that you can get a 'good' representation of [101( when you send it to [rawprint] (from zexy), but the same message sent through netsend/netreceive become [100(. I must therefore conclude that [rawprint] can get exactly 101

[PD] can signal inlets that aren't the main inlet have float or message methods?

Hey y'all, I'm actually the one that needs this, I've been working with Alexandre on updating Cyclone. If further info is needed, the method I've been trying to use is inlet_new. The part of documentation that seems to drive the nail in the coffin is this bullet-point: "It is not possible to

Re: [PD] strange result with netsend/netreceive

What surprised me, it's that you can get a 'good' representation of [101( when you send it to [rawprint] (from zexy), but the same message sent through netsend/netreceive become [100(. I must therefore conclude that [rawprint] can get exactly 101 (and maybe netsend can too), but the

Re: [PD] strange result with netsend/netreceive

Le 26/03/2016 00:12, cyrille henry a écrit : > > > Le 25/03/2016 23:52, Jack a écrit : >> What surprised me, it's that you can get a 'good' representation of >> [101( when you send it to [rawprint] (from zexy), but the same >> message sent through netsend/netreceive become [100(. >> I

Re: [PD] can signal inlets that aren't the main inlet have float or message methods?

2016-03-25 19:21 GMT-03:00 Jonathan Wilkes via Pd-list : > (Unless of course you are trying to be compatible with a Max/MSP object > that does it that way.) > yep, [scope~] by the way, second signal inlet should set "bufsize" when receiving a float, to be more specific.

Re: [PD] can signal inlets that aren't the main inlet have float or message methods?

2016-03-25 19:21 GMT-03:00 Jonathan Wilkes via Pd-list : > There's a way to do it. Search the mailing list for "proxy inlet". > this is where the search took me to http://puredata.info/Members/mjmogo Inlet Proxy Object