You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have an SSL 2+ usb audio interface. Its control panel reports the buffersize when an app is using asio. If for example, the buffersize is set to 256 in the SSL control panel, when i start pyo with a buffersize of 256, the SSL control panel switches the buffer to 512. If i close and reopen pyo without changing anything, the buffer in SSL control panel increase to 1024. The same thing again to 2048. After that, it stays at 2048 because the device does not support anything higher. I think with Portaudio, you should be setting the 'Latency' parameter and leaving the buffersize parameter in the opensream to 0 for asio devices.
The text was updated successfully, but these errors were encountered:
I just test portaudio by itself and setting the buffersize for asio works as expected so ignore what i said about using the latency parameter. It seems that pyo is storing the buffer size and adding to it everytime it starts like a '+=' instead of '='
I have an SSL 2+ usb audio interface. Its control panel reports the buffersize when an app is using asio. If for example, the buffersize is set to 256 in the SSL control panel, when i start pyo with a buffersize of 256, the SSL control panel switches the buffer to 512. If i close and reopen pyo without changing anything, the buffer in SSL control panel increase to 1024. The same thing again to 2048. After that, it stays at 2048 because the device does not support anything higher. I think with Portaudio, you should be setting the 'Latency' parameter and leaving the buffersize parameter in the opensream to 0 for asio devices.
The text was updated successfully, but these errors were encountered: