At Fri, 06 Feb 2015 02:01:02 +1100, Bruce wrote: > > On 6/02/2015 1:29 AM, Tino Mettler wrote: > > On Thu, 2015-02-05 at 14:56 +0100, Takashi Iwai wrote: > > > >> looking at the code diff between 1.0.15 and 1.0.18, there is no > >> significant changes in hdspm.c, and most of them are just typo fixes > >> and core-side API cleanup that is irrelevant with HDSPM > >> functionality. > > Hi, > > > > as Bruce seems to have the same problem as I do, I can state that at > > least Debian Lenny which uses 1.0.16 worked out of the box on the same > > hardware and test sample. > > Hi Tino, > > That's interesting. Great to see some confirmation at last and that I'm > not suffering some sort of weird 3 year long delusion :) Well, it would have been better to be reported at the right time at the right place. alsa-users ML isn't always the best place for reporting regressions. Please report it rather to alsa-devel ML. And report as soon as possible you found the regression. > Note I think I have *2 problems*. They may or may not be related ! > > 1/ Somewhere between 1.0.15 and 1.0.18 aplay gave distorted/jerky/pulsed > output playing a wav file on the RME. Callbacks stopped working to my > own alsa application after approx 1s of playback. It could well be > between 1.0.16 and 1.0.18. *Or*, your setup/somehow/ doesn't suffer 1/, > but only 2/, and the problem 1/ came for me between 15 & 16 :) Less > likely, but still possible. Is it with the very same hardware and is with the same kernel? If the same machine but different kernel versions, rather point out the working and non-working kernel versions. > 2/ On a very recently installed system with alsa 1.0.28 (alsa driver now > part of kernel though?), Yes, the alsa-driver version doesn't help at all for identifying the code base. Please refer to the kernel version you're using instead. > the playback with aplay speeds up, and I get > that weird 5 channel output thing happening. Callbacks to my alsa app > cease after a very short (few ms) burst of audio). > If you use "aplay --disable-resample", and attempt to play a 96k stereo > wav file, it won't play and claims the only rate possible is 176.4k, > which I don't /think /this particular card even supports ! (later RME > cards did come with quad speed). > I can't tell you if the speedup is due to the 2 channels being spread > over 5, and /using up/ the samples faster, or if it's a clocking problem. So this can be a mismatching hardware profile that is detected by the driver. How is your card recognized? Is it same between the old working and the latest versions? Takashi ------------------------------------------------------------------------------ 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
