Etienne Dechamps

`suggestedLatencySeconds` is only one third of the equation. The most important option is the backend, followed by buffer size. Have you tried experimenting with those? For example, I doubt there's...

I don't know. I don't care about latency as far as my personal use cases are concerned, so I haven't looked too deeply into the latency characteristics of FlexASIO. The...

I'm not surprised that WASAPI would invalidate devices when waking from sleep (especially USB devices which probably undergo something similar to a disconnection event). I would expect DirectSound to better...

Do you mean your mic gets muted *system-wide*? That shouldn't happen, unless perhaps you were using the mic in FlexASIO with an exclusive backend (WASAPI Exclusive or WDM-KS).

By "mid stream" did you mean it happened outside of your computer waking up from sleep? If so, can you file a separate ticket and try to [get a log](https://github.com/dechamps/FlexASIO#logging)...

@Kurausukun if you have time, do you mind answering the following questions: 1. Can you confirm it's the `sampleType = "Int24"` option that's causing Pro Tools to crash? That's not...

Reproducing locally with Pro Tools First 2019.6.0, the following configuration: ``` [output] sampleType = "Int24" ``` Doesn't make Pro Tools crash, but the sound signal on the output is garbage....

I'm unable to reproduce with FlexASIOTest, REW, and Max MSP. I am therefore going to treat this as a Pro Tools bug.

I just realized that this problem can also be triggered by automatic sample type detection in WASAPI Exclusive mode if input and output devices have different "native" sample types, which...

Here's the simplest possible setup that can still reproduce: ```toml bufferSizeSamples = 1024 [input] channels = 1 sampleType = "Int16" [output] channels = 1 ```