Linux Media Controller development
 help / color / mirror / Atom feed
From: "Alexander Wipperfürth" <wpprfrth@posteo.de>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: linux-media@vger.kernel.org
Subject: Re: game capture usb device stops working
Date: Tue, 17 May 2022 23:35:06 +0000	[thread overview]
Message-ID: <7412d089-1276-5fda-bfb6-ea90a6b5c15b@posteo.de> (raw)
In-Reply-To: <YoQv1CTNTInprDXd@pendragon.ideasonboard.com>

Hi Laurent,

Right now I have the following scenario, after re-plugging it in for 3 
times it started working again as it should, then I changed the setting 
for Video Format and I get the following in the kernel log:

[15207.692208] uvcvideo 2-4:1.1: Failed to set UVC probe control : -32 
(exp. 34).

On 18.05.22 01:29, Laurent Pinchart wrote:
> Hi Alexander,
>
> On Tue, May 17, 2022 at 08:34:18PM +0000, Alexander Wipperfürth wrote:
>> Hello, today I got a usb capture card (Elgato HD60 S+) which is uvc
>> compatible and the first time I connected it to my computer it was
>> immediately recognized and the video from the game console was displayed
>> in OBS, but when I change any setting in the configuration menu the
>> device stops working, no video will be displayed anymore, I have to plug
>> it in and out multiple times until it starts showing video again, I hope
>> with me stating this issue here someone maybe knows a solution or
>> explanation why this could happen.
>>
>> Is there anything I should provide that may be useful?
> Are there any messages printed to the kernel log when this occurs ?
>

  reply	other threads:[~2022-05-17 23:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-17 20:34 game capture usb device stops working Alexander Wipperfürth
2022-05-17 23:29 ` Laurent Pinchart
2022-05-17 23:35   ` Alexander Wipperfürth [this message]
2022-05-18  1:04     ` Alexander Wipperfürth

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=7412d089-1276-5fda-bfb6-ea90a6b5c15b@posteo.de \
    --to=wpprfrth@posteo.de \
    --cc=laurent.pinchart@ideasonboard.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