From: Rich Sahlender <rsahlender@gmail.com>
To: linux-media@vger.kernel.org
Subject: Re: No Sound from EM2861 Device
Date: Tue, 30 Aug 2022 09:33:57 -0400 [thread overview]
Message-ID: <a1af00d2-b997-00c1-dc9f-efef1306c3f4@gmail.com> (raw)
In-Reply-To: <35680d5e-26f0-04f7-15bd-3be3317ffec3@gmail.com>
Is this not the correct place to ask? Did I perhaps not provide
sufficient detail?
The EM28xx card list at kernel.org seems to imply that this device
should work however the list at linuxtv.org seems to imply that it is
not yet validated upstream and that one should send detail to this list
for assistance.
Should I be asking elsewhere?
Thanks.
On 8/25/22 10:43, Rich Sahlender wrote:
> Hello - I have a USB capture device from ClearClick. This device has
> both analog and s-video connections and lsusb shows the device as:
>
> Bus 002 Device 004: ID eb1a:2861 eMPIA Technology, Inc. EasyCAP DC60+
> [EM2861]
>
> Using the Qt V4L2 Test Bench utility and selecting this device and
> setting NTSC as the standard the video looks good from a DVD player
> but there is no sound. In the User Controls tab of the test bench
> utility I found the mute box was checked by default. When I uncheck
> the mute box and restart there is still no sound regardless if using
> the analog connections or the s-video connection.
>
> The playback tab in the alsa mixer shows 100% for ALSA plug-in
> [qv4l2]. The input devices tab shows EasyCAP DC60+ [EM2861] Digital
> Stereo (IEC958) at 100% and Port for this shows Digital Input (S/PDIF)
> with no other choices.
>
> I have read that many other EM28xx devices work well but perhaps there
> is something different about this one from ClearClick or I have just
> not set things up properly yet? Any suggestions on how to troubleshoot
> further?
>
> Thanks.
>
> Rich
>
prev parent reply other threads:[~2022-08-30 13:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-25 14:43 No Sound from EM2861 Device Rich Sahlender
2022-08-30 13:33 ` Rich Sahlender [this message]
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=a1af00d2-b997-00c1-dc9f-efef1306c3f4@gmail.com \
--to=rsahlender@gmail.com \
--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