[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Mic. and softphones [was Voice redirection: from mic. to speakers on wheezy laptop].

Good time of the day, Camaleón.

Thank You for Your time and answer.
You wrote:

> > May other OS components cause this? Though I do not know what. :o)
> It could be but I can't guess what. 
> The kernel version? Sure, but sound is working fine from the command
> line utilities and also from another programs (e.g.,
> gnome-sound-recorder).
> The network card? My Lenny system uses a wired card while the netbook 
> uses a wireless adapter but I wouldn't give a penny for that argument.

Then, Ekiga - diver versions + other versions of sound software? Just

> 3 on 3 fails. Wow. I love Linux >:-P

Yet I really love Linux! Just more work needed, more packagers/testers.
May, w/ a time I will maintain a package but not for now. But I try to
report bugs when notice, though it seems a problem: where to send -
often maintainers would not accept it advicing me to talk to developers
directly (in my opinion it should not be - because sometimes
registration is required for that - that the maintainers for sure have
whereas common users - don't). Report just will be lost, and nobody
will benefit from it. - It is the rising power of free software, being
put down for diver reasons - like that simple denial.
> > And I saw no more soft phones in Debian from repo.s.
> There are more (yate, twinkle) but sadly not available for wheezy :-(

Out of repos/debian security testing is an issue for me here. - Unless
I make a VM where I will use all such programs from diver sources.

> > So far, ekiga is the best option for me, and I would say, most
> > comfortable its GUI comparing w/ the above.
> Errr, yes. Although I find more confortable/easy to use the old
> interface.

I didn't see those. What do You miss in  new version?

I think they have to have an option of logging network connection -
similar like email clients do.
> > But was is bad to me w/ ekiga is - its doc.s do not specify my
> > problem - as what is expected to not work and therefore a fix is
> > offered - works for me and therefore the fix works not for me -
> > though the problem is listed by those fix makers but diagnostic is
> > applicable for me and so their solution.
> > 
> > Thus, both modes - mono and stereo, 8/16 kHz work w/ my SB:
> > 
> > $ arecord -D plughw:0,0 -c 1 -r 16000 -f S16_LE - | aplay -D
> > plughw:0,0 -c 1 -r 16000 -f S16_LE -
> > 
> > BTW, as a workaround w/ latency for redirection of my voice (from
> > mic. to speakers) :o) Not what I wanted, but better than nothing.
> > 
> > But ekiga does not echos my voice though as I have mentioned in
> > other messages - mic. volume reflects my speech.
> I've never had Ekiga echoing my voice, that's for sure. And not just 
> Ekiga but any other capture audio application I can remember. I don't 
> think this is the default, though, so you will have to fight hard to
> get that working for you :-)

Do I recall right saying, You could speak w/ a softphone w/ a person -
but voice transmission was horrible? - Though echo service did not
return Your voice back? - In other words, echo service is not a prove
whither a particular softphone can be of use or not?

> >> > . Voice redirection from mic. to speakers (they have mentioned on
> >> > simplification of SB circuits - and I believe it is my case -
> >> > therefore another mic. type is needed - do not know when - if
> >> > ever - I obtain one);
> >> 
> >> http://bit.ly/PEwU5U
> >> 
> >> Google suggests using "jackd" to get this working (mic going
> >> through speakers) among other solutions but I don't know if it's
> >> worth the effort. In the end, what's your goal for having this?
> > 
> > Sometimes, for singing is good. :o)
> Ah, karaoke, yes X-)

YES! :o)

> > Thank You for link but sends me google start page.
> Uh? :-?
> Okay, I'll put the long URI (you will have to reconstruct it on your 
> side):
> (search keyword: mic out speakers linux)
> <http://www.google.com/webhp?
> complete=0&hl=en#hl=en&complete=0&site=webhp&source=hp&q=mic+out+speakers
> +linux&oq=mic+out+speakers
> +linux&gs_l=hp.3...2187.6675.0.6902.;..0.0...1c.d3pM2VuSJ1E&pbx=1&fp=1&biw=1280&bih=888&bav=on.2,or.r_gc.r_pw.&cad=b>

Oh, OK, thank You.

> >> I have in my radar "Jitsi" (https://jitsi.org/), it was an
> >> application I've been following very close because I like the fact
> >> it's written in Java thus can be used also from a windows system,
> >> although still not tested :-P
> > 
> > OK. Thank You. I just would not install software from non-debian
> > repo.s. In case I will move it to a VM, then I will try it, though
> > do not know when.
> Fair, but the problem is that not all the packages are available for
> all of the flavours :-(

I know, that's why I'll keep fighting w/ Ekiga - as the best option for
Debian currently - the most developed out of Debian available. Until
new phones come into Debian. Or much time will pass and I will maintain
one in Debian.

> >> > I guess ekiga people should make a diagnostic tool - that
> >> > audio/net problems might be inspected more accurate.
> >> 
> >> Sure. And what is worse, now there is no way to tell Ekiga what
> >> input/ output hardware device to choose, it has to be done from
> >> the GNOME sound applet first :-/
> > 
> > That's what I think is bad in DEs: they develop their software only
> > in conjunction w/ whole DE instead of making working standing alone
> > functionality - like konsole or kate from KDE, ekiga, evince from
> > gnome, etc. Who prevents them from feeding command line parameters
> > to the GUI programs - at least?!
> Now you say... Ekiga does provide a nice command line debugging tool 
> (ekiga -d4 &) at least to debug the SIP protocol problem :-)

Oh, yes! I saw that - just forgot - was looking for some option that
did not find, so halted for command line options.



Reply to: