On Tue, Nov 20, 2012 at 12:59:00PM +0100, Stefan Blixt wrote:

This is just a wild shot, and since you're using Ubuntu you're probably familiar with this stuff, but sometimes "localhost" doesn't work. To eliminate this, replace "localhost" with "127.0.0.1" in your source files and try again.

Probably not the solution, but you never know.

That would be a Ubuntu bug then. I think that by default Ubuntu maps localhost to 127.0.0.1 in /etc/hosts cat /etc/hosts ...should confirm whether the file is there and what is in it. The hosts file getting ignored would potentially have unpleasant repercussions, but I agree we can't rule that out. Could also be a over-active firewall? I haven't kept up with Ubuntu's latest antics. Kas.

Hehe I half didn't expect that to be the problem actually, glad it helped! :) It's possible that other applications suffer from this, so you might want to check the file /etc/hosts, and see if you can add localhost on a line of its own in there, like this: 127.0.0.1 localhost This will solve this problem generally, and the chuck examples will work out of the box. /Stefan On Tue, Nov 20, 2012 at 7:38 PM, Romain Michon wrote:

Thanks guys for your fast answers! I replaced localhost with 127.0.0.1 and it now works like a charm!

Cheers,

Romain

On 11/20/2012 03:59 AM, Stefan Blixt wrote:

This is just a wild shot, and since you're using Ubuntu you're probably familiar with this stuff, but sometimes "localhost" doesn't work. To eliminate this, replace "localhost" with "127.0.0.1" in your source files and try again.

Probably not the solution, but you never know.

BTW, OSC_send.ck and OSC_receive.ck worked here on my Mac.

/Stefan

On Tue, Nov 20, 2012 at 7:56 AM, Romain Michon

...

wrote:

...

Hi List,

I'm totally new in the Chuck world! I'm trying to use the OSC examples provided at http://chuck.cs.princeton.edu/doc/examples/osc/ and both

chuck OSC_send.ck OSC_receive.ck

and

chuck s.ck r.ck

don't work on machine. In the first case, OSC_send.ck seems to send correctly the OSC messages (it returns sent (via OSC): 0.895094 ...) but OSC_receive.ck never get them. r.ck runs the sine wave oscillator fine but never receive the messages sent by s.ck. I didn't make any change to the files (except for the path to the audio file in OSC_receive.ck, of course ;) ).

I tried to send OSC messages to both OSC_receive.ck and r.ck with SuperCollider and PureData without any success. OSC works fine to communicate inside and between these two programs though.

Am I missing some flags/options?

I'm running chuck on Ubuntu 12.04 64bits.

Thanks a lot for your help!

Cheers,

Romain _______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users

-- Release me, insect, or I will destroy the Cosmos!

_______________________________________________ chuck-users mailing listchuck-users@lists.cs.princeton.eduhttps://lists.cs.princeton.edu/mailman/listinfo/chuck-users

_______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users

-- Release me, insect, or I will destroy the Cosmos!

localhost was actually set up in my /etc/hosts so it must be another problem... ++ Romain On 11/20/2012 02:13 PM, Stefan Blixt wrote:

@Kassen: I know that every once in a while I come across a linux system where localhost isn't set up in /etc/hosts. I don't know the circumstances when you don't want it there, but it could be that packages set up the hosts file as needed, and Romain just hasn't installed a package that needed the localhost name.

Unix hackers probably think it's just an unnecessary hassle: "why write localhost when I can write 127.0.0.1" ;)

/Stefan

On Tue, Nov 20, 2012 at 8:50 PM, Stefan Blixt mailto:stefan.blixt@gmail.com> wrote:

Hehe I half didn't expect that to be the problem actually, glad it helped! :) It's possible that other applications suffer from this, so you might want to check the file /etc/hosts, and see if you can add localhost on a line of its own in there, like this:

127.0.0.1 localhost

This will solve this problem generally, and the chuck examples will work out of the box.

/Stefan

