On Sun, 21 Jan 2007, devsk wrote: > I have put out a sample that I collected with 'mplayer /dev/video0 > -dumpaudio' and chopped into to .wav with mpg123 -n 180 at
Actually, it would be more useful if you just cat'ed the unchanged mpeg data to a file and make that available. Then we can figure out if the pops are coming directly from the hardware or if it is an mplayer issue. > > http://home.comcast.net/~funtoos/sample.wav > > Also, I want to take the HD 5.1 thingy back. The pops are not specific to HD > material. OK. Not a surprise since HD material is simply not possible on an NTSC broadcast. Relating to your previous post, the pvrusb2 driver causes the I2C chip-level driver modules to dump their status early on when they attach to the pvrusb2 driver. Since you haven't really tuned anything at that point, the results may not be very meaningful. However if you do this: cat /sys/class/pvrusb2/*/debuginfo Not only will you get some info to the terminal, but all the I2C chip-level driver modules will be requested to dump their state again to the system log. Have a look at dmesg again and see what it says about its tuning / decoding status. -Mike -- | Mike Isely | PGP fingerprint Spammers Die!! | | 03 54 43 4D 75 E5 CC 92 | isely @ pobox (dot) com | 71 16 01 E2 B5 F5 C1 E8 | | _______________________________________________ pvrusb2 mailing list [email protected] http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2
