workaround for the moment, I disabled the USB audio via
>> > pavucontrol configuration altogether, so it is only seen and selected by
>> > Blink and doesn't pop up in PA at all while accepting or doing phone calls.
>> >
>> > Regards,
>> > Michael
>> &g
00 />/From: Jeff Pyle <https://lists.ag-projects.com/mailman/listinfo/blink>> ugnd.org <https://lists.ag-projects.com/mailman/listinfo/blink>> />/To: Blink Support Forum <https://lists.ag-projects.com/mailman/listinfo/blink>> lists.ag-projects.com
<https://lists
I've been looking into this and once it's hung, you can hook into the
thread with the highest cpu usage with gdb and it appears that
python-sipsimple is stuck in the alsa function `snd_pcm_drain (pcm);` (
Blink Support Forum <https://lists.ag-projects.com/mailman/listinfo/blink>> lists.ag-projects.com
<https://lists.ag-projects.com/mailman/listinfo/blink>> />/Subject: Re: [Blink] Blink for Linux hangs on second call when using />/PulseAudio input device />/Message-ID: /&g
onfiguration altogether, so it is only seen and selected by
> Blink and doesn't pop up in PA at all while accepting or doing phone calls.
>
> Regards,
> Michael
>
> Date: Tue, 7 May 2019 11:07:17 -0400
> From: Jeff Pyle
> To: Blink Support Forum
>
> Subject:
Unfortunately the programming is a bit over my head but I was able so solve
my problem with an ALSA loopback device [1]. The modified the full example
in the link from two subdevices to one, changed to 48khz, and Blink handles
it like a champ.
[1] -
On 9 Jan 2019, at 14:41, Jeff Pyle wrote:
> Dan,
>
> Ok. Can you point me to where in the Blink scripts it creates the audio
> device? I'd like to see exactly what it's doing, as well as try to get some
> Pulse logs to see if I can make any sense of it.
On Tue, 8 Jan 2019 21:55:34 -0500
Jeff Pyle wrote:
> Has anyone else experienced this?
I'm also using Blink with PulseAudio, but I have not experienced
this (yet). I'm still using Blink 3.0.3 on Debian 9.x "stretch" with
PulseAudio 10.0.
Regression, perhaps? If so, I'd also like to see this
Dan,
Ok. Can you point me to where in the Blink scripts it creates the audio
device? I'd like to see exactly what it's doing, as well as try to get
some Pulse logs to see if I can make any sense of it.
- Jeff
On Wed, Jan 9, 2019 at 6:34 AM Dan Pascu wrote:
> I have used blink with pulse
I have used blink with pulse audio in the past (approximately 1.5-2 years ago)
and it worked (except messing up echo cancelation but that is another story),
so this may be an issue with newer ALSA/Pulse Audio.
What I can tell you for sure though is that Blink doesn't use Pulse Audio
directly.
Hello,
I'm running Blink for Linux 3.1.0 on Arch Linux x86_64 with PulseAudio 12.2.
The subject describes the problem. The first call works fine. Once the
first call terminates, Blink can no longer place or receive a second
call...usually. On my last last test, I got a second call dialed but
11 matches
Mail list logo
