Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Marth64 <marth64@proxyid.net>
To: scott.the.elm@gmail.com
Cc: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 1/2] libavcodec: add AV_CODEC_ID_IVTV_VBI
Date: Mon, 3 Feb 2025 20:59:53 -0600
Message-ID: <CAAhd_PVGXC7NgM0TZ7o3NHbsoPSoc6PpmfikZy27KOxrGpVF-A@mail.gmail.com> (raw)
In-Reply-To: <CA+28BfByJ7BxH1RQ6+tyhe5TCaTUGX+pjLkkpsYANBTLKJAsRQ@mail.gmail.com>

Hi Scott,

LGTM.
I will push soon and fix the APIchanges on the way.

Apologies for the delay on this simple patch.
Had a lot of issues getting the machine up and running.

I was able to capture a sample finally and test this out.
I wanted to test it to get an idea of how EIA-608 travels through this stream.
The patch works and detects the discrete ivtv sliced VBI stream correctly.

Based on the V4L2 docs and controls the coded VBI stream can contain
EIA-608, Teletext, WSS (PAL widescreen signaling), or VPS (PAL VCR
signaling).

Even though there is no decoder/further demuxer yet to unwrap this, I
am good with AVMEDIA_TYPE_SUBTITLE since this is effectively like
AV_CODEC_ID_EIA_608 (where EIA608/DTVCC/XDS are clumped together
similarly).

I'm working on a prototype/idea to improve handling of these wrapped
caption formats and will take this one into consideration.

For anyone who wants to try,
```
v4l2-ctl -b cc  -d /dev/vbi0 # set device to capture CC in sliced VBI
v4l2-ctl -B -d /dev/vbi0 # validate above

v4l2-ctl -d /dev/video0 -c stream_vbi_format=1 # tell V4L2 to inject
the sliced VBI as IVTV format
v4l2-ctl -d /dev/video0 -l # validate the above
```
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

           reply	other threads:[~2025-02-04  3:00 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <CA+28BfByJ7BxH1RQ6+tyhe5TCaTUGX+pjLkkpsYANBTLKJAsRQ@mail.gmail.com>]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAAhd_PVGXC7NgM0TZ7o3NHbsoPSoc6PpmfikZy27KOxrGpVF-A@mail.gmail.com \
    --to=marth64@proxyid.net \
    --cc=ffmpeg-devel@ffmpeg.org \
    --cc=scott.the.elm@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
		ffmpegdev@gitmailbox.com
	public-inbox-index ffmpegdev

Example config snippet for mirrors.


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git