JK keeps resetting Presonus buffer size to 16

[StuartR]

Terles - Block size of 16 is not optimal for my laptops with my audio interfaces when using JamKazam. I'm not here to debate this. You suggest to "look elsewhere" - can you suggest some resources?

I am asking this question in this forum because I suspect other Presonus users may have experienced this same issue. I see other posts from owners of other brands of audio equipment also complaining that JK keeps resetting their buffer sizes as well.

So the question remains (for JK itself as well as the JK community at large): Does anybody know of a solution that will prevent JK from changing my Presonus block size to 16 every time I start/enter a session (or hit resync)?

Thanks in advance for any constructive advice.

Have you tried setting the optimal buffer size using the ASIO control panel button while in the JK setup screen? Or is that what you are doing now?

Yes. The ASIO program and GUI is supplied by Presonus. It is called Universal Controller. Clicking 'ASIO Control Panel' inside of JK or any ASIO compliant application opens the Universal Controller as it should. I can change the buffer all I want but at as soon as I enter a session it is reset to 16. I can change it again even when in a session but then I see JK 're-initializing' my audio interface (or something to that effect - the message appears above the JK icon in the system tray but disappears quickly) and then the buffer is reset to 16 right before my eyes.

I know another person with same problem with JK and Presonus interface who could not get by this and instead abandoned JK and moved to another platform (where his equipment runs correctly).

Actually a buffer size of 16 with the correct sample rate provides excellent latency and audio quality for many audio interfaces. For example, a MOTU M2 provides a latency of just 3.5 msecs with a sample size of 41k and a buffer size of 16.

Well that's great - if I had a MOTU M2. Blocksize of 16 on these Presonus boxes at 41.1 or 48.0 sample rate does not provide consistent audio performance with JK. They work better at 64 or 128. The real issue is that the buffer keeps getting reset. Is it the new Presonus driver responding improperly to an 'ASIO reset' request from JK, or has JK only recently added an 'ASIO reset' to it's processing?

I am going to try the suggestion of first opening a DAW and "locking in" my ASIO settings before invoking JK. I shouldn't have to do this but first priority is to find a workaround. I would like to see the real problem - the reset - acknowledged or rebuked by a JK engineer who knows the codebase.

Let them know at: support@Jamkazam.com

Here's a quote from their knowledge base about the Prosonus USB96: "the Presonus Audiobox delivers 5ms latency for just $100, again with all the features you'd expect"