From owner-freebsd-multimedia Mon Mar 17 14:07:32 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id OAA07633 for multimedia-outgoing; Mon, 17 Mar 1997 14:07:32 -0800 (PST) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA07628 for ; Mon, 17 Mar 1997 14:07:27 -0800 (PST) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.5/8.7.3) with ESMTP id OAA03757; Mon, 17 Mar 1997 14:07:24 -0800 (PST) Message-Id: <199703172207.OAA03757@rah.star-gate.com> X-Mailer: exmh version 1.6.9 8/22/96 To: Randall Hopper cc: multimedia@freebsd.org Subject: Re: 3/16 bt848 driver In-reply-to: Your message of "Mon, 17 Mar 1997 16:55:50 EST." <19970317165550.46327@ct.picker.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 17 Mar 1997 14:07:24 -0800 From: Amancio Hasty Sender: owner-multimedia@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I am aware of the CAP_SINGLE problem and will try to work on it this weekend. Try playing around with the driver since you have the databook. I find that in problems like this printing the status registers in bktr_intr helps a lot. As for the audio stuff I have not played with it yet. All in all I will back working on the Bt848 stuff this weekend because I am currently behind on my contract. Cheers, Amancio >From The Desk Of Randall Hopper : > When I freeze the video in fxtv, I switch over from CAP_CONTINUOUS > direct-video to a CAP_SINGLE-to-driver-mem which, when complete (signal > received), is displayed via XImage. > > Half the time, it works fine. But the other half, this CAP_SINGLE > only grabs one field instead of two. If I do this enough, I can see > successive freezes where the odd (or even) field is that left over from 4 > or 5 freezes ago. BTW, I'm not setting the ODD_ONLY or EVEN_ONLY flags in > the oformat, so I think it should always be grabbing two fields. Also, I'm > yanking the entire image each time from the driver buffer so the stale > field is from the driver. > > Could the driver possibly be not waiting on a cap single for the start > of the next frame to ensure it gets a complete two frames? > > Also, haven't gotten to digging in the driver yet, but was wondering > Amancio if your Wincast audio also stays glued to the Ext1 Input's audio > when switching between Tuner, Ext1, and SVHS. > > Randall > >