You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As of this writing, the bitrate is set to 1441Kbps, which is, apparently, uncompressed CD quality. For non-Safari browsers, we're using the Opus codec, which is the newer version of Vorbis, but I wonder if and how recording quality could be improved. Ideally we have some way to physically test this. When recording waves this week, the level was quite low so you could easily hear the compression. I'd like to have a sound source that I can quickly and easily test sitting at my desk and that causes the listener to hear the compression.
This task consists of:
Research codecs and recording quality settings that may be available starting with the links below
Write a plan to improve the quality of recordings starting with the most impactful changes
Create separate tasks for each improvement based on the plan
The MDN documentation is a bit misleading with regards to support for containers and codecs. Specifically, it suggests that webm is widely supported, as is mpeg. However, the audio types are not nearly as widely supported as the video types. Specifically, Safari only supports audio/mp4 while Chrome and Firefox only support audio/webm. Furthermore, I've been unable to find any information on specifying the codec for audio on Safari.
Using the Web Audio API might be the solution. It's unclear when the compression is applied: before the Web Audio API stuff or after? If it is after, maybe we can reroute the destination to a file without compression.
The text was updated successfully, but these errors were encountered:
As of this writing, the bitrate is set to 1441Kbps, which is, apparently, uncompressed CD quality. For non-Safari browsers, we're using the Opus codec, which is the newer version of Vorbis, but I wonder if and how recording quality could be improved. Ideally we have some way to physically test this. When recording waves this week, the level was quite low so you could easily hear the compression. I'd like to have a sound source that I can quickly and easily test sitting at my desk and that causes the listener to hear the compression.
This task consists of:
Links for research
Particularly useful for working with Gain, echo cancellation and noise cancellation
Alternate packages
Findings
The MDN documentation is a bit misleading with regards to support for containers and codecs. Specifically, it suggests that webm is widely supported, as is mpeg. However, the audio types are not nearly as widely supported as the video types. Specifically, Safari only supports
audio/mp4
while Chrome and Firefox only supportaudio/webm
. Furthermore, I've been unable to find any information on specifying the codec for audio on Safari.Neither browser natively supports lossless codecs of any kind with MediaRecorder.
Using the Web Audio API might be the solution. It's unclear when the compression is applied: before the Web Audio API stuff or after? If it is after, maybe we can reroute the destination to a file without compression.
The text was updated successfully, but these errors were encountered: