Re: [PD] OSC Communication between PD and SC

2015-06-21 Thread Alexandre Torres Porres
works!

thanks

2015-06-21 23:42 GMT-03:00 Clifford Dunn :

> Totally. For the SC side, you actually shouldn't be too specific with
> the ports. So all that seems to be needed is this:
>
> OSCFunc({arg msg, time, add, recvPort; msg.postln;}, '/test');
>
> Then on PD
>
> message: connect 127.0.0.1 57120
> *connect*
> object: udpsend
>
> 57120 is the default port that SC listens to. It doesn't hurt to
> double check that by running NetAddr.langPort
>
> Then also on PD:
>
> message: send /test $1
> *connect*
> object: packOSC
> *connect*
> object: udpsend
>
> And that seems to work just fine!
> Clifford Dunn
> Flutist/Composer
> http://www.ckdmusic.weebly.com
>
>
>
> On Sun, Jun 21, 2015 at 12:21 PM, Alexandre Torres Porres
>  wrote:
> > can you share de code from supercollider and the pd patch for us please?
> >
> > 2015-06-21 2:46 GMT-03:00 Clifford Dunn :
> >>
> >> Okay, I figured it out.
> >>
> >> It's a supercollider thing. Turns out that I was being too specific
> >> when defining the NetAddr. By not specifying in the OSCdef, everything
> >> is working fine now. Thanks for all the help!
> >> Clifford Dunn
> >> Flutist/Composer
> >> http://www.ckdmusic.weebly.com
> >>
> >>
> >>
> >> On Sat, Jun 20, 2015 at 5:54 PM, Martin Peach 
> >> wrote:
> >> > Are you sure NetAddr.langPort is 57120?
> >> >
> >> > Martin
> >> >
> >> > On Sat, Jun 20, 2015 at 5:27 PM, Clifford Dunn  >
> >> > wrote:
> >> >>
> >> >> Hi PD list,
> >> >>
> >> >> I want to be sending this to the SC list as well, but for some reason
> >> >> I can't get through there.
> >> >>
> >> >> I'm getting pretty frustrated as I try to figure out why these two
> >> >> programs are currently refusing to talk to each other. I'm not really
> >> >> sure about how to type out PD code, so please bear with me.
> >> >>
> >> >> First, I have SC set up to receive OSC:
> >> >>
> >> >> n = NetAddr("127.0.0.1", NetAddr.langPort);
> >> >>
> >> >> OSCFunc({arg msg, time, addr, recvPort; "Hello World".postln;},
> >> >> '/test',
> >> >> n);
> >> >>
> >> >> Testing this internally with SC works fine:
> >> >>
> >> >> m = NetAddr("127.0.0.1", NetAddr.langPort);
> >> >>
> >> >> m.sendMsg("/test", "Hi")
> >> >>
> >> >>
> >> >> PD on the other hand:
> >> >>
> >> >> object: import mrpeach
> >> >> message: connect 127.0.0.1 57120
> >> >> *connected to*
> >> >> object: udpsend
> >> >>
> >> >> The listener tells me: udpsend connecting to port 57120
> >> >>
> >> >> message: send /test 5
> >> >> *connected to*
> >> >> object: packOSC
> >> >> *connected to*
> >> >> object udpsend
> >> >>
> >> >> Nothing happens on the supercollider end. However, within PD, if I
> set
> >> >> up a udpreceiver, I get a response
> >> >>
> >> >> object: udpreceive 57120
> >> >> *connected to*
> >> >> object: unpackOSC
> >> >> *connected to*
> >> >> object: spigot (toggle on right inlet)
> >> >> *connected to*
> >> >> object: print received
> >> >>
> >> >> And then I can send messages within PD and it prints fine.
> >> >>
> >> >> Also, if I send from SC:
> >> >>
> >> >> n.sendMsg("/test", 45);
> >> >>
> >> >> It prints fine in PD.
> >> >>
> >> >> So what am I missing that is preventing PD from sending to SC? If it
> >> >> helps, I'm running ArchLinux, SC 3.6.6, and Pd 0.43.4-extended.
> >> >>
> >> >> Thanks a lot for any help you can provide!
> >> >>
> >> >> connect 1
> >> >> Clifford Dunn
> >> >> Flutist/Composer
> >> >> http://www.ckdmusic.weebly.com
> >> >>
> >> >> ___
> >> >> Pd-list@lists.iem.at mailing list
> >> >> UNSUBSCRIBE and account-management ->
> >> >> http://lists.puredata.info/listinfo/pd-list
> >> >
> >> >
> >>
> >> ___
> >> Pd-list@lists.iem.at mailing list
> >> UNSUBSCRIBE and account-management ->
> >> http://lists.puredata.info/listinfo/pd-list
> >
> >
>
___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
http://lists.puredata.info/listinfo/pd-list


