Roger Miliker | 1 Dec 2003 02:31
Picon
Picon

Re: saa7134 sound problems

On Tuesday 25 November 2003 21:37, Mircea HUTANU wrote:
> 	hi,
>
> 	I have a medion 5044 tv card with saa7134 chipset.
> I've patched the kernel for v4l2 and the video is working fine, but I
> can't solve the sound problem.

>
> 	What am I doing wrong ? Can anyone help me ?
> 	Thank you !
>
>

I have the same card. I have to use a mixer to mute/unmute the card (my 
line-in actually).
(I have a cable from the audio-out of the card to my line-in)
Only starting xawtv unmutes the card itself  the first time. Closing xawtv 
doesn't mute.
So I have to mute line-in to get rid of tv-sound.
What exactly is your problem?

Roger

> --
> video4linux-list mailing list
> Unsubscribe mailto:video4linux-list-request <at> redhat.com?subject=unsubscribe
> https://www.redhat.com/mailman/listinfo/video4linux-list

--
video4linux-list mailing list
(Continue reading)

suriya mohan | 1 Dec 2003 06:17
Favicon

Re: Re: Recommended kernel patches for video capture

Hi steven,
  If at all any frame dropping occurs, then it is not due to the
driver we use. If you try frame capturing in desktop linux then frame
dropping will occur rather should occur. Because the processor is not
dedicated. If u try this in any embedded device like set-top box or
PVR then you will probably have good result. So I think there will not
be any problem with the patches we apply to the kernel source.

Any comments from others in the group regarding this ?

On Sun, 30 Nov 2003 hermann pitton wrote :
>Es schrieb Steven Ellis:
> >
> > Currently running a custom 2.4.20 kernel with various v4l2 patches
for my
> > saa7134 based capture card.
> >
> > Thinking of upgrading as if i'm capturing to full D1 Pal still get
frame
> > drops, and wondered what recommendations people have for kernel
> > releases/patches.
> >
> > My preference is to stick witj 2.4.xx with some low latency kernel
patches
> > for now, but also whats people's opinion on 2.6.0 test?
> >
>
>Hi Steven,
>
>for 2.4.xx I can recommend the 22 with kraxelpatch-3, for 2.6.0
test11
>with test10-kraxelpatch-2.
>Disable any debugging and profiling if you are out on performance.
Bad
>luck can be to have a piece of hardware, where the decision is not
>already made, what why should be blacklisted for certain
improvements.
>If you are set up once for test kernels, new changed builds can be
done
>within minutes for testing features. Further next improvements are
more
>to expect from the environment I guess. 2.6.0 is clearly straight on
its
>way ... nothing to wait for anymore. (the driver seems to like
>gcc-3.3.1-x, but 3.2.2 will do it too)
>
>Greetings
>
>Hermann
>
>--
>p.s. nvrec you need a current cvs :)
>
>
>--
>video4linux-list mailing list
>Unsubscribe
mailto:video4linux-list-request <at> redhat.com?subject=unsubscribe
>https://www.redhat.com/mailman/listinfo/video4linux-list

There is no substitution for hard work.
Information is wealth.

Hank Barta | 1 Dec 2003 15:33
Picon

Re: Re: Recommended kernel patches for video capture

On Sun, 2003-11-30 at 23:17, suriya mohan wrote:
> Hi steven, 
>   If at all any frame dropping occurs, then it is not due to the 
> driver we use. If you try frame capturing in desktop linux then frame 
> dropping will occur rather should occur. Because the processor is not 
> dedicated. If u try this in any embedded device like set-top box or 
> PVR then you will probably have good result. So I think there will not 
> be any problem with the patches we apply to the kernel source. 
>  
> Any comments from others in the group regarding this ? 
>  

Is there any indication why the capture is dropping frames? I'm a rank
newbie at this, having just tried DV capture for the first time
yesterday. I had problems with 'dvgrab' keeping up until I discovered
that I had neglected to compile in specific support for the motherboard
chipset. Once that was done, I was able to capture without dropping
frames until my hard drive was full. But that's a different problem. In
any case, the warnings produced by 'dvgrab' clearly indicated that
writing to the hard drive was not keeping up. Also compiling the correct
chipset drivers allow disk I/O to use DMA and this reduced CPU load from
about 50% to about 5% as reported by 'top.' 

