Support for word lengths longer than 16 bits and multichannel would also be very welcome.
Best regards, John ________________________________ From: sound-dev <sound-dev-boun...@openjdk.java.net> on behalf of Izmar Verhage <izmaelverh...@gmail.com> Sent: 01 March 2020 14:28 To: Sergey Bylokhov <sergey.bylok...@oracle.com> Cc: sound-dev@openjdk.java.net <sound-dev@openjdk.java.net> Subject: Re: <Sound Dev> WASAPI Hi Sergey, My hope is to get lower latency audio. However, after reading up on DirectSound and WASAPI(shared) I'm becoming skeptical that this is possible, due to both going through a Windows software mixer before going to the hardware, which is an impediment to low latency audio. I'll try to write some tests in C/C++ to measure performance of DirectSound vs WASAPI(shared). On Thu, Feb 13, 2020 at 9:06 AM Sergey Bylokhov <sergey.bylok...@oracle.com<mailto:sergey.bylok...@oracle.com>> wrote: Hi Izmar, You are very welcome to the OpenJDK team! And thank you for sharing your ideas on how to improve JavaSound. Before you start, could you tell us more about WASAPI(shared)? What are the advantages over DirectSound? I am not sure we can use WASAPI(exclusive) and block everything else on the system. On 2/9/20 12:32 am, Izmar Verhage wrote: > I recently joined OpenJDK after concluding that the Java Sound API seems to > have no way to speak WASAPI. In the OpenJDK sources that I checked I was only > able to find PLATFORM_API_WinOS_DirectSound.cpp and no WASAPI variant of a > similar file. > > To my knowledge WASAPI should give us much lower latency than DirectSound, > regardless of whether shared or exclusive WASAPI mode is used. > > Additionally DirectSound has been deprecated for quite some time. > > If the only impediment to have WASAPI is that someone should build it, I > would like to work on this. -- Best regards, Sergey.
