-
Notifications
You must be signed in to change notification settings - Fork 102
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
Audient ID4 Confirmation #295
Comments
Thank you for the confirmation. I've linked the entry on the list to this issue. 👍 I did notice you're using a 512 sample buffer size for your input. Since your config is set to use the driver preference, you can use your interface's control panel to decrease this in order to achieve better latency. |
Thanks for information. I will look into this. 👍 |
My iD4 mk2 should be set to second channel input being "input channel=1" |
Thank you everyone for your combined efforts, I got it working finally:
I had "CustomBufferSize" at null but 256 has been working great, I am sure it cam go lower. |
@alexdmc93 you might be using the wasapi output there, it's unclear since you specify both |
So I am using my Audient ID4 as both Instrument input and headphone output. I changed When I tried using |
@alexdmc93 are you using RTC mode in the game, or microphone mode? Other than that, if you have problems with the output I'll only be able to help if you post your config and log. |
why not use ASIOforALL ? |
|
Audient id4 works well with rs_asio.
Product page : https://audient.com/products/audio-interfaces/id4/overview/
Config and log files : rs_asio_id4.zip
The text was updated successfully, but these errors were encountered: