On Mon, 2015-02-09 at 09:18 +0100, Takashi Iwai wrote: > At Mon, 09 Feb 2015 16:28:23 +1100, > Bruce wrote: > > > > Hi Adrian, > > > > OK. I have made some progress ! > > I now have good sound using *jackd*. I have managed to get this working > > at both single and double speed. > > There are some weirdnesses I can't explain (below), however. > > > > Where does this leave us wrt alsa vanilla alsa playpack ? > > Compare the hw_params setups found in > /proc/asound/card*/pcm*/sub*/hw_params between jack and native-aplay. > Then try aplay with the buffer size and period size via options. > Possibly some hw constraints are missing, e.g. the alignment of buffer > size with the period size. Hi, thanks for the hint. I tried aplay -B 2500 and output was fine. $ grep "" /proc/asound/card2/pcm*/sub*/hw_params /proc/asound/card2/pcm0c/sub0/hw_params:closed /proc/asound/card2/pcm0p/sub0/hw_params:access: MMAP_NONINTERLEAVED /proc/asound/card2/pcm0p/sub0/hw_params:format: S32_LE /proc/asound/card2/pcm0p/sub0/hw_params:subformat: STD /proc/asound/card2/pcm0p/sub0/hw_params:channels: 16 /proc/asound/card2/pcm0p/sub0/hw_params:rate: 48000 (48000/1) /proc/asound/card2/pcm0p/sub0/hw_params:period_size: 64 /proc/asound/card2/pcm0p/sub0/hw_params:buffer_size: 128 It seems like buffer size 128 is the maximum, as distortions during playback start with larger values. Regards, Tino ------------------------------------------------------------------------------ Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ Alsa-user mailing list Alsa-user@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/alsa-user
