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
NEW INFO: After further investigations, I found a blunder in that an attempt was done to setSampleRate() after other calls like asioDriver.getChannelInput(i), which does not work.
Setting the samplerate as the first step, A4A will now accept 192.
However, the setting of samplerate = 0, which according to API should cause obedience to external sync, we could not get to work. This could be A4A since we were unable to set this value also from other (non-Java) DAWs. Case closed
Original text
While this and that ASIO driver + JasioHost is obedient to the input samplerate that the driver detects, for example 192, the ASIO4ALL driver (v2.14 as of 2017) will always report 44.1 on the getSampleRate(). There is a setSampleRate(), but is there another way to force the ASIO driver to always and automatically report on its output what it receives on its input?
The text was updated successfully, but these errors were encountered:
NEW INFO: After further investigations, I found a blunder in that an attempt was done to setSampleRate() after other calls like asioDriver.getChannelInput(i), which does not work.
Setting the samplerate as the first step, A4A will now accept 192.
However, the setting of samplerate = 0, which according to API should cause obedience to external sync, we could not get to work. This could be A4A since we were unable to set this value also from other (non-Java) DAWs. Case closed
Original text
While this and that ASIO driver + JasioHost is obedient to the input samplerate that the driver detects, for example 192, the ASIO4ALL driver (v2.14 as of 2017) will always report 44.1 on the getSampleRate(). There is a setSampleRate(), but is there another way to force the ASIO driver to always and automatically report on its output what it receives on its input?
The text was updated successfully, but these errors were encountered: