Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Connection Refused #30

Closed
developius opened this issue Nov 2, 2013 · 6 comments
Closed

Connection Refused #30

developius opened this issue Nov 2, 2013 · 6 comments

Comments

@developius
Copy link

Hi,

Whenever I booted up sonic-Pi and tried to play a sound, it always said:

/opt/sonic-pi/app/scripts/vendor/osc-ruby/lib/osc-ruby/client.rb:10:in `send’: Connection

refused – send(2) (Errno::ECONNREFUSED)
from /opt/sonic-pi/app/scripts/vendor/osc-ruby/lib/osc-ruby/client.rb:10:in send’ from /opt/sonic-pi/app/gui/../../app/scripts/run-code.rb:180:inblock in osc’
from :10:in synchronize’ from /opt/sonic-pi/app/gui/../../app/scripts/run-code.rb:178:inosc’
from /opt/sonic-pi/app/gui/../../app/scripts/run-code.rb:149:in clear_scsynth’ from /opt/sonic-pi/app/gui/../../app/scripts/run-code.rb:132:inreset_scsynth!’
from /opt/sonic-pi/app/gui/../../app/scripts/run-code.rb:41:in initialize’ from /opt/sonic-pi/app/gui/../../app/scripts/run-code.rb:225:innew’
from /opt/sonic-pi/app/gui/../../app/scripts/run-code.rb:225:in initialize’ from /opt/sonic-pi/app/gui/../../app/scripts/run-code.rb:320:innew’
from /opt/sonic-pi/app/gui/../../app/scripts/run-code.rb:320:in `’

However, yesterday, it suddenly started working, but now it doesn't again!
I'll be at the Junction workshop in Cambridge today, so maybe we could have a quick talk about it then?

I love this idea, and really want ot use it!

Thanks,
Finnian

@samaaron
Copy link
Collaborator

samaaron commented Nov 8, 2013

Hi Finnian,

if you're still interested in debugging this, it would help me if you were able to post your SD card so I can see if I can replicate your issue on one of my RPs. Unfortunately, I've not run into this specific bug myself.

If you're happy to do that, feel free to contact my directly by email: [email protected]

@dataknut
Copy link

as per the post on the google group, this is resolved. Fresh install of NOOBS etc and all working fine.

thanks
Ben

@whaleygeek
Copy link

Yeah, I raised this with alex bradbury and Sam when I was first looking at sonic pi, some of the installed packages on the older images don't work with Sonic Pi, I had to update to at least NOOBS 1.2 to get it to work. The wheezy image I was using was dated May 2013 and it seemed to be too old.

@samaaron
Copy link
Collaborator

I believe that this is an issue with running Sonic Pi on older versions of the Raspberry Pi OS. If this error is still occurring on the latest releases, please feel free to re-open this issue.

@whaleygeek
Copy link

I chatted this over with Alex a month or so ago and we came to a similar conclusion at the time, updating to NOOBS (from an old May2013 image) solved the problem for me. We did see this error at Pi club on Saturday, and I restarted the Pi and the problem went away and everything worked fine. This was NOOBS V1.3, which had been booted a couple of times before. I think it's right to leave this issue closed, but I suspect it's something to do with jackd or related server software not quite starting properly that leads to the Connection Refused message. Restarting Sonic Pi did not resolve it, we had to restart the Pi. But they everything worked fine. I'll keep a look out for it and report back if I find anything, but I've only seen this once in the field.

@samaaron
Copy link
Collaborator

Great, thanks for the feedback :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants