Good point! I didn't think about it. I would lean more toward one sound per batch because it can be annoying when you have multiple small cells. On the other hand, having a sound for each cells could provide more informative feedback (I'm thinking of the possibility of counting the cues for knowing which cell is currently being executed). There is also the option of having the user deciding it with an additional setting.

@roblourens we sort of encountered this with the build task audio cues and decided to just play one sound at a time instead of capturing the requests and playing them sequentially. #164921

Do the cells get run in parallel? I imagine they don't necessarily finish in order, so it could be pretty confusing for the user if multiple sounds play... for example:

Cell 1
Cell 2
Cell 3

Cell 2 succeeds
Cell 1 fails
Cell 3 succeeds

Could sound misleading given the order the cells appear in is not consistent w the order in which the noise gets played.

I've changed the behavior of the audio cues. Now the successful execution cue is played on the last cell scheduled, while the failed one always plays whenever a cell fails, since a failed execution interrupts the all the remaining scheduled ones.

Every other Audio Cues setting has values like this:

please match that pattern. I'm not hearing your audio cue, that's probably because I don't have a screenreader enabled currently, but I hear the others when setting them to On

I'm using the audioCues.taskCompleted cue for successful cells and audioCues.taskFailed for failed ones as proposed in the discussion of the issue. These audio cues must be enabled in the settings along with the newly added option in order to hear the sounds:

The checks for the 2 cues are done at the level of the audioCueService:

• Modify the audioCueService
• Create new cues with the same sounds (don't like to duplicate stuff tbh)
• Call playSound directly in the callback (but this would remove a bit of the abstraction provided by the service)

There is also the option to scrap the new setting completely since cell execution can be considered a "task", and, probably users who turn on the options would likely want to have cues played for notebooks.

What do you think? I'm open to every option.

A notebook cell is not a task. Looking at the code, there are more to audio cues than I thought- the notebook AudioCues should be registered with the others here:

so that they should show up in the "List Audio Cues" command like the others. This isn't duplicating stuff- notebook cell execution is its own feature and should be listed and controlled independently.

I've added the audioCues and removed the old setting. The settings for the cues will appear as audioCues.notebookCellCompleted and audioCues.notebookCellFailed in the settings. I've put the settings in the audioCues group instead of the notebook one because I've seen that the cues for other contribs such as the terminal or the debugger are in the audioCues group too.