element-hq / element-hq/element-web
Has the Voice Message codec or processing changed recently ?
- Dominant language
- TypeScript
- Stars
- 13.5k
- Forks
- 2.8k
- PR merge metrics
- PR metrics pending
Description
### Steps to reproduce
1. On the web app in a conversation (I only have bridged conversations with bots)
2. I start recording a voice message
3. It records alright and sends itself
### Outcome
#### What did you expect?
I think I remember not long ago but the sound seemed almost uncompressed with no major artifacts, this is what I would expect.
#### What happened instead?
The audio is seriously lacking bass and is often getting major artifacts that completely distort the voice, especially when there's a bit of background noise. It seems that there's some sort of noise removal activated, that wasn't here before or maybe I didn't notice but I doubt that.
Is there a way to choose the codec settings for the voice messages, especially the processing part ? At least to remove the noise reduction. I use a professional headset processed in a professional mixer with standard broadcast/radio tools, with monitoring activated. This is not an issue on the input audio side.
### Operating system
Windows 11 22H2
### Browser information
Rambox 2.0.10 so Electron/Chromium but not sure where to find the Version
### URL for webapp
Private server
### Application version
Element version: 1.11.20 Olm version: 3.2.12
### Homeserver
Synapse 1.76.0 (pretty sure)
### Will you send logs?
Yes
Contributor guide
Research direction
No source files or tests are named. Start by reproducing voice-message recording in the web app using the reported Electron/Chromium environment, then trace the recording, codec, and processing path to identify any changed noise reduction or encoding behavior. Done means the cause is identified and the expected voice quality is restored or codec-processing options are clearly exposed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- electron, typescript
- Domain
- audio-video-rtc, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100