On Tue, Nov 20, 2012 at 7:38 PM, Romain Michon mailto:rmichon@ccrma.stanford.edu> wrote:

Thanks guys for your fast answers! I replaced localhost with 127.0.0.1 and it now works like a charm!

Cheers,

Romain

On 11/20/2012 03:59 AM, Stefan Blixt wrote:

...

This is just a wild shot, and since you're using Ubuntu you're probably familiar with this stuff, but sometimes "localhost" doesn't work. To eliminate this, replace "localhost" with "127.0.0.1" in your source files and try again.

Probably not the solution, but you never know.

BTW, OSC_send.ck and OSC_receive.ck worked here on my Mac.

/Stefan

On Tue, Nov 20, 2012 at 7:56 AM, Romain Michon mailto:rmichon@ccrma.stanford.edu> wrote:

Hi List,

I'm totally new in the Chuck world! I'm trying to use the OSC examples provided at http://chuck.cs.princeton.edu/doc/examples/osc/ and both

chuck OSC_send.ck OSC_receive.ck

and

chuck s.ck http://s.ck r.ck http://r.ck

don't work on machine. In the first case, OSC_send.ck seems to send correctly the OSC messages (it returns sent (via OSC): 0.895094 ...) but OSC_receive.ck never get them. r.ck http://r.ck runs the sine wave oscillator fine but never receive the messages sent by s.ck http://s.ck. I didn't make any change to the files (except for the path to the audio file in OSC_receive.ck, of course ;) ).

I tried to send OSC messages to both OSC_receive.ck and r.ck http://r.ck with SuperCollider and PureData without any success. OSC works fine to communicate inside and between these two programs though.

Am I missing some flags/options?

I'm running chuck on Ubuntu 12.04 64bits.

Thanks a lot for your help!

Cheers,

Romain _______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu mailto:chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users

-- Release me, insect, or I will destroy the Cosmos!

_______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu mailto:chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users

_______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu mailto:chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users

-- Release me, insect, or I will destroy the Cosmos!

-- Release me, insect, or I will destroy the Cosmos!

_______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users

Curious. I didn't think you could bypass the hosts file, I guess I'm no Unix hacker. Maybe it's because it's UDP? On Tue, Nov 20, 2012 at 11:37 PM, Kassen wrote:

On Tue, Nov 20, 2012 at 02:21:02PM -0800, Romain Michon wrote:

...

localhost was actually set up in my /etc/hosts so it must be another problem...

Ok, then it's a ChucK bug, IMHO. I don't feel it is reasonable to expect people to remember arcane trains of numbers just to bounce some messages around. Remembering that kind of number is for computers while we enlighten audiences with our High Art or provide a backdrop for drinking beer.

Kas. _______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users

-- Release me, insect, or I will destroy the Cosmos!

On Tue, Nov 20, 2012 at 11:13:24PM +0100, Stefan Blixt wrote:

@Kassen: I know that every once in a while I come across a linux system where localhost isn't set up in /etc/hosts. I don't know the circumstances when you don't want it there, but it could be that packages set up the hosts file as needed, and Romain just hasn't installed a package that needed the localhost name.

Thanks. I didn't know that, I thought that file was simply supposed to always be there and have at least this one line.

Unix hackers probably think it's just an unnecessary hassle: "why write localhost when I can write 127.0.0.1" ;)

Sure, Unix Hackers take that in their stride... Last weekend I was recompiling my (Linux) Window Manager after I had found and fixed a inconsistency at 4am, and yet I'm still no "Unix Hacker", they are a sort of mythical creature always a few steps beyond us, like "next week" is, as a concept :-). For the rest of us "localhost" is either clear where the IP isn't or at least one less mental step. I am personally in favour of naming everything that can be named, then using the name over the number, though that is admittedly a matter of style and what puts a strain on my brain others might find very easy. Anyway; solved, though this means there are examples that might not work on stock Ubuntu which is arguably a bad thing, even though it could be argued this is a Ubuntu issue, not a ChucK one. Yours, Kas.