PP | 1 Jan 2007 01:27
Favicon

Problems with dvbstream and full featured card

Hi.

Don't know if this is a v4l-problem but I guess the knowledge is here 
how to solve this. I have a Hauppauge Nexus-S rev 2.1 DVB-S card. 
Recording from it works well with "szap -r Das\ Erste && cat 
/dev/dvb/adapter0/dvr0 > file.ts" but this way I only get the mpeg 
audio. I'm trying to find out how I can also add AC3-audio to this file.
I'm running this on a 2.6.19 kernel - all modules are loaded 
automatically so I feed them no extra parameters.

THIS WORKS:
dvbstream -v 101 -a 102 -o > file.ts
dvbstream 101 -o > file.ts	#video
dvbstream 102 -o > file.ts	#mpeg audio
dvbstream 106 -o > file.ts	#AC3 audio

THIS DOESN'T WORK:
dvbstream -v 101 -a 102 -a 106 -o > file.ts
Only gives me mpeg audio.

dvbstream 101 102 106 -o > file.ts
Gives me corrupt video. As soon as I have 2 or more pids, without using 
-a and -v, the video is corrupted. This doesn't happen on a budget card 
I have in another computer.

So, is there any way around this? Am I doing something wrong or is there 
a limitation in the FF card? DVB.NET for Windows can do this so perhaps 
the answer is another software? Suggestions are highly appreciated at 
this time. I'm out of ideas...

(Continue reading)

Jerome Robert | 1 Jan 2007 11:12
Picon

Re: Crackle sound with ASUSTeK 4871

Just to be clearer than when I say "crackled but understandable sound" 
here is a sample of what I hear: http://xrunhprof.free.fr/crackle.ogg

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

Jerome Robert | 1 Jan 2007 11:14
Picon

Re: Crackle sound with ASUSTeK 4871

> try like "arecord -D hw:1,0 -r 32000 -c 2 -f S16_LE | aplay"
> or connect the analog audio out on the card to your soundcard.
>   

I'm already playing sound like this. I don't have sound without using 
arecord/aplay.

I do not have accessible audio out on my card, I cannot plug it to my 
sound card with an external cable. There are cables plugged on my card 
inside my box so I guess this is how sound go to my sound card. It 
cannot easily see where this cable go. On Windows I only have sound with 
Media Center, with K!TV I don't have sound.

> With the current mercurial you can also just set "secam=L" as an option
> for the saa7134 module (e.g. for tvtime) or select it from an app like
> xawtv or mplayer directly.
>   
I just tried but it does not help. I guess this is equivalent to the 
secam=l parameter of the tuner module.

Just to be clearer than when I say "crackled but understandable sound" 
here is a sample of what I hear: http://xrunhprof.free.fr/crackle.ogg

I run regspy on windows to get my audio clock frequency (and may be use 
the audio_clock_override parameter) but the value I get is very strange 
(0x90909090):

SAA7133 Card [0]:

Vendor ID:           0x1131
(Continue reading)

Dwaine Garden | 1 Jan 2007 12:18
Favicon

Patch: Add Kworld ATSC110 HDTV CARD Remote Functionality

Been testing this patch for a couple of weeks.   Functionality works great.  A lot of people have been requesting
this patch.

Patch contents:
- Add ir remote functionality for the Kworld ATSC110 HDTV tuner card.

Signed-off-by: Dwaine P. Garden <DwaineGarden <at> rogers.com>
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request <at> redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
Dwaine Garden | 1 Jan 2007 12:18
Favicon

Fw: [linux-dvb] Problem with Kworld ATSC-110


----- Forwarded Message ----
From: Dwaine Garden <dwainegarden <at> rogers.com>
To: John <jharitos <at> yahoo.com>
Sent: Monday, January 1, 2007 6:10:05 AM
Subject: Re: [linux-dvb] Problem with Kworld ATSC-110

My understanding is the Dual decoder functionality is disabled for now for the moment.

Jan  1 05:34:16 mythtv kernel: saa7130/34: v4l2 driver version 0.2.14 loaded
Jan  1 05:34:16 mythtv kernel: saa7133[0]: found at 0000:00:0a.0, rev: 240, irq: 19, latency: 32, mmio: 0xe6000000
Jan  1 05:34:16 mythtv kernel: saa7133[0]: subsystem: 17de:7350, board: Kworld ATSC110 [card=90,autodetected]
Jan  1 05:34:16 mythtv kernel: saa7133[0]: board init: gpio is 100
Jan  1 05:34:16 mythtv kernel: saa7133[0]: Kworld ATSC110: dual saa713x broadcast decoders
Jan  1 05:34:16 mythtv kernel: saa7133[0]: Sorry, none of the inputs to this chip are supported yet.
Jan  1 05:34:16 mythtv kernel:
 saa7133[0]: Dual decoder functionality is disabled for now, use the other chip.
Jan  1 05:34:16 mythtv kernel: input: Kworld ATSC110 as /class/input/input9
Jan  1 05:34:16 mythtv kernel: ir-kbd-i2c: Kworld ATSC110 detected at i2c-0/0-0030/ir0 [saa7133[0]]
Jan  1 05:34:16 mythtv kernel: saa7133[0]: i2c eeprom 00: de 17 50 73 ff ff ff ff ff ff ff ff ff ff ff ff
Jan  1 05:34:16 mythtv kernel: saa7133[0]: i2c eeprom 10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Jan  1 05:34:16 mythtv kernel: saa7133[0]: i2c eeprom 20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Jan  1 05:34:16 mythtv kernel: saa7133[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Jan  1 05:34:16 mythtv kernel: saa7133[0]: i2c eeprom 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Jan  1 05:34:16 mythtv kernel: saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Jan  1 05:34:16 mythtv
 kernel: saa7133[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Jan  1 05:34:16 mythtv kernel: saa7133[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Jan  1 05:34:16 mythtv kernel: saa7133[0]: registered device video0 [v4l2]
Jan  1 05:34:16 mythtv kernel: saa7133[0]: registered device vbi0
(Continue reading)

Adam Hajduk | 1 Jan 2007 15:55
Picon
Favicon

Help!: v4l or Fedora versus saa7133

Hi!

Maybe somebody can point me to the right direction.

I'm using tv card based on a saa7133. The application derived from
xawtv-3.95 code is using the zvbi-0.2.22 library to receive teletext pages
and store it as the plain text in a file.

All this worked fine with old Red Hat distribution. After upgrade to Fedora
Core 6 it is not working properly anymore. It seems that page handler from
ZVBI is called very rarely. To complete a teletext page with few subpages it
takes hours. I have found some old mail threads explained the bug with
VBI_OFFSET setup, but I'm using now kernel version 2.6.18-1.2868, where the
VBI_OFFSET seems to have correct value. 

I really appreciate any hints.

Happy New Year! :-)

Adam

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

allenpauna | 1 Jan 2007 20:35

ivtv drivers load, but mplayer only shows upper part of channel

Hello all,

I am new to video4linux, so I choose to use the safe path for the install of 
MythTv. I followed the instructions in:

https://help.ubuntu.com/community/Install_IVTV_Edgy 

However, if I attempt to do the following for my PVR-350:

cat /dev/video0 > /tmp/test_capture.mpg

and the try to play it back with:

mplayer /tmp/test_capture.mpg

I get the video, but everything is stretched and I only see the top part of 
the channel. I have confirmed that I am set to NTSC and that I am on us-cable 
as the type, but nothing seems to matter. I have re-installed and this was the 
same problem that I had on Dapper version as well.

Has anyone else ran into this problem?

Are there any fixes for it?

I know my configuration works because I also rebuilt the PC using the Fedora 
HOWTO:

http://wilsonet.com/mythtv/fcmyth.php?
SID&expandables=open&ivtv=open&pvr350out=open

(Continue reading)

Michael Krufky | 1 Jan 2007 20:57
Gravatar

Re: [Fwd: Re: Ultraview DVB-T Lite Tv Card FC5 X86 64]

Arch Murphy wrote:
> Mike,
> 
> Thanks very much for your help.
> 
> It all works fine now. I am using the mplayer software already installed and it 
> appears to be ok.
> 
> I added these lines to /etc/rc.local
> 
> /sbin/modprobe dvb-bt8xx
> chmod 666 /dev/dvb/adapter0/*
> echo 1024 > /proc/sys/dev/rtc/max-user-freq
> 
> Did you get the photos?
> 
> Please advise if you need any further information about my installation. I will 
> help in any way I can.
> 
> Happy new year.

Arch,

Yes, I have received the photos, thanks.  I'm glad that your card is working now... Thanks
for the testing.  Could you revert the changes that you have made, and test this patch for me?

This patch adds support for your card while not affecting the already existing DVB-T Lite entry.

Please let me know how this works for you -- this is the change that will be applied to the official kernel.

(Continue reading)

Adam Hajduk | 1 Jan 2007 21:02
Picon
Favicon

RE: Help!: v4l or Fedora versus saa7133

Of course the saa driver is not using the VBI_OFFSET value, and when
checking the code at saa7146_vbi.c looks like the analogical value for saa
has not been changed from long time:
fh->vbi_fmt.offset = 248;

Anyway for me, as the end user, it looks like after one of the kernel
updates the text capturing ceased to work for this saa card. Any clue how to
pinpoint it down?

Adam

-----Original Message-----
From: video4linux-list-bounces <at> redhat.com
[mailto:video4linux-list-bounces <at> redhat.com] On Behalf Of Adam Hajduk
Sent: Monday, January 01, 2007 3:56 PM
To: video4linux-list <at> redhat.com
Subject: Help!: v4l or Fedora versus saa7133

Hi!

Maybe somebody can point me to the right direction.

I'm using tv card based on a saa7133. The application derived from
xawtv-3.95 code is using the zvbi-0.2.22 library to receive teletext pages
and store it as the plain text in a file.

All this worked fine with old Red Hat distribution. After upgrade to Fedora
Core 6 it is not working properly anymore. It seems that page handler from
ZVBI is called very rarely. To complete a teletext page with few subpages it
takes hours. I have found some old mail threads explained the bug with
(Continue reading)

Andrew Morton | 1 Jan 2007 22:30

KM_BOUNCE_READ in vivi.c


KM_BOUCE_READ is used by the block code from, it appears, interrupt
context.  At least, its main users in mm/bounce.c uses local_irq_save()
protection for it.

But afaict vivi.c uses the KM_BOUNCE_READ with local interrupts enabled. 
This means that if a disk interrupt occurs while vivi.c is using this
fixmap slot, the vivi.c driver will, upon return from that interrupt, find
that the fixmap slot now points at a different physical page.

The net result will probably be rare corruption of disk file contents,
because viv.c will now be altering the page which the disk code was
recently using. 

Bottom line: if vivi.c wants to use KM_BOUNCE_READ, it *must* keep local
interupts disabled for the entire operation.

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


Gmane