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.

Sign up for GitHub

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

Jump to bottom

OSCpathResponder broken, needs fix like OSCresponderNode #113

Closed
jleben opened this issue May 6, 2012 · 0 comments
Closed

OSCpathResponder broken, needs fix like OSCresponderNode #113

jleben opened this issue May 6, 2012 · 0 comments
Labels
bug Issues that relate to unexpected/unwanted behavior. Don't use for PRs. comp: sclang sclang C++ implementation (primitives, etc.). for changes to class lib use "comp: class library"

Comments

@jleben
Copy link
Member

jleben commented May 6, 2012

[Issue migrated from SourceForge | ID: 2930691 | Submitted by 'danstowell']
[http://sourceforge.net/support/tracker.php?aid=2930691]

OSCresponder and OSCresponderNode were recently updated to detect messages with-or-without a slash at first. OSCpathResponder needs similarly updating. Various things fail otherwise, such as:

s.boot;
{SinOsc.ar}.loadToFloatArray(0.3, s, {"GOT IT".postln}) // Message never posted, though it should be

(This is with svn rev 9674)
@jleben jleben closed this as completed May 6, 2012
mossheim pushed a commit that referenced this issue Aug 24, 2020
Merge pull request #113 from supercollider/topic/bleeding-edge
759e70b 
Downloads: link to develop branch builds
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Issues that relate to unexpected/unwanted behavior. Don't use for PRs. comp: sclang sclang C++ implementation (primitives, etc.). for changes to class lib use "comp: class library"
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jleben