Re: [PD] OSC Communication between PD and SC

2015-06-21 Thread Clifford Dunn
Totally. For the SC side, you actually shouldn't be too specific with
the ports. So all that seems to be needed is this:

OSCFunc({arg msg, time, add, recvPort; msg.postln;}, '/test');

Then on PD

message: connect 127.0.0.1 57120
*connect*
object: udpsend

57120 is the default port that SC listens to. It doesn't hurt to
double check that by running NetAddr.langPort

Then also on PD:

message: send /test $1
*connect*
object: packOSC
*connect*
object: udpsend

And that seems to work just fine!
Clifford Dunn
Flutist/Composer
http://www.ckdmusic.weebly.com



On Sun, Jun 21, 2015 at 12:21 PM, Alexandre Torres Porres
 wrote:
> can you share de code from supercollider and the pd patch for us please?
>
> 2015-06-21 2:46 GMT-03:00 Clifford Dunn :
>>
>> Okay, I figured it out.
>>
>> It's a supercollider thing. Turns out that I was being too specific
>> when defining the NetAddr. By not specifying in the OSCdef, everything
>> is working fine now. Thanks for all the help!
>> Clifford Dunn
>> Flutist/Composer
>> http://www.ckdmusic.weebly.com
>>
>>
>>
>> On Sat, Jun 20, 2015 at 5:54 PM, Martin Peach 
>> wrote:
>> > Are you sure NetAddr.langPort is 57120?
>> >
>> > Martin
>> >
>> > On Sat, Jun 20, 2015 at 5:27 PM, Clifford Dunn 
>> > wrote:
>> >>
>> >> Hi PD list,
>> >>
>> >> I want to be sending this to the SC list as well, but for some reason
>> >> I can't get through there.
>> >>
>> >> I'm getting pretty frustrated as I try to figure out why these two
>> >> programs are currently refusing to talk to each other. I'm not really
>> >> sure about how to type out PD code, so please bear with me.
>> >>
>> >> First, I have SC set up to receive OSC:
>> >>
>> >> n = NetAddr("127.0.0.1", NetAddr.langPort);
>> >>
>> >> OSCFunc({arg msg, time, addr, recvPort; "Hello World".postln;},
>> >> '/test',
>> >> n);
>> >>
>> >> Testing this internally with SC works fine:
>> >>
>> >> m = NetAddr("127.0.0.1", NetAddr.langPort);
>> >>
>> >> m.sendMsg("/test", "Hi")
>> >>
>> >>
>> >> PD on the other hand:
>> >>
>> >> object: import mrpeach
>> >> message: connect 127.0.0.1 57120
>> >> *connected to*
>> >> object: udpsend
>> >>
>> >> The listener tells me: udpsend connecting to port 57120
>> >>
>> >> message: send /test 5
>> >> *connected to*
>> >> object: packOSC
>> >> *connected to*
>> >> object udpsend
>> >>
>> >> Nothing happens on the supercollider end. However, within PD, if I set
>> >> up a udpreceiver, I get a response
>> >>
>> >> object: udpreceive 57120
>> >> *connected to*
>> >> object: unpackOSC
>> >> *connected to*
>> >> object: spigot (toggle on right inlet)
>> >> *connected to*
>> >> object: print received
>> >>
>> >> And then I can send messages within PD and it prints fine.
>> >>
>> >> Also, if I send from SC:
>> >>
>> >> n.sendMsg("/test", 45);
>> >>
>> >> It prints fine in PD.
>> >>
>> >> So what am I missing that is preventing PD from sending to SC? If it
>> >> helps, I'm running ArchLinux, SC 3.6.6, and Pd 0.43.4-extended.
>> >>
>> >> Thanks a lot for any help you can provide!
>> >>
>> >> connect 1
>> >> Clifford Dunn
>> >> Flutist/Composer
>> >> http://www.ckdmusic.weebly.com
>> >>
>> >> ___
>> >> Pd-list@lists.iem.at mailing list
>> >> UNSUBSCRIBE and account-management ->
>> >> http://lists.puredata.info/listinfo/pd-list
>> >
>> >
>>
>> ___
>> Pd-list@lists.iem.at mailing list
>> UNSUBSCRIBE and account-management ->
>> http://lists.puredata.info/listinfo/pd-list
>
>

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


Re: [PD] OSC Communication between PD and SC

2015-06-21 Thread Alexandre Torres Porres
can you share de code from supercollider and the pd patch for us please?

2015-06-21 2:46 GMT-03:00 Clifford Dunn :

