JackOfAll wrote: > Hmmm. Not too sure about a 3.10.30 kernel. From a CS point of view with > the Wandboard, (Cubox-i is imx6, right?), I can vouch for the Freescale > vendor 3.0.35 kernel and recent mainline as far as USB goes.I mentioned that > I have a build of Volumio that exhibits the sonically identical symption, assuming I don't over sample? Well I popped the microSD with that into the Cubox-I, and it's 3.0.35. So I can say with reasonable certainty, that this problem extends back that far - with this particular hardware. This problem is not unique to 3.10.X.
JackOfAll wrote: > And ISTR that when someone did have issues with the Dragonfly and > Wandboard they were solved with a hub.A Google did not produce any results > for "Wanderboard DragonFly". So all I can say is maybe that is due to people setting the Wanderboard's volume too high? Audioquest is quite specific about setting the volume to 100% on the app supplying the tunes (Squeezelite in this case), and controlling the volume at the OS level, starting around 25%. And hubs somehow appear to "fix" that. Though other than on an iPhone, that's the first I've ever read of a hub being required. Lot's and lots of people using these on lots of platforms without a hub. JackOfAll wrote: > Have you checked dmesg? Anything there related to USB? Maybe an error > corresponding with the click/pop?Great suggestion. Thank you. I can say that > no new messages pop up after a click/pop. But I don't have the knowledge to know whether there are other clues from dmesg. If you are interested in looking, here are links to the dmesg output after playing a FLC with pop/click/crackle on 'Squeezelite' (http://www.colley.org/images/squeezelite-dmesg.txt), and also on 'Volumio' (http://www.colley.org/images/volumio-dmesg.txt). Triode wrote: > The problem you describe sounds like the feedback mechanism not working > - you can diagnose this by looking at /proc/asound/<card>/stream0 while > it is running and checking that the Momentary freq is changing while > playing (it should vary on repeated cats of that file around the nominal > frequency). If this is not happening then there is something wrong with > the way the asych mechanism is working.If I was doing this correctly - > repeated cats every second or so - showed no changes in the Momentary Frequency, which remained a steady 44100 - even right before/after pop/crackles. So that's NOT what I was supposed to see? Thanks again. I don't want this to get OT. But if knowing how Squeezelite responds to such a problem is of value here, I'd love your thoughts. Thanks. ------------------------------------------------------------------------ scolley's Profile: http://forums.slimdevices.com/member.php?userid=62931 View this thread: http://forums.slimdevices.com/showthread.php?t=97046 _______________________________________________ unix mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/unix
