[Portaudio] Fwd: Re: Windows MME (Mobile compile fix + x64 type fix)
Ross Bencina
rossb-lists at audiomulch.com
Tue Dec 8 19:56:08 EST 2009
Hello Dmitry
Thanks for these, looks like you've been busy :-)
I will check in the WMME and DS patches but I don't build WASAPI here so we'll have to get someone else to review and check in the WASAPI patch. Hopefully David Viens has time (David?)
Thanks
Ross.
===================================
Perform, Compose, Mangle
AudioMulch 2.0 modular audio software for PC and Mac
http://www.audiomulch.com
----- Original Message -----
From: Dmitry Kostjuchenko
To: portaudio at music.columbia.edu
Sent: Tuesday, December 08, 2009 10:10 PM
Subject: [Portaudio] Fwd: Re: Windows MME (Mobile compile fix + x64 type fix)
Hello Ross,
Yes there were couple of patches actually.
So, here with I enclose cumulative patch for Windows MME, DirectSound, and WASAPI cores. The log of fixes can be as:
WMME:
- fixed compile for Windows Mobile platform (was compiled and tested under WM 6.0 SDK)
- fixed device names filling in case Unicode is enabled (Windows Mobile as we all know uses only Unicode API)
- fixed old issue (actually a repeated patch) with x64 platform problems were 64-bit pointers get casted to 32-bit integral type due to wrong DWORD_PTR define
- fixed IsFormatSupported not correctly operating for default device, resulting in distorted sound if user tries to open device with more channels than device can handle
DirectSound:
- fixes old issue (actually a repeated patch) with x64 platform problems were 64-bit pointers get casted to 32-bit integral type due to wrong DWORD_PTR define
- fixed IsFormatSupported not correctly operating for default device, resulting in distorted sound if user tries to open device with more channels than device can handle
WASAPI:
- completed support for Capturing, it works now
- improved Output support (better sized buffers, channels mapping)
- improved IsFormatSupported, it is correctly working for Input/Output
- provided low-level callback redirection for performance addicted applications
WASAPI can be enabled already as its Input/Output works normal. It only missing blocking operations, but my application is using callback mechanism so I do not have real testing application to test blocking operations and thus implementing it blindely for me is not really a good way of doing things. For me WASAPI is a default API for Vista+ platforms as it provides best performance and latency for my project.
A patch is an extraction from my working version from my project which uses PortAudio thus things are proven to be working ok and are tested with some time already.
It would be great if you could apply patch as keeping tracks of them is also a problem for me :)
Best regards,
Dmitry.
------------------------------------------------------------------------------
_______________________________________________
Portaudio mailing list
Portaudio at music.columbia.edu
http://music.columbia.edu/mailman/listinfo/portaudio
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://music.columbia.edu/pipermail/portaudio/attachments/20091209/21a1893a/attachment.html
More information about the Portaudio
mailing list