feature: add settings to disable sounds and delays in callouts

[RDMurray]

Sounds can be useful, but they can also get annoying. the callouts also have delays inserted. There should be settings for both of them.

[steinbro]

By "delay" do you mean the time inserted to prevent the sound effect from overlapping with the speech? I can't think of a reason you'd want to keep the delay if the sound effect were disabled.

I'm also imagining a mode of just sound effects and no speech. Probably not an option to enable, but I'd still be curious what that experience would be like, particularly for partially-sighted users. "Something nearby is worth knowing about, but I won't tell you what."

[JJGatchalian]

Also, where should the option to disable sounds be located? If we're just talking about the sounds for the callouts, we could put it under Manage Callouts. But if we're talking about all sounds across the board, it could be listed under General Settings.

[RDMurray]

@steinbro There's additional delay inserted between callouts, which can make it feel quite sluggish.

@JJGatchalian I was thinking mainly about the callout related sounds. The beacon can already be muted and the only other one I can think of is street preview. Street preview can be frustratingly slow while you listen to all the unnecessarily long sounds but I think that's a different issue.

[JJGatchalian]

Since these are sound effects specific to callouts, I feel that the most logical place to put the toggle switches is within Manage Callouts, probably right after "Allow Callouts". The labels could be "Sound Effects" and "Delays". Here's my attempt at the accessible hints. Sound Effects, "Sounds that play before the spoken messages". Delays, "Short pauses between callouts". We could also put these switches towards the end of the list, right before "Repeat Callouts".

[MBtheOtaku]

If no one else is working on this I can look into it

[YCK03]

I have this issue completed on PR 250 could someone check and authorize it?

[YCK03]

I have made another pull request here, for the issue please review PR259

[JJGatchalian]

It looks like there are two different pull requests to resolve this issue. Probably the better solution is to use the one that is based on the newest main branch. Many of the storyboards have already been removed, and trying to merge an older branch with the storyboards that no longer exist may not make sense anymore. In addition, it may be a good idea to close any pull request for the "Redundant Language" issue before I close that issue because the new Swift UI implementation should already fix the language issue (correct me if I'm wrong).

[RDMurray]

Yes the Language and Region fix is already in with the swiftUI implementation. I'll take a look at the two PRs when I get a chance.

It's best to stick to just one fix or feature in a PR. That way it can be reviewed quicker and merged independently of other changes.

[JJGatchalian]

Since the Language and Region issue was already fixed in the main code, I'll close the issue right now. Thanks.Sent from my iPhoneOn Apr 16, 2026, at 13:01, RDMurray ***@***.***> wrote:RDMurray left a comment (soundscape-community/soundscape#226) Yes the Language and Region fix is already in with the swiftUI implementation. I'll take a look at the two PRs when I get a chance. It's best to stick to just one fix or feature in a PR. That way it can be reviewed quicker and merged independently of other changes. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>

[YCK03]

PR259 is my active implementation, I closed my other Pull Request yesterday. I am happy to address any feedback.

[JJGatchalian]

The two pull requests I was referring to were 258 and 259. I wasn't talking about an older pull request that got taken down. I believe that the problem with 259 is that it fixes 240, but that issue had already been resolved in the main code when Pull Request 255 got merged. Besides, I had to close Issue 240 for that reason. Also, Pull Request 247 may not be necessary anymore because 258 is the second attempt of resolving this issue.