[05:56] <OvenWerks> Eickmeyer: Bug #1909030 does not make sense being a studio-controls problem.
[05:57] <OvenWerks> maybe leave it for a week to see if they do attach the file I asked for before marking it invalid
[06:02] <OvenWerks> as a side note, having to run a USB device at 4096 sounds like other problems. USB running at a lower priority than a mouse or video or something.
[16:05] <Eickmeyer[m]> OvenWerks: Looks like they replied, but it's 100% looking like a support issue and not a bug.
[22:29] <OvenWerks> Eickmeyer[m]: the issue does seem to be unique to discord.
[22:31] <OvenWerks> I think they have used opus as a streaming protocol (standard for html5) and decided that SRC was a waste of time because windows runs at 48k.... the same a OPUS
[22:31] <OvenWerks> and becasue windows includes builtin SRC in all of it's audio.
[22:33] <OvenWerks> Eickmeyer[m]: for reference: I was talking to someone in the Ardour forums who was upset that he could use Ardour at 44k1 in windows but not in Linux... the device description clearly described the device as 48k only but windows will make a device look like it can support any SR without telling the user "hey we had to SRC your sound to do that."
[22:36] <OvenWerks> Eickmeyer[m]: pulse uses a period size of 44100 :) but I have heard that internally they slide the point where they read the buffer to give various application the actual buffer size they ask for. This makes it look like 44k1 will work even with a 48k App. There may be a pop once in a while or a skip that is almost not noticed by the user... anyway they do odd stuff
[23:20] <Eickmeyer[m]> OvenWerks: Yeah, that sounds about right. FWIW, I have routed to Discord using the jack-pa bridge just fine, but there's always some latency that can't be avoided.
[23:21] <OvenWerks> Eickmeyer[m]: he was able to as well when he reduced the buffer size.