Re: [LAD] [alsa-devel] Fw: Using loopback card to Connect GSM two way call to the real sound card UDA1345TS

2015-07-01 Thread Clemens Ladisch
Srinivasan S wrote: Am facing overrun underrun issues, when I run the the above GSM application with the attached asound.conf The sound card and the GSM streams are not synchronized. You need to compensate for the drift between the clocks, typically by resampling. (Jack's alsa_in/alsa_out

Re: [LAD] [alsa-devel] Fw: Using loopback card to Connect GSM two way call to the real sound card UDA1345TS

2015-06-01 Thread Clemens Ladisch
Srinivasan S wrote: 2. Could you please let me know, I have downloaded jack-1.9.10.tar.bz2, how this needs to be installed in my rootfs IIRC Jack uses some non-standard build system. Try asking on the Jack mailing list how to cross-compile it. Please note that the ALSA Jack plugin is part of

Re: [LAD] [alsa-devel] Fw: Using loopback card to Connect GSM two way call to the real sound card UDA1345TS

2015-04-24 Thread Clemens Ladisch
Srinivasan S wrote: could you please provide me some sample application links without using dshare plugin , ie., using the two channels ie., left right directly I am not aware of any (sample) program that does something like this (except maybe Jack, but floating-point samples would not be

Re: [LAD] [alsa-devel] Fw: Using loopback card to Connect GSM two way call to the real sound card UDA1345TS

2015-04-02 Thread Clemens Ladisch
Srinivasan S wrote: CPU consumption is 18%, with above asound.conf the app alsa_loopback_min_mono.c for establishing my GSM two way call (ie., VINR to VOUTR VINL to VOUTL) , this is very huge I want to reduce this CPU consumption drastically, Is there any other ways in alsa where I can do

Re: [LAD] [alsa-devel] Fw: Using loopback card to Connect GSM two way call to the real sound card UDA1345TS

2015-04-02 Thread Clemens Ladisch
Srinivasan S wrote: I didn't understand what is 'two channel devices' does The two channels are left and right. Regarding bindings as you explainedbindings.x y or bindings { x y } maps channel x of this device to channel y of the slave device. I didn't understand channel x of this device