For reference this is a Sony Vaio laptop with 750 MHz P-III, 256MB RAM
and 20 GB hard drive. The kernel is 2.4.22 custom compiled but no
patches applied save a one line fix to scanner.c (USB scanner bug.)

--

-- 
Hank Barta
Beautiful Sunny Winfield
Illinois, USA

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request <at> redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

bj | 1 Dec 2003 18:07

Re: Recommended kernel patches for video capture

Hi Hank,

I've got problems performing capture with a couple of computers.  Can
you give me a brief description of how you compile in chipset-specific
support?  Are there obvious steps in 'make config', or obvious error
messages in the kernel make output to work with?

Thanks,

BJ
Hank Barta wrote:
> On Sun, 2003-11-30 at 23:17, suriya mohan wrote:
> 
>>Hi steven, 
>>  If at all any frame dropping occurs, then it is not due to the 
>>driver we use. If you try frame capturing in desktop linux then frame 
>>dropping will occur rather should occur. Because the processor is not 
>>dedicated. If u try this in any embedded device like set-top box or 
>>PVR then you will probably have good result. So I think there will not 
>>be any problem with the patches we apply to the kernel source. 
>> 
>>Any comments from others in the group regarding this ? 
>> 
> 
> 
> Is there any indication why the capture is dropping frames? I'm a rank
> newbie at this, having just tried DV capture for the first time
> yesterday. I had problems with 'dvgrab' keeping up until I discovered
> that I had neglected to compile in specific support for the motherboard
> chipset. Once that was done, I was able to capture without dropping
> frames until my hard drive was full. But that's a different problem. In
> any case, the warnings produced by 'dvgrab' clearly indicated that
> writing to the hard drive was not keeping up. Also compiling the correct
> chipset drivers allow disk I/O to use DMA and this reduced CPU load from
> about 50% to about 5% as reported by 'top.' 
> 
> For reference this is a Sony Vaio laptop with 750 MHz P-III, 256MB RAM
> and 20 GB hard drive. The kernel is 2.4.22 custom compiled but no
> patches applied save a one line fix to scanner.c (USB scanner bug.)
> 

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request <at> redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

Sayankar Tushar D-A16600 | 1 Dec 2003 18:23

Getting YUV 4:2:2 dat from V4L

Hi Guys,
 
Has anybody tried to get data in YUV 4:2:2 format through V4L from USB camera?
 
If so then pls help me out to understand it.
 
Thanks,
Tushar
Tuukka Toivonen | 1 Dec 2003 18:40
Picon
Picon
Favicon

Re: Getting YUV 4:2:2 dat from V4L

On Mon, 1 Dec 2003, Sayankar Tushar D-A16600 wrote:

>Has anybody tried to get data in YUV 4:2:2 format through V4L from USB camera?

A V4L device might not and probably won't support all possible formats.
You should use a format conversion library that can read any possible
V4L format and convert it to YUV 4:2:2. For libraries, look e.g.

http://www.smcc.demon.nl/webcam/release.html#ccvt

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request <at> redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

Jave | 1 Dec 2003 19:00
Picon

Hercules Smart Tv hardware support

Hi,

I am trying to setup bttv to use my Hercules Smart Tv (not stéréo) under
Linux without success.

I found that Hercules Smart Tv Stéréo card is supported as card 100 and
tuner 5 but it apparently this card is not the same as mine which as not 
the stéreo option.

Has somebody already tryied this card with success ?

Please help.

Jave.

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request <at> redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

Hank Barta | 1 Dec 2003 19:40
Picon

Re: Recommended kernel patches for video capture

On Mon, 2003-12-01 at 11:07, bj wrote:
> Hi Hank,
> 
> I've got problems performing capture with a couple of computers.  Can
> you give me a brief description of how you compile in chipset-specific
> support?  Are there obvious steps in 'make config', or obvious error
> messages in the kernel make output to work with?

This is what I found in a Google search:

Run the command "lspci|grep IDE" to see what hardware Linux found on
your system. On one desktop with a VIA KT133 (Abit MB) I get:
  00:07.1 IDE interface: VIA Technologies, Inc. VT82C586/B/686A/B 
  PIPC Bus Master IDE (rev 10)
(all on one line)
and on my Vaio I get:
  00:07.1 IDE interface: Intel Corp. 82371AB/EB/MB PIIX4 IDE (rev 01)

Then in the kernel configuration under:

    ATA/IDE/MFM/RLL support ->
        IDE, ATA and ATAPI Block devices
these correspond to 
	VIA82CXXX chipset support 
and
	Intel PIIXn chipsets support

(I'm assuming that you already know how to build and install a custom
kernel and are using IDE drives.) If this is a boot drive, you do not
want to compile these as modules but rather built into the kernel. You
just need to figure out what chipset you have and which configuration
option corresponds to it. There are other options and for those I
suggest starting with the help that comes with the kernel configuration
and moving on to google groups if that doesn't help.

I use 'make xconfig' but the prompts and selections should also be
available in 'make config', but IIRC the latter drags you through *all*
settings even if you only want to tweak one. You might also consider
'make menuconfig'

There are no error messages from 'make config' that I am aware of and if
there are errors when you build the kernel or modules, you will not have
anything to install.

HTH,
hank

--

-- 
Hank Barta
Beautiful Sunny Winfield
Illinois, USA

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request <at> redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

Roger Oberholtzer | 1 Dec 2003 22:55
Picon
Gravatar

Re: Hercules Smart Tv hardware support

On Mon, 2003-12-01 at 19:00, Jave wrote:
> Hi,
> 
> I am trying to setup bttv to use my Hercules Smart Tv (not stéréo) under
> Linux without success.
> 
> I found that Hercules Smart Tv Stéréo card is supported as card 100 and
> tuner 5 but it apparently this card is not the same as mine which as not 
> the stéreo option.
> 
> Has somebody already tryied this card with success ?

I posted questions like this a while back without answer. Well, one kind
soul tried. But happy though I was to get a response, I already knew the
suggestions.

I can get mine show images with, say, xawtv. But no sound. Other than
static. Mine is the Stereo version.

My system prints the attachment's listing when modules are loaded. All
looks ok. But no sound. I tried:

OSS

ALSA

TVAUDIO

No difference. I checked the output of the card's speaker connection
when trying OSS and ALSA. When I tried TVAUDIO, a new mixed showed up in
ALSA, but still no sound. Just static.

How does your module loading trace statements compare to these?

Linux video capture interface: v1.00
bttv: driver version 0.7.107 loaded
bttv: using 4 buffers with 2080k (8320k total) for capture
bttv: Host bridge is Intel Corp. 82850 850 (Tehama) Chipset Host Bridge (MCH)
bttv: Bt8xx card found (0).
PCI: Found IRQ 10 for device 02:08.0
PCI: Sharing IRQ 10 with 00:1f.3
PCI: Sharing IRQ 10 with 02:08.1
bttv0: Bt878 (rev 17) at 02:08.0, irq: 10, latency: 64, mmio: 0xf2001000
bttv0: using: BT878(Hercules Smart TV Stere) [card=100,insmod option]
i2c-core.o: adapter bt848 #0 registered as adapter 0.
bttv0: using tuner=5
bttv0: i2c: checking for TDA9875  <at>  0xb0... found
i2c-core.o: driver i2c tda9875 driver registered.
tda9875: no such chip at 0xb0 (dic=0x11 rev=0x2)
bttv0: i2c: checking for TDA7432  <at>  0x8a... not found
tvaudio: TV audio decoder + audio/video mux driver
tvaudio: known chips:
tda9840,tda9873h,tda9874h/a,tda9850,tda9855,tea6300,tea6420,tda8425,pic16c54 (PV951),ta8874z
i2c-core.o: driver generic i2c audio driver registered.
tvaudio: found pic16c54 (PV951)  <at>  0x96
i2c-core.o: client [pic16c54 (PV951)] registered to adapter [bt848 #0](pos. 0).
tvaudio: found tda9874a.
tvaudio: found tda9874h/a  <at>  0xb0
i2c-core.o: client [tda9874h/a] registered to adapter [bt848 #0](pos. 1).
i2c-core.o: driver i2c TV tuner driver registered.
tuner: chip found  <at>  0xc0
tuner: type set to 5 (Philips PAL_BG (FI1216 and compatibles))
i2c-core.o: client [Philips PAL_BG (FI1216 and comp] registered to adapter [bt848 #0](pos. 2).
bttv0: PLL: 28636363 => 35468950 .. ok
bttv0: registered device video0
bttv0: registered device vbi0
btaudio: driver version 0.7 loaded [digital+analog]
PCI: Found IRQ 10 for device 02:08.1
PCI: Sharing IRQ 10 with 00:1f.3
PCI: Sharing IRQ 10 with 02:08.0
btaudio: Bt878 (rev 17) at 02:08.1, irq: 10, latency: 64, mmio: 0xf2000000
btaudio: using card config "default"
btaudio: registered device dsp0 [digital]
btaudio: registered device dsp1 [analog]
btaudio: registered device mixer0
suriya mohan | 2 Dec 2003 06:07
Favicon

Re: Re: Recommended kernel patches for video capture

Hi,
  There are tv tuner cards based on bttv or saa7130/34. Relevant v4l2
drivers are available. There is nothing specific in compiling. The
drivers are specific. Though u try to work it out in different PC's
they are still desktop linux boxes where the processor is not
dedicated. Say suppose if u work in X windows it itself requires 8MB
ram and some processor power. likewise so many process will run
including background processes. These are the reasons for frame
dropping. If we try this using a dedicated processor, in any embedded
device then there will not be in any frame dropping.

On Mon, 01 Dec 2003 bj wrote :
>Hi Hank,
>
>I've got problems performing capture with a couple of computers.  Can
>you give me a brief description of how you compile in
chipset-specific
>support?  Are there obvious steps in 'make config', or obvious error
>messages in the kernel make output to work with?
>
>Thanks,
>
>BJ
>Hank Barta wrote:
>>On Sun, 2003-11-30 at 23:17, suriya mohan wrote:
>>
>>>Hi steven,  If at all any frame dropping occurs, then it is not due
to the driver we use. If you try frame capturing in desktop linux then
frame dropping will occur rather should occur. Because the processor
is not dedicated. If u try this in any embedded device like set-top
box or PVR then you will probably have good result. So I think there
will not be any problem with the patches we apply to the kernel
source. 
>>>Any comments from others in the group regarding this ? 
>>
>>
>>Is there any indication why the capture is dropping frames? I'm a
rank
>>newbie at this, having just tried DV capture for the first time
>>yesterday. I had problems with 'dvgrab' keeping up until I
discovered
>>that I had neglected to compile in specific support for the
motherboard
>>chipset. Once that was done, I was able to capture without dropping
>>frames until my hard drive was full. But that's a different problem.
In
>>any case, the warnings produced by 'dvgrab' clearly indicated that
>>writing to the hard drive was not keeping up. Also compiling the
correct
>>chipset drivers allow disk I/O to use DMA and this reduced CPU load
from
>>about 50% to about 5% as reported by 'top.' 
>>For reference this is a Sony Vaio laptop with 750 MHz P-III, 256MB
RAM
>>and 20 GB hard drive. The kernel is 2.4.22 custom compiled but no
>>patches applied save a one line fix to scanner.c (USB scanner bug.)
>>
>
>
>
>
>--
>video4linux-list mailing list
>Unsubscribe
mailto:video4linux-list-request <at> redhat.com?subject=unsubscribe
>https://www.redhat.com/mailman/listinfo/video4linux-list

There is no substitution for hard work.
Information is wealth.


Gmane