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
we have been successfully using JSyn as part of the Processing sound library with the precompiled JPortAudio bindings for both Mac and Windows available from the JSyn website. Since we want to add ASIO support we have tried to substitute the bundled Windows dll with other precompiled binaries that we found, but we have not been able to get the java bindings to work with any of them (see processing/processing-sound#87). Before we get started on compiling the Windows dlls ourselves we were wondering if there are any constraints on which version of the PortAudio API/codebase is compatible with the bindings, since we found no concrete information on this (and it seemed like some of the issues with other binaries that we tried had to do with v18/19)?
Many thanks,
Kevin
The text was updated successfully, but these errors were encountered:
So I suspect that the binary incompatibilities may be due to linker settings.
Building fresh binaries and JAR files is probably the best way to get a consistent set of libraries.
I normally build for Mac and Linux. So I cannot offer much advice for Windows/ASIO builds.
For build advice I would consult the PortAudio mail list. https://www.portaudio.com/contacts.html
Hello,
we have been successfully using JSyn as part of the Processing sound library with the precompiled JPortAudio bindings for both Mac and Windows available from the JSyn website. Since we want to add ASIO support we have tried to substitute the bundled Windows dll with other precompiled binaries that we found, but we have not been able to get the java bindings to work with any of them (see processing/processing-sound#87). Before we get started on compiling the Windows dlls ourselves we were wondering if there are any constraints on which version of the PortAudio API/codebase is compatible with the bindings, since we found no concrete information on this (and it seemed like some of the issues with other binaries that we tried had to do with v18/19)?
Many thanks,
Kevin
The text was updated successfully, but these errors were encountered: