public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Devin Heitmueller <dheitmueller@kernellabs.com>
Cc: Ivan <ivan.q.public@gmail.com>, linux-media@vger.kernel.org
Subject: Re: em28xx: success report for KWORLD DVD Maker USB 2.0 (VS-USB2800) [eb1a:2860]
Date: Fri, 09 Jul 2010 17:57:25 -0300	[thread overview]
Message-ID: <4C378D35.3080007@redhat.com> (raw)
In-Reply-To: <AANLkTilSonpCN_gzfsOYVaMpXbmfPFVi6Wdxb06dK7W1@mail.gmail.com>

Em 09-07-2010 15:12, Devin Heitmueller escreveu:
> On Fri, Jul 9, 2010 at 2:03 PM, Mauro Carvalho Chehab
> <mchehab@redhat.com> wrote:
>> Em 09-07-2010 14:19, Ivan escreveu:
>>> On 07/09/2010 08:47 AM, Mauro Carvalho Chehab wrote:
>>>> I never saw the em28xx scaler generating such vertical stripes. This
>>>> could be a mplayer or a video adapter driver problem. Are you using a
>>>> proprietary video driver? You may try to use ffmeg or mencoder to
>>>> generate a mpeg file at 640x480 and then try to play it on another
>>>> player (preferably on another machine), to see if this problem
>>>> disappears.
>>>
>>> Huh? Does there even *exist* a proprietary linux driver for my card? And because you never saw stripes with em28xx, they must not exist? :^P
>>
>> Well, it depends. What are your video adapter card? ATI? Nvidia?
> 
> Mauro,
> 
> His issue with the "vertical stripes" has been fixed when he updated
> to the latest v4l-dvb code.  It's the issue I fixed a couple of months
> ago with the saa7113 chroma gain behavior when there is an overdriven
> signal.  The problem he's having now with the latest is the picture
> appears to be shifted.  I have to wonder if perhaps I screwed
> something up when I did the VBI support, in that it may not work
> properly when the scaler is in use.
> 
> I will have to do some testing.

I meant that vertical risk that appeared when scaling is on. I never saw em28xx
scaler doing something like that. It maybe some bug at mplayer or at the nvidia
proprietary driver. We know that this driver has serious issues with their Xv
support, and that it do some evil things when allocating kernel memory.

Cheers,
Mauro.

  parent reply	other threads:[~2010-07-09 20:57 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-08  1:56 em28xx: success report for KWORLD DVD Maker USB 2.0 (VS-USB2800) [eb1a:2860] Ivan
2010-07-08  2:12 ` Devin Heitmueller
2010-07-08 17:44   ` Ivan
2010-07-08 17:52     ` Devin Heitmueller
2010-07-08 19:52       ` Ivan
2010-07-08 20:02         ` Devin Heitmueller
2010-07-08 20:35           ` Ivan
2010-07-08 21:33             ` Ivan
2010-07-08 21:49               ` Devin Heitmueller
2010-07-08 22:10                 ` Ivan
2010-07-09 12:47                   ` Mauro Carvalho Chehab
2010-07-09 17:19                     ` Ivan
2010-07-09 18:03                       ` Mauro Carvalho Chehab
2010-07-09 18:12                         ` Devin Heitmueller
2010-07-09 19:02                           ` Ivan
2010-07-09 20:57                           ` Mauro Carvalho Chehab [this message]
2010-07-09 21:09                             ` Ivan

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=4C378D35.3080007@redhat.com \
    --to=mchehab@redhat.com \
    --cc=dheitmueller@kernellabs.com \
    --cc=ivan.q.public@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