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

notes may hang in NodeProxy when using synth def names (symbols) #1246

Closed
telephon opened this issue Nov 9, 2014 · 6 comments
Closed

notes may hang in NodeProxy when using synth def names (symbols) #1246

telephon opened this issue Nov 9, 2014 · 6 comments
Labels
bug Issues that relate to unexpected/unwanted behavior. Don't use for PRs. comp: class library SC class library

Comments

@telephon
Copy link
Member

telephon commented Nov 9, 2014

// hanging notes
n = NodeProxy.audio(s, 2);

(
n.put(2, \default);
n.put(2, \default);
)
s.queryAllNodes;
// this works

n = NodeProxy.audio(s, 2);

(
n.put(2, { SinOsc.ar(440) * 0.1 });
n.put(2, { SinOsc.ar(440) * 0.1 });
)
s.queryAllNodes;
@telephon telephon added bug Issues that relate to unexpected/unwanted behavior. Don't use for PRs. comp: class library SC class library labels Nov 9, 2014
@adcxyz
Copy link
Contributor

adcxyz commented Nov 10, 2014

still get hanging notes with this,
on brand new symlinked build:

// hanging notes
n = NodeProxy.audio(s, 2);

(
n.put(2, \default);
n.put(2, \default);
)
s.queryAllNodes;

@adcxyz adcxyz reopened this Nov 10, 2014
@telephon
Copy link
Member Author

Ah ok, now I know -- it must have to do with the non-freeing of envelopes. The \default SynthDef uses a normal Envelope which is subject to that, well, "specification problem". There is a solution in EnvGate, so maybe have a look if it goes away for SynthDefs which do their release in this way.

@telephon
Copy link
Member Author

For reference: the solution is to add an initial impulse to the gate value:
gate = gate + Impulse.kr(0)

@telephon
Copy link
Member Author

related: #1063

@LFSaw
Copy link
Member

LFSaw commented Dec 24, 2014

Is the intrusion mentioned in b573dfd considered too intrusive?
Otherwise, I'd like to merge this with HEAD

@telephon
Copy link
Member Author

should be ok as far as i can see

@LFSaw LFSaw closed this as completed in 0945701 Dec 25, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issues that relate to unexpected/unwanted behavior. Don't use for PRs. comp: class library SC class library
Projects
None yet
Development

No branches or pull requests

3 participants