From owner-freebsd-multimedia Mon May 22 13:47:23 2000 Delivered-To: freebsd-multimedia@freebsd.org Received: from MexComUSA.Net (adsl-63-200-120-86.dsl.mtry01.pacbell.net [63.200.120.86]) by hub.freebsd.org (Postfix) with ESMTP id 8232937BC31 for ; Mon, 22 May 2000 13:47:17 -0700 (PDT) (envelope-from eculp@EnContacto.Net) Received: from EnContacto.Net (adsl-63-200-120-86.dsl.mtry01.pacbell.net [63.200.120.86]) by MexComUSA.Net (8.9.3/8.9.3) with ESMTP id NAA34271 for ; Mon, 22 May 2000 13:46:58 -0700 (PDT) (envelope-from eculp@EnContacto.Net) Message-ID: <39299CC2.FE3F2A69@EnContacto.Net> Date: Mon, 22 May 2000 13:46:58 -0700 From: Edwin Culp Organization: Mexico Communicates, S.C. X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: multimedia@FreeBSD.Org Subject: USB Scanners Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-multimedia@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Is anyone using a USB Scanner with FreeBSD. I see that the SANE says that it does support some models. I have always used SCSI but now that I need a new one I see that the prices are much more attractive for USB. Thanks, ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-multimedia" in the body of the message From owner-freebsd-multimedia Mon May 22 17:44:57 2000 Delivered-To: freebsd-multimedia@freebsd.org Received: from rr.com (rdu25-28-182.nc.rr.com [24.25.28.182]) by hub.freebsd.org (Postfix) with ESMTP id 9B57437B9C3 for ; Mon, 22 May 2000 17:44:52 -0700 (PDT) (envelope-from rhh@rr.com) Received: (from rhh@localhost) by rr.com (8.9.3/8.9.3) id UAA07197; Mon, 22 May 2000 20:45:46 -0400 (EDT) (envelope-from rhh) Date: Mon, 22 May 2000 20:45:46 -0400 From: Randall Hopper To: Udo Erdelhoff Cc: multimedia@FreeBSD.ORG Subject: PCM set/get volume (was Re: Another datapoint) Message-ID: <20000522204546.B7033@nc.rr.com> References: <20000508110728.A33101@gruft.de> <3916966C.C5C3EB31@cs.strath.ac.uk> <20000508134336.A33792@gruft.de> <20000508131332.A10497@ipass.net> <20000517012159.A28648@gruft.de> <20000516200522.A815@ipass.net> <20000518184009.F19157@nathan.ruhr.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000518184009.F19157@nathan.ruhr.de>; from ue@nathan.ruhr.de on Thu, May 18, 2000 at 06:40:10PM +0200 Sender: owner-freebsd-multimedia@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Udo Erdelhoff: |I've used a small shell script to get "The Big Picture"(tm) |#!/bin/sh |A=0 |while [ $A -le 100 ]; do | mixer vol $A | mixer | A=`expr $A + 1` |done | |The result is consistent for all mixer devices: |Input Value Output Value |0 0 |1 4 |2 4 |3 4 |4 7 |5 7 |6 7 |7 10 ... |And that's the reason for the original poster's problem: fxtv reads the |mixer setting and writes it back. And that's enough to increase the volume |to max with just 32 cycles... | |/s/Udo |Config details: | |Kernel config: device pcm |FreeBSD 5.0-CURRENT #7: Thu Mar 30 07:45:57 CEST 2000 |pcm0: port 0xe000-0xe03f irq 5 at device 9.0 on pci0 Glad that you got it tracked down. Now the question is who maintains the ES1371 PCM driver. -- Randall Hopper aa8vb@nc.rr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-multimedia" in the body of the message From owner-freebsd-multimedia Mon May 22 19:27: 5 2000 Delivered-To: freebsd-multimedia@freebsd.org Received: from oxygen.yy.ics.keio.ac.jp (oxygen.yy.ics.keio.ac.jp [131.113.47.3]) by hub.freebsd.org (Postfix) with ESMTP id 7309237B656 for ; Mon, 22 May 2000 19:27:01 -0700 (PDT) (envelope-from sanpei@sanpei.org) Received: from lavender.yy.cs.keio.ac.jp (ppp144.dialup.st.keio.ac.jp [131.113.27.144]) by oxygen.yy.ics.keio.ac.jp (8.9.3+3.2W/3.7W) with ESMTP id LAA21484; Tue, 23 May 2000 11:26:52 +0900 (JST) (envelope-from sanpei@sanpei.org) Received: (from sanpei@localhost) by lavender.yy.cs.keio.ac.jp (8.9.3/3.7W) id LAA03519; Tue, 23 May 2000 11:26:50 +0900 (JST) Message-Id: <200005230226.LAA03519@lavender.yy.cs.keio.ac.jp> To: multimedia@FreeBSD.org Subject: [patch, ESS sound chip] ess_resume code for NOTE-PC X-Mailer: Mew version 1.70 on Emacs 19.34.1 / Mule 2.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 23 May 2000 11:26:50 +0900 From: MIHIRA Sanpei Yoshiro Sender: owner-freebsd-multimedia@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have NOTE-PC which has ESS 1869 sound chip. NEC MobioNX MMX Pentium120MHz [kernel configuration, this on-board card is not PnP] device pcm0 device sbc0 at isa? port 0x220 irq 5 drq 1 flags 0x13 % cat /dev/sndstat (under 5-current) FreeBSD Audio Driver (newpcm) May 21 2000 17:43:39 Installed devices: pcm0: at io 0x220 irq 5 drq 1:3 (1p/1r channels) ---------- After split up ess and sb code at 2000/03/28 by Cameron Grant-san, if I once suspend and resume NOTE-PC, I could not play MP3 file after resume. boot up kernel <--- I can play MP3 file suspend resume <--- I could not play MP3 file anymore mpg123 was run but increase count and no sound So I created quick hack patch for ess.c. Sorry I don't know why new ess.c code does not support above situation, what happen after resume.... If I have time, I will check it. P.S. I have another problem under ESS1869. If I set volume by /usr/sbin/mixer command. But it was not set correctly. % mixer vol 10 Setting the mixer vol to 10:10. ~~ ~~ % mixer vol Mixer vol is currently set to 9:9 ~ ~ Thank you. --- MIHIRA Sanpei Yoshiro Yokohama, Japan. --- sys/dev/sound/isa/ess.c.org Sun May 21 22:50:34 2000 +++ sys/dev/sound/isa/ess.c Tue May 23 11:11:30 2000 @@ -855,10 +855,25 @@ return ess_doattach(dev, sc); } +static int +ess_resume(device_t dev) +{ + struct ess_info *sc; + + sc = pcm_getdevinfo(dev); + if (ess_reset_dsp(sc)) { + device_printf(dev, "unable reset at resume\n"); + } else { + device_printf(dev, "reset at resume\n"); + } + return 0; +} + static device_method_t ess_methods[] = { /* Device interface */ DEVMETHOD(device_probe, ess_probe), DEVMETHOD(device_attach, ess_attach), + DEVMETHOD(device_resume, ess_resume), { 0, 0 } }; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-multimedia" in the body of the message From owner-freebsd-multimedia Tue May 23 5:50:58 2000 Delivered-To: freebsd-multimedia@freebsd.org Received: from peace.upol.cz (peace.upol.cz [158.194.200.76]) by hub.freebsd.org (Postfix) with ESMTP id 859BB37B83D; Tue, 23 May 2000 05:50:38 -0700 (PDT) (envelope-from zeno@peace.upol.cz) Received: from localhost (zeno@localhost) by peace.upol.cz (8.9.3/8.9.3) with ESMTP id OAA00580; Tue, 23 May 2000 14:50:39 +0200 (CEST) (envelope-from zeno@peace.upol.cz) Date: Tue, 23 May 2000 14:50:39 +0200 (CEST) From: Zeno To: freebsd-multimedia@freebsd.org, freebsd-questions@freebsd.org Subject: MAD16 in FreeBSD 4.0 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-multimedia@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi! I'm using FreeBSD-4.0-RELEASE and I'm not able to get my sound card work. my soundcard is "Monte Carlo 929" by "Turtle Beach". AFAIK there is MAD16 (OPTi 82C929) and is compatible w/ mss, sb (i guess sb pro), midi (YM 3812/OPL3) and have MPU 401 interface. I only need mss to work. There are some documents about configuring it but now... I found out this: using device snd is obsolete, I tried it and there is much more nois than real sounds device pcm doesnt find the card device pcm0 irq 10 ... etc.... then this if found: pcm0: at port 0x530-0x537 irq 10 drq 1 flags 0xa100 on isa0 but at boot time and at any time I want to use it, it seems to wait for some time-out... nothing there's nothing to be heared. $ cat /dev/sndstat FreeBSD Audio Driver (newpcm) May 23 2000 11:08:18 Installed devices: pcm0: at io 0x530 irq 10 drq 1 (1p/1r channels) I had the similar (or the same) problem in linux, it seems that it found mss (CS4231A) but do not use MAD16 which is really needed to be used to make sound (AFAIK - but maybe I'm wrong). I have found some information in list-archives - there was some options MAD16_PORT but it doesn't seem to work. And handbook is about kernel 3.x :( - am I missing the newest one? Any help? Zeno To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-multimedia" in the body of the message From owner-freebsd-multimedia Tue May 23 6:51:41 2000 Delivered-To: freebsd-multimedia@freebsd.org Received: from nts.mapisrael.com (nts.mapa.co.il [192.116.157.1]) by hub.freebsd.org (Postfix) with ESMTP id 14C7537BAD4; Tue, 23 May 2000 06:51:31 -0700 (PDT) (envelope-from ak@freenet.co.uk) Received: from freenet.co.uk (ALEX [192.116.157.120]) by nts.mapisrael.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id LHGYQWPT; Tue, 23 May 2000 16:51:15 +0200 Message-ID: <392A9ABF.9839713C@freenet.co.uk> Date: Tue, 23 May 2000 16:50:39 +0200 From: A G F Keahan X-Mailer: Mozilla 4.72 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Daniel Pouzzner Cc: freebsd-hackers@FreeBSD.ORG, freebsd-multimedia@FreeBSD.ORG Subject: Re: new device drivers for RME soundcard and G400-TV References: <200005230409.AAA24720@mega.mega.nu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-multimedia@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Daniel, First of all, I think you will get a lot more replies if you re-post your message to freebsd-multimedia (cc'd). Secondly, the author and maintainer of the new pcm driver in 4-stable and -current is Cameron Grant (cg@freebsd.org), and you should talk to him before starting anything serious. The sound driver in FreeBSD 3.4 (and earlier) is unmaintained and basically dead -- if your system is 3-stable or older, go -current, then backport your changes to 4-stable. I believe that newpcm was specifically designed to support advanced features of modern sound cards, and also to be easily extensible. The only functionality currently missing is MIDI, and you should talk to Seigo Tanimura about it (he has some patches to fix it). I also believe (and I'm sure that many people will agree with me) that we should try to stay clear of GPLd code unless absolutely unavoidable. FreeBSD's driver framework is sufficiently different from that of Linux that in practice it's not much of a problem. On the other hand, if porting the ALSA library would buy us support for a whole lot of new soundcards, it might be well worth it. Personally, I think that your time would be better spent improving the existing system rather than designing a new one. If you discover that newpcm is not powerful enough to accommodate some of the more advanced features of your card, then we should find a way to improve it. Good luck Alex Keahan Daniel Pouzzner wrote: > > I'm about to get cracking on a device driver for the RME Digi96/8 PAD. > > The card's full set of I/O channels is: S/PDIF I/O (2 channels in, 2 > out, 16-24 bits@32-96kHz), AES/EBU I/O (2ch in, 2 out, 16-24 > bits@32-96kHz), analog I/O (2ch in, 2 out, 16-24 bits@32-96kHz), and > ADAT I/O (8 channels in, 8 out, 16-24 bits@44.1 or 48kHz). > > The hardware supports on-board routing between these channels, > e.g. ADAT->S/PDIF or S/PDIF->ADAT. I will be supporting these > features. For those who are simply curious about features, see > http://www.rme-audio.com/english/digi96/digi96pa.htm > > My starting point (what I have in hand) is (1) a complete and > functioning driver (supporting most key functionalities of the card) > for Linux and the ALSA ("Advanced Linux Sound Architecture") > subsystem, and (2) complete internal documentation on the card, from > the manufacturer. > > Is FreeBSD's OSS-like audio subsystem powerful enough to provide > access to all the card's features (particularly, all its ports, word > sizes, and sample rates)? ac97.c goes only to 20 bits/sample, for > example, but the card is 24 bits throughout. > > I have to decide what strategy to pursue: do I write a new driver > based on an existing FreeBSD driver, using the Linux driver for hints, > or do I use a FreeBSD driver for hints, basing the new driver on the > Linux one (and thereby winding up with a GPL'd driver)? Or indeed do > I write a driver truly from the ground up? The only FreeBSD soundcard > driver I know of that includes analog and digital I/O support is the > SB Live! driver, which in my experience doesn't work particularly well > (in particular, capture didn't work at all when I tried it in April), > so my sense is that there exists no smoothly working FreeBSD driver > for a soundcard with anything remotely approaching the capabilities of > the RME products. > > Finally, I have to decide whether I will port the ALSA library (in > whole or in part - appealing because it would facilitate support for > the dozens of other soundcards ALSA supports and FreeBSD doesn't), > write a glue layer so that a driver that supplies an ALSA-type > interface will work with the FreeBSD audio subsystem, simply create a > driver that supplies a FreeBSD-style audio interface, or finally, > create a driver that allows direct and specialized ioctl access to > unusual card features not accommodated by the FreeBSD audio subsystem, > but otherwise providing access via /dev/dsp et al. > > This will be the first device driver I write. Any advice, assistance, > caveats, etc., will certainly be much appreciated. In particular, if > anyone has a guide to device driver implementation, draft or polished > form, complete or incomplete, it would surely be helpful to me. I > understand some basic porting issues, e.g. bus_space_read_4 instead of > readl(), copyin() instead of copy_from_user(), etc. The details will > come into focus with determination and repeated exposure. > > I already have the card on the PCI bus, and am quite committed to BSD, > so I will see this project to its successful conclusion (unless > someone beats me to it (by all means, go ahead!:-)). > > -Daniel Pouzzner > > P.S. Also, if no one beats me to it, I will port G400-TV support for > the realtime MJPEG codec, the TV/radio tuner, and video I/O and audio > routing. The Linux development effort > (http://marvel.sourceforge.net/) is just coming together and I won't > be embarking on the project until they've got things basically working > smoothly and I've got the RME card basically working smoothly. I do > already have a G400-TV on my machine, currently not using the -TV part > of course. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-multimedia" in the body of the message From owner-freebsd-multimedia Tue May 23 8:53:34 2000 Delivered-To: freebsd-multimedia@freebsd.org Received: from mega.mega.nu (mega.ne.mediaone.net [24.147.232.87]) by hub.freebsd.org (Postfix) with ESMTP id 02FE537B69F; Tue, 23 May 2000 08:53:22 -0700 (PDT) (envelope-from douzzer@mega.mega.nu) Received: (from douzzer@localhost) by mega.mega.nu (8.9.3/8.9.3) id LAA25710; Tue, 23 May 2000 11:52:47 -0400 (EDT) (envelope-from douzzer@mega.mega.nu) Date: Tue, 23 May 2000 11:52:47 -0400 (EDT) Message-Id: <200005231552.LAA25710@mega.mega.nu> X-Authentication-Warning: mega.mega.nu: douzzer set sender to douzzer@mega.mega.nu using -f To: ak@freenet.co.uk Cc: cg@freebsd.org, freebsd-hackers@freebsd.org, freebsd-multimedia@freebsd.org Subject: Re: new device drivers for RME soundcard and G400-TV From: Daniel Pouzzner Sender: owner-freebsd-multimedia@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >I think you will get a lot more replies if you re-post >your message to freebsd-multimedia (cc'd). I've added myself to that list. >Secondly, the author and >maintainer of the new pcm driver in 4-stable and -current is Cameron >Grant (cg@freebsd.org) That's the subsystem I'm working with. -* uname -a FreeBSD mega 4.0-RELEASE FreeBSD 4.0-RELEASE #10: Mon Apr 24 19:27:08 EDT 2000 douzzer@mega:/usr/src/sys/compile/MEGA i386 >I believe that newpcm was specifically designed to support advanced >features of modern sound cards, and also to be easily extensible. I think the best strategy is to document the procedure whereby an ALSA driver is morphed into a newpcm driver, starting with the RME driver as a test case and example. >we >should try to stay clear of GPLd code No doubt. >if >porting the ALSA library would buy us support for a whole lot of new >soundcards, it might be well worth it. I'm going to try to have it both ways, by semi-automating the process of transplanting ALSA card drivers into newpcm. >If you discover that >newpcm is not powerful enough to accommodate some of the more advanced >features of your card, then we should find a way to improve it. Fair enough. -Daniel >Daniel Pouzzner wrote: >> >> I'm about to get cracking on a device driver for the RME Digi96/8 PAD. >> >> The card's full set of I/O channels is: S/PDIF I/O (2 channels in, 2 >> out, 16-24 bits@32-96kHz), AES/EBU I/O (2ch in, 2 out, 16-24 >> bits@32-96kHz), analog I/O (2ch in, 2 out, 16-24 bits@32-96kHz), and >> ADAT I/O (8 channels in, 8 out, 16-24 bits@44.1 or 48kHz). >> >> The hardware supports on-board routing between these channels, >> e.g. ADAT->S/PDIF or S/PDIF->ADAT. I will be supporting these >> features. For those who are simply curious about features, see >> http://www.rme-audio.com/english/digi96/digi96pa.htm >> >> My starting point (what I have in hand) is (1) a complete and >> functioning driver (supporting most key functionalities of the card) >> for Linux and the ALSA ("Advanced Linux Sound Architecture") >> subsystem, and (2) complete internal documentation on the card, from >> the manufacturer. >> >> Is FreeBSD's OSS-like audio subsystem powerful enough to provide >> access to all the card's features (particularly, all its ports, word >> sizes, and sample rates)? ac97.c goes only to 20 bits/sample, for >> example, but the card is 24 bits throughout. >> >> I have to decide what strategy to pursue: do I write a new driver >> based on an existing FreeBSD driver, using the Linux driver for hints, >> or do I use a FreeBSD driver for hints, basing the new driver on the >> Linux one (and thereby winding up with a GPL'd driver)? Or indeed do >> I write a driver truly from the ground up? The only FreeBSD soundcard >> driver I know of that includes analog and digital I/O support is the >> SB Live! driver, which in my experience doesn't work particularly well >> (in particular, capture didn't work at all when I tried it in April), >> so my sense is that there exists no smoothly working FreeBSD driver >> for a soundcard with anything remotely approaching the capabilities of >> the RME products. >> >> Finally, I have to decide whether I will port the ALSA library (in >> whole or in part - appealing because it would facilitate support for >> the dozens of other soundcards ALSA supports and FreeBSD doesn't), >> write a glue layer so that a driver that supplies an ALSA-type >> interface will work with the FreeBSD audio subsystem, simply create a >> driver that supplies a FreeBSD-style audio interface, or finally, >> create a driver that allows direct and specialized ioctl access to >> unusual card features not accommodated by the FreeBSD audio subsystem, >> but otherwise providing access via /dev/dsp et al. >> >> This will be the first device driver I write. Any advice, assistance, >> caveats, etc., will certainly be much appreciated. In particular, if >> anyone has a guide to device driver implementation, draft or polished >> form, complete or incomplete, it would surely be helpful to me. I >> understand some basic porting issues, e.g. bus_space_read_4 instead of >> readl(), copyin() instead of copy_from_user(), etc. The details will >> come into focus with determination and repeated exposure. >> >> I already have the card on the PCI bus, and am quite committed to BSD, >> so I will see this project to its successful conclusion (unless >> someone beats me to it (by all means, go ahead!:-)). >> >> -Daniel Pouzzner >> >> P.S. Also, if no one beats me to it, I will port G400-TV support for >> the realtime MJPEG codec, the TV/radio tuner, and video I/O and audio >> routing. The Linux development effort >> (http://marvel.sourceforge.net/) is just coming together and I won't >> be embarking on the project until they've got things basically working >> smoothly and I've got the RME card basically working smoothly. I do >> already have a G400-TV on my machine, currently not using the -TV part >> of course. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-multimedia" in the body of the message From owner-freebsd-multimedia Wed May 24 1:18: 4 2000 Delivered-To: freebsd-multimedia@freebsd.org Received: from blizzard.sabbo.net (blizzard.sabbo.net [193.193.218.18]) by hub.freebsd.org (Postfix) with ESMTP id CB2A237B733; Wed, 24 May 2000 01:17:56 -0700 (PDT) (envelope-from SoboMax@FreeBSD.org) Received: from vega.vega.com (vic.sabbo.net [193.193.218.106]) by blizzard.sabbo.net (8.9.1/8.9.3) with ESMTP id LAA07172; Wed, 24 May 2000 11:17:01 +0300 (EEST) Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.9.3/8.9.3) with ESMTP id LAA82248; Wed, 24 May 2000 11:17:26 +0300 (EEST) (envelope-from SoboMax@FreeBSD.org) Message-ID: <392B9011.368FEC6B@FreeBSD.org> Date: Wed, 24 May 2000 11:17:21 +0300 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.73 [en] (WinNT; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: daeron@wit401305.student.utwente.nl Cc: cg@FreeBSD.org, multimedia@FreeBSD.org Subject: Re: cvs commit: ports/audio/wsoundserver Makefile ports/audio/wsoundserver/files md5 ports/audio/wsoundserver/patches patch-aa patch-ab patch-ac patch-ad ports/audio/wsoundserver/pkg DESCR PLIST References: <200005230633.XAA68264@freefall.freebsd.org> <20000524021016.A24438@shadowmere.student.utwente.nl> <392B7DEB.9344C331@FreeBSD.org> <20000524095458.C71443@shadowmere.student.utwente.nl> Content-Type: multipart/mixed; boundary="------------F189634FBF935B75CB181369" Sender: owner-freebsd-multimedia@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a multi-part message in MIME format. --------------F189634FBF935B75CB181369 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Pascal Hofstee wrote: > On Wed, May 24, 2000 at 09:59:55AM +0300, Maxim Sobolev wrote: > > Pascal Hofstee wrote: > > Yes, it is already in my TODO list ;). > > > > BTW, there is some problem with playing short sounds, at least on my -current > > with OPL3-SA soundcard. It seems that if length of sound is less that default > > buffer used to write sounds (8k for 8 bit and 4k for 16 bit) then it simple > > doesn't produce any sound. Reducing length of the buffer helps, but it might be > > not the ideal solution. Now I'm looking into the problem and probably will came > > with the workaround soon. > > This problem is something that i noticed quite a while back around the > first time the emu10k-support was introduced into CURRENT .... from that > moment on Any wav file that i try to play basically just "skips" the first > x couple of frames ... i am still convinced this si a bug in the current > pcm-code Yes, it is definitely a bug in the pcm driver. It seems that driver needs at least two write() operations for sound to be actually played. With this message I'm attaching small workarround which seems fix this problem in wsoundserver, at least for my OPL3-SA card. Probably we should contact Cameron (he is the current maintainer of the pcm stuff), for proper kernel fix. -Maxim --------------F189634FBF935B75CB181369 Content-Type: text/plain; charset=koi8-r; name="wsound.patch" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="wsound.patch" --- wslib/audio_voxware.c.orig Fri Mar 31 23:14:40 2000 +++ wslib/audio_voxware.c Wed May 24 11:08:24 2000 @@ -403,6 +403,7 @@ long blkFrames; /* number of frames in current audio block */ int blockSize = 8192; /* Size of an audio block buffer in frames */ int i; + u_int8_t fakebuffer[2] = {0, 0}; #ifdef DEBUG fprintf(stderr, " >> writing data\n"); @@ -413,7 +414,11 @@ SErrorCode = SERR_NOMEMORY; return -1; } - + + /* Following line is a simple workarround for buggy pcm driver, which seens need at least to write() + calls for sound to be actually played */ + write(audiofd, fakebuffer, 2); + curFrame = 0; while (curFrame < afInfo->FrameCount) { if ((blkFrames = (afInfo->FrameCount - curFrame)) > blockSize) { @@ -503,6 +508,7 @@ long blkFrames; /* number of frames in current audio block */ int blockSize = 4096; /* Size of an audio block buffer in frames */ int i; + u_int16_t fakebuffer[2] = {0, 0}; #ifdef DEBUG fprintf(stderr, " >> writing data\n"); @@ -513,7 +519,11 @@ SErrorCode = SERR_NOMEMORY; return -1; } - + + /* Following line is a simple workarround for buggy pcm driver, which seens need at least to write() + calls for sound to be actually played */ + write(audiofd, fakebuffer, 4); + curFrame = 0; while (curFrame < afInfo->FrameCount) { if ((blkFrames = (afInfo->FrameCount - curFrame)) > blockSize) { --------------F189634FBF935B75CB181369-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-multimedia" in the body of the message From owner-freebsd-multimedia Wed May 24 13: 9: 6 2000 Delivered-To: freebsd-multimedia@freebsd.org Received: from aphex.peterson.org (aphex.peterson.org [209.228.7.160]) by hub.freebsd.org (Postfix) with ESMTP id 45A2737BD89; Wed, 24 May 2000 13:08:59 -0700 (PDT) (envelope-from matt@peterson.org) Received: from aphex.peterson.org (aphex.peterson.org [209.228.7.160]) by aphex.peterson.org (8.9.3/8.9.3) with ESMTP id NAA29632; Wed, 24 May 2000 13:08:58 -0700 (PDT) Date: Wed, 24 May 2000 13:08:58 -0700 (PDT) From: Matt Peterson To: freebsd-multimedia@freebsd.org, freebsd-questions@freebsd.org Subject: digital output sound cards? Message-ID: X-URL: http://matt.peterson.org/ X-UIN: 1998182 X-AIM: lardcm MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-multimedia@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm wondering (if any at all) sound cards have drivers which output digital (ie: S/PDIF connector)? Such as the Sound Blaster Live, Xitel Storm Platinum, Maudio Dio, etc. I know the Live has only recently gotten analog output, what about us who want to record to minidisc and stuff. Thx. -- Matt Peterson another.geek.without.a.life matt@peterson.org http://matt.peterson.org/ ------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-multimedia" in the body of the message From owner-freebsd-multimedia Wed May 24 16:20:47 2000 Delivered-To: freebsd-multimedia@freebsd.org Received: from arthur.caida.org (arthur.caida.org [204.212.46.6]) by hub.freebsd.org (Postfix) with ESMTP id BFC7837B91B for ; Wed, 24 May 2000 16:20:44 -0700 (PDT) (envelope-from dwm@arthur.caida.org) Received: from arthur.caida.org (localhost.caida.org [127.0.0.1]) by arthur.caida.org (8.9.0/8.9.0.Beta5) with ESMTP id TAA27230 for ; Wed, 24 May 2000 19:20:37 -0400 (EDT) Message-Id: <200005242320.TAA27230@arthur.caida.org> To: freebsd-multimedia@freebsd.org Subject: HP9210i CD-RW drive Date: Wed, 24 May 2000 19:20:37 -0400 From: Daniel McRobb Sender: owner-freebsd-multimedia@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Just FYI, I've changed my mind on this drive. It worked fine for 2 days, but it now appears to be braindead. The eject button no longer works, and the SCSI no longer sees it on the bus. It behaves as if the firmware has lost its mind. HP customer service wasn't helpful, so I'll be returning it (and replacing with a Plextor). Daniel ~~~~~~ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-multimedia" in the body of the message From owner-freebsd-multimedia Wed May 24 18:24:31 2000 Delivered-To: freebsd-multimedia@freebsd.org Received: from cis.ohio-state.edu (mail.cis.ohio-state.edu [164.107.115.5]) by hub.freebsd.org (Postfix) with ESMTP id A081837BB51; Wed, 24 May 2000 18:24:25 -0700 (PDT) (envelope-from matey@cis.ohio-state.edu) Received: from alpha.cis.ohio-state.edu (matey@alpha.cis.ohio-state.edu [164.107.112.15]) by cis.ohio-state.edu (8.9.1/8.9.1) with ESMTP id VAA05349; Wed, 24 May 2000 21:24:23 -0400 (EDT) Received: (from matey@localhost) by alpha.cis.ohio-state.edu (8.9.1/8.9.1) id VAA02860; Wed, 24 May 2000 21:25:08 -0400 (EDT) Date: Wed, 24 May 2000 21:24:16 -0400 From: Alexander Matey To: freebsd-multimedia@freebsd.org Cc: freebsd-hackers@freebsd.org Subject: Driver for Aureal Vortex* based soundcards is available Message-ID: <20000524212416.A486@cis.ohio-state.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-multimedia@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [Please, remove hackers from Cc: list when replying] Finally took the time to put this stuff together. I am releasing the newpcm driver for Aureal Vortex1, Vortex2, Vortex Advantage based soundcards (au8830, au8820, au8810 chipsets). This is not a "true" driver, it needs to be linked with Aureal's Linux Vortex binary core which provides the interface to the Vortex hardware. Detailed information can be found on: http://www.cis.ohio-state.edu/~matey/au88x0/ Driver supports 4 playback channels at sampling rates 4 though 48kHz. Recording is also supported to some extent. The only soundcard I had the chance to test it with was my Diamond Monster MX-300 (Vortex2, au8830 based card). If your soundcard is based on au8820 or au8810 chipsets please give it a try. I'd like to know if it works for other chipsets as well. I tested it on 5.0-CURRENT although I believe it should compile and run on 4.0-STABLE as well. This my first driver, any comments are appreciated. :) -- lx To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-multimedia" in the body of the message From owner-freebsd-multimedia Thu May 25 5: 1:12 2000 Delivered-To: freebsd-multimedia@freebsd.org Received: from sasi.com (sasi.com [164.164.56.2]) by hub.freebsd.org (Postfix) with ESMTP id 476AA37BE93 for ; Thu, 25 May 2000 05:01:07 -0700 (PDT) (envelope-from gbnaidu@sasi.com) Received: from samar (sasi.com [164.164.56.2]) by sasi.com (8.9.3/8.9.3) with SMTP id RAA15377 for ; Thu, 25 May 2000 17:29:20 +0530 (IST) Received: from pcd75.sasi.com ([10.0.16.75]) by sasi.com; Thu, 25 May 2000 17:29:19 +0000 (IST) Received: from localhost (gbnaidu@localhost) by pcd75.sasi.com (8.9.3/8.9.3) with ESMTP id RAA01682; Thu, 25 May 2000 17:32:16 +0530 Date: Thu, 25 May 2000 17:32:16 +0530 (IST) From: "G.B.Naidu" To: Alexander Matey Cc: freebsd-multimedia@FreeBSD.ORG Subject: Re: Driver for Aureal Vortex* based soundcards is available In-Reply-To: <20000524212416.A486@cis.ohio-state.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-multimedia@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, Could you please tell me where can I get the H/W details information for this driver? Can I get it over the online? I want to see the pin description, registers, memory informatoin etc. Basically I want to see the Data sheets of the H/w for which this driver is written. thanks --gb On Wed, 24 May 2000, Alexander Matey wrote: > [Please, remove hackers from Cc: list when replying] > > Finally took the time to put this stuff together. > > I am releasing the newpcm driver for Aureal Vortex1, Vortex2, > Vortex Advantage based soundcards (au8830, au8820, au8810 chipsets). > This is not a "true" driver, it needs to be linked with Aureal's > Linux Vortex binary core which provides the interface to the > Vortex hardware. Detailed information can be found on: > > http://www.cis.ohio-state.edu/~matey/au88x0/ > > Driver supports 4 playback channels at sampling rates 4 though > 48kHz. Recording is also supported to some extent. > > The only soundcard I had the chance to test it with was my Diamond > Monster MX-300 (Vortex2, au8830 based card). If your soundcard is > based on au8820 or au8810 chipsets please give it a try. I'd like > to know if it works for other chipsets as well. > > I tested it on 5.0-CURRENT although I believe it should compile > and run on 4.0-STABLE as well. > > This my first driver, any comments are appreciated. > :) > > -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-multimedia" in the body of the message From owner-freebsd-multimedia Thu May 25 6: 5:58 2000 Delivered-To: freebsd-multimedia@freebsd.org Received: from midget.dons.net.au (daniel.lnk.telstra.net [139.130.137.70]) by hub.freebsd.org (Postfix) with ESMTP id 37CA337BF62 for ; Thu, 25 May 2000 06:05:54 -0700 (PDT) (envelope-from darius@guppy.dons.net.au) Received: from guppy.dons.net.au (guppy.dons.net.au [203.31.81.9]) by midget.dons.net.au (8.9.3/8.9.1) with ESMTP id WAA06530; Thu, 25 May 2000 22:35:38 +0930 (CST) (envelope-from darius@guppy.dons.net.au) Received: (from darius@localhost) by guppy.dons.net.au (8.9.3/8.9.3) id WAA00639; Thu, 25 May 2000 22:35:35 +0930 (CST) (envelope-from darius) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Thu, 25 May 2000 22:35:34 +0930 (CST) From: "Daniel O'Connor" To: "G.B.Naidu" Subject: Re: Driver for Aureal Vortex* based soundcards is available Cc: freebsd-multimedia@FreeBSD.ORG, Alexander Matey Sender: owner-freebsd-multimedia@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 25-May-00 G.B.Naidu wrote: > Could you please tell me where can I get the H/W details information for > this driver? Can I get it over the online? I want to see the pin > description, registers, memory informatoin etc. Basically I want to see > the Data sheets of the H/w for which this driver is written. You can't, the driver is binary only. Alexander's driver is a shim which links against the Linux .o file and provides stubs for its Linux functions.. (And talks to newpcm) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-multimedia" in the body of the message From owner-freebsd-multimedia Thu May 25 6:25:39 2000 Delivered-To: freebsd-multimedia@freebsd.org Received: from cis.ohio-state.edu (mail.cis.ohio-state.edu [164.107.115.5]) by hub.freebsd.org (Postfix) with ESMTP id 9F9EF37C15B for ; Thu, 25 May 2000 06:25:35 -0700 (PDT) (envelope-from matey@cis.ohio-state.edu) Received: from eta.cis.ohio-state.edu (matey@eta.cis.ohio-state.edu [164.107.112.62]) by cis.ohio-state.edu (8.9.1/8.9.1) with ESMTP id JAA01535; Thu, 25 May 2000 09:25:34 -0400 (EDT) Received: (from matey@localhost) by eta.cis.ohio-state.edu (8.9.1/8.9.1) id JAA12679; Thu, 25 May 2000 09:25:34 -0400 (EDT) Date: Thu, 25 May 2000 09:25:29 -0400 From: Alexander Matey To: "Alexander N. Kabaev" Cc: "G.B.Naidu" , freebsd-multimedia@FreeBSD.ORG Subject: Re: Driver for Aureal Vortex* based soundcards is available Message-ID: <20000525092528.A537@cis.ohio-state.edu> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from kabaev@mail.ru on Thu, May 25, 2000 at 08:15:16AM -0400 Sender: owner-freebsd-multimedia@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, May 25, 2000 at 08:15:16AM -0400, Alexander N. Kabaev wrote: > As far as I know, nowhere. This user uses binary 'core' module released by > Aureal for Linux. By implementing various linux_ functions it was possible to > trick core into believing that it runs on Linux :) Exactly. And to my knowledge, Vortex hardware specs are not publicly available. > PS. Alexander, the use of pmap_ calls in linux_ioremap and linux_iounmap is not > stricly necessary, I believe. rman_get_virtual on memory mapped resource should > give you the same result as long as resource has been allocated with RF_ACTIVE > flag or bus_activate_resource has been called in order to activate it. I'd really like to get rid of the linked list in linux_ioremap(), linux_iounmap(). Unfortunately, I couldn't think of a better way of implementing these. Core wants device to virtual address space mappings for addresses beyond the initial address of SYS_RES_MEMORY resource, which is allocated in au_pci_attach(). So, I'm not able to use rman_get_virtual(). I could do it myself having addresses returned by rman_get_start() and rman_get_virtual() just by calculating the difference b/w former one and an address passed as a parameter to linux_ioremap() and then adding this difference to the address returned by rman_get_virtual(). But I'm not sure if this not too dirty. -- lx To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-multimedia" in the body of the message From owner-freebsd-multimedia Thu May 25 10: 1:27 2000 Delivered-To: freebsd-multimedia@freebsd.org Received: from mx4.mail.ru (mx4.mail.ru [194.67.23.39]) by hub.freebsd.org (Postfix) with ESMTP id 3401E37BF87 for ; Thu, 25 May 2000 10:01:22 -0700 (PDT) (envelope-from kabaev@mail.ru) Received: from base2.mail.ru (mx7.int [10.0.0.44]) by mx4.mail.ru (8.9.3/8.9.3) with ESMTP id UAA46547 for ; Thu, 25 May 2000 20:49:42 +0400 (MSD) (envelope-from kabaev@mail.ru) Received: from h0050da20495b.ne.mediaone.net ([24.147.104.88] helo=kan.ne.mediaone.net) by base2.mail.ru with esmtp (Exim 3.02 #9) id 12uwXq-0006EK-00; Thu, 25 May 2000 16:15:22 +0400 Received: (from kan@localhost) by kan.ne.mediaone.net (8.9.3/8.9.3) id IAA00498; Thu, 25 May 2000 08:15:16 -0400 (EDT) (envelope-from kan) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Thu, 25 May 2000 08:15:16 -0400 (EDT) From: "Alexander N. Kabaev" To: "G.B.Naidu" Subject: Re: Driver for Aureal Vortex* based soundcards is available Cc: freebsd-multimedia@freebsd.org, Alexander Matey Sender: owner-freebsd-multimedia@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As far as I know, nowhere. This user uses binary 'core' module released by Aureal for Linux. By implementing various linux_ functions it was possible to trick core into believing that it runs on Linux :) PS. Alexander, the use of pmap_ calls in linux_ioremap and linux_iounmap is not stricly necessary, I believe. rman_get_virtual on memory mapped resource should give you the same result as long as resource has been allocated with RF_ACTIVE flag or bus_activate_resource has been called in order to activate it. > > Hi, > > Could you please tell me where can I get the H/W details information for > this driver? Can I get it over the online? I want to see the pin > description, registers, memory informatoin etc. Basically I want to see > the Data sheets of the H/w for which this driver is written. > > thanks > --gb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-multimedia" in the body of the message From owner-freebsd-multimedia Thu May 25 16:45: 3 2000 Delivered-To: freebsd-multimedia@freebsd.org Received: from rr.com (rdu25-28-182.nc.rr.com [24.25.28.182]) by hub.freebsd.org (Postfix) with ESMTP id A910737B6B9; Thu, 25 May 2000 16:44:54 -0700 (PDT) (envelope-from rhh@rr.com) Received: (from rhh@localhost) by rr.com (8.9.3/8.9.3) id TAA44482; Thu, 25 May 2000 19:46:00 -0400 (EDT) (envelope-from rhh) Date: Thu, 25 May 2000 19:46:00 -0400 From: Randall Hopper To: multimedia@freebsd.org, stable@freebsd.org Cc: "David O'Brien" , Conrad Sabatier Subject: 3DNow! binutils & Mesa for -STABLE Message-ID: <20000525194600.A44195@nc.rr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i Sender: owner-freebsd-multimedia@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Thanks to David O'Brien for upgrading -current's binutils. This new version supports AMD 3DNow! for the K6-2, K6-III, and Athelon folks. Wanting 3DNow support in gas, I pulled a copy from CVS and built it for 3.4-RELEASE (w/ gdb commented out). Now Mesa and friends detect and build in 3DNow support for Mesa on -stable. For other -stable folks that want to give it a shot, just fetch copies of src/contrib/binutils and src/gnu/usr.bin/binutils modules from the latest CVS ("cvs checkout "). Also, I'll be happy to send binutils exec binaries to anyone running 3.4. ...now off to find more 3DNow apps! ;-) -- Randall Hopper aa8vb@nc.rr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-multimedia" in the body of the message From owner-freebsd-multimedia Thu May 25 18: 2:36 2000 Delivered-To: freebsd-multimedia@freebsd.org Received: from rr.com (rdu25-28-182.nc.rr.com [24.25.28.182]) by hub.freebsd.org (Postfix) with ESMTP id 1F38037BE66 for ; Thu, 25 May 2000 18:02:30 -0700 (PDT) (envelope-from rhh@rr.com) Received: (from rhh@localhost) by rr.com (8.9.3/8.9.3) id VAA45538 for multimedia@freebsd.org; Thu, 25 May 2000 21:03:41 -0400 (EDT) (envelope-from rhh) Date: Thu, 25 May 2000 21:03:41 -0400 From: Randall Hopper To: multimedia@freebsd.org Subject: TV Users - Let me bounce this off you Message-ID: <20000525210340.A44725@nc.rr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i Sender: owner-freebsd-multimedia@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Been thinking about a way to make writing TV apps easier (not just easy; trivial!). An API that would allow folks to literally write their own in Python or Tcl TV app with 5-10 lines of code. If you like the idea, read on. My thought is to embed all the "configure, capture, convert, and blast" needed for a TV client of any sort into a daemon. An app wanting video data in some format would simply say: tv.Connect() tv.Configure() tv.Start() tv.Stop() tv.Close() something along those lines. Does this kind of interface interest anyone? Potential clients would be, for example, GUI applications, one-shot frame grabbers, webcams, on-the-fly MPEG encoders, etc. Potential destinations for the video data would be: any X Window (created by Tk, wxWindows, Motif, ...whatever!), the frame buffer, a socket, named pipe, file(s), memory buffer (user, XImage, XvShmImage), raw device, ... Possible video sources are, of course, the TV cards (either directly though the driver API or indirectly via the new Xv extension). BTW, GUI apps would simply say "here; take this X Window", and the daemon would take care of all the rest (determine src and dest pixel format, configure and fire up the TV driver, handle any format conversions necessary [and FAST! -- using MMX if available], possibly changing between XImage and DGA transfer automagically, using Shared memory, YUV images, or whatever capture/convert/transfer path supported is fastest on your box, ...) Basically, the idea is to bury all the low-level nastiness in the daemon so users don't have to care about driver capture formats, pixel format conversions, available X protocols, throttling, etc. Hermes or SDL might be good libraries to use under-the-hood to do the the pixel format conversion (Hermes already has MMX support; been testing it recently with bktr TV and it looks promising). Anyway, thanks for reading. Please fire off any opinions, for or against. No sense in spending time on this if desire for it is just lukewarm. -- Randall Hopper aa8vb@nc.rr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-multimedia" in the body of the message From owner-freebsd-multimedia Thu May 25 19:39:41 2000 Delivered-To: freebsd-multimedia@freebsd.org Received: from rr.com (rdu25-28-182.nc.rr.com [24.25.28.182]) by hub.freebsd.org (Postfix) with ESMTP id 3518737B668 for ; Thu, 25 May 2000 19:39:38 -0700 (PDT) (envelope-from rhh@rr.com) Received: (from rhh@localhost) by rr.com (8.9.3/8.9.3) id WAA46844; Thu, 25 May 2000 22:39:42 -0400 (EDT) (envelope-from rhh) Date: Thu, 25 May 2000 22:39:42 -0400 From: Randall Hopper To: jlm@seaholm.caamora.com.au Cc: multimedia@freebsd.org Subject: Re: TV Users - Let me bounce this off you Message-ID: <20000525223942.A46565@nc.rr.com> References: <20000525210340.A44725@nc.rr.com> <20000526112215.A17124@phoenix.welearn.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000526112215.A17124@phoenix.welearn.com.au>; from jon@welearn.com.au on Fri, May 26, 2000 at 11:22:17AM +1000 Sender: owner-freebsd-multimedia@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi! Jonathan Michaels: |> Hermes or SDL might be good libraries to use under-the-hood to do the |> the pixel format conversion (Hermes already has MMX support; been testing |> it recently with bktr TV and it looks promising). | |here goes, what if your cpu dosnt have teh mmx extensions ? |will this mean that the software, won't run, or run so pooryly |that you will have to get a cpu that does do mmx or not bother |witht he software package. Very good question. No, definitely not. If MMX isn't supported by the CPU it wouldn't be used. Slower non-MMX code would kick in. Also, different from Fxtv today, this daemon would pace itself so it wouldn't bring your machine "to its knees" when it needs to revert to CPU-intensive conversion methods. This pacing ideally would be configurable based on a target CPU load or target frame rate. |reason i ask is that me (and a group of fellow freebsd users) |have old hardware, that is intel processors circa pentium pro |and the plain pentiums (the ones that didn't do mmx). i'm |looking at getting a g400 with video and possibly tv latter |this year. I think it's very important to support all our existing hardware! (Heck, all my video/multimedia cards are still hanging off a 33MHz PCI bus with a Socket 7 MB and 66MHz memory bus; until recently running a P-233MMX too. Hey, with my recent K6-III 400 upgrade, my trusty old Socket 7 can do full-speed DVD decode in software and full-screen video/audio playback with no dropped frames! Best CPU I ever bought. 3 Cheers for Old Hardware!). |i may be a bit premature with my question .. sorry, if i am. Not at all. Good questions! Send more. -- Randall Hopper aa8vb@nc.rr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-multimedia" in the body of the message From owner-freebsd-multimedia Fri May 26 0: 6:51 2000 Delivered-To: freebsd-multimedia@freebsd.org Received: from kiew.egd.igd.fhg.de (kiew.egd.igd.fhg.de [192.102.170.32]) by hub.freebsd.org (Postfix) with ESMTP id C5DDE37B856 for ; Fri, 26 May 2000 00:06:44 -0700 (PDT) (envelope-from runge@rostock.zgdv.de) Received: from rostock.zgdv.de (penguin.egd.igd.fhg.de [192.102.170.145]) by kiew.egd.igd.fhg.de (Netscape Messaging Server 3.6) with ESMTP id AAA3236 for ; Fri, 26 May 2000 09:06:37 +0200 Message-ID: <392E231D.BA8C1519@rostock.zgdv.de> Date: Fri, 26 May 2000 09:09:17 +0200 From: Thomas Runge X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 4.0-STABLE i386) X-Accept-Language: en, de MIME-Version: 1.0 Cc: multimedia@FreeBSD.ORG Subject: Re: TV Users - Let me bounce this off you References: <20000525210340.A44725@nc.rr.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-multimedia@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Randall Hopper wrote: > > Been thinking about a way to make writing TV apps easier (not just > easy; trivial!). An API that would allow folks to literally write their > own in Python or Tcl TV app with 5-10 lines of code. Well, making complicated things esier is almost always a good idea :-) But it's necessary to specify a good API, which lets you make simple things easy, but doesn't stop you making more complicated tasks. I didn't have a look into the Video4Linux API, but wouldn't it be a good idea to support that? And how about supporting multiple output sources? -- Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-multimedia" in the body of the message From owner-freebsd-multimedia Fri May 26 6:17: 2 2000 Delivered-To: freebsd-multimedia@freebsd.org Received: from proton.hexanet.fr (proton.hexanet.fr [194.98.140.18]) by hub.freebsd.org (Postfix) with ESMTP id 71F6937B8B4 for ; Fri, 26 May 2000 06:16:58 -0700 (PDT) (envelope-from chris@hexanet.fr) Received: from hexanet.fr (localhost [127.0.0.1]) by proton.hexanet.fr (8.9.3/8.9.3) with ESMTP id PAA01652 for ; Fri, 26 May 2000 15:16:58 +0200 (CEST) (envelope-from chris@hexanet.fr) Message-ID: <392E7949.44309A68@hexanet.fr> Date: Fri, 26 May 2000 13:16:57 +0000 From: Christophe Prevotaux Organization: HEXANET X-Mailer: Mozilla 4.72 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: fr, en MIME-Version: 1.0 Newsgroups: muc.lists.freebsd.multimedia To: freebsd-multimedia@freebsd.org Subject: FreeBSD and Real Video Server Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-multimedia@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi I would like to setup a freebsd based real video live encoder machine as well as a proxy linked by a 256Kbps ISDN line and a realvideo server Does anyone knows if this is possible ? Does this makes sense ? What is a FreeBSD and RealVideo Server supported video capture board ? Can all this setup works for the capture and encoding part , the real proxy and the real server ? -- =================================================================== Christophe Prevotaux Email: chris@hexanet.fr HEXANET SARL URL: http://www.hexanet.fr/ Z.A Farman Sud Tel: +33 (0)3 26 79 30 05 9 rue Roland Coffignot Direct: +33 (0)3 26 79 08 02 BP415 Fax: +33 (0)3 26 79 30 06 51689 Reims Cedex 2 FRANCE =================================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-multimedia" in the body of the message From owner-freebsd-multimedia Fri May 26 10: 6:29 2000 Delivered-To: freebsd-multimedia@freebsd.org Received: from alpha.netvision.net.il (alpha.netvision.net.il [194.90.1.13]) by hub.freebsd.org (Postfix) with ESMTP id C81CE37BE51 for ; Fri, 26 May 2000 10:06:23 -0700 (PDT) (envelope-from ak@freenet.co.uk) Received: from freenet.co.uk (RAS3-p24.rlz.netvision.net.il [62.0.169.26]) by alpha.netvision.net.il (8.9.3/8.8.6) with ESMTP id UAA12814; Fri, 26 May 2000 20:05:19 +0300 (IDT) Message-ID: <392EBEA7.EFDCE058@freenet.co.uk> Date: Fri, 26 May 2000 21:12:55 +0300 From: A G F Keahan X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Randall Hopper Cc: multimedia@freebsd.org Subject: Re: TV Users - Let me bounce this off you References: <20000525210340.A44725@nc.rr.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-multimedia@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Randall, This sounds like a great idea. I did something similar for my webcam server/client application using SysV shared memory -- the server part was continuously capturing (and optionally jpeg-compressing) data into a shared memory buffer, and web clients (CGI scripts) were reading and sending that data to the user. However, you need some locking mechanisms that would tell your daemon when it's safe to update the buffer -- you don't want a client to read the first half of one frame, and the second half of another. In my application the solution was trivial -- to use a SysV semaphore to lock the buffer for writing, so no-one can read while it's being written into. But since your idea is much more general, you probably have to think of a more general synchronisation solution. Alex Randall Hopper wrote: > > Been thinking about a way to make writing TV apps easier (not just > easy; trivial!). An API that would allow folks to literally write their > own in Python or Tcl TV app with 5-10 lines of code. > > If you like the idea, read on. My thought is to embed all the > "configure, capture, convert, and blast" needed for a TV client of any sort > into a daemon. An app wanting video data in some format would simply say: > > tv.Connect() > tv.Configure() > tv.Start() > tv.Stop() > tv.Close() > > something along those lines. > > Does this kind of interface interest anyone? > > Potential clients would be, for example, GUI applications, one-shot > frame grabbers, webcams, on-the-fly MPEG encoders, etc. > > Potential destinations for the video data would be: any X Window > (created by Tk, wxWindows, Motif, ...whatever!), the frame buffer, a > socket, named pipe, file(s), memory buffer (user, XImage, XvShmImage), raw > device, ... > > Possible video sources are, of course, the TV cards (either directly > though the driver API or indirectly via the new Xv extension). > > BTW, GUI apps would simply say "here; take this X Window", and the > daemon would take care of all the rest (determine src and dest pixel > format, configure and fire up the TV driver, handle any format conversions > necessary [and FAST! -- using MMX if available], possibly changing between > XImage and DGA transfer automagically, using Shared memory, YUV images, or > whatever capture/convert/transfer path supported is fastest on your box, ...) > > Basically, the idea is to bury all the low-level nastiness in the > daemon so users don't have to care about driver capture formats, pixel > format conversions, available X protocols, throttling, etc. > > Hermes or SDL might be good libraries to use under-the-hood to do the > the pixel format conversion (Hermes already has MMX support; been testing > it recently with bktr TV and it looks promising). > > Anyway, thanks for reading. Please fire off any opinions, for or > against. No sense in spending time on this if desire for it is just > lukewarm. > > -- > Randall Hopper > aa8vb@nc.rr.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-multimedia" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-multimedia" in the body of the message From owner-freebsd-multimedia Fri May 26 13: 6:31 2000 Delivered-To: freebsd-multimedia@freebsd.org Received: from goku.cl.msu.edu (goku.cl.msu.edu [35.8.3.20]) by hub.freebsd.org (Postfix) with ESMTP id 7165D37B683 for ; Fri, 26 May 2000 13:06:25 -0700 (PDT) (envelope-from dervish@goku.cl.msu.edu) Received: (from dervish@localhost) by goku.cl.msu.edu (8.9.3/8.9.3) id QAA28262; Fri, 26 May 2000 16:06:24 -0400 (EDT) (envelope-from dervish) Date: Fri, 26 May 2000 16:06:24 -0400 From: Bush Doctor To: Alexander Matey Cc: freebsd-multimedia@FreeBSD.ORG Subject: Re: Driver for Aureal Vortex* based soundcards is available Message-ID: <20000526160624.A82464@goku.cl.msu.edu> References: <20000524212416.A486@cis.ohio-state.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000524212416.A486@cis.ohio-state.edu>; from matey@cis.ohio-state.edu on Wed, May 24, 2000 at 09:24:16PM -0400 X-Operating-System: FreeBSD 5.0-CURRENT i386 WWW-Home-Page: http://bantu.cl.msu.edu Organisation: Fraternal Order of Whipped Husbands -- (F.O.O.W.H.) Sender: owner-freebsd-multimedia@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Out of da blue Alexander Matey aka (matey@cis.ohio-state.edu) said: > [Please, remove hackers from Cc: list when replying] > > Finally took the time to put this stuff together. > > I am releasing the newpcm driver for Aureal Vortex1, Vortex2, > Vortex Advantage based soundcards (au8830, au8820, au8810 chipsets). > This is not a "true" driver, it needs to be linked with Aureal's > Linux Vortex binary core which provides the interface to the > Vortex hardware. Detailed information can be found on: > > http://www.cis.ohio-state.edu/~matey/au88x0/ > > Driver supports 4 playback channels at sampling rates 4 though > 48kHz. Recording is also supported to some extent. > > The only soundcard I had the chance to test it with was my Diamond > Monster MX-300 (Vortex2, au8830 based card). If your soundcard is > based on au8820 or au8810 chipsets please give it a try. I'd like > to know if it works for other chipsets as well. > > I tested it on 5.0-CURRENT although I believe it should compile > and run on 4.0-STABLE as well. > > This my first driver, any comments are appreciated. Good work. I've been giving it a workout since this morning. Actually went out and bought a couple on new cd's :). My box at work has a Turtle Beach Montego A3D II (Vortex2 au8830). The driver has been performing flawlessly! > :) > > -- > lx > #;^) -- f u cn rd ths, u cn gt a gd jb n cmptr prgrmmng. bush doctor To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-multimedia" in the body of the message From owner-freebsd-multimedia Fri May 26 13:59:43 2000 Delivered-To: freebsd-multimedia@freebsd.org Received: from cis.ohio-state.edu (mail.cis.ohio-state.edu [164.107.115.5]) by hub.freebsd.org (Postfix) with ESMTP id 3E9D537B724 for ; Fri, 26 May 2000 13:59:41 -0700 (PDT) (envelope-from matey@cis.ohio-state.edu) Received: from theta.cis.ohio-state.edu (matey@theta.cis.ohio-state.edu [164.107.112.63]) by cis.ohio-state.edu (8.9.1/8.9.1) with ESMTP id QAA07289; Fri, 26 May 2000 16:59:37 -0400 (EDT) Received: (from matey@localhost) by theta.cis.ohio-state.edu (8.9.1/8.9.1) id QAA28389; Fri, 26 May 2000 16:59:37 -0400 (EDT) Date: Fri, 26 May 2000 16:59:26 -0400 From: Alexander Matey To: Bush Doctor Cc: freebsd-multimedia@FreeBSD.ORG Subject: Re: Driver for Aureal Vortex* based soundcards is available Message-ID: <20000526165925.A4350@cis.ohio-state.edu> References: <20000524212416.A486@cis.ohio-state.edu> <20000526160624.A82464@goku.cl.msu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000526160624.A82464@goku.cl.msu.edu>; from dervish@goku.cl.msu.edu on Fri, May 26, 2000 at 04:06:24PM -0400 Sender: owner-freebsd-multimedia@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, May 26, 2000 at 04:06:24PM -0400, Bush Doctor wrote: > > I tested it on 5.0-CURRENT although I believe it should compile > > and run on 4.0-STABLE as well. > > > > This my first driver, any comments are appreciated. > Good work. I've been giving it a workout since this morning. Actually > went out and bought a couple on new cd's :). My box at work has a > Turtle Beach Montego A3D II (Vortex2 au8830). The driver has been > performing flawlessly! Chris Watson has reported system lockups when using this driver with Turtle Beach Montego II+ on an AMD Athlon system. The problem seems to be with Aureal Vortex2 binary core. Could you give me more details about your system. More specifically is it AMD Athlon or Intel based? -- lx To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-multimedia" in the body of the message From owner-freebsd-multimedia Fri May 26 15:25: 0 2000 Delivered-To: freebsd-multimedia@freebsd.org Received: from relay02.chello.nl (relay02.chello.nl [212.83.68.146]) by hub.freebsd.org (Postfix) with ESMTP id 995C137B920; Fri, 26 May 2000 15:24:38 -0700 (PDT) (envelope-from wkb@chello.nl) Received: from chello.nl ([213.46.78.184]) by relay02.chello.nl (InterMail vK.4.02.00.00 201-232-116 license 2ee4e7c625482f2f2a1950a80f6c8d58) with ESMTP id <20000526222420.TMKB13476.relay02@chello.nl>; Sat, 27 May 2000 00:24:20 +0200 Received: (from wkb@localhost) by chello.nl (8.9.3/8.9.3) id AAA02287; Sat, 27 May 2000 00:24:43 GMT (envelope-from wkb) Date: Sat, 27 May 2000 00:24:43 +0000 From: Wilko Bulte To: Randall Hopper Cc: multimedia@FreeBSD.ORG, stable@FreeBSD.ORG, "David O'Brien" , Conrad Sabatier Subject: Re: 3DNow! binutils & Mesa for -STABLE Message-ID: <20000527002443.D1977@freebie.wbnet> Reply-To: wc.bulte@chello.nl References: <20000525194600.A44195@nc.rr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000525194600.A44195@nc.rr.com>; from aa8vb@nc.rr.com on Thu, May 25, 2000 at 07:46:00PM -0400 X-OS: FreeBSD 4.0-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-multimedia@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, May 25, 2000 at 07:46:00PM -0400, Randall Hopper wrote: > Thanks to David O'Brien for upgrading -current's binutils. This new > version supports AMD 3DNow! for the K6-2, K6-III, and Athelon folks. > > Wanting 3DNow support in gas, I pulled a copy from CVS and built it for > 3.4-RELEASE (w/ gdb commented out). Now Mesa and friends detect and build > in 3DNow support for Mesa on -stable. > > For other -stable folks that want to give it a shot, just fetch copies of > src/contrib/binutils and src/gnu/usr.bin/binutils modules from the latest > CVS ("cvs checkout "). Also, I'll be happy to send binutils exec > binaries to anyone running 3.4. Do thinks like fxtv use 3dnow to their advantage (I guess not)? But I assume the various mpeg* things might? -- Wilko Bulte FreeBSD, the power to serve http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-multimedia" in the body of the message From owner-freebsd-multimedia Fri May 26 18:33:25 2000 Delivered-To: freebsd-multimedia@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 077BA37B87E for ; Fri, 26 May 2000 18:33:22 -0700 (PDT) (envelope-from gadde@cs.duke.edu) Received: from cod.cs.duke.edu (cod.cs.duke.edu [152.3.140.124]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id VAA09070 for ; Fri, 26 May 2000 21:33:20 -0400 (EDT) Received: (gadde@localhost) by cod.cs.duke.edu (8.8.5/8.6.9) id VAA16320 for freebsd-multimedia@FreeBSD.ORG; Fri, 26 May 2000 21:33:12 -0400 (EDT) Date: Fri, 26 May 2000 21:33:12 -0400 From: Syam Gadde To: freebsd-multimedia@FreeBSD.ORG Subject: Re: Driver for Aureal Vortex* based soundcards is available Message-ID: <20000526213311.A16304@cod.cs.duke.edu> References: <20000524212416.A486@cis.ohio-state.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <20000524212416.A486@cis.ohio-state.edu> Sender: owner-freebsd-multimedia@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Quoting Alexander Matey (matey@cis.ohio-state.edu): > I am releasing the newpcm driver for Aureal Vortex1, Vortex2, > Vortex Advantage based soundcards (au8830, au8820, au8810 chipsets). Awesome! Now I can get rid of that cheapo ESS sound card I bought just for FreeBSD and stop worrying about Aureal going under... One strange thing I noticed when changing mic settings with /usr/sbin/mixer: gaddeppp gadde [0] 43> mixer mic Mixer mic is currently set to 0:0 gaddeppp gadde [0] 44> mixer mic 50 Setting the mixer mic to 50:50. gaddeppp gadde [0] 45> mixer mic Mixer mic is currently set to 23:50 gaddeppp gadde [0] 58> mixer mic 60 Setting the mixer mic to 60:60. gaddeppp gadde [0] 59> mixer mic Mixer mic is currently set to 33:60 gaddeppp gadde [0] 60> mixer mic 70 Setting the mixer mic to 70:70. gaddeppp gadde [0] 61> mixer mic Mixer mic is currently set to 43:70 It sounds fine, the reported values just look screwy. "mic" seems like the only mixer device affected. I have an MX300, and am running 4.0-STABLE, though my last cvsup was April 2. relevant dmesg output: pcm0: port 0xe800-0xe807,0xe400-0xe407 mem 0xe7100000-0xe71 3ffff irq 10 at device 9.0 on pci0 pcm1: on sbc0 unknown1: at port 0x201 on isa0 -syam To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-multimedia" in the body of the message From owner-freebsd-multimedia Fri May 26 19:15:10 2000 Delivered-To: freebsd-multimedia@freebsd.org Received: from rr.com (rdu25-28-182.nc.rr.com [24.25.28.182]) by hub.freebsd.org (Postfix) with ESMTP id E246B37B9FB; Fri, 26 May 2000 19:15:03 -0700 (PDT) (envelope-from rhh@rr.com) Received: (from rhh@localhost) by rr.com (8.9.3/8.9.3) id WAA23842; Fri, 26 May 2000 22:16:07 -0400 (EDT) (envelope-from rhh) Date: Fri, 26 May 2000 22:16:07 -0400 From: Randall Hopper To: wc.bulte@chello.nl Cc: multimedia@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: 3DNow! binutils & Mesa for -STABLE Message-ID: <20000526221607.A21656@nc.rr.com> References: <20000525194600.A44195@nc.rr.com> <20000527002443.D1977@freebie.wbnet> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000527002443.D1977@freebie.wbnet>; from wkb@chello.nl on Sat, May 27, 2000 at 12:24:43AM +0000 Sender: owner-freebsd-multimedia@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Wilko Bulte: | |Do thinks like fxtv use 3dnow to their advantage (I guess not)? But I assume |the various mpeg* things might? No fxtv doesn't, and I think you're right. As I recall MMX adds SIMD integer ops which is where the boost would be for things like pixel repacking. 3DNow's primary add was parallel floating/fixed point I believe. Rather than reinvent the wheel, I'll likely stack fxtv on the hermes port one of these days if there isn't a big turn-out for an alternative video API. -- Randall Hopper aa8vb@nc.rr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-multimedia" in the body of the message From owner-freebsd-multimedia Fri May 26 20: 0:44 2000 Delivered-To: freebsd-multimedia@freebsd.org Received: from rr.com (rdu25-28-182.nc.rr.com [24.25.28.182]) by hub.freebsd.org (Postfix) with ESMTP id BD7BF37B885 for ; Fri, 26 May 2000 20:00:39 -0700 (PDT) (envelope-from rhh@rr.com) Received: (from rhh@localhost) by rr.com (8.9.3/8.9.3) id XAA25465; Fri, 26 May 2000 23:01:46 -0400 (EDT) (envelope-from rhh) Date: Fri, 26 May 2000 23:01:45 -0400 From: Randall Hopper To: A G F Keahan Cc: multimedia@freebsd.org Subject: Re: TV Users - Let me bounce this off you Message-ID: <20000526230145.A25153@nc.rr.com> References: <20000525210340.A44725@nc.rr.com> <392EBEA7.EFDCE058@freenet.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <392EBEA7.EFDCE058@freenet.co.uk>; from ak@freenet.co.uk on Fri, May 26, 2000 at 09:12:55PM +0300 Sender: owner-freebsd-multimedia@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org A G F Keahan: |This sounds like a great idea. I did something similar for my webcam |server/client application using SysV shared memory -- the server part |was continuously capturing (and optionally jpeg-compressing) data into a |shared memory buffer, and web clients (CGI scripts) were reading and |sending that data to the user. Sounds pretty cool. If quite a bit more interest perks up, maybe we should start with yours and see what folks need additionally. |However, you need some locking mechanisms that would tell your daemon |when it's safe to update the buffer -- you don't want a client to read |the first half of one frame, and the second half of another. Good point. So I take it your webcam doesn't do a one-shot capture, grab frame, and repeat. The server tries to keep the buffer filled with the latest constantly, and only stops temporarily when the client is using the buffer? |In my application the solution was trivial -- to use a SysV semaphore to |lock the buffer for writing, so no-one can read while it's being written |into. But since your idea is much more general, you probably have to |think of a more general synchronisation solution. Certainly some handshaking will be needed, if nothing else to tell the client when a request has completed. Maybe semaphores would be the way to go. Did you consider having the client do one-shot captures? Why have the daemon constantly pumping video into the buffer. Multiple clients? -- Randall Hopper aa8vb@nc.rr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-multimedia" in the body of the message From owner-freebsd-multimedia Fri May 26 23:14:51 2000 Delivered-To: freebsd-multimedia@freebsd.org Received: from cis.ohio-state.edu (mail.cis.ohio-state.edu [164.107.115.5]) by hub.freebsd.org (Postfix) with ESMTP id 23C9737B57A for ; Fri, 26 May 2000 23:14:47 -0700 (PDT) (envelope-from matey@cis.ohio-state.edu) Received: from epsilon.cis.ohio-state.edu (matey@epsilon.cis.ohio-state.edu [164.107.112.10]) by cis.ohio-state.edu (8.9.1/8.9.1) with ESMTP id CAA27697; Sat, 27 May 2000 02:14:46 -0400 (EDT) Received: (from matey@localhost) by epsilon.cis.ohio-state.edu (8.9.1/8.9.1) id CAA05677; Sat, 27 May 2000 02:14:46 -0400 (EDT) Date: Sat, 27 May 2000 02:14:40 -0400 From: Alexander Matey To: Syam Gadde Cc: freebsd-multimedia@FreeBSD.ORG Subject: Re: Driver for Aureal Vortex* based soundcards is available Message-ID: <20000527021440.A8471@cis.ohio-state.edu> References: <20000524212416.A486@cis.ohio-state.edu> <20000526213311.A16304@cod.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000526213311.A16304@cod.cs.duke.edu>; from gadde@cs.duke.edu on Fri, May 26, 2000 at 09:33:12PM -0400 Sender: owner-freebsd-multimedia@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, May 26, 2000 at 09:33:12PM -0400, Syam Gadde wrote: > > I am releasing the newpcm driver for Aureal Vortex1, Vortex2, > > Vortex Advantage based soundcards (au8830, au8820, au8810 chipsets). > > One strange thing I noticed when changing mic settings with > /usr/sbin/mixer: > > It sounds fine, the reported values just look screwy. "mic" seems like > the only mixer device affected. Thanks, Syam. It's fixed now. Together with some other cleanups I put up a new tarball at http://www.cis.ohio-state.edu/~matey/au88x0/ . -- lx To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-multimedia" in the body of the message From owner-freebsd-multimedia Sat May 27 9:29:33 2000 Delivered-To: freebsd-multimedia@freebsd.org Received: from mailgw1.netvision.net.il (mailgw1.netvision.net.il [194.90.1.14]) by hub.freebsd.org (Postfix) with ESMTP id 5B80937B520 for ; Sat, 27 May 2000 09:29:24 -0700 (PDT) (envelope-from ak@freenet.co.uk) Received: from freenet.co.uk (RAS3-p118.rlz.netvision.net.il [62.0.169.120]) by mailgw1.netvision.net.il (8.9.3/8.9.3) with ESMTP id TAA25804; Sat, 27 May 2000 19:29:17 +0300 (IDT) Message-ID: <39300787.AC2BF3C8@freenet.co.uk> Date: Sat, 27 May 2000 20:36:07 +0300 From: A G F Keahan X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Randall Hopper Cc: multimedia@freebsd.org Subject: Re: TV Users - Let me bounce this off you References: <20000525210340.A44725@nc.rr.com> <392EBEA7.EFDCE058@freenet.co.uk> <20000526230145.A25153@nc.rr.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-multimedia@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Randall Hopper wrote: > > A G F Keahan: > |This sounds like a great idea. I did something similar for my webcam > |server/client application using SysV shared memory -- the server part > |was continuously capturing (and optionally jpeg-compressing) data into a > |shared memory buffer, and web clients (CGI scripts) were reading and > |sending that data to the user. > > Sounds pretty cool. If quite a bit more interest perks up, maybe we should > start with yours and see what folks need additionally. Sure -- I don't have access to the sources right now, but will do in a couple of weeks time. > |However, you need some locking mechanisms that would tell your daemon > |when it's safe to update the buffer -- you don't want a client to read > |the first half of one frame, and the second half of another. > > Good point. So I take it your webcam doesn't do a one-shot capture, grab > frame, and repeat. The server tries to keep the buffer filled with the > latest constantly, and only stops temporarily when the client is using > the buffer? Yes. The server also stops when there are no clients connected (each client increments a counter in the shared memory location). The clients were using Netscape's server-push technology to display real-time streaming video in a browser window. Server-push video looks really good, and the best thing is that no special tools or plugins are required. If your network connection is good enough, you can even watch TV in a browser window -- all you have to do is change the input from METEOR_INPUT_DEV0 to whatever TV input is called these days. Unfortunately, only Netscape can do server-push, so MSIE clients had to do a one-shot capture every couple of seconds and then refresh. The server also jpeg-compressed the data -- to make it scale well to hundreds of clients -- all a client had to do was lock the buffer, memcpy the data, unlock the buffer, and then send the data across the network. This also guaranteed that clients always got the latest available frame, regardless of their network bandwidth. The big question is how often should the server jpeg-compress the data? I had a dedicated machine (P200 MMX), which was doing it continuously, as fast as it could manage, but other people might want to do it less frequently, maybe every 2 seconds or so. > |In my application the solution was trivial -- to use a SysV semaphore to > |lock the buffer for writing, so no-one can read while it's being written > |into. But since your idea is much more general, you probably have to > |think of a more general synchronisation solution. > > Certainly some handshaking will be needed, if nothing else to tell the > client when a request has completed. Maybe semaphores would be the way to > go. > > Did you consider having the client do one-shot captures? Why have the > daemon constantly pumping video into the buffer. Multiple clients? Yes, multiple clients, a few hundred of them. Server-side compression can be CPU-intensive, but then you can basically have as many clients as you like (each client was taking about 0.001% CPU on my P200). The funny thing is that the CPU load actually drops as the number of clients goes up: more clients increase lock contention, causing the server to update the buffer less often. As for one-shot captures, this is exactly what I did for MS Explorer clients. I was thinking of making the server "smarter", so that any client can request single shots of different sizes, brightness, contrast, etc -- this would require reprogramming of the bktr device on the fly -- but it shouldn't be too hard. Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-multimedia" in the body of the message From owner-freebsd-multimedia Sat May 27 19:45:21 2000 Delivered-To: freebsd-multimedia@freebsd.org Received: from rr.com (rdu25-28-182.nc.rr.com [24.25.28.182]) by hub.freebsd.org (Postfix) with ESMTP id 153C737B75D for ; Sat, 27 May 2000 19:45:16 -0700 (PDT) (envelope-from rhh@rr.com) Received: (from rhh@localhost) by rr.com (8.9.3/8.9.3) id WAA31304 for multimedia@FreeBSD.ORG; Sat, 27 May 2000 22:46:24 -0400 (EDT) (envelope-from rhh) Date: Sat, 27 May 2000 22:46:24 -0400 From: Randall Hopper To: multimedia@FreeBSD.ORG Subject: Re: TV Users - Let me bounce this off you Message-ID: <20000527224624.A31185@nc.rr.com> References: <20000525210340.A44725@nc.rr.com> <392E231D.BA8C1519@rostock.zgdv.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <392E231D.BA8C1519@rostock.zgdv.de>; from runge@rostock.zgdv.de on Fri, May 26, 2000 at 09:09:17AM +0200 Sender: owner-freebsd-multimedia@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Thomas Runge: |Well, making complicated things esier is almost always a good idea :-) | |But it's necessary to specify a good API, which lets you make simple |things easy, but doesn't stop you making more complicated tasks. Agreed. If sufficient interest (and interested developers) popped up, that was going to be the next thread. (Though doesn't look like we're going to get critical mass for this one.) |I didn't have a look into the Video4Linux API, but wouldn't it be |a good idea to support that? I did a quick browse of their docs, and AFAICT it's an app-driver (i.e. userland-kernel) interface spec. It doesn't appear to abstract the machinizations necessary for talking to X11 or for example. So the scope of this userland driver would likely be a superset of whatever driver interface is used, be it V4L/V4U or bktr. Though you make a good point. If we're planning on switching the low-level driver interface to V4U anytime, we should do that first so we don't need a massive rewrite for yet another userland service built on top. |And how about supporting multiple output sources? Do you mean multiple capture cards in one machine? I'm not completely sure I know what you mean, because doesn't bktr currently support that (/dev/bktr{0,1,...}, /dev/tuner{0,1,...})? -- Randall Hopper aa8vb@nc.rr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-multimedia" in the body of the message