Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

winhost='asio' unusual behaviour when using buffersize. #273

Open
agorangetek opened this issue Feb 3, 2024 · 2 comments
Open

winhost='asio' unusual behaviour when using buffersize. #273

agorangetek opened this issue Feb 3, 2024 · 2 comments

Comments

@agorangetek
Copy link

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.

@agorangetek
Copy link
Author

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 '='

@agorangetek
Copy link
Author

After doing more tests, the buffersize parameter is not working as it should for any of the windows host types.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant