From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Luigi Baldoni <aloisio@gmx.com>,
linux-media@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Antti Palosaari <crope@iki.fi>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Hans Verkuil <hverkuil@xs4all.nl>
Subject: Re: Video glitch with Hanftek Astrometa
Date: Mon, 21 Aug 2023 17:59:14 +0700 [thread overview]
Message-ID: <ZONDguFpqRTHf_UV@debian.me> (raw)
In-Reply-To: <trinity-4a9cf567-5613-4ace-8e63-fa27d4450df6-1692446595564@3c-app-mailcom-bs14>
[-- Attachment #1: Type: text/plain, Size: 1476 bytes --]
On Sat, Aug 19, 2023 at 02:03:15PM +0200, Luigi Baldoni wrote:
> Hello everyone,
> last year I replaced my old RTL2832U/R820T DVB-T dongle (which worked
> perfectly) and replaced it with a Hanftek Astrometa (RTL2832/CXD2837ER)
> DVB-T2 one and my troubles started.
> Every channel I tune to shows a periodic glitch, as per included sample.
>
> I tried the following things:
> * connected a regular TV set to the same antenna cable and the picture looks
> fine
> * replaced the usb cable
> * switched distros (from debian to arch)
> * installed a current kernel snapshot
> * replaced the minipc on which it's installed
> * used usbip to access the hardware from my desktop machine and tested
> it directly with vlc, mpv and kaffeine: at best the stream was glitchy
> and at worst the app crashed
> * toggled every parameter available for each involved module
> * ran tzap directly
>
> None of the above made the slightest difference, therefore I'm asking you
> if there's something I might have overlooked or if this is truly a bug.
>
> Video sample here, captured with tzap:
> https://www.mediafire.com/file/qantvq916uy7o4k/rai1hd.ts/file
> https://www.4shared.com/s/folTulDcljq
>
(also Cc: RTL2832 and media subsystem maintainers)
What kernel version are you running?
Also, can you try with different dongle (ideally with different chipset)?
Thanks.
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next parent reply other threads:[~2023-08-21 10:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <trinity-4a9cf567-5613-4ace-8e63-fa27d4450df6-1692446595564@3c-app-mailcom-bs14>
2023-08-21 10:59 ` Bagas Sanjaya [this message]
2023-08-22 13:37 ` Video glitch with Hanftek Astrometa Luigi Baldoni
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=ZONDguFpqRTHf_UV@debian.me \
--to=bagasdotme@gmail.com \
--cc=aloisio@gmx.com \
--cc=crope@iki.fi \
--cc=hverkuil@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@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