<div dir="ltr">Hi,<div><br></div><div>Interesting, someone has actually reported this in the past but Ive never been able to reproduce it. The two most likely explanations are either opening up a UDP listener port is forbidden by some security/firewall policy on your system (many OS's have started enabling these by default), or something else is using the port you are trying to create the OSC server on. </div><div><br></div><div>Im not sure how to test the former on Linux, but you can see if anything is listening on that port using netstat -lntu. If any of the ports on the local addresses (the part after : ) matches the OSC port you are trying to use, then that would be your problem- you can just use a different OSC port in ChucK in that case. </div><div><br></div><div>spencer</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jun 8, 2015 at 5:38 PM, <span dir="ltr"><<a href="mailto:ermina@studioplume.com" target="_blank">ermina@studioplume.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello,<br>
<br>
so far i have been chucking exclusively from within the miniAudicle (1.3.3).<br>
I am using the jack-enabled linux 64 bits version, on Linux Mint Betsy (which is mostly Debian 8).<br>
Today i wanted to try the command-line (chuck --loop and chuck + <a href="http://file.ck" target="_blank">file.ck</a>) and it seems the behavior of the VM is somehow different.<br>
Instantiating an OscIn object does not work in the cli, it returns: "OscIn: error: unable to create server instance".<br>
<br>
I was using the same version of chuck (1.3.5.0) as bundled with miniAudicle.<br>
Using -v9, the logs between chuck --loop and miniAudicle console are identical.<br>
If i start the VM in the miniAudicle (accepting network commands) and then use chuck + <a href="http://file.ck" target="_blank">file.ck</a>, <a href="http://file.ck" target="_blank">file.ck</a> is shredded correctly and OscIn created.<br>
<br>
That problem might be related to my config since on a second machine this error does not happen (1.3.4.0 64bits. I copied the chuck executable over to the first computer and the error was there again.<br>
<br>
<br>
Is there something obvious i am missing / should be looking for ?<br>
Thanks for your help.<br>
<br>
. e<br>
_______________________________________________<br>
chuck-users mailing list<br>
<a href="mailto:chuck-users@lists.cs.princeton.edu" target="_blank">chuck-users@lists.cs.princeton.edu</a><br>
<a href="https://lists.cs.princeton.edu/mailman/listinfo/chuck-users" target="_blank">https://lists.cs.princeton.edu/mailman/listinfo/chuck-users</a><br>
<br>
<br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div style="font-family:arial;font-size:small"><div>Spencer Salazar<br></div><div>Doctoral Candidate</div><div>Center for Computer Research in Music and Acoustics</div><div>Stanford University</div><div><br></div><div><a href="mailto:spencer@ccrma.stanford.edu" target="_blank">spencer@ccrma.stanford.edu</a></div><div></div><div>+1 831.277.4654<br></div><div><a href="https://ccrma.stanford.edu/~spencer/" style="color:rgb(17,85,204)" target="_blank">https://ccrma.stanford.edu/~spencer/</a><br></div><div><br></div></div></div></div></div></div></div></div></div></div>
</div>