[Portaudio] portaudio windows build - unicode versus multibyte char set versus not char set specified

Ross Bencina rossb-lists at audiomulch.com
Tue Nov 13 00:24:40 EST 2018

Dennis: The question is very applicable. It relates to how PortAudio 
marshals device names.

Steph: In principle it should be "seamless" but I don't think you can 
necessarily expect it to be bug-free with configurations other than 
those used in the shipped build files (e.g. cmake and msvs project file).

In general, PortAudio aims to deliver UTF-8 device names to the client 
irrespective of the build settings.


On 13/11/2018 7:28 AM, Dennis Towne wrote:
> AFAIK portaudio works on raw byte data, so the question isn't applicable.
> On Sun, Nov 11, 2018 at 8:11 AM Stephane Poirier 
> <stephane.poirier at oifii.org <mailto:stephane.poirier at oifii.org>> wrote:
>     Hi All,
>     Can portaudio library be built seemlessly specifying unicode char
>     set or
>     multibyte char set?
>     I am asking the pros before trying.
>     Steph

More information about the Portaudio mailing list