On Fri, 2015-02-06 at 12:03 +0100, Adrian Knoth wrote: > I'm lost. Can we get a fresh proper test case? > > - current kernel (your 3.18.x is fine) > - up-to-date distro (your Arch should be good) > - running with jackd I didn't use jack, but this test setup: - Debian unstable with Kernel 3.16 - pure ALSA (no jack, no pulseaudio etc.) - several WAV files (mono, stereo, 44,1 kHz, 48 kHz) - aplay > I especially recommend running jackd instead of a hand-written app. > There are just too many pitfalls on those pro-audio cards, and jackd got > them all right. I'll try. > Also check alsamixer for the various settings regarding clock selection > and frequency multiplier. I guess Clock Master at 48kHz would be a good > first start - this should actually be the driver's default setting when > the card comes up. I also checked these settings, and tested if they change anything. They didn't. > > Last not least: maybe update the card's firmware on a Windows machine. Playback with an ancient Kernel from Debian 5 was ok, as well as playback in Windows 7. So the card seems to work fine. > PS: I see alcnetworx in the CC. How did you guys end up in there? Isn't > AES67 all the rage these days? :) Yes, it's burning, and it's quite a pitty to have AES67 and no device to feed it with audio, because the AES3 output doesn't work. :-) 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
