Thanks. That's great news.

Cheers.


Clive Lansink
Email: Clive@Lansink.Co.NZ
Phone: +64 9 520-4242
Mobile: +64 21 663-999
Fax: +64 21 789-150

-----Original message-----
From: Michael Jerris <mike@jerris.com>
To: FreeSWITCH Users Help <freeswitch-users@lists.freeswitch.org>
Subject: Re: [Freeswitch-users] PortAudio and Windows devices
Reply-to: FreeSWITCH Users Help <freeswitch-users@lists.freeswitch.org>
Date: Mon, 11 Sep 2017 15:35:45 -0400

https://freeswitch.org/jira/browse/FS-10663 <https://freeswitch.org/jira/browse/FS-10663>

fixed in master now.

Thanks Andrey!

> On Sep 9, 2017, at 9:04 PM, Clive Lansink <clive@lansink.co.nz> wrote:
> 
> Hi again everyone.
> 
> OK I appreciate that nobody has yet answered this but now I have more info that may help.
> 
> I succeeded in building the Freeswitch executable for Windows from the source. I git cloned version 1.6.19 which I understand is the most recent stable release. I am using Visual Studio 2015 Express.
> 
> I first built the debug version 64-bit. There were three errors but at least there was an executable so I ran that. Now the pa devlist command lists my sound devices so that works. Also the debug information indicates that it is using DirectSound. I actually haven't made a call because of another issue but at least I can confirm that mod_portaudio sees my audio devices in this situation.
> 
> Then I cleaned the solution and built the release version. Again I got three errors but again there was an executable so I ran that. Now the pa devlist command produces no devices.
> 
> This suggests to me that something is amiss with the process for generating the release version for Windows which also makes the Windows installer, that impacts on PortAudio. In that case, the result In my experience is that PortAudio just doesn't work because it doesn't see any audio devices.
> 
> It's beyond me I'm afraid to figure out the difference here. I'm just not experienced with Visual Studio to understand what is going on with these two scenarios. 
> 
> Hope this helps.
> 
> 
> Clive Lansink
> Email: Clive@Lansink.Co.NZ
> Phone: +64 9 520-4242
> Mobile: +64 21 663-999
> Fax: +64 21 789-150
> 
> -----Original message-----
> From: Clive Lansink <clive@lansink.co.nz>
> To: "Freeswitch users list" <freeswitch-users@lists.freeswitch.org>
> Subject: [Freeswitch-users] PortAudio and Windows devices
> Reply-to: FreeSWITCH Users Help <freeswitch-users@lists.freeswitch.org>
> Date: Fri, 8 Sep 2017 10:03:32 +1200
> 
> 
> Hi everyone. Can someone please help with the following problem? I have spent several hours on this today, just googling around, and although I think I am not the only one with this problem, I haven't actually found the solution.
> 
> Problem is PortAudio reports there are no input and output devices. I am running Freeswitch on Windows 10 64-bit. The Freeswitch installer is FreeSWITCH-1.6.18-x64-Release.msi which I downloaded recently from files.freeswitch.org. I should explain that I have been using Freeswitch for a number of years and PortAudio used to work, even on this Windows 10 PC. The problem seems to be with the more recent versions of Freeswitch.
> 
> We know that Freeswitch for Windows includes PortAudio. That's good because I don't know how to build Freeswitch for Windows. I just know how to install and use it.
> 
> I think I read somewhere that the Freeswitch PortAudio is built for DirectEx. I came across the Dxdiag tool which tells me about DirectEx devices. I have several input and output devices on this machine, but Dxdiag only lists one output device and it lists no input devices. It tells me I have DirectEx version 12.
> 
> I do a lot of programming in Python and that includes a Python module that provides bindings for PortAudio. That code still works.
> 
> I read that PortAudio by default is built for MME, or maybe it is PyAudio that is built for MME. Whatever the case, that code works.
> 
> But if Freeswitch's PortAudio module is built for DirectEx, could there be a problem with DirectEx on Windows 10? I just get the impression that Microsoft is favouring newer Windows sound APIs. Issuing the pa devlist command just lists nothing so it is as if it is just not seeing any devices, but they are certainly there.
> 
> I think this has been a problem for several years because I have Freeswitch version 1.5.15 on another Windows 10 64-bit PC and PortAudio on that PC has the same problem. I just haven't had to use it on that PC.
> 
> By the way, I did try running Freeswitch in console mode with administrator privileges and it made no difference.
> 
> I hope someone can suggest something to help me fix this problem.
> 
> 
> Clive Lansink
> Email: Clive@Lansink.Co.NZ
> Phone: +64 9 520-4242
> Mobile: +64 21 663-999
> Fax: +64 21 789-150
> 

_________________________________________________________________________
Professional FreeSWITCH Consulting Services:
consulting@freeswitch.org
http://www.freeswitchsolutions.com

Official FreeSWITCH Sites
http://www.freeswitch.org
http://confluence.freeswitch.org
http://www.cluecon.com

FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org

