from the field, it seems that asking students to use headphones helps a lot, but not enough.
...they are all getting hung up on the recording quality. While it is better than it was with headphones, it still cuts in/out frequently, and has a very distorted quality, almost like it's under water. This does not happen when we test the mics on mictest.com. I'm wondering if the quality would even be assessable by myself and your team when it comes time- they are pretty bad.
I suspect that the mp3 compression is what's killing us. let's drop it to whatever the native thing is in browser (cursory exploration suggests it'll be ogg on ffox, webm in chrome, and mov on safari.
fwiw: (for devs) with ffmpeg installed, one might also have ffprobe and can check a file via
safari doesn't seem as agreeable (as ffox and chrome) to the audio element's src being a file with filename ending in wrong things (e.g. .txt) or unsupported things (e.g. .ogg) even though it seems able to play a file that's ogg-encoded, but just named as whatever.wav
from the field, it seems that asking students to use headphones helps a lot, but not enough.
I suspect that the mp3 compression is what's killing us. let's drop it to whatever the native thing is in browser (cursory exploration suggests it'll be ogg on ffox, webm in chrome, and mov on safari.
fwiw: (for devs) with
ffmpeginstalled, one might also haveffprobeand can check a file viasafari doesn't seem as agreeable (as ffox and chrome) to the audio element's src being a file with filename ending in wrong things (e.g.
.txt) or unsupported things (e.g..ogg) even though it seems able to play a file that's ogg-encoded, but just named aswhatever.wav