04-12-2020, 07:14 PM
Dimitri wrote: IMHO there is no such thing as "Mac drivers" for Behringer (or any interface). It is all handled by coreaudio. (maybe not very well but it is what it is ...)
Thinking about it more, even if there are "Behringer drivers", they would be optimized for the hardware into the Core Audio backbone. It probably would not change how the JamKazam application gets data from the Core Audio. Existence of "drivers" or not, problem will still exist, I can't choose the sample rate at the audio interface setup window. Maybe I'm wrong about this, hopefully I'm wrong.
It's weird that in a JK session window, if you hover over your status light, there is something called "Gear Driver" that lists Core Audio. That implies that you can change it. Might not be true. Could just be from the application ported from Windows to Mac. I could see where it would be useful in Windows (if you had latency issues and this showed WDM instead of ASIO drivers, you could fix it). Not so useful in Mac if you have a choice of 1.
I can get my latency down by adjusting the sample rate up to 96K (in both JK and external software controls), then within a session, go to the top menu Manage, Audio Settings, Audio Booster, and setting the Audio FrameSize to 1ms experimental. I don't know if this is messing with stability, or if FrameSize is the same thing as sampling buffer size. Is it the hardware holding samples before sending it to the Mac computer (USB timing), or is it JK holding data before sending it out on the network (Ethernet timing)? I am still not down at Windows ASIO latency times or the measured latency in the Round Trip Latency tests I ran on the Mac.
Thinking about it more, even if there are "Behringer drivers", they would be optimized for the hardware into the Core Audio backbone. It probably would not change how the JamKazam application gets data from the Core Audio. Existence of "drivers" or not, problem will still exist, I can't choose the sample rate at the audio interface setup window. Maybe I'm wrong about this, hopefully I'm wrong.
It's weird that in a JK session window, if you hover over your status light, there is something called "Gear Driver" that lists Core Audio. That implies that you can change it. Might not be true. Could just be from the application ported from Windows to Mac. I could see where it would be useful in Windows (if you had latency issues and this showed WDM instead of ASIO drivers, you could fix it). Not so useful in Mac if you have a choice of 1.
I can get my latency down by adjusting the sample rate up to 96K (in both JK and external software controls), then within a session, go to the top menu Manage, Audio Settings, Audio Booster, and setting the Audio FrameSize to 1ms experimental. I don't know if this is messing with stability, or if FrameSize is the same thing as sampling buffer size. Is it the hardware holding samples before sending it to the Mac computer (USB timing), or is it JK holding data before sending it out on the network (Ethernet timing)? I am still not down at Windows ASIO latency times or the measured latency in the Round Trip Latency tests I ran on the Mac.