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

Regarding default sounds #247

Closed
Mohamed00 opened this issue Aug 16, 2018 · 14 comments
Closed

Regarding default sounds #247

Mohamed00 opened this issue Aug 16, 2018 · 14 comments

Comments

@Mohamed00
Copy link
Contributor

Mohamed00 commented Aug 16, 2018

From multiple threads on Twitter, I've noticed that one of the primary issues people have with TWBlue is the default soundpack. Many people have said that the current soundpack is loud, clangy and rather intrusive. And in my opinion, I agree, and I believe we need a much better soundpack as the default. Yes, the soundpack in use can be changed, absolutely, but the current one creates a negative first impression and affects people's judgement of the quality of the project. I think we need to remove the current default soundpack entirely and replace it with a new pack, with quieter and more subtle sounds. Thoughts?

@Menelion
Copy link
Contributor

I tend to agree. I wouldn't say it's too loud, though, for me the volume of the sounds is too different (there are loud sounds like the greeting sound and there are too quiet sounds like the top/bottom of the buffer sound).

@codeofdusk
Copy link
Contributor

codeofdusk commented Aug 16, 2018 via email

@Mohamed00
Copy link
Contributor Author

Yeah, that soundpack is actually not that bad. Maybe it should be the default again.

@manuelcortez
Copy link
Member

Sounds a good idea. I think we should do that and see what will happen in snapshots, as usual.

@Mohamed00
Copy link
Contributor Author

Though I think some of the sounds in that pack could be better, such as the like tweet, new follower and mentions sounds. Also the audio tweet sound should be converted to mono, it's panned a bit to the right for some reason and that seems really out of place.

@manuelcortez
Copy link
Member

@Mohamed00 do you know howto do that? I don't know anything regarding sounds, to be honest.

@Mohamed00
Copy link
Contributor Author

Yes. I'll convert it in a bit.

manuelcortez added a commit that referenced this issue Aug 19, 2018
Convert audio.ogg in classic soundpack to mono #247
@manuelcortez
Copy link
Member

Regarding a possible new default soundpack, What about the one created by Andre Louis? If you can give it a try and let me know your thoughts, it's at This link. I've asked him and he said he is agree in making his pack the default, in case everyone here is agree. Personally I liked it and think it can be what we need.

@codeofdusk
Copy link
Contributor

codeofdusk commented Aug 25, 2018 via email

@Mohamed00
Copy link
Contributor Author

Mohamed00 commented Aug 25, 2018 via email

@manuelcortez
Copy link
Member

So:

  • Let's add the new pack as a new option,and ask everyone wether it should be the default in the next stable or it will keep being an option.
  • The "default"pack will be renamed to next-gen, if the new pack will be the default one.
  • Let's add an item in the help menu for sending everyone to the soundpacks section in the website.

@burakyuksek
Copy link

I think this default pack is better than the old one. Sounds more modern.

@codeofdusk
Copy link
Contributor

We should also be careful to avoid breaking user configs (if "default" is the configured sound pack before the update, change it to next-gen so current users aren't unexpectedly switched to the new pack).

@Mohamed00
Copy link
Contributor Author

Any updates on making the new pack the default?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants