From owner-freebsd-multimedia Thu Apr 17 14:17:42 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id OAA06550 for multimedia-outgoing; Thu, 17 Apr 1997 14:17:42 -0700 (PDT) Received: from whqvax.picker.com (whqvax.picker.com [144.54.1.1]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id OAA06543 for ; Thu, 17 Apr 1997 14:17:40 -0700 (PDT) Received: from ct.picker.com by whqvax.picker.com with SMTP; Thu, 17 Apr 1997 17:16:24 -0400 (EDT) Received: from elmer.ct.picker.com ([144.54.57.34]) by ct.picker.com (4.1/SMI-4.1) id AA08241; Thu, 17 Apr 97 17:16:35 EDT Received: by elmer.ct.picker.com (SMI-8.6/SMI-SVR4) id RAA01803; Thu, 17 Apr 1997 17:16:24 -0400 Message-Id: <19970417171623.21430@ct.picker.com> Date: Thu, 17 Apr 1997 17:16:23 -0400 From: Randall Hopper To: Amancio Hasty Cc: multimedia@freebsd.org Subject: Re: Fxtv 0.4 References: <19970416173828.02068@ct.picker.com> <199704170031.RAA00609@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: <199704170031.RAA00609@rah.star-gate.com>; from Amancio Hasty on Wed, Apr 16, 1997 at 05:31:35PM -0700 Sender: owner-multimedia@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Amancio Hasty: |Most cool. Works like a charm over here. |When moving the window around, can you freeze the last shown frame |so that we don't get a black window. Sounds like a good idea, but first let me get you to try something to see if its easily done: 1) Freeze frame once 2) Turn continuous back on 3) Then move the window while the video is running If you see the last freeze frame in the video window while you're moving, should be an easy fix. That is, the window manager would seem to be blasting refresh events at the window while its configuring. Which window manager are you using and how do you have your move policy configured (I'm assuming you've got opaque moves turned on)? Also, do you have any window manager whiz-bangs pop up on top of fxtv when you're moving/resizing it that can change visibility (e.g. the "window position-queue pop-up"). With fvwm2 outline moves on a direct-video fxtv work fine because the configure doesn't come in until after the drag and release. With opaque moves on fvwm2 though, fxtv leaves some pixel trash in its wake because continuous reconfigures are being sent and the video is just rolling away, moving a little with each Configure event -- its on my list of things to look at fixing. |We have to get you clipping support and then you will be all set. | |So for version 1.x we will add clipping and arbiratry support for |different orders of pixels RGB vs BGR etc.. | |An experimental version of the driver has some primitive clipping so |that functionality seems to work with the bt848. Sounds cool! Randall