However, it's worth noting that #87 can still be reproduced with a power of 2 buffer size. This issue could possibly be related to #87. If I change the code so that FlexASIO advertises a 441-sample minimum buffer size with all backends, then the issue occurs with all backends. ![]() Supporting that hypothesis, Pro Tools will use a 64-sample buffer size if the advertised minimum size is smaller (which is true when using FlexASIO and a backend other than DirectSound), and it works fine in that case. That doesn't make a ton of sense and leads me to suspect Pro Tools is automatically selecting a buffer size that it doesn't actually support. But if the option isn't used, and FlexASIO advertises a minimum buffer size of 441 samples (10 ms at 44.1 kHz), then Pro Tools will use that buffer size, even though it's not a power of 2. One thing that's suspicious here is that, when explicitly setting bufferSizeSamples (which makes FlexASIO advertise the same minimum, suggested, and maximum buffer size), Pro Tools refuses to start with an error message if the size is not a power of 2. When the input is disabled, Pro Tools still behaves erratically and outputs garbage, but only when actually playing sound.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |