John Biundo wrote: > John Biundo wrote: > >>Interesting. I'm running 0.4.2 and have the tinny audio problem. >>Someone else reported dropping back to 0.4.1 and solving the problem. >> >>Has anyone else had the problem with 0.4.2? >> >>How about 0.4.1 or earlier? >> >>This might indicate a problem from a change introduced between 0.4.1 and >>0.4.2. >> > > > Nix that theory. > > I just downgraded to 0.4.1 and I'm still able to trigger the tinny audio > by issuing ivtctl -q 0. > > I run it in a loop, once every 5 seconds. It seems, subjectively, like > 0.4.1 might be somewhat less susceptible to triggering a good->bad state > change, but I can still trigger the change (and therefore, I assume that > whatever environmental factor that occassionally produces it while > recording can still trigger it). > > I'm unable to downgrade to 0.4.0 to continue testing. I get compile > errors. Is 0.4.0 incompatible with kernel 2.6.15? >
Replying to myself to pass along the following message from Paul Andreassen on the mythtv user mailing list: I attempted an upgrade to Linux 2.6.15 which required ivtv 0.4.2 and experienced tinny audio. Since I had no problem with Linux 2.6.11.7 and ivtv 0.4.0 I went back. Why not downgrade to Linux 2.6.14 and use ivtv 0.4.0 to fix the problem? _______________________________________________ ivtv-devel mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-devel
