From owner-freebsd-multimedia Wed Jan 2 5: 2:46 2002 Delivered-To: freebsd-multimedia@freebsd.org Received: from mcqueen.wolfsburg.de (pns.wobline.de [212.68.68.5]) by hub.freebsd.org (Postfix) with ESMTP id 2C34F37B420 for ; Wed, 2 Jan 2002 05:02:43 -0800 (PST) Received: from colt.ncptiddische.net (ppp-189.wobline.de [212.68.69.200]) by mcqueen.wolfsburg.de (8.11.3/8.11.3/tw-20010821) with ESMTP id g02D2I721208; Wed, 2 Jan 2002 14:02:18 +0100 Received: from tisys.org (jodie.ncptiddische.net [192.168.0.2]) by colt.ncptiddische.net (8.11.6/8.11.6) with ESMTP id g02D2hX06267; Wed, 2 Jan 2002 14:02:43 +0100 (CET) (envelope-from nils@tisys.org) Received: (from nils@localhost) by tisys.org (8.11.6/8.11.6) id g02D2IN00399; Wed, 2 Jan 2002 14:02:18 +0100 (CET) (envelope-from nils) Date: Wed, 2 Jan 2002 14:01:43 +0100 From: Nils Holland To: Randall Hopper Cc: Roger Hardiman , freebsd-multimedia@FreeBSD.ORG Subject: Re: bktr / fxtv problem revisited... Message-ID: <20020102140143.A370@tisys.org> References: <20020101134607.A151@tisys.org> <20011230170550.A33828@tisys.org> <20020101104922.C19839@nc.rr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020101104922.C19839@nc.rr.com>; from aa8vb@nc.rr.com on Tue, Jan 01, 2002 at 10:49:22AM -0500 X-Operating-System: FreeBSD jodie.ncptiddische.net 4.5-PRERELEASE FreeBSD 4.5-PRERELEASE X-Machine-Uptime: 1:53PM up 21 mins, 1 user, load averages: 0.01, 0.03, 0.01 Sender: owner-freebsd-multimedia@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi folks, I have (once again) done some more research on my bktr problem, and I'd like to share what I have found out. Again, any hints to make sense of what I am seeing are welcome! 1) I have now made a screenshot of this "interlaced" screen I see when using the PAL/BDGHI norm, which is basically the norm I should be using. The screenshot is at http://www.tisys.org/misc/fxtv_interlace.png. As you will notice, it seems as if every odd line is missing. Strangely, I only need to switch from PAL/BDGHI to PAL/N and everything looks normal. 2) One more strange thing: During my testing, I tried xawtv in order to display my TV picture. Now, in xawtv I can select between two capture modes: Overlay and screen grab. Overlay is the mode where the TV stream gets DMA'ed over to the graphics card, while in screen grab mode, I noticed something weird: When using screen grab in connection with PAL/BDGHI mode, I can see a "SIGALRM" message in the xterm from which I started xawtv about every second, followed by a screen refresh in the xawtv window. So, it seems that xawtv is using a timer to grab the screen at regular intervals. However, if I use PAL/N and screen grab, the SIGALRM timer no longer seems to be there, and I do no longer get a screen that updates once a second, but a smoothly moving stream (strange, is screen grab + PAL/N should behave the same as screen grab + PAL/BDGHI, I think). Well, mostly with this PAL/N workaround my WinTV card works as expected, though I find it strange that this workaround is needed. Therefore, I only wanted to post this last message along with my screenshot, in order to let everyone know what I have found out recently ;-) Greetings Nils (Again, plese CC replies to me! Thanks in advance!) -- Nils Holland Ti Systems - FreeBSD in Tiddische, Germany http://www.tisys.org * nils@tisys.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-multimedia" in the body of the message