> Okay, I figured it out.
>
> It's a supercollider thing. Turns out that I was being too specific
> when defining the NetAddr. By not specifying in the OSCdef, everything
> is working fine now. Thanks for all the help!
> Clifford Dunn
> Flutist/Composer
> http://www.ckdmusic.weebly.com
>
>
>
> On Sat, Jun 20, 2015 at 5:54 PM, Martin Peach 
> wrote:
> > Are you sure NetAddr.langPort is 57120?
> >
> > Martin
> >
> > On Sat, Jun 20, 2015 at 5:27 PM, Clifford Dunn 
> > wrote:
> >>
> >> Hi PD list,
> >>
> >> I want to be sending this to the SC list as well, but for some reason
> >> I can't get through there.
> >>
> >> I'm getting pretty frustrated as I try to figure out why these two
> >> programs are currently refusing to talk to each other. I'm not really
> >> sure about how to type out PD code, so please bear with me.
> >>
> >> First, I have SC set up to receive OSC:
> >>
> >> n = NetAddr("127.0.0.1", NetAddr.langPort);
> >>
> >> OSCFunc({arg msg, time, addr, recvPort; "Hello World".postln;}, '/test',
> >> n);
> >>
> >> Testing this internally with SC works fine:
> >>
> >> m = NetAddr("127.0.0.1", NetAddr.langPort);
> >>
> >> m.sendMsg("/test", "Hi")
> >>
> >>
> >> PD on the other hand:
> >>
> >> object: import mrpeach
> >> message: connect 127.0.0.1 57120
> >> *connected to*
> >> object: udpsend
> >>
> >> The listener tells me: udpsend connecting to port 57120
> >>
> >> message: send /test 5
> >> *connected to*
> >> object: packOSC
> >> *connected to*
> >> object udpsend
> >>
> >> Nothing happens on the supercollider end. However, within PD, if I set
> >> up a udpreceiver, I get a response
> >>
> >> object: udpreceive 57120
> >> *connected to*
> >> object: unpackOSC
> >> *connected to*
> >> object: spigot (toggle on right inlet)
> >> *connected to*
> >> object: print received
> >>
> >> And then I can send messages within PD and it prints fine.
> >>
> >> Also, if I send from SC:
> >>
> >> n.sendMsg("/test", 45);
> >>
> >> It prints fine in PD.
> >>
> >> So what am I missing that is preventing PD from sending to SC? If it
> >> helps, I'm running ArchLinux, SC 3.6.6, and Pd 0.43.4-extended.
> >>
> >> Thanks a lot for any help you can provide!
> >>
> >> connect 1
> >> Clifford Dunn
> >> Flutist/Composer
> >> http://www.ckdmusic.weebly.com
> >>
> >> ___
> >> Pd-list@lists.iem.at mailing list
> >> UNSUBSCRIBE and account-management ->
> >> http://lists.puredata.info/listinfo/pd-list
> >
> >
>
> ___
> Pd-list@lists.iem.at mailing list
> UNSUBSCRIBE and account-management ->
> http://lists.puredata.info/listinfo/pd-list
>
___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
http://lists.puredata.info/listinfo/pd-list


Re: [PD] Error Compiling Gem on Ubuntu 15.04

2015-06-21 Thread Jim Ruxton





I am getting the following errors in compiling Gem on Ubuntu 15.04. Any
thought on what I need to do to correct this. Thanks.

this has been fixed in Gem's git for a long time.

I was having trouble with autoconf so went with the stable version.

but there hasn't been a release for an even longer time.
but if you need to stick with a properly released version of Gem, why
don't you just use the Gem that comes with ubuntu?

as in:
$ sudo apt-get install gem

Thanks for this, the documentation I saw said

which documentation?
can it be fixed?


Sorry I don't remember where I saw this and now that I think of it 
perhaps it didn't say pd-gem specifically but rather to add pd- in front 
of external names when loading them using apt-get. I understand now that 
isn't the case for gem. Thanks again for clarifying this.

Jim







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


Re: [PD] open $1 GUI - no outlet

2015-06-21 Thread Jack
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hello,

Use a message instead of object for "open $1".
++

Jack



Le 21/06/2015 14:05, Michael-Jon Mizra a écrit :
> open $1 creates a gui object with no outlet - i am trying to patch
> it to pix_image . my structure goes bng - openpanel - open $1-
> pix_image - pix_texture
> 
> thank you
> 
> 
> ___ 
> Pd-list@lists.iem.at mailing list UNSUBSCRIBE and
> account-management -> http://lists.puredata.info/listinfo/pd-list
> 

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBAgAGBQJVhqqIAAoJEOuluecjw8GUgj4H/3j5LJ8I4h0WdelVhSi3Km1c
HLU2CehlkZZIxLDtyLPhywQrzoXt9QmHsvOTxuRUS/9m3yttaLRT9Pbs/9VvWuYH
XjbQwN+/T13ofeGdHEczPtge9QYazWR7wcGJ0Untu3iNPNYn/soyfX+DRYgNvPA2
ntQmCzXnTbIdw7h+3XQGQvFPAhFwptmtx3FvonnTN7ePjj3ekkPwP5ACaTB4ZAAF
ttoehMLgqi+hzOBDu/dhFfZuDsDC5qV/aGzMiyZ1kJV3+ddnYAhXcUPkbivbuZvr
WQiY2A+DZZWu9xjApI0IcwLZoiSuU/kNPREX2/0mefSGiwohGQ1ya22VTQyVMfs=
=8utZ
-END PGP SIGNATURE-

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


