![]() ![]() I'm not here to argue about what sample rates sound best. Discord should work with this set to 44.1 kHz, not to mention the fact that it should also extend an arm and do the tiny effort to additionally support 192 kHz. ![]() It's tangential to the conversation, this is a genuine bug that needs a fix, not an edge case where people have misconfigured hardware. If every other application can handle this device at 192 kHz, and Discord still cuts out and breaks even when I have it set to 44.1 kHz, there is really no reason to attack people who have high sample rate audio gear. Steam Voice uses Opus - the same codec as Discord - so the issue is strictly with Discord and is clearly completely remediable. Mumble can handle it just fine, as can Steam Voice. It's unbearable to have a device that has wonderful sound quality suddenly have horrible quality due to the random audio cuts only in discord. ![]() a 192 kHz parcel of audio) to the 44.1 kHz / 48 kHz that Discord may want to use. It'd also be trivial for the Discord App to downsample a high sample rate audio buffer (e.g. my Focusrite Scarlett Solo) still cut out constantly on Discord when set to 44.1 kHz. Irsl, that doesn't change the fact that people who have gear that ~can~ record with high sample rate (e.g. Except I know there are a lot of audiophile gamers who want their *cough of disapproval* 384kHz, 32-bit DACs to run Discord and games. It'd be easier if Discord could just do its own SRC between higher sample rates, but I suppose the demand is just too low. I could then patch the line outputs of that interface into spare line inputs of my main interface, and set up direct monitoring of those inputs so I'd hear then in my headphones. I could have the second interface run at 44.1 to send and receive through Discord. ![]() I suppose I could also plug in my backup audio interface, and just deliberately not sync the clocks. And my mic runs through my interface (Antelope Audio) to Discord, so it has to follow the same sample rate as my DAW session. It's pretty insane! But I'll have a Discord channel running alongside that, so that I can have video and two-way communication. I no longer need to route my session audio directly through Discord, as I use an audio plugin called Audiomovers Listento to stream low-latency multichannel PCM audio to people I work with. But it's often during this crucial pitch shifting phase that I need to communicate with my clients about their preferences, and for this (now more than EVER, in spring of 2020) I often use Discord. After pitch shifting, I return the project to 48k. But, I record vocals at high sample rates like 96 and 192 when I intend to do pitch correction and pitch shifting, because I find Melodyne and other similar pitch shifters produce much more believable results when they have access to those ultrasonic frequencies. I'm a huge proponent for consumer and audiophile gear not requiring over 48k sample rates, and even for most people not needing 24-bit depth! 16-bit is all most people need, even the most discerning listeners. I hear a clear difference between 44.1 and 48, but nothing above that. I agree, 48 is all I need for most situations. Just trust me when I say I am definitely the audio engineer who occasionally does need these higher sample rates. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |