| /dports/multimedia/libv4l/linux-5.13-rc2/Documentation/userspace-api/media/v4l/ |
| H A D | dev-sliced-vbi.rst | 7 Sliced VBI Data Interface
53 Sliced VBI Format Negotiation
80 The sliced VBI API is more complicated than the raw VBI API because the
211 Sliced VBI services
294 Reading and writing sliced VBI data
375 Sliced VBI Data in MPEG Streams
382 sliced VBI data insertion with the
396 VBI data in the MPEG stream, if an application has negotiated sliced VBI
453 sliced VBI data is specified by struct
565 sliced VBI data. The sliced VBI data lines present correspond to
[all …]
|
| H A D | dev-raw-vbi.rst | 7 Raw VBI Data Interface
10 VBI is an abbreviation of Vertical Blanking Interval, a gap in the
11 sequence of lines of an analog video signal. During VBI no picture
21 of samples per line, we call this a VBI image.
29 To address the problems of finding related video and VBI devices VBI
55 Raw VBI Format Negotiation
118 first sample in the VBI image will be located ``offset`` /
137 line of the VBI image, of the first and the second field
187 .. flat-table:: Raw VBI Format Flags
249 Reading and writing VBI images
[all …]
|
| H A D | vidioc-g-sliced-vbi-cap.rst | 13 VIDIOC_G_SLICED_VBI_CAP - Query sliced VBI capabilities
34 To find out which data services are supported by a sliced VBI capture or
39 the sliced VBI API is unsupported or ``type`` is invalid.
94 - :cspan:`2` The number of VBI lines the hardware can capture or
129 .. flat-table:: Sliced VBI services
|
| /dports/multimedia/v4l-utils/linux-5.13-rc2/Documentation/userspace-api/media/v4l/ |
| H A D | dev-sliced-vbi.rst | 7 Sliced VBI Data Interface
53 Sliced VBI Format Negotiation
80 The sliced VBI API is more complicated than the raw VBI API because the
211 Sliced VBI services
294 Reading and writing sliced VBI data
375 Sliced VBI Data in MPEG Streams
382 sliced VBI data insertion with the
396 VBI data in the MPEG stream, if an application has negotiated sliced VBI
453 sliced VBI data is specified by struct
565 sliced VBI data. The sliced VBI data lines present correspond to
[all …]
|
| H A D | dev-raw-vbi.rst | 7 Raw VBI Data Interface
10 VBI is an abbreviation of Vertical Blanking Interval, a gap in the
11 sequence of lines of an analog video signal. During VBI no picture
21 of samples per line, we call this a VBI image.
29 To address the problems of finding related video and VBI devices VBI
55 Raw VBI Format Negotiation
118 first sample in the VBI image will be located ``offset`` /
137 line of the VBI image, of the first and the second field
187 .. flat-table:: Raw VBI Format Flags
249 Reading and writing VBI images
[all …]
|
| H A D | vidioc-g-sliced-vbi-cap.rst | 13 VIDIOC_G_SLICED_VBI_CAP - Query sliced VBI capabilities
34 To find out which data services are supported by a sliced VBI capture or
39 the sliced VBI API is unsupported or ``type`` is invalid.
94 - :cspan:`2` The number of VBI lines the hardware can capture or
129 .. flat-table:: Sliced VBI services
|
| /dports/multimedia/v4l_compat/linux-5.13-rc2/Documentation/userspace-api/media/v4l/ |
| H A D | dev-sliced-vbi.rst | 7 Sliced VBI Data Interface
53 Sliced VBI Format Negotiation
80 The sliced VBI API is more complicated than the raw VBI API because the
211 Sliced VBI services
294 Reading and writing sliced VBI data
375 Sliced VBI Data in MPEG Streams
382 sliced VBI data insertion with the
396 VBI data in the MPEG stream, if an application has negotiated sliced VBI
453 sliced VBI data is specified by struct
565 sliced VBI data. The sliced VBI data lines present correspond to
[all …]
|
| H A D | dev-raw-vbi.rst | 7 Raw VBI Data Interface
10 VBI is an abbreviation of Vertical Blanking Interval, a gap in the
11 sequence of lines of an analog video signal. During VBI no picture
21 of samples per line, we call this a VBI image.
29 To address the problems of finding related video and VBI devices VBI
55 Raw VBI Format Negotiation
118 first sample in the VBI image will be located ``offset`` /
137 line of the VBI image, of the first and the second field
187 .. flat-table:: Raw VBI Format Flags
249 Reading and writing VBI images
[all …]
|
| H A D | vidioc-g-sliced-vbi-cap.rst | 13 VIDIOC_G_SLICED_VBI_CAP - Query sliced VBI capabilities
34 To find out which data services are supported by a sliced VBI capture or
39 the sliced VBI API is unsupported or ``type`` is invalid.
94 - :cspan:`2` The number of VBI lines the hardware can capture or
129 .. flat-table:: Sliced VBI services
|
| /dports/devel/libzvbi/zvbi-0.2.35/ |
| H A D | NEWS | 46 license. The VBI proxy daemon, contributed programs, test programs
69 - The DVB VBI demultiplexer entered an endless loop on some input.
75 raw VBI data was added. It is now part of the API.
109 Capturing through the VBI proxy was added by Tom Zoerner. The
126 VBI proxy.
164 This version adds a simulated raw and sliced VBI capture device
167 convert sliced VBI data to raw VBI images are public now and an example
184 in the raw VBI decoder.
189 a work-around for a VBI offset bug in the bttv driver, enables
199 its own VBI decoder.
[all …]
|
| H A D | README | 2 libzvbi - VBI capture and decoding library
22 directories, and the VBI proxy daemon, are licensed under the
36 The vertical blanking interval (VBI) is an interval in an analog
41 during the VBI would naturally not be displayed; various test
46 FreeBSD BKTR raw VBI capture devices, from Linux DVB devices and
47 from a VBI proxy to share V4L and V4L2 VBI devices between multiple
50 It can demodulate raw to sliced VBI data in software, with support
55 Basically ZVBI offers all functions needed by VBI applications
|
| H A D | zvbi.spec.in | 2 Summary: Raw VBI, Teletext and Closed Caption decoding library
15 Routines to access raw VBI capture devices (currently the V4L and
16 V4L2 API, and the *BSD bktr driver are supported), a versatile VBI
|
| /dports/devel/libzvbi/zvbi-0.2.35/daemon/ |
| H A D | README | 1 About Linux "VBI proxy"
5 capture VBI data. The 2nd generation "v4l2" API allows multiple clients
8 able to start a Teletext application. The VBI proxy was developed as a
11 VBI can transport many independent data streams: VPS, WSS, Closed
16 signalling and more. We want to share one VBI stream between for
29 How does it work? The VBI proxy is implemented as a daemon "zvbid",
32 opens the VBI device and starts capturing and decoding the services
34 sliced VBI data, reducing the required bandwidth and saving repeated
38 instead of opening the VBI device as usual, clients have to connect to
86 them, perhaps only pure VBI apps - YMMV) in parallel.
[all …]
|
| /dports/multimedia/libv4l/linux-5.13-rc2/Documentation/userspace-api/media/drivers/ |
| H A D | cx2341x-uapi.rst | 132 Format of embedded V4L2_MPEG_STREAM_VBI_FMT_IVTV VBI data
138 This section describes the V4L2_MPEG_STREAM_VBI_FMT_IVTV format of the VBI data
141 chips), in particular a maximum size for the VBI data. Anything longer is cut
144 The advantage of this format is it is very compact and that all VBI data for
147 The stream ID of the VBI data is 0xBD. The maximum size of the embedded data is
148 4 + 43 * 36, which is 4 bytes for a header and 2 * 18 VBI lines with a 1 byte
150 the cx23415/6 firmware. Besides the data for the VBI lines we also need 36 bits
152 signifying that this data package contains V4L2_MPEG_STREAM_VBI_FMT_IVTV VBI data.
161 'ITV0': This magic number assumes all VBI lines are captured, i.e. it implicitly
165 captured VBI lines start:
|
| /dports/multimedia/v4l-utils/linux-5.13-rc2/Documentation/userspace-api/media/drivers/ |
| H A D | cx2341x-uapi.rst | 132 Format of embedded V4L2_MPEG_STREAM_VBI_FMT_IVTV VBI data
138 This section describes the V4L2_MPEG_STREAM_VBI_FMT_IVTV format of the VBI data
141 chips), in particular a maximum size for the VBI data. Anything longer is cut
144 The advantage of this format is it is very compact and that all VBI data for
147 The stream ID of the VBI data is 0xBD. The maximum size of the embedded data is
148 4 + 43 * 36, which is 4 bytes for a header and 2 * 18 VBI lines with a 1 byte
150 the cx23415/6 firmware. Besides the data for the VBI lines we also need 36 bits
152 signifying that this data package contains V4L2_MPEG_STREAM_VBI_FMT_IVTV VBI data.
161 'ITV0': This magic number assumes all VBI lines are captured, i.e. it implicitly
165 captured VBI lines start:
|
| /dports/multimedia/v4l_compat/linux-5.13-rc2/Documentation/userspace-api/media/drivers/ |
| H A D | cx2341x-uapi.rst | 132 Format of embedded V4L2_MPEG_STREAM_VBI_FMT_IVTV VBI data
138 This section describes the V4L2_MPEG_STREAM_VBI_FMT_IVTV format of the VBI data
141 chips), in particular a maximum size for the VBI data. Anything longer is cut
144 The advantage of this format is it is very compact and that all VBI data for
147 The stream ID of the VBI data is 0xBD. The maximum size of the embedded data is
148 4 + 43 * 36, which is 4 bytes for a header and 2 * 18 VBI lines with a 1 byte
150 the cx23415/6 firmware. Besides the data for the VBI lines we also need 36 bits
152 signifying that this data package contains V4L2_MPEG_STREAM_VBI_FMT_IVTV VBI data.
161 'ITV0': This magic number assumes all VBI lines are captured, i.e. it implicitly
165 captured VBI lines start:
|
| /dports/devel/libzvbi/zvbi-0.2.35/po/ |
| H A D | nl.po | 369 msgstr "Niet genoeg geheugen om VBI-capturebuffer (%d kB) te reserveren."
383 msgstr "Kan de VBI-capture-parameters voor %s (%s) niet activeren: %s."
435 msgstr "%s (%s) is geen VBI-apparaat."
496 msgstr "Kan de huidige VBI-parameters van %s (%s) niet uitlezen: %s."
532 "%s (%s) ontbeert een VBI-leesinterface, driver bug of apparaat is "
635 #~ msgid "V4L/V4L2 VBI interface: Failed to read from the device"
636 #~ msgstr "V4L/V4L2 VBI-interface: Leesfout"
642 #~ msgstr "%s (%s) geeft een onmogelijke VBI-framegrootte aan. %s\n"
648 #~ msgid "V4L2 VBI interface: Capture stalled, no station tuned in?"
651 #~ msgid "V4L2 VBI interface: Failed to read from the device"
[all …]
|
| /dports/net-mgmt/observium/observium/mibs/cisco/ |
| H A D | CISCO-DMN-DSG-VBI-MIB | 2 -- CISCO_DMN_DSG_VBI.mib: MIB file for VBI control and status.
9 CISCO-DMN-DSG-VBI-MIB
35 DESCRIPTION "Cisco VBI MIB."
48 -- VBI Branch
|
| /dports/lang/gcc6-aux/gcc-6-20180516/gcc/testsuite/gcc.target/powerpc/ |
| H A D | altivec-30.c | 26 #define VBI vector bool int macro
32 VBI e;
|
| H A D | altivec-31.c | 23 #define VBI vector _Bool int macro
29 VBI e;
|
| /dports/lang/gcc12-devel/gcc-12-20211205/gcc/testsuite/gcc.target/powerpc/ |
| H A D | altivec-30.c | 26 #define VBI vector bool int macro
32 VBI e;
|
| H A D | altivec-31.c | 23 #define VBI vector _Bool int macro
29 VBI e;
|
| /dports/lang/gcc8/gcc-8.5.0/gcc/testsuite/gcc.target/powerpc/ |
| H A D | altivec-31.c | 23 #define VBI vector _Bool int macro
29 VBI e;
|
| /dports/devel/riscv64-none-elf-gcc/gcc-8.4.0/gcc/testsuite/gcc.target/powerpc/ |
| H A D | altivec-31.c | 23 #define VBI vector _Bool int macro
29 VBI e;
|
| H A D | altivec-30.c | 26 #define VBI vector bool int macro
32 VBI e;
|