search for: interlaces

dv file from minidv camera - interlaced. small dv created by imported jpeg images - not interlaced. seems that when I use ffmpeg2theora with deinterlace switch and reduce size, it works. But when the only reduction I am doing is to width (720x480 -> 640x480) the encoder ignores the naturally interlaced bit and uses the last de-interlaced frame. Since the small bit made from jpegs is a dv

Hello, I'll start by applauding your efforts to make an open source driver for nv hardware. I imagine it is a very difficult task trying to reverse engineer hardware and produce something useful and featureful. I wish to make a change to the nouveau source. You might say I am considering becoming a nouveau developer. I am one of those crazy nutters who connects my nvidia card directly to

http://bugs.freedesktop.org/show_bug.cgi?id=22317 Summary: Interlace does not work with Geforce 6200 / NV44a Product: xorg Version: git Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org

Right now, we make the mistake of allowing interlacing on all connectors. Nvidia hardware does not always support interlacing with DP though, so we need to make sure that we don't allow interlaced modes to be set in such situations as otherwise we'll end up accidentally hanging the display HW. This fixes some hangs with Turing, which would be caused by attempting to set an interlaced mode

Hi, I tried using the nouveau driver that comes latest with Fedora Rawhide (xorg-x11-drv-nouveau-0.0.10-1.20080311git460cb26) on my HP Pavilion dv2000 laptop with a GeForce 7150M (PCI 10de:0531) but couldn't even get the server up. The server spit out the following log. Could someone tell me how to get things working? Or even if I should file a bug? Xorg.0.log: X.Org X Server 1.4.99.901

We advertise being able to set interlaced modes, so let's actually make sure to do that. Otherwise, we'll end up hanging the display engine due to trying to set a mode with timings adjusted for interlacing without telling the hardware it's actually an interlaced mode. Signed-off-by: Lyude Paul <lyude at redhat.com> --- drivers/gpu/drm/nouveau/dispnv50/headc37d.c | 5 +++--

I want to interlace two vectors. This I can do: > x <- 1:4 > z <- x+0.5 > as.vector(t(cbind(x,z))) [1] 1.0 1.5 2.0 2.5 3.0 3.5 4.0 4.5 but this seems rather inelegant. Any suggestions? Murray -- Dr Murray Jorgensen http://www.stats.waikato.ac.nz/Staff/maj.html Department of Statistics, University of Waikato, Hamilton, New Zealand Email: maj at waikato.ac.nz

We advertise being able to set interlaced modes, so let's actually make sure to do that. Otherwise, we'll end up hanging the display engine due to trying to set a mode with timings adjusted for interlacing without telling the hardware it's actually an interlaced mode. Signed-off-by: Lyude Paul <lyude at redhat.com> Cc: stable at vger.kernel.org ---

Can anyone tell me if it is possible to encode music in an "interlaced" format.. perhaps I should explain what I mean by this. Say I'm getting 1k/sec off some guy's modem on opennap. It would be sweet if I could listen to the song as it is downloading but obviously the quality is gunna suck. So suppose the song was encoded in this interlaced fashion, I would be able to

Quite a while ago, the specification was modified to change the way the nondefault scan format was signalled; this patch fixes that. Index: liboggz/dirac.c =================================================================== --- liboggz/dirac.c (revision 3759) +++ liboggz/dirac.c (working copy) @@ -122,6 +122,10 @@ 1, 9, 10, 9, 10, 9, 10, 4, 3, 7, 6, 4, 3, 7, 6, 2, 2, 7, 6, 7, 6, }; +

NVIDIA G98 mesa-dri-drivers-11.2.1-2.20160501.fc22.x86_64 (incl. mesa commit 38fcf7c) vdpauinfo | grep -i deint DEINTERLACE_TEMPORAL y DEINTERLACE_TEMPORAL_SPATIAL - https://cgit.freedesktop.org/vdpau/libvdpau/tree/include/vdpau/vdpau.h#n3420 #define VDP_VIDEO_MIXER_FEATURE_DEINTERLACE_TEMPORAL ((VdpVideoMixerFeature)0) /** * \hideinitializer * \brief A

On 09.05.2016 19:37, Ilia Mirkin wrote: > Mesa only supports the non-spatial temporal deinterlace (deint=3). I'm > guessing that due to some unfortunate issues, you're no longer getting > hw accelerated video decoding. Check in vdpauinfo to make sure that > it's indeed showing the relevant codec as supported. If not, you can > turn that back on by updating to mesa

http://bugs.freedesktop.org/show_bug.cgi?id=18071 Summary: Interlaced DVI on NV34M doesn't work properly. Product: xorg Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org

On Mon, May 11, 2020 at 6:42 PM Lyude Paul <lyude at redhat.com> wrote: > diff --git a/drivers/gpu/drm/nouveau/nouveau_connector.c b/drivers/gpu/drm/nouveau/nouveau_connector.c > index 43bcbb6d73c4..6dae00da5d7e 100644 > --- a/drivers/gpu/drm/nouveau/nouveau_connector.c > +++ b/drivers/gpu/drm/nouveau/nouveau_connector.c > @@ -1065,7 +1065,7 @@

Currently, nouveau doesn't actually bother to try probing whether or not it can actually handle interlaced modes over DisplayPort. As a result, on volta and later we'll end up trying to set an interlaced mode even when it's not supported and cause the front end for the display engine to hang. So, let's teach nouveau to reject interlaced modes on hardware that can't actually

The mt address is about to be used more, make sure it's set appropriately. Reported-by: Emil Velikov <emil.l.velikov at gmail.com> Tested-by: Emil Velikov <emil.l.velikov at gmail.com> Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> Cc: "10.2 10.3" <mesa-stable at lists.freedesktop.org> --- src/gallium/drivers/nouveau/nv50/nv84_video.c | 2 ++ 1 file

Currently, nouveau doesn't actually bother to try probing whether or not it can actually handle interlaced modes over DisplayPort. As a result, on volta and later we'll end up trying to set an interlaced mode even when it's not supported and cause the front end for the display engine to hang. So, let's teach nouveau to reject interlaced modes on hardware that can't actually

Currently, nouveau doesn't actually bother to try probing whether or not it can actually handle interlaced modes over DisplayPort. As a result, on volta and later we'll end up trying to set an interlaced mode even when it's not supported and cause the front end for the display engine to hang. So, let's teach nouveau to reject interlaced modes on hardware that can't actually

On Tue, Nov 4, 2008 at 12:56 AM, David Flynn <davidf+nntp at woaf.net> wrote: > Quite a while ago, the specification was modified to change the > way the nondefault scan format was signalled; this patch fixes that. Thanks for the patch. I've tried to fix things as discussed on irc. Please review r3762. Index: /liboggz/trunk/src/liboggz/dirac.c

as per yesterday's discussion at #theora -- It has been suggested that we devise a method such that we will be able to add certain features to the bitstream (interlace, exotic color subsampling, clip length flag for download, etc), in such a way as to not obsolete streams encoded previously. Rillian's suggestion, which is pretty much standard practice, is to add a bitstream revision