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

Customize ringing/notification sound #5891

Open
Luraktinus opened this issue Dec 28, 2017 · 134 comments
Open

Customize ringing/notification sound #5891

Luraktinus opened this issue Dec 28, 2017 · 134 comments
Assignees
Labels
A-Notifications A-VoIP O-Occasional Affects or can be seen by some users regularly or most users rarely T-Enhancement X-Needs-Design X-Needs-Product More input needed from the Product team Z-GetYourUpdates

Comments

@Luraktinus
Copy link

Some users (including me) find this high pitched sound unappealing, please let the users change it or go an octave lower.
thank you
--Lue

@lampholder
Copy link
Member

I wonder - do fb messenger/web whatsapp/slack let you configure notif sounds? Or do they just pick a more universally appealing sound?

@lampholder lampholder changed the title Feature request, change notification sound Feature request, change ringing/notification sound May 30, 2018
@hdoupe
Copy link

hdoupe commented Sep 17, 2018

What's the status on this issue? My colleague and I are testing out the app. It's great so far, but this noise gives me a mini-heart attack every time I get a message.

cc @andersonfrailey

@NintendoManiac64
Copy link

NintendoManiac64 commented Oct 16, 2018

If you're OK with manually doing the process every single time Riot updates, then you can at the very least manually replace the "message.mp3" and "message.ogg" files found at the following location on Windows:

%localappdata%\riot\app-0.17.0\resources\webapp\media

(replace the "0.17.0" text with whatever the newest version of Riot is at any given time; I find it easier to just go to "%localappdata%\riot" instead and then just manually click through the folders from there)

@turt2live turt2live added the Z-Community-PR Issue is solved by a community member's PR label Apr 27, 2020
@itay-grudev
Copy link

itay-grudev commented Apr 27, 2020

Here is a link to the newly proposed sound:

⏯️ Ringtone by Baptiste Gelez

⏯️ Current ringtone (for comparison)

@Maffsie
Copy link

Maffsie commented May 25, 2020

I'm in agreement here, the current notification sound for new messages gives me a not-insignificant amount of anxiety every time I hear it, which means I miss notifications because I need to have the sound turned off. Please give users the option of choosing their own tone without having to reapply a manual file swap on every (frequent!) Riot update.
@itay-grudev Those audio files appear to be for an incoming call, not for a notification of a new instant message. This issue covers both the ringtone (incoming call) and the notification tone (new message); the linked PR should not close this issue.

@Bandie
Copy link

Bandie commented May 25, 2020

For Arch Linux users:
You can manually change out/patch the files in /usr/lib/riot/webapp/media/

@t3chguy
Copy link
Member

t3chguy commented May 25, 2020

/usr/lib/riot/webapp/media/

Sounds like you're using some unofficial distribution, official one stores its files in /opt/riot-desktop/

@Bandie
Copy link

Bandie commented May 25, 2020

@t3chguy Well, it seems the package maintainer decided to put things there.
(I use arch btw. >:) )

@t3chguy

This comment was marked as off-topic.

@Bandie

This comment was marked as off-topic.

@lectrode
Copy link

IMHO, the proposed ringtone is much better than the current. Has a decision been made on whether or not to switch to it?

@domoritz
Copy link

domoritz commented Mar 8, 2021

Besides changing the default, it would be nice to allow people to choose a sound. That was in #6776 and merged into this issue.

@monstro1

This comment has been minimized.

@DanH42
Copy link

DanH42 commented May 9, 2021

I wonder - do fb messenger/web whatsapp/slack let you configure notif sounds? Or do they just pick a more universally appealing sound?

For starters, none of them uses such a LOUD notification sound. When my system volume is set such that everything else (notifications, videos, etc) is a comfortable volume, an Element notification is borderline painful it's so loud. I have to keep the tab muted and rely on visual cues to tell when I've gotten a message.

A volume control would be great, but custom notification sounds would also allow for an easy workaround that would also satisfy others who don't like the sound itself, regardless of how loud it is.

@caniko
Copy link

caniko commented May 19, 2021

Why can't we select from a list of ringtones? Why just one default tone?

Please hurry up with the solution, I get anxious every time somebody calls me 🍡 (no need to hurry, just trying to be lighthearted)

@monstro1

This comment has been minimized.

@igeljaeger

This comment has been minimized.

