mplayer still broken
- From: hermann pitton <hermann-pitton (at) arcor.de>
- Date: Sat, 25 Mar 2006 05:02:17 +0100
Am Freitag, den 24.03.2006, 18:58 -0800 schrieb David Liontooth:
> hermann pitton wrote:
> > Am Freitag, den 24.03.2006, 17:11 -0800 schrieb David Liontooth:
> >
> >> hermann pitton wrote:
> >>
> >>> Am Freitag, den 24.03.2006, 06:25 -0300 schrieb Paulo Cavalcanti:
> >>>
> >>>
> >>>> Hi, Mauro
> >>>>
> >>>> I installed mercurial from extra rpms, and
> >>>> used hg clone http://linuxtv.org/hg/v4l-dvb, as
> >>>> you told me to do.
> >>>>
> >>>> Therefore, now I must have the latest of the latest version, and
> >>>> mplayer still has no sound with bttv driver. Everything else
> >>>> seems to be fine. I can change channels, etc ....
> >>>> tvtime is perfect, however.
> >>>>
> >>>>
> >>>> Seems the same problem reported in the link below.
> >>>>
> >>>> http://www.ussg.iu.edu/hypermail/linux/kernel/0512.2/0842.html
> >>>>
> >>>> Could anyone take a look at that? Has anyone noticed the same
> >>>> problem?
> >>>>
> >>>>
> >>> Hi Paulo,
> >>>
> >>> since several people reported saa7134-alsa and saa7134-oss without sound
> >>> I have installed the recent mercurial and can confirm this. Also for
> >>> mplayer (quite old cvs) in direct pci audio mode and saa7134-alsa. The
> >>> recording from the soundcard at hardware.0,0 was still working, but I
> >>> have no bttv card to test.
> >>>
> >>> I'm currently back to my previously used from 20060311, which also needs
> >>> to manually copy the videodev.ko from that version to replace the newest
> >>> one from the prior and now automated install.(also unload and depmod -a)
> >>> Hans is working on tuner/audio stuff, but I can't say yet if it could be
> >>> related.
> >>>
> >>> Cheers,
> >>> Hermann
> >>>
> >> On mainline 2.6.16, I get good sound using this, where $DEV is the
> >> number of the device node:
> >>
> >> mencoder -tv
> >> driver=v4l2:device=/dev/video$DEV:fps=30000/1001:chanlist=us-bcast:\
> >> audiorate=32000:alsa:adevice=hw.$DEV:input=0:amode=1:normid=4:width=576:height=432
> >> \
> >> -ovc x264 -x264encopts
> >> threads=2:bitrate=500:bframes=2:subq=1:me=1:frameref=4:8x8dct \
> >> -oac mp3lame -lameopts cbr:br=64 -endpos $TIM -o $DIR/$FIL.avi tv:// >
> >> /dev/null
> >>
> >> So the alsa device is simply called hw.1 -- not hw.1,0 or whatever. I used
> >>
> >> alsamixergui -c 1
> >>
> >> to set recording to channel 1 first, and the volume to max, for each of
> >> the four cards.
> >>
> >> I used this to load the saa7134 cards and the alsa module:
> >>
> >> saa7134 card=2,2,2,2 tuner=43,43,43,43 video_nr=1,2,3,4 vbi_nr=1,2,3,4
> >> radio_nr=1,2,3,4 alsa=1,1,1,1
> >>
> >> dmesg is happy:
> >>
> >> input: saa7134 IR (LifeView FlyVIDEO30 as /class/input/input5
> >> tuner 5-0061: chip found (at) 0xc2 (saa7133[3])
> >> tuner 5-0061: type set to 43 (Philips NTSC MK3 (FM1236MK3 or FM1236/F))
> >> tuner 5-0063: chip found (at) 0xc6 (saa7133[3])
> >> saa7133[3]: i2c eeprom 00: 69 51 38 01 10 28 ff ff ff ff ff ff ff ff ff ff
> >> saa7133[3]: i2c eeprom 10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> >> saa7133[3]: i2c eeprom 20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> >> saa7133[3]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> >> saa7133[3]: i2c eeprom 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> >> saa7133[3]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> >> saa7133[3]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> >> saa7133[3]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> >> saa7133[3]: registered device video4 [v4l2]
> >> saa7133[3]: registered device vbi4
> >> saa7133[3]: registered device radio4
> >> saa7134 ALSA driver for DMA sound loaded
> >> saa7133[0]/alsa: saa7133[0] at 0xf5006000 irq 19 registered as card 1
> >> saa7133[1]/alsa: saa7133[1] at 0xf5007000 irq 20 registered as card 2
> >> saa7133[2]/alsa: saa7133[2] at 0xf5004000 irq 21 registered as card 3
> >> saa7133[3]/alsa: saa7133[3] at 0xf5005000 irq 22 registered as card 4
> >>
> >> Dave
> >>
> >>
> >
> > Hi Dave,
> >
> > thanks for the report. Maybe I should have a closer look, but it was
> > working well even with auto enumerated minors until now.
> >
> > What makes me more concerned is, just at the moment, that even with the
> > above 20060311 mercurial, a machine is going in some corrupted state
> > after about one hour TV or radio, since yesterday second time now.
> >
> > It shows this darkened red colors and pops on audio, like it was so
> > infamous for bttv only until now. A warm reboot helps.
> >
> > Unfortunately it is this asus AV133 with KT133A and 2.6.16-rc1-git4 ;)
> > and NVIDIA binary drivers I still have around ...
> >
> > Despite of all, it was stable on FC5 with all updates up to latest from
> > November last year until now.
> >
> > Since I don't worry much on that one and have fallbacks, the dma sound
> > is needed meanwhile by many folks and we should have it working also on
> > the next kernel.
> >
> > Can you try the current mercurial?
> >
> Hi Herman,
>
> I was excited to see the new module and would like to help out with
> further testing, but it's going to be a couple of months before I can
> spend time installing new versions. I can say though that I have the
> 2.6.16 saa7134-alsa working on two quite different amd64 machines, in
> one case with the card in a PCI-X slot. The released code seems pretty
> robust. I put some instructions up at
> http://linuxtv.org/v4lwiki/index.php/Saa7134-alsa -- please improve,
>
> Dave
Dave,
it is OK.
Testing won't do harm to you, but I understand.
Thanks for all your prior and future help and the done testing on the
hard stuff!
Best again,
Hermann
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request (at) redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list