Re: [PD] [text3dml] => text3d multiline with all accents

2015-06-21 Thread Jack
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

An enhanced version of Gem abstraction [text3d_ml]...

Added :
clear message : to clear text
replace message : to replace a line at a certain position
add message : to add a line at the end of the text

Now [text3d_ml] returns the number of lines.

If needed for people using a pd version < 0.46, it should not be
difficult to change [text] with [textfile] or [msgfile] (zexy) and
[list fromsymbol] with [any2bytes] (moocow).
++

Jack



Le 17/06/2015 11:51, Jack a écrit :
> Here a final version of [text3d_ml]. Should be faster and without
> error. ++
> 
> Jack
> 
> 
> 
> Le 16/06/2015 22:38, Jack a écrit :
>> Yes, you need Pd 0.46.0 minimum, for [list fromsymbol], [list 
>> tosymbol] and [text] familly objects used in this abstraction.
>> ++
> 
>> Jack
> 
> 
>> Le 16/06/2015 16:26, IOhannes m zmölnig a écrit :
>>> On 06/16/2015 04:06 PM, Philippe Boisnard wrote:
 I haven't list from symbol (last vanilla ...)
> 
>>> it's called [list fromsymbol] (without the space between 'from'
>>>  and 'symbol') and it is included in Pd-vanilla since 0.46-0.
> 
>>> most likely you don't have "last vanilla" (which is 0.46-6).
> 
>>> fgmards IOhannes
> 
> 
> 
>>> ___ 
>>> Pd-list@lists.iem.at mailing list UNSUBSCRIBE and 
>>> account-management -> 
>>> http://lists.puredata.info/listinfo/pd-list
> 
> 
> 
>> ___ 
>> Pd-list@lists.iem.at mailing list UNSUBSCRIBE and 
>> account-management ->
>> http://lists.puredata.info/listinfo/pd-list
> 
> 
> 
> 
> 
> ___ 
> Pd-list@lists.iem.at mailing list UNSUBSCRIBE and
> account-management -> http://lists.puredata.info/listinfo/pd-list
> 

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBAgAGBQJVhqopAAoJEOuluecjw8GU0ZQH/2cPOLfF/84Tsz5xrFbpcId1
6kHKikNtl/UJnCLJVi4ZKlxj4oI12lJPIFPkJJH/lTHTxDUYnkIXYtMZGlZA6bHM
DW+onFWJiAO1If1oXvApITR0f6bU+/DKuL1s2QbOwvNAMvyvb0i72rQ0q03LGj47
feNuO+J8zfMaaOupfCbmJu32rvGrjMl9HOUKDRybRmAm1UySBmuSQBLBNmiTD5Kb
s1WnDUWKFsyGWxJwc6EXtmZa8LWRkV++gYlTp392yam1vxotJT9Q6otxt8CfmiTd
4vFOGA7WHGekJMAdSt3rCwdCX4MEEsBVFA2XVZUlE7NAwi7zkoQK/Fsah1QpptA=
=ZIHb
-END PGP SIGNATURE-

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


[PD] open $1 GUI - no outlet

2015-06-21 Thread Michael-Jon Mizra
open $1 creates a gui object with no outlet - i am trying to patch it to 
pix_image . my structure goes bng - openpanel - open $1- pix_image - pix_texture

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


Re: [PD] Error Compiling Gem on Ubuntu 15.04

2015-06-21 Thread IOhannes m zmölnig
On 06/21/2015 03:59 AM, Jim Ruxton wrote:
> 
>>> >I am getting the following errors in compiling Gem on Ubuntu 15.04. Any
>>> >thought on what I need to do to correct this. Thanks.
>> this has been fixed in Gem's git for a long time.
> I was having trouble with autoconf so went with the stable version.
>> but there hasn't been a release for an even longer time.
>> but if you need to stick with a properly released version of Gem, why
>> don't you just use the Gem that comes with ubuntu?
>>
>> as in:
>> $ sudo apt-get install gem
> Thanks for this, the documentation I saw said

which documentation?
can it be fixed?


gfmards
IOhannes




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