@ShadowJonathan
Copy link
Contributor

For what it's worth, there's some more information here: matrix-org/matrix-react-sdk#4500 (comment)

While this may be a marked improvement, we wouldn't like to merge this into the project as is. This clashes with some notification work we're (@matrix-org/design) doing internally and any updates to the sounds would have to be part of a pack with variations for multiple contexts, rather than just one sound being changed arbitrarily.

...

As the Design team mentioned above that they'd like to handle this as part of reworking notifications more generally, I don't think it makes sense to keep this open for the moment. We'll keep the sound in mind as we work on notifications.

TLDR; This is still happening, only it's part of the design team's (large) workload, which they'll get to in time. They've already done a lot of work recently to improve the look and feel of Element, most of which equally important as this, so this will happen sometime in the future, just be patient for a little while longer.

@ShadowJonathan
Copy link
Contributor

ShadowJonathan commented Jul 3, 2023

Alright, I have been understanding of Element's priorities for at least a long while now, but this has crossed my personal threshold for how much patience I have for this kind of corporate behaviour.

Since this is clearly not a priority, and still affecting a lot of users, either Element employees have gotten deaf or muted the sound themselves, or they simply don't care about accessibility like this, since there is clearly a breakdown of communication between those who prioritise, and those who consider user accessibility like this.

Therefore, I don't think that, in the end, Element cares about user accessibility, or user care, at all. Except for what looks good and what's flashy, given that this is still on the backburner, compared to other features and fixed being shipped left and right.

I understand Element's financial situation, but I have lost enough patience to care, and am now seeing this as a deficiency of theirs to not come back to the community on this.

@t3chguy
Copy link
Member

t3chguy commented Jul 4, 2023

either Element employees have gotten deaf or muted the sound themselves, or they simply don't care about accessibility like this

@ShadowJonathan you are aware matrix-org/matrix-react-sdk#9143 landed, yes? It'll be in today's release. Its not the final state of the situation but it resolves the primary complaint of volume.

I don't think that, in the end, Element cares about user accessibility

As someone who has personally spent many weeks both paid and unpaid working on accessibility you can rightly fact check yourself.

@KaKi87
Copy link

KaKi87 commented Jul 4, 2023

That's not enough.
Especially for a several years old issue.
We want what we actually asked for.

@offsetcyan
Copy link

If you've needed the feature for several years, you could always submit a PR

@piegamesde
Copy link

piegamesde commented Jul 4, 2023

@grxnola You mean like this? matrix-org/matrix-react-sdk#11078
(also allegedly there have been several PRs on that topic who either rot or got rejected, mine is far from being the first one)

@lectrode
Copy link

lectrode commented Jul 4, 2023

@ShadowJonathan you are aware matrix-org/matrix-react-sdk#9143 landed, yes? It'll be in today's release. Its not the final state of the situation but it resolves the primary complaint of volume.

While that is certainly a small step in the right direction (it took nearly an entire year just to accept a PR to reduce the volume of some of the sounds?! Wtf...), that does not resolve the primary complaint that the existing ring/notification sounds are jarring enough to wake the dead.

As someone who has personally spent many weeks both paid and unpaid working on accessibility you can rightly fact check yourself.

I don't think anyone is questioning work ethic of contributors - only the apparent strictness with which PRs and other improvements are adopted. A review and approval process is definitely a good thing, but there is such a thing as "letting the perfect be the enemy of the good". In this case, smaller improvements that provide a net benefit are rejected because there are projects "in the works" that will resolve something related.

That would be fine, except that those projects take years to complete (the supposed sound theming project has been in progress for over 7 years), leaving a gaping accessibility hole in the client for everyone during the interim. The proper solution for this would be to adopt a better ring and notification sound for now, and provide a refined/"perfect" sound theming solution later.

@epicEaston197
Copy link

Bro when I first heard the notification sound for ringing I thought my spaceship was under attack

@luixxiul
Copy link

luixxiul commented Aug 4, 2023

This is a cross-post from #5031 (comment) to let you guys know that schildichat, an Element-based client, has implemented an option to select a less stressful notification sound which should not be so jarring.

Screenshot_2023-08-03_07-08-45

The proper solution for this would be to adopt a better ring and notification sound for now, and provide a refined/"perfect" sound theming solution later.

@adamency
Copy link

adamency commented Sep 15, 2023

@daniellekirkwood

We are not looking at allowing folks the ability to personalise the sounds of Element as a whole.

Please explain the reasoning behind this decision ? You have simply stated this without ever explaining why this idea was rejected. I don't understand how changing a sound file on your own instance can be problematic.

@cknoll
Copy link

cknoll commented Oct 22, 2023

As I understand this issue will remain open quite a while. While I personally do not like the element sounds I can live with this becaus as a whole I really like the app.

Anyway it would be nice to have some collections of workarround in this issue. Some of the first messages discuss which files to change manually. I would like to do so but I use element via flatpak. If anyone knows how to exchange the media files inside a flatpak container, please let me know.

Update: At least I managed to get reading access to the actual media files:

  • on the host system: flatpak run --filesystem=home --command=bash im.riot.Riot
  • inside the flatpak bash: cp /app/Element/resources/webapp.asar /home/myuser
  • on the host system in your homedir: npx asar extract webapp.asar webapp.asar.unpacked

Remaining steps:

  • exchange media files (e.g. use /usr/share/sounds/Oxygen-Im-Phone-Ring.ogg from KDE (path might be debian specific))
  • recreate compressed file webapp.asar
  • copy that file to the correct location such that flatpak run im.riot.Riot will use it.

@daniellekirkwood
Copy link
Contributor

@daniellekirkwood

We are not looking at allowing folks the ability to personalise the sounds of Element as a whole.

Please explain the reasoning behind this decision ? You have simply stated this without ever explaining why this idea was rejected. I don't understand how changing a sound file on your own instance can be problematic.

We will be reviewing sound as a holistic topic across our product set in the future. Until then, we are focussing our efforts on gnarly bugs, things such as stuck notifications and threads issues.

When we get to reviewing Sound and our notifications interactions as a whole we'll aboslutely consult folks here and take all of this feedback into consideration.

Please bear in mind: There are a lot of switches and customisations in our product and this makes Element harder to use for many people. We are trying to reduce the number of customisations in the product and re-introduce them purposefully with the right level of consideration and feedback.

@cknoll
Copy link

cknoll commented Oct 24, 2023

We will be reviewing sound as a holistic topic across our product set in the future.

I, personally understand this approach. After all I use element as a free product and I do not have any right to arrogate specific features or to decide how to prioritize development.

On the other hand the developers should keep in mind that sound is an emotional topic and sounds which are perceived as "bad" can alienate users much more than some (minor) bugs. I think the general problem is that people in this issue are probably not affected by other bugs and issues and see the sound problem as the one big thing. Therefore, they lack understanding why this takes so long (issue open since 2017).

I think, compiling some comunity-contributed tutorials for workarounds (like manually changing the sound files) would help here. Because people who are really passionate about this topic then would have another option then just wo wait (or abandon element).

@adamency
Copy link

Please bear in mind: There are a lot of switches and customisations in our product and this makes Element harder to use for many people. We are trying to reduce the number of customisations in the product and re-introduce them purposefully with the right level of consideration and feedback.

I can understand this. However, couldn't we set a default and then simply allow in settings to modify the sound if wanted ? This wouldn't add another necessary configuration option and still allow folks to change the sounds if they want to.

TLATER added a commit to TLATER/dotfiles that referenced this issue Nov 9, 2023
Just can't take the notificaiton sounds anymore, and
element-hq/element-web#5891 is going nowhere.
@Californian
Copy link

@daniellekirkwood
Please bear in mind: There are a lot of switches and customisations in our product and this makes Element harder to use for many people. We are trying to reduce the number of customisations in the product and re-introduce them purposefully with the right level of consideration and feedback.

I think this is the main point of tension, but I totally understand where you're coming from from a product perspective: 90%+ of users will never change a default notification sound, but all users might see the clutter that would come from adding a UI for the option!

"Customization reduction" is, however, is a terrifying thing for any power user to ponder and, depending on implementation, risks significant user churn among the most active users and advocators of the product.

There is, however, a very common UX pattern for dealing with this tension that I sincerely hope you're adopting (for this issue and in general): an "advanced"/"developer" mode. Let power users tinker and change stuff in a maximalist settings screen world, let normal users get their messages reliably without clutter. It's really the best of both worlds! It's already in use in some sections of the UI, but a global toggle (or settings-tab-level toggles, but not the current intra-tab, section-level toggles) would do wonders to reduce cluter while still allowing for the flexibility of contributions like the PRs enabling users to choose a different sound.

Just my 2 cents!

@ThiefMaster
Copy link

"Customization reduction" is, however, is a terrifying thing for any power user to ponder and, depending on implementation, risks significant user churn among the most active users and advocators of the product.

Yes. I had to restrain myself not to write a much more strongly-worded comment as a reply to this quote (which I hadn't seen before). Because I'm fucking sick of applications dumbing down their stuff all the time, and every time they do this I tend to use some feature/switch which I found very useful.

Just have a simple set of basic settings for "normal users". Good defaults, and easy to change those where the defaults may not be everyone's liking (ctrl+senter vs enter to send for example - all the messengers like Skype that removed this added it back ;))

And then as @Californian suggested hide the rest under some "advanced settings" toggle. Maybe not as crazy as about:config in Firefox, but just so power users can still customize things...

@KaKi87
Copy link

KaKi87 commented Nov 15, 2023

Concretely : what in the world do we have to do to get this feature now ?!

@eslerm
Copy link

eslerm commented Nov 15, 2023

Concretely : what in the world do we have to do to get this feature now ?!

Community requests for accessibility will likely continue not being a priority #5031.

If you work for an organization or government which is considering hiring or granting money to Element.io or Matrix developers, make sure their sales reps know that accessibility issues, like this, are important.

@Bugsbane
Copy link

Bugsbane commented Nov 22, 2023

Take a listen to the ringtone here:
https://freesound.org/people/Thoribass/sounds/254822/

The player has a "loop" option, just click the refresh-page-like, two arrows in a circle icon.

I think most people would prefer this to the current sound, and it's already permissively licensed (CC-BY). It's certainly much less stress-inducing!

@azymohliad
Copy link

I would really like an option to set a custom ringtone. I startle every time I get an unexpected call in Element. I would really want a ringtone that starts quietly and then ramps up in 10 seconds or so. On the phone I might prefer a faster ramp up time, but on desktop I'm often in my headphones. I guess there's no one size fits all here with a predefined ringtone, and a customizable one would be really really useful.

@ShadowJonathan
Copy link
Contributor

Happy belated 6-year issue birthday, by the way.

@VermiumSifell
Copy link

I really think this feature should be implemented, will probably make more power users ask more friends to join the Matrix world too.

@sl5net
Copy link

sl5net commented May 10, 2024

90%+ of users will never change a default

Having separate simple and advanced options menus is a great way to cater to both beginner and experienced users in your app.

Simple Menu:

  • Focus on the most essential functionalities.

Advanced Menu:

  • Offer more granular control. This could include different sounds.

@autoteelar
Copy link

autoteelar commented May 12, 2024 via email

@sircoderin
Copy link

sircoderin commented Jul 22, 2024

Can we please have an update on this? Me and my friends literally avoid using Element because of the horrifying ring tone. Would it be ok to create a PR ourselves implementing a custom ring sound?

@noideastowork
Copy link

Where can I find the notification sounds on macOS so that I can replace them myself?

@0xilly
Copy link

0xilly commented Oct 10, 2024

Is there any update on this or could the element come out with an official statement that they're not working on fixing this and close the issue so we can move on it's been over six years and it's unacceptable at this point and alternatives were given matrix-org/matrix-react-sdk#4500, matrix-org/matrix-react-sdk#10494 and closed without thought. I'm starting to regret the money I've donated to matrix I'm tired of the excuse train please please please fix this already.

@RubensRainelli
Copy link

RubensRainelli commented Nov 25, 2024

I wonder - do fb messenger/web whatsapp/slack let you configure notif sounds? Or do they just pick a more universally appealing sound?

They use a more appealing one.

The actual notification sound of Element is quite similar to System Error in Linux or Windows or Mac, I don't remember which one.

There should be even more options like multiple different sounds, like:

  • reply or direct message and tagging
  • @room messages and multiuser messages.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Notifications A-VoIP O-Occasional Affects or can be seen by some users regularly or most users rarely T-Enhancement X-Needs-Design X-Needs-Product More input needed from the Product team Z-GetYourUpdates
Projects
None yet
Development

Successfully merging a pull request may close this issue.