search

LubosD / twinkle

Qt 5 port of Twinkle
http://twinkle.dolezel.info
GNU General Public License v2.0
169 stars 50 forks source link

Cannot select multiple audio interfaces with pulseaudio running, so it would be a good idea to implement JACK and/or PulseAudio compatibility #103

Open wifimaclet opened 6 years ago

wifimaclet commented 6 years ago

I didn't notice you revived Twinkle until earlier this week when I couldn't find a way to install ekiga in debian testing. Please keep up the nice work.

So, I use Pulseaudio for the headset and JACK for the speakers. I can route between pulse and jack, but, since there seems be native support for none of them, I have to use ALSA's default (that routes to pulse's default) for Twinkle. That limits the soundcards I can use with it to one, and I'd really like the ring tone output to be on a different interface than the call sound. Therefore:

wifimaclet commented 6 years ago

I'd say this makes #9 even more important? I'm not sure, I'm not good with C++, so I don't understand the codebase.

elraymond commented 6 years ago

Off topic:

Just dropped by because I recently switched from OSS4 to Alsa/Pulse and wanted to see what people's experiences are. Specifically the "Playback buffer underrun"s seem to pose major trouble to Pulse, which I couldn't configure to accommodate Twinkle's needs. So what effectively happens is choppy sound and Twinkle occasionally even freezing to the point of requiring a "kill -KILL".

Pure Alsa works seamlessly though, so I'm fine with leaving it at that. From glancing over the code, a rewrite appears to require a major effort, too. Unfortunately I'm not sufficiently proficient in C++ either to contribute a rewrite within a reasonable limit of time. Glad though the client is still around, because it's a particularly nice one.

fbriere commented 5 years ago

@wifimaclet Would it not be possible to create two ALSA devices, with the pulse and jack plugins respectively, and use them (as "ALSA: other device") instead of the default?