LifeView FlyVideo3000FM NTSC: Difference between revisions

From LinuxTVWiki
Jump to navigation Jump to search
m (→‎Installation instructions: -- formatting, update)
Line 1: Line 1:
[[image:FlyVideo-3000-small.png_ntsc_a.jpg|right]]
====Installation instructions====

===Introduction ===
Identification

This card works perfectly -- it gets 640x480 frames, audio directly from the card, and closed captioning. Up to four cards can be placed in one computer, though you need a powerful CPU to keep up with the data flow.

For detailed images of the various slightly different models, see [http://www.bttv-gallery.de/ bttv gallery].

See also [[FlyVideo3000_PAL-N]].

=== Identification ===


lspci -vvv: 0000:02:0a.0 Multimedia controller: Philips Semiconductors SAA713X Audio+video broadcast decoder (rev 10)
lspci -vvv: 0000:02:0a.0 Multimedia controller: Philips Semiconductors SAA713X Audio+video broadcast decoder (rev 10)
Subsystem: Unknown device 5169:0138
Subsystem: Unknown device 5169:0138


This card has the [http://www.semiconductors.philips.com/pip/SAA7133HL_V101.html saa7133HL-v101] chip.
This card has the [http://www.semiconductors.philips.com/pip/SAA7133HL_V101.html saa7133HL-v101] chip.


=== Selecting the tuner ===
Use card 2 in the /usr/src/linux-2.6.12-rc2/Documentation/video4linux/CARDLIST.saa7134. Versions of FlyVideo 3000 are shipped with different [[Tuners |tuners]]; to find yours, grep on the card and your television standard to pull up relevant alternatives:


cat /usr/src/linux/Documentation/video4linux/CARDLIST.tuner | grep Philips | grep NTSC
Use card 2 in the Documentation/video4linux/CARDLIST.saa7134. Versions of FlyVideo 3000 are shipped with different [[Tuners |tuners]]; to find yours, grep on the card and your television standard to pull up relevant alternatives:

grep Philips Documentation/video4linux/CARDLIST.tuner | grep NTSC


For the NTSC tuner, I found 17 was the right one. A second and third card I got, also called FlyVideo3000FM, turned out to have a different tuner, namely 43. I had to reboot to reset the tuner; modprobe didn't do it.
For the NTSC tuner, I found 17 was the right one. A second and third card I got, also called FlyVideo3000FM, turned out to have a different tuner, namely 43. I had to reboot to reset the tuner; modprobe didn't do it.

=== Inserting the module ===


Boot with this in /etc/modules:
Boot with this in /etc/modules:


saa7134 card=2 tuner=17 oss=1
saa7134 card=2 tuner=17 oss=1

=== Getting PCI audio ===


The "oss=1" will create /dev/dsp1 and /dev/mixer1, and is added to take advantage of this card's ability to use PCI audio transfer -- that is to say, you can get the audio straight off the card, without needing a patch cable to your sound card. For detailed instructions, see [http://gentoo-wiki.com/HARDWARE_saa7134 Gentoo's saa7134 wiki].
The "oss=1" will create /dev/dsp1 and /dev/mixer1, and is added to take advantage of this card's ability to use PCI audio transfer -- that is to say, you can get the audio straight off the card, without needing a patch cable to your sound card. For detailed instructions, see [http://gentoo-wiki.com/HARDWARE_saa7134 Gentoo's saa7134 wiki].
Line 24: Line 38:
aumix -d /dev/mixer1 -I
aumix -d /dev/mixer1 -I


to set the recording channel to 1 and then use something like this:
to set the recording channel to 1.

=== Recording with mencoder ===

Use something like this:
mencoder tv:// -tv driver=v4l2:device=/dev/video1:fps=30000/1001:chanlist=us-cable:audiorate=32000:
mencoder tv:// -tv driver=v4l2:device=/dev/video1:fps=30000/1001:chanlist=us-cable:audiorate=32000:
Line 32: Line 50:
This gives me stereo audio with high-quality video. I found that if I included "-of mpeg" to create a true mpeg stream, the audio got delayed -- there are no sync problems with the avi file.
This gives me stereo audio with high-quality video. I found that if I included "-of mpeg" to create a true mpeg stream, the audio got delayed -- there are no sync problems with the avi file.


You can also use transcode:
=== Recording with transcode ===

You can also use transcode to record:


transcode -x v4l2,v4l2 -M 2 -i /dev/video$DEV -p /dev/dsp1 -e 32000,16,2 -y ffmpeg -F mpeg4
transcode -x v4l2,v4l2 -M 2 -i /dev/video$DEV -p /dev/dsp1 -e 32000,16,2 -y ffmpeg -F mpeg4
-c 00:30 -g 640x480 -f 29.970,4 -I 1 -u 1024 -Q 3 -E 32000,16,2 --lame_preset medium -o output.avi
-c 00:30 -g 640x480 -f 29.970,4 -I 1 -u 1024 -Q 3 -E 32000,16,2 --lame_preset medium -o output.avi


Note the "-e 32000,16,2", letting transcode know about the parameters of the audio stream from the saa7134 card. The files produced in this manner are almost twice as large as the ones produced by the mencoder command above, but show significantly less pixillation. CPU utilization is also about double. For the saa7134, 48000Hz is only valid for external audio input to the card; for tv you have to use 32000Hz.
Note the "-e 32000,16,2", letting transcode know about the parameters of the audio stream from the saa7134 card.

The files produced in this manner are almost twice as large as the ones produced by the mencoder command above, but show significantly less pixillation. CPU utilization is also about double. For the saa7134, 48000Hz is only valid for external audio input to the card; for tv you have to use 32000Hz.

=== Loading multiple cards ===


If you have more than one card in the same machine, and want to control which devices they create, you can use this sort of thing:
If you have more than one card in the same machine, and want to control which devices they create, you can use this sort of thing:
Line 44: Line 68:


This will give you video1, vbi1, dsp1, radio1, and mixer1 for the first card, and so on up.
This will give you video1, vbi1, dsp1, radio1, and mixer1 for the first card, and so on up.

=== Remote control ===


With the FlyVideo 3000, you should have the small grey credit-card sized remote. And yes, this is supported and should be working (I haven't tested it).
With the FlyVideo 3000, you should have the small grey credit-card sized remote. And yes, this is supported and should be working (I haven't tested it).


=== Closed captioning ===
Closed captioning on saa713x is now working; Michael Schimek has posted the necessary patches to the v4l and lkml mailing lists (mid-May 2005).

Closed captioning on saa713x is now working; Michael Schimek has added support to libzvbi (mid-May 2005).

Revision as of 23:55, 19 March 2006

Introduction

This card works perfectly -- it gets 640x480 frames, audio directly from the card, and closed captioning. Up to four cards can be placed in one computer, though you need a powerful CPU to keep up with the data flow.

For detailed images of the various slightly different models, see bttv gallery.

See also FlyVideo3000_PAL-N.

Identification

 lspci -vvv: 0000:02:0a.0 Multimedia controller: Philips Semiconductors SAA713X Audio+video broadcast decoder (rev 10)
 Subsystem: Unknown device 5169:0138

This card has the saa7133HL-v101 chip.

Selecting the tuner

Use card 2 in the Documentation/video4linux/CARDLIST.saa7134. Versions of FlyVideo 3000 are shipped with different tuners; to find yours, grep on the card and your television standard to pull up relevant alternatives:

grep Philips Documentation/video4linux/CARDLIST.tuner | grep NTSC

For the NTSC tuner, I found 17 was the right one. A second and third card I got, also called FlyVideo3000FM, turned out to have a different tuner, namely 43. I had to reboot to reset the tuner; modprobe didn't do it.

Inserting the module

Boot with this in /etc/modules:

  saa7134 card=2 tuner=17 oss=1

Getting PCI audio

The "oss=1" will create /dev/dsp1 and /dev/mixer1, and is added to take advantage of this card's ability to use PCI audio transfer -- that is to say, you can get the audio straight off the card, without needing a patch cable to your sound card. For detailed instructions, see Gentoo's saa7134 wiki.

In brief, you use

  aumix -d /dev/mixer1 -I

to set the recording channel to 1.

Recording with mencoder

Use something like this:

  mencoder tv:// -tv driver=v4l2:device=/dev/video1:fps=30000/1001:chanlist=us-cable:audiorate=32000:
  adevice=/dev/dsp1:input=0:amode=1:normid=4 -ffourcc DIVX -ovc lavc -lavcopts vcodec=mpeg4:vhq 
  -oac mp3lame -lameopts cbr:br=128 -endpos 60 -o output.avi

This gives me stereo audio with high-quality video. I found that if I included "-of mpeg" to create a true mpeg stream, the audio got delayed -- there are no sync problems with the avi file.

Recording with transcode

You can also use transcode to record:

  transcode -x v4l2,v4l2 -M 2 -i /dev/video$DEV -p /dev/dsp1 -e 32000,16,2 -y ffmpeg -F mpeg4 
  -c 00:30 -g 640x480 -f 29.970,4 -I 1 -u 1024 -Q 3 -E 32000,16,2 --lame_preset medium -o output.avi

Note the "-e 32000,16,2", letting transcode know about the parameters of the audio stream from the saa7134 card.

The files produced in this manner are almost twice as large as the ones produced by the mencoder command above, but show significantly less pixillation. CPU utilization is also about double. For the saa7134, 48000Hz is only valid for external audio input to the card; for tv you have to use 32000Hz.

Loading multiple cards

If you have more than one card in the same machine, and want to control which devices they create, you can use this sort of thing:

saa7134 video_nr=1,2,3 vbi_nr=1,2,3 mixer_nr=1,2,3 radio_nr=1,2,3 card=2,2,2 tuner=43,43,17 oss=1,1,1

This will give you video1, vbi1, dsp1, radio1, and mixer1 for the first card, and so on up.

Remote control

With the FlyVideo 3000, you should have the small grey credit-card sized remote. And yes, this is supported and should be working (I haven't tested it).

Closed captioning

Closed captioning on saa713x is now working; Michael Schimek has added support to libzvbi (mid-May 2005).