linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Zigotzky <chzigotzky@xenosoft.de>
To: linux-media@vger.kernel.org,
	Deborah Brouwer <deborahbrouwer3563@gmail.com>,
	Hans Verkuil <hverkuil-cisco@xs4all.nl>
Subject: Re: [BTTV] [FSL P50x0] [PASEMI] TV Time doesn't work anymore after dropping the overlay support
Date: Sun, 10 Sep 2023 13:19:31 +0200	[thread overview]
Message-ID: <56c8ab9a-9084-40ad-be52-5394708e6755@xenosoft.de> (raw)

On 10 September 2023 at 04:33 am, Deborah Brouwer wrote:
 >
 > This is not debug code.  I made the change to fix the latency and
 > frame drop issues
 > that were otherwise occurring with vb2; as I said in the cover letter 
to v3:
 >
 > "- remove the last four lines in interlaced,
 > sequential top/bottom, and alternating buffers
 > to prevent long latency and frame drops
 > (this is instead of just enabling the existing
 > VCR hack by default);"
 > 
https://lore.kernel.org/linux-media/cover.1689379982.git.deborah.brouwer@collabora.com/
 >
 > However, if your testing shows that it isn't needed, then it would be
 > fine to remove this
 > code and just let the user enable the "vcr hack" as needed. This was
 > my original approach
 > in v2, but I thought you had said at the time that you were seeing
 > massive framedrops in v2?
 >
 > I didn't notice this green line before because I was testing in qv4l2
 > with the default
 > Pixel Format  : 'BGR3' (24-bit BGR 8-8-8) whereas tvtime is using
 > YUYV' (YUYV 4:2:2)
 >
 > One fix that worked for me was to adjust the "OverScan" configuration 
in tvtime
 > so that it is at least 3.5.  The /etc/tvtime/tvtime.xml configuration
 > file recommends
 > even higher at 8.0.  Christian, please try adjusting the overscan
 > value to see if
 > that is a possible solution as well.
 >
 > Thanks,
 > Deb

Hi Deb,

It works! :-)

I adjusted the OverScan configuration to 3.5 today (.tvtime/tvtime.xml) 
and this solved this issue.

Thanks a lot!

Cheers,
Christian

             reply	other threads:[~2023-09-10 11:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-10 11:19 Christian Zigotzky [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-04-26 14:09 [BTTV] [FSL P50x0] [PASEMI] TV Time doesn't work anymore after dropping the overlay support Christian Zigotzky
2023-05-01 15:20 ` Christian Zigotzky
2023-05-02  6:57   ` Hans Verkuil
2023-05-05  6:25     ` Christian Zigotzky
2023-05-05  6:45       ` Hans Verkuil
2023-05-05  7:20         ` Christian Zigotzky
2023-09-04 11:51           ` Christian Zigotzky
2023-09-04 12:02             ` Christian Zigotzky
2023-09-07 15:23             ` Hans Verkuil
2023-09-07 15:49               ` Christian Zigotzky
2023-09-10  2:33               ` Deborah Brouwer
2023-09-11  9:51                 ` Hans Verkuil
2023-09-14  7:01                   ` Hans Verkuil

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=56c8ab9a-9084-40ad-be52-5394708e6755@xenosoft.de \
    --to=chzigotzky@xenosoft.de \
    --cc=deborahbrouwer3563@gmail.com \
    --cc=hverkuil-cisco@xs4all.nl \
    --cc=linux-media@vger.kernel.org \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).