| By Date: | <-- --> |
| By Thread: | <-- --> |
On Friday 31 March 2006 03:34, Roland Scheidegger wrote:Hans Verkuil wrote:Please try my v4l-dvb mercurial repository: http://linuxtv.org/hg/~hverkuil/v4l-dvb
This should fix all problems (I hope :-) for both bttv and msp3400.I'll try that tomorrow (couldn't quite find the right file to download which actually has the changes included and need some sleep now...)
Ok I've finally found this: hg-hverkuil-v4l-dvb-9abb710ed22c
That line in the spec should be changed as it is confusing. The only time a driver sets audmode is during initialization. The reason is simple: say the user selects audmode=stereo, then goes to a mono channel at which point the driver would switch audmode to mono. Then back to a stereo channel and audmode would remain mono. Not what you want.That's true but you could argue it's the applications responsibility to check from time to time that it really gets the mode it wants. The xawtv author certainly thinked that audmode is not only used to be set by the app (the -v 2 output will list that audmode as "tuner current"). I would consider that as a flaw in the v4l2 api btw, it doesn't quite make sense both ways - if it's never set by the driver then an app has to go through hoops to figure out what the current mode actually is (query both rxsubchans and audmode, then determine the mode according to that fallback matrix, and it's downright impossible if there is a dual-language program and audmode is stereo, since two answers are possbile in that case according to api spec).
Ah, thanks. I'll look into that too. There are no doubt more bugs in that area, there are so many msp versions that it's difficult to make sure I've covered all combinations. Oh well, one step at a time. At least it is much improved over the previous msp3400 drivers.Basically works (with the caveat that now xawtv will always show stereo, no matter what, except if you change it manually to say, lang2, then it will from there on always show lang2 on all channels due to the reasons above), however the crackling and popping noises, if anything (hard to say), got worse when channel switching (I'm not sure the chip reset is really a good idea there?), and are still present when changing volume/muting (still doing the full restart scan, am/fm detection,...).
Roland
-- video4linux-list mailing list Unsubscribe mailto:video4linux-list-request (at) redhat.com?subject=unsubscribe https://www.redhat.com/mailman/listinfo/video4linux-list