Pressing "Stop" doesn't stop the sounds about rsound HOT 8 OPEN

It's not clear to me what the right thing here is. In particular, as I understand it, the "stop" button currently means "raise an exception on the user's computation, and return control to the REPL. If I run (play long-sound), then the evaluation of this expression returns immediately to the REPL, while the sound plays.

Put differently, It seems like hitting the "stop" button when the cursor is at the REPL prompt is currently a no-op, and it seems like changing that behavior might be difficult to implement or have unforseen consequences.

However, you could always call the '(stop)' function...

from rsound.

Can you spawn a thread that kills the sound on stop? It seems like this ought to be already possible in DrRacket. @rfindler, any thoughts?

from rsound.

Stop breaks the thread. Rsound's prims just enquque the sounds to some
other thread I guess?

Do sounds stop when there are runtime errors?

Robby

On Monday, September 22, 2014, Sam Tobin-Hochstadt [email protected]
wrote:

Can you spawn a thread that kills the sound on stop? It seems like this
ought to be already possible in DrRacket. @rfindler
https://github.com/rfindler, any thoughts?

—
Reply to this email directly or view it on GitHub
#12 (comment).

from rsound.

No, they don't. Getting that right seems a bit fiddly, seems like I'd have to rewrite #%top or something.

from rsound.

I guess the question is how do you want to decide how to stop a sound. What
is the criterion that's best to use? The prompt appearing?

On Monday, September 22, 2014, John Clements [email protected]
wrote:

No, they don't. Getting that right seems a bit fiddly, seems like I'd have
to rewrite #%top or something.

—
Reply to this email directly or view it on GitHub
#12 (comment).

from rsound.

I think the confusion here is that pressing the stop button in DrRacket seems to do nothing if the repl is waiting for user input. It doesn't even clear the current line of text like the command line repl does. If DrRacket does not throw an exn:break?, there is nothing really for RSound to catch in order to know when to kill the sounds.

Regardless, I think that the sounds should not stop playing on a user-break. RSound is awesome to use for live synth coding, and sounds persisting on a user-break is really necessary for creating music via the repl.

However, I should add that when I first began using RSound about a year ago (I was new to Racket at the time), lack of sound stopping in DrRacket confused me for a while too. Maybe the solution to this issue is discussing behavior early in the documentation, including why it is beneficial to the library for it to remain this way.

from rsound.

from rsound.

Ah, thanks! It's helpful to know DrRacket works as such.

from rsound.