From owner-freebsd-multimedia@FreeBSD.ORG Sun Aug 29 04:02:21 2004 Return-Path: Delivered-To: freebsd-multimedia@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5E6DF16A4CF for ; Sun, 29 Aug 2004 04:02:21 +0000 (GMT) Received: from pandora.afflictions.org (asylum.afflictions.org [64.7.134.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id 656CB43D5A for ; Sun, 29 Aug 2004 04:02:20 +0000 (GMT) (envelope-from dgerow@afflictions.org) Received: from localhost (localhost [127.0.0.1]) by pandora.afflictions.org (Postfix) with ESMTP id 378B878C8D; Sun, 29 Aug 2004 00:07:30 -0400 (EDT) Received: from dementia.afflictions.org (dementia.afflictions.org [172.19.206.56]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by pandora.afflictions.org (Postfix) with ESMTP id 5EC7078C8C; Sun, 29 Aug 2004 00:07:24 -0400 (EDT) Received: by dementia.afflictions.org (Postfix, from userid 1001) id 06CE2170C9; Sat, 28 Aug 2004 20:02:09 -0400 (EDT) Date: Sat, 28 Aug 2004 20:02:09 -0400 From: Damian Gerow To: Michael Nottebrock Message-ID: <20040829000209.GA58703@afflictions.org> References: <20040827053643.GB29321@afflictions.org> <200408282225.09364.michaelnottebrock@gmx.net> <20040828210443.GC38908@afflictions.org> <200408282326.15520.michaelnottebrock@gmx.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200408282326.15520.michaelnottebrock@gmx.net> X-Operating-System: FreeBSD 5.3-BETA1 on a i386 X-GPG-Fingerprint: B3D7 D901 A53A 1A99 BFD6 E6DF 9F3B 742B C288 9CC9 User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at afflictions.org cc: freebsd-multimedia@freebsd.org Subject: Re: mplayer/mencoder with bktr(4) device X-BeenThere: freebsd-multimedia@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Multimedia discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Aug 2004 04:02:21 -0000 Thus spake Michael Nottebrock (michaelnottebrock@gmx.net) [28/08/04 17:31]: : > I mean that the picture is fuzzy, there's horizontal lines going down the : > back, the colour's off in places... : : With S-Video? That really sounds like there's something wrong with the video : source. Are you using a SCART/S-VIDEO converter perhaps? In that case you'd : might to switch the signal to s-video at the video source first... Yep, with S-Video. Via mplayer, the RCA in is much cleaner than the S-Video in. Which is the whole reason for my post -- I'm obviously doing something wrong, I just don't know what. I rebooted into Windows and tested the card out -- while the S-Video is not as clear as I'd like it to be, it's better than RCA in under that OS -- the picture's much cleaner and crisper, there's no artifacts on the screen, and it doesn't hurt my eyes to watch for longer than ten minutes. I'm wondering if cabling will be an issue here -- I've got a dirt-cheap cable that I'm using, I might try to find a different one to see if that helps at all. No, it won't help the deinterlacing issues, but it might make other problems go away. And no, I believe it's S-Video at the source. From owner-freebsd-multimedia@FreeBSD.ORG Sun Aug 29 10:07:30 2004 Return-Path: Delivered-To: freebsd-multimedia@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5141116A4CE for ; Sun, 29 Aug 2004 10:07:30 +0000 (GMT) Received: from meitner.wh.uni-dortmund.de (meitner.wh.Uni-Dortmund.DE [129.217.129.133]) by mx1.FreeBSD.org (Postfix) with ESMTP id C609343D60 for ; Sun, 29 Aug 2004 10:07:29 +0000 (GMT) (envelope-from michaelnottebrock@gmx.net) Received: from lofi.dyndns.org (pc2-105.intern.meitner [10.3.12.105]) by meitner.wh.uni-dortmund.de (Postfix) with ESMTP id C90AE1675A5; Sun, 29 Aug 2004 12:07:28 +0200 (CEST) Received: from kiste.my.domain (lofi@kiste.my.domain [192.168.8.4]) (authenticated bits=0) by lofi.dyndns.org (8.12.10/8.12.10) with ESMTP id i7TA7Q7O090719 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Sun, 29 Aug 2004 12:07:27 +0200 (CEST) (envelope-from michaelnottebrock@gmx.net) From: Michael Nottebrock To: Damian Gerow Date: Sun, 29 Aug 2004 12:07:18 +0200 User-Agent: KMail/1.7 References: <20040827053643.GB29321@afflictions.org> <200408282326.15520.michaelnottebrock@gmx.net> <20040829000209.GA58703@afflictions.org> In-Reply-To: <20040829000209.GA58703@afflictions.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart5259585.T7i28G70gG"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200408291207.25722.michaelnottebrock@gmx.net> X-Virus-Scanned: by amavisd-new cc: freebsd-multimedia@freebsd.org Subject: Re: mplayer/mencoder with bktr(4) device X-BeenThere: freebsd-multimedia@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Multimedia discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Aug 2004 10:07:30 -0000 --nextPart5259585.T7i28G70gG Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Sunday 29 August 2004 02:02, Damian Gerow wrote: > Thus spake Michael Nottebrock (michaelnottebrock@gmx.net) [28/08/04 17:31= ]: > : > I mean that the picture is fuzzy, there's horizontal lines going down > : > the back, the colour's off in places... > : > : With S-Video? That really sounds like there's something wrong with the > : video source. Are you using a SCART/S-VIDEO converter perhaps? In that > : case you'd might to switch the signal to s-video at the video source > : first... > > Yep, with S-Video. Via mplayer, the RCA in is much cleaner than the > S-Video in. Which is the whole reason for my post -- I'm obviously doing > something wrong, I just don't know what. Ah. Hm, I suppose you already tried various values for the input parameter= =20 with mplayer/mencoder (perhaps you could post some of the commandlines you'= ve=20 already tried, particularly the one which gives you the bad picture)? =2D-=20 ,_, | Michael Nottebrock | lofi@freebsd.org (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org --nextPart5259585.T7i28G70gG Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (FreeBSD) iD8DBQBBMardXhc68WspdLARAjLyAJwMJD1lT2xgjT0N/6/qSlGRf4zCDACffzrC PR1UEdGCRXap35/+KK8C5OI= =bez3 -----END PGP SIGNATURE----- --nextPart5259585.T7i28G70gG-- From owner-freebsd-multimedia@FreeBSD.ORG Sun Aug 29 14:59:46 2004 Return-Path: Delivered-To: freebsd-multimedia@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 28F7516A4CE for ; Sun, 29 Aug 2004 14:59:46 +0000 (GMT) Received: from pandora.afflictions.org (asylum.afflictions.org [64.7.134.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id 66B3C43D3F for ; Sun, 29 Aug 2004 14:59:45 +0000 (GMT) (envelope-from dgerow@afflictions.org) Received: from localhost (localhost [127.0.0.1]) by pandora.afflictions.org (Postfix) with ESMTP id ED28F78C8D; Sun, 29 Aug 2004 11:04:54 -0400 (EDT) Received: from dementia.afflictions.org (dementia.afflictions.org [172.19.206.56]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by pandora.afflictions.org (Postfix) with ESMTP id 1813878C8C; Sun, 29 Aug 2004 11:04:49 -0400 (EDT) Received: by dementia.afflictions.org (Postfix, from userid 1001) id 1A6121700B; Sun, 29 Aug 2004 10:59:37 -0400 (EDT) Date: Sun, 29 Aug 2004 10:59:36 -0400 From: Damian Gerow To: Michael Nottebrock Message-ID: <20040829145936.GA10969@afflictions.org> References: <20040827053643.GB29321@afflictions.org> <200408282326.15520.michaelnottebrock@gmx.net> <20040829000209.GA58703@afflictions.org> <200408291207.25722.michaelnottebrock@gmx.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200408291207.25722.michaelnottebrock@gmx.net> X-Operating-System: FreeBSD 5.3-BETA1 on a i386 X-GPG-Fingerprint: B3D7 D901 A53A 1A99 BFD6 E6DF 9F3B 742B C288 9CC9 User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at afflictions.org cc: freebsd-multimedia@freebsd.org Subject: Re: mplayer/mencoder with bktr(4) device X-BeenThere: freebsd-multimedia@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Multimedia discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Aug 2004 14:59:46 -0000 Thus spake Michael Nottebrock (michaelnottebrock@gmx.net) [29/08/04 06:12]: : > Yep, with S-Video. Via mplayer, the RCA in is much cleaner than the : > S-Video in. Which is the whole reason for my post -- I'm obviously doing : > something wrong, I just don't know what. : : Ah. Hm, I suppose you already tried various values for the input parameter : with mplayer/mencoder (perhaps you could post some of the commandlines you've : already tried, particularly the one which gives you the bad picture)? Here's what I'm using right now, and it seems to produce the best picture (don't think pullup does much of anything here, though): mplayer tv:// -tv input=2:driver=bsdbt848:norm=ntsc:audioid=1 -vf lavcdeint,hqdn3d=12:9:18,pullup And wow -- I just tried input=5, and what a difference! The picture's on par with Windows (if not a tad bit better), better than fxtv, there's no artifacts. And while I'm sure I cycled through /all/ inputs from 0-12 (don't know how high they go), I guess I wasn't paying attention. Thanks! Note that dropping hqdn3d results in the same vertical lines in the background. Dropping pullup does absolutely nothing. Do you know why S-Video would have two different input values, that produce two different picture qualities? From owner-freebsd-multimedia@FreeBSD.ORG Sun Aug 29 15:05:40 2004 Return-Path: Delivered-To: freebsd-multimedia@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 93F0816A4CE for ; Sun, 29 Aug 2004 15:05:40 +0000 (GMT) Received: from meitner.wh.uni-dortmund.de (meitner.wh.uni-dortmund.de [129.217.129.133]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5280443D3F for ; Sun, 29 Aug 2004 15:05:40 +0000 (GMT) (envelope-from michaelnottebrock@gmx.net) Received: from lofi.dyndns.org (pc2-105.intern.meitner [10.3.12.105]) by meitner.wh.uni-dortmund.de (Postfix) with ESMTP id 930441674DE; Sun, 29 Aug 2004 17:05:39 +0200 (CEST) Received: from kiste.my.domain (lofi@kiste.my.domain [192.168.8.4]) (authenticated bits=0) by lofi.dyndns.org (8.12.10/8.12.10) with ESMTP id i7TF5b7O094389 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Sun, 29 Aug 2004 17:05:38 +0200 (CEST) (envelope-from michaelnottebrock@gmx.net) From: Michael Nottebrock To: Damian Gerow Date: Sun, 29 Aug 2004 17:05:32 +0200 User-Agent: KMail/1.7 References: <20040827053643.GB29321@afflictions.org> <200408291207.25722.michaelnottebrock@gmx.net> <20040829145936.GA10969@afflictions.org> In-Reply-To: <20040829145936.GA10969@afflictions.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1947304.OoHozZnpet"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200408291705.36868.michaelnottebrock@gmx.net> X-Virus-Scanned: by amavisd-new cc: freebsd-multimedia@freebsd.org Subject: Re: mplayer/mencoder with bktr(4) device X-BeenThere: freebsd-multimedia@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Multimedia discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Aug 2004 15:05:40 -0000 --nextPart1947304.OoHozZnpet Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Sunday 29 August 2004 16:59, Damian Gerow wrote: > Do you know why S-Video would have two different input values, that produ= ce > two different picture qualities? Input is a pretty generic parameter that's passed to the driver almost=20 verbatim - and from the driver to the hardware, so it depends how the=20 manufacturer of your bktr-card has wired things there. =2D-=20 ,_, | Michael Nottebrock | lofi@freebsd.org (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org --nextPart1947304.OoHozZnpet Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (FreeBSD) iD8DBQBBMfDAXhc68WspdLARAju1AJ0aE37O0mKwz761YlIqk5ezwmR5/QCfTAeV U3IEO7SKd6p4ayWv9ueUDYg= =BuiW -----END PGP SIGNATURE----- --nextPart1947304.OoHozZnpet-- From owner-freebsd-multimedia@FreeBSD.ORG Sun Aug 29 16:08:19 2004 Return-Path: Delivered-To: freebsd-multimedia@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DE6EA16A4CE; Sun, 29 Aug 2004 16:08:19 +0000 (GMT) Received: from abigail.blackend.org (blackend.org [212.11.35.229]) by mx1.FreeBSD.org (Postfix) with ESMTP id D7A4143D3F; Sun, 29 Aug 2004 16:08:18 +0000 (GMT) (envelope-from marc@blackend.org) Received: from abigail.blackend.org (localhost [127.0.0.1]) i7TG8Hr6054539; Sun, 29 Aug 2004 18:08:17 +0200 (CEST) (envelope-from marc@abigail.blackend.org) Received: (from marc@localhost) by abigail.blackend.org (8.12.11/8.12.11/Submit) id i7TG8GsR054538; Sun, 29 Aug 2004 18:08:17 +0200 (CEST) (envelope-from marc) Date: Sun, 29 Aug 2004 18:08:16 +0200 From: Marc Fonvieille To: Ruslan Ermilov Message-ID: <20040829160815.GB54085@abigail.blackend.org> References: <20040828142503.GA52613@ip.net.ua> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="HlL+5n6rz5pIUxbD" Content-Disposition: inline In-Reply-To: <20040828142503.GA52613@ip.net.ua> User-Agent: Mutt/1.4.2.1i X-Useless-Header: blackend.org X-Operating-System: FreeBSD 4.10-PRERELEASE cc: Cameron Grant cc: multimedia@FreeBSD.org cc: "Simon L. Nielsen" cc: Seigo Tanimura cc: current@FreeBSD.org Subject: Re: [PATCH] sound(4) related manpages 5.3 TODO item X-BeenThere: freebsd-multimedia@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Multimedia discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Aug 2004 16:08:20 -0000 --HlL+5n6rz5pIUxbD Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Aug 28, 2004 at 05:25:03PM +0300, Ruslan Ermilov wrote: > Gang, >=20 > [ Please keep me Cc:ed when replying. ] >=20 > I've picked up the "sound(4) related manual pages" item from > the 5.3-RELEASE TODO list. >=20 > While working on adopting the pcm(4) and related manpages to > the new world order, I have noticed some odds that I'd like > your comments on first, before I proceed further. >=20 > One and most important thing I'm not sure I understand, and > that's causing a lot of confusion, is why "device pcm" was > renamed to "device sound" in the first place? I believe the > reason is that "device sound" is a generic sound driver, > which has support for PCM playback, mixer, /dev/sndstat, > eventually MIDI, sequencer, and so on. Individual sound > drivers are free to implement either of these interfaces. > Most of them implement "pcm" nowadays, so saying that > "pcm was renamed to sound" is not quite correct. In other > words, the sound.ko module provides the infrastructure for > more than just PCM, and the sound(4) manpage should eventually > document more than just PCM. Does that sound correct? > I'm not a sound(4) expert, but I think you're right. However, I see something that may be confusing for the new comer: in the kernel we add: device sound device snd_ich # as example and in /dev/sndstat we see: FreeBSD Audio Driver (newpcm) Installed devices: pcm0: at io 0xd800, 0xdc80 irq 5 bufsz 16384 kld snd_ich (1p/2r/0v channels duplex default) or in dmesg: pcm0: port 0xdc80-0xdcbf,0xd800-0xd8ff irq 5 at device 31.5 on pci0 pcm0: [GIANT-LOCKED] pcm0: Are the "pcm0" and "newpcm" words totally correct here, why no sound/snd ? > Also, there seems to be some confusion between the modules, > drivers, and devices that they implement, which are different > beasties, and are often named differently, and this causes > some misunderstandings and bugs (see below). >=20 > Anyway, the attached patch adopts the sound(4) related man > pages to the new world order. How to proceed: >=20 > 1. The following repo-copies in /home/ncvs/src/share/man/man4 > should be made (there were made locally to produce the > patch): >=20 > pcm.4,v -> sound.4,v > csa.4,v -> snd_csa.4,v > gusc.4,v -> snd_gusc.4,v=20 > maestro3.4,v -> snd_maestro3.4,v=20 > sbc.4,v -> snd_sbc.4,v > uaudio.4,v -> snd_uaudio.4,v >=20 > 2. The old manpages (on the left) were removed, and aren't > included in the patch. >=20 > 3. After repo-copies and deletes, the attached patch should be > applied. It's mostly mechanical (foo -> snd_foo, pcm -> sound), > with the following notable exceptions: >=20 > - Note that non-PnP ISA cards, such as those handled by snd_mss(4) > and snd_ad1816(4), still require hints of the form >=20 > hint.pcm.0.at=3D"isa" > hint.pcm.0.irq=3D"5" > hint.pcm.0.drq=3D"1" > hint.pcm.0.flags=3D"0x0" >=20 > because they implement device "pcm". Granted, the difference > between module and driver name is confusing enough that Seigo > misspelled hints names in sys/conf/NOTES, and Simon misspelled > them in the new snd_ad1816(4) manpage. The patch corrects the > hints names in the snd_ad1816(4) manpage and NOTES. The patch > removes the "hint.snd_mss" from NOTES because (like was said) > the snd_mss(4) module implements the "pcm" device, hence the > hints start with "hint.pcm", and this is already documented > in the sound(4) manpage. Module snd_sbc(4) and snd_gusc(4) > are special in that they implement PCM support through the > bridge device ("sbc" and "gusc", respectively), with "pcm" > device as a child. For them, ISA hints should be spelled > "hint.sbc" and "hint.gusc", respectively. This is also fixed > in NOTES. >=20 > - The patch also fixes the SYNOPSIS section of the snd_maestro3(4) > manpage to align it with other sound drivers manpages, and adds > missing "device sound" to almost all of the snd_*(4) manpages. >=20 perfect! > Does that look sane? I'd be grateful is someone more fluent with > our sound subsystem could review this. >=20 I'm not more fluent than you, but your changes seem correct. Marc --HlL+5n6rz5pIUxbD Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFBMf9u81T1MWxkgcoRAvz7AJ9mKhPMDSXxP8mg9cMbEKNGW1ivqwCfTuqk jytHD5GGutJSaRkn831R7sQ= =at/T -----END PGP SIGNATURE----- --HlL+5n6rz5pIUxbD-- From owner-freebsd-multimedia@FreeBSD.ORG Sun Aug 29 17:16:45 2004 Return-Path: Delivered-To: freebsd-multimedia@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 68BB116A4CE; Sun, 29 Aug 2004 17:16:45 +0000 (GMT) Received: from mindfields.energyhq.es.eu.org (73.Red-213-97-200.pooles.rima-tde.net [213.97.200.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id 85AC743D46; Sun, 29 Aug 2004 17:16:42 +0000 (GMT) (envelope-from flynn@energyhq.es.eu.org) Received: from scienide (scienide.energyhq.es.eu.org [192.168.100.1]) by mindfields.energyhq.es.eu.org (Postfix) with SMTP id B18DE35032; Sun, 29 Aug 2004 19:16:39 +0200 (CEST) Date: Sun, 29 Aug 2004 19:16:15 +0200 From: Miguel Mendez To: freebsd-ports@freebsd.org Message-Id: <20040829191615.2f10acf0.flynn@energyhq.es.eu.org> X-Mailer: Sylpheed version 0.9.12-gtk2-20040622 (GTK+ 2.4.9; i386-portbld-freebsd5.2.1) Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="pgp-sha1"; boundary="Signature=_Sun__29_Aug_2004_19_16_15_+0200_Vz/YPzeDZKMBDuBF" cc: freebsd-multimedia@freebsd.org Subject: Attention beep-media-player users on FreeBSD 5.x X-BeenThere: freebsd-multimedia@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Multimedia discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Aug 2004 17:16:45 -0000 --Signature=_Sun__29_Aug_2004_19_16_15_+0200_Vz/YPzeDZKMBDuBF Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Content-Transfer-Encoding: 7bit Hi all, Because I've gotten about 5 e-mails so far about this. It's explained in the pkg-message anyway. If bmp crashes upon start with a libpthread related error, modify your /etc/libmap.conf and add this: # Might crash if used with libpthread [beep-media-player] libc_r.so.5 libc_r.so.5 libc_r.so libc_r.so [/usr/X11R6/bin/beep-media-player] libc_r.so.5 libc_r.so.5 libc_r.so libc_r.so Also, make sure your gnomevfs2 port is up to date. I've updated the beepmp FAQ wiki with this info as well. I'm working on finding out who's to blame on this, a bug in libpthread or some bad coding on beepmp's side. Cheers, -- Miguel Mendez http://www.energyhq.es.eu.org PGP Key: 0xDC8514F1 Note: All HTML and non-english mail goes to /dev/null --Signature=_Sun__29_Aug_2004_19_16_15_+0200_Vz/YPzeDZKMBDuBF Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (FreeBSD) iD8DBQFBMg9inLctrNyFFPERAhA5AJwI3uo4/aAO55Pe2D06h3DzYwVVfACfTwZ1 bAI8z8ygzwL/pC5tgLkJLRI= =nna7 -----END PGP SIGNATURE----- --Signature=_Sun__29_Aug_2004_19_16_15_+0200_Vz/YPzeDZKMBDuBF-- From owner-freebsd-multimedia@FreeBSD.ORG Sun Aug 29 19:01:27 2004 Return-Path: Delivered-To: freebsd-multimedia@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D541216A4DC; Sun, 29 Aug 2004 19:01:20 +0000 (GMT) Received: from hak.cnd.mcgill.ca (hak.cnd.McGill.CA [132.216.11.133]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7072D43D4C; Sun, 29 Aug 2004 19:01:20 +0000 (GMT) (envelope-from mat@hak.cnd.mcgill.ca) Received: from hak.cnd.mcgill.ca (localhost [127.0.0.1]) by hak.cnd.mcgill.ca (8.12.9/8.12.8) with ESMTP id i7TJ8X1M011556; Sun, 29 Aug 2004 15:08:33 -0400 (EDT) (envelope-from mat@hak.cnd.mcgill.ca) Received: (from mat@localhost) by hak.cnd.mcgill.ca (8.12.9/8.12.8/Submit) id i7TJ8X5P011555; Sun, 29 Aug 2004 15:08:33 -0400 (EDT) Date: Sun, 29 Aug 2004 15:08:33 -0400 From: Mathew Kanner To: Ruslan Ermilov Message-ID: <20040829190833.GA9796@cnd.mcgill.ca> References: <20040828142503.GA52613@ip.net.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040828142503.GA52613@ip.net.ua> User-Agent: Mutt/1.4.1i Organization: I speak for myself, operating in Montreal, CANADA X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.62 X-Spam-Checker-Version: SpamAssassin 2.62 (2004-01-11) on hak.cnd.mcgill.ca cc: Cameron Grant cc: multimedia@freebsd.org cc: "Simon L. Nielsen" cc: Seigo Tanimura cc: current@freebsd.org Subject: Re: [PATCH] sound(4) related manpages 5.3 TODO item X-BeenThere: freebsd-multimedia@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Multimedia discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Aug 2004 19:01:27 -0000 On Aug 28, Ruslan Ermilov wrote: Hello Ruslan, > One and most important thing I'm not sure I understand, and > that's causing a lot of confusion, is why "device pcm" was > renamed to "device sound" in the first place? I believe the > reason is that "device sound" is a generic sound driver, > which has support for PCM playback, mixer, /dev/sndstat, > eventually MIDI, sequencer, and so on. Individual sound > drivers are free to implement either of these interfaces. > Most of them implement "pcm" nowadays, so saying that > "pcm was renamed to sound" is not quite correct. In other > words, the sound.ko module provides the infrastructure for > more than just PCM, and the sound(4) manpage should eventually > document more than just PCM. Does that sound correct? Sounds correct on all accounts. Also, the synopsis should indicate that the preferred method to load sound is to set sound_load="YES" in loader.conf and barely mention kernel options, and otherwise ignore ISA and PNP. > Also, there seems to be some confusion between the modules, > drivers, and devices that they implement, which are different > beasties, and are often named differently, and this causes > some misunderstandings and bugs (see below). Note that sndstat now lists the kld name (if loaded as such) in the device listings. > > Anyway, the attached patch adopts the sound(4) related man > pages to the new world order. How to proceed: > > 1. The following repo-copies in /home/ncvs/src/share/man/man4 > should be made (there were made locally to produce the > patch): > > pcm.4,v -> sound.4,v > csa.4,v -> snd_csa.4,v > gusc.4,v -> snd_gusc.4,v > maestro3.4,v -> snd_maestro3.4,v > sbc.4,v -> snd_sbc.4,v > uaudio.4,v -> snd_uaudio.4,v Good. > > 2. The old manpages (on the left) were removed, and aren't > included in the patch. > > 3. After repo-copies and deletes, the attached patch should be > applied. It's mostly mechanical (foo -> snd_foo, pcm -> sound), > with the following notable exceptions: > > - Note that non-PnP ISA cards, such as those handled by snd_mss(4) > and snd_ad1816(4), still require hints of the form > > hint.pcm.0.at="isa" > hint.pcm.0.irq="5" > hint.pcm.0.drq="1" > hint.pcm.0.flags="0x0" > > because they implement device "pcm". Granted, the difference > between module and driver name is confusing enough that Seigo > misspelled hints names in sys/conf/NOTES, and Simon misspelled > them in the new snd_ad1816(4) manpage. The patch corrects the > hints names in the snd_ad1816(4) manpage and NOTES. The patch > removes the "hint.snd_mss" from NOTES because (like was said) > the snd_mss(4) module implements the "pcm" device, hence the > hints start with "hint.pcm", and this is already documented > in the sound(4) manpage. Module snd_sbc(4) and snd_gusc(4) > are special in that they implement PCM support through the > bridge device ("sbc" and "gusc", respectively), with "pcm" > device as a child. For them, ISA hints should be spelled > "hint.sbc" and "hint.gusc", respectively. This is also fixed > in NOTES. This is a very good catch, I never noticed this. > > - The patch also fixes the SYNOPSIS section of the snd_maestro3(4) > manpage to align it with other sound drivers manpages, and adds > missing "device sound" to almost all of the snd_*(4) manpages. Yes please. > > Does that look sane? I'd be grateful is someone more fluent with > our sound subsystem could review this. I've read the diff and it all looks very good to me, thank you very much for taking this on. --Mat -- Applicants must also have extensive knowledge of UNIX, although they should have sufficiently good programming taste to not consider this an achievement. - MIT AI Lab job ad in the /Boston Globe/ From owner-freebsd-multimedia@FreeBSD.ORG Sun Aug 29 19:06:00 2004 Return-Path: Delivered-To: freebsd-multimedia@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A7F0216A4CE; Sun, 29 Aug 2004 19:06:00 +0000 (GMT) Received: from mail.ipnet.kiev.ua (ns.ip.net.ua [82.193.96.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 90DD743D53; Sun, 29 Aug 2004 19:05:59 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from heffalump.ip.net.ua (heffalump.ip.net.ua [82.193.96.213]) by mail.ipnet.kiev.ua (8.12.11/8.12.11) with ESMTP id i7TJ5ssd008219 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 29 Aug 2004 22:05:55 +0300 (EEST) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.1/8.13.1) id i7TJ5xeC039616; Sun, 29 Aug 2004 22:05:59 +0300 (EEST) (envelope-from ru) Date: Sun, 29 Aug 2004 22:05:59 +0300 From: Ruslan Ermilov To: Marc Fonvieille Message-ID: <20040829190559.GA39435@ip.net.ua> References: <20040828142503.GA52613@ip.net.ua> <20040829160815.GB54085@abigail.blackend.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="nFreZHaLTZJo0R7j" Content-Disposition: inline In-Reply-To: <20040829160815.GB54085@abigail.blackend.org> User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new cc: Cameron Grant cc: multimedia@freebsd.org cc: "Simon L. Nielsen" cc: Seigo Tanimura cc: current@freebsd.org Subject: Re: [PATCH] sound(4) related manpages 5.3 TODO item X-BeenThere: freebsd-multimedia@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Multimedia discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Aug 2004 19:06:00 -0000 --nFreZHaLTZJo0R7j Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Aug 29, 2004 at 06:08:16PM +0200, Marc Fonvieille wrote: > On Sat, Aug 28, 2004 at 05:25:03PM +0300, Ruslan Ermilov wrote: [...] > > One and most important thing I'm not sure I understand, and > > that's causing a lot of confusion, is why "device pcm" was > > renamed to "device sound" in the first place? I believe the > > reason is that "device sound" is a generic sound driver, > > which has support for PCM playback, mixer, /dev/sndstat, > > eventually MIDI, sequencer, and so on. Individual sound > > drivers are free to implement either of these interfaces. > > Most of them implement "pcm" nowadays, so saying that > > "pcm was renamed to sound" is not quite correct. In other > > words, the sound.ko module provides the infrastructure for > > more than just PCM, and the sound(4) manpage should eventually > > document more than just PCM. Does that sound correct? > > >=20 > I'm not a sound(4) expert, but I think you're right. > However, I see something that may be confusing for the new comer: in the > kernel we add: >=20 > device sound > device snd_ich # as example >=20 > and in /dev/sndstat we see: >=20 > FreeBSD Audio Driver (newpcm) > Installed devices: > pcm0: at io 0xd800, 0xdc80 irq 5 bufsz 16384 kld > snd_ich (1p/2r/0v channels duplex default) >=20 > or in dmesg: >=20 > pcm0: port 0xdc80-0xdcbf,0xd800-0xd8ff irq 5 at > device 31.5 on pci0 > pcm0: [GIANT-LOCKED] > pcm0: >=20 >=20 > Are the "pcm0" and "newpcm" words totally correct here, why no sound/snd ? >=20 It's my current understanding that pcm(4) is only one part of the sound(4) subsystem. midi(4) will be another part of it, and mixer(4) is another such device. The sound(4) man page should eventually document the entire sound subsystem. The snd_foo(4) module can register with the sound(4) system one "pcm" device, one "midi" device, and one "mixer" device. > > Does that look sane? I'd be grateful is someone more fluent with > > our sound subsystem could review this. > >=20 >=20 > I'm not more fluent than you, but your changes seem correct. >=20 Thanks, Marc. I will wait for one more day, then if nothing changes, will order repo-copies and proceed with the patch and merging this to RELENG_5. Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --nFreZHaLTZJo0R7j Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (FreeBSD) iD8DBQFBMikXqRfpzJluFF4RAi5vAJ9/INbHV7uoOrB3OSR9RzpEzxFk4QCfYxds Sy1VSmW30qZdcHr4CBf+VbI= =D4bc -----END PGP SIGNATURE----- --nFreZHaLTZJo0R7j-- From owner-freebsd-multimedia@FreeBSD.ORG Sun Aug 29 19:35:36 2004 Return-Path: Delivered-To: freebsd-multimedia@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2F1C316A4CE; Sun, 29 Aug 2004 19:35:36 +0000 (GMT) Received: from zaphod.nitro.dk (port324.ds1-khk.adsl.cybercity.dk [212.242.113.79]) by mx1.FreeBSD.org (Postfix) with ESMTP id 90CE543D46; Sun, 29 Aug 2004 19:35:35 +0000 (GMT) (envelope-from simon@zaphod.nitro.dk) Received: by zaphod.nitro.dk (Postfix, from userid 3000) id 25B2111AB1; Sun, 29 Aug 2004 21:35:34 +0200 (CEST) Date: Sun, 29 Aug 2004 21:35:33 +0200 From: "Simon L. Nielsen" To: Ruslan Ermilov Message-ID: <20040829193533.GA760@zaphod.nitro.dk> References: <20040828142503.GA52613@ip.net.ua> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="8t9RHnE3ZwKMSgU+" Content-Disposition: inline In-Reply-To: <20040828142503.GA52613@ip.net.ua> User-Agent: Mutt/1.5.6i cc: Cameron Grant cc: current@FreeBSD.org cc: Seigo Tanimura cc: multimedia@FreeBSD.org Subject: Re: [PATCH] sound(4) related manpages 5.3 TODO item X-BeenThere: freebsd-multimedia@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Multimedia discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Aug 2004 19:35:36 -0000 --8t9RHnE3ZwKMSgU+ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2004.08.28 17:25:03 +0300, Ruslan Ermilov wrote: > I've picked up the "sound(4) related manual pages" item from > the 5.3-RELEASE TODO list. Great :-). I hope to get as many sound device manual in as possible before 5.3, but I also have the Hardware Notes project to get done for 5.3, and I'm starting again at the university tomorrow... so help from others (including non-committers) would be great and I will be happy to review/commit for others. [snip parts I can't answer anyway] > Anyway, the attached patch adopts the sound(4) related man > pages to the new world order. How to proceed: [snip "TODO" list] > Does that look sane? I'd be grateful is someone more fluent with > our sound subsystem could review this. I'm (very) far from an expert on the sound system, but in general this looks very good to me. --=20 Simon L. Nielsen FreeBSD Documentation Team --8t9RHnE3ZwKMSgU+ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (FreeBSD) iD8DBQFBMjAFh9pcDSc1mlERAjqUAJ9fKXYm+ObwhWUh/VeerrCW6PW85gCfZ0ib jQMA1eA7yIj/NF7h42mTxV4= =4veA -----END PGP SIGNATURE----- --8t9RHnE3ZwKMSgU+-- From owner-freebsd-multimedia@FreeBSD.ORG Sun Aug 29 20:59:46 2004 Return-Path: Delivered-To: freebsd-multimedia@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 19C7C16A4CE; Sun, 29 Aug 2004 20:59:46 +0000 (GMT) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 45BB543D2D; Sun, 29 Aug 2004 20:59:45 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from heffalump.ip.net.ua (heffalump.ip.net.ua [82.193.96.213]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id i7TKxbTs051278 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 29 Aug 2004 23:59:38 +0300 (EEST) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.1/8.13.1) id i7TKxgIx040203; Sun, 29 Aug 2004 23:59:42 +0300 (EEST) (envelope-from ru) Date: Sun, 29 Aug 2004 23:59:42 +0300 From: Ruslan Ermilov To: Mathew Kanner Message-ID: <20040829205942.GC39813@ip.net.ua> References: <20040828142503.GA52613@ip.net.ua> <20040829190833.GA9796@cnd.mcgill.ca> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="M/SuVGWktc5uNpra" Content-Disposition: inline In-Reply-To: <20040829190833.GA9796@cnd.mcgill.ca> User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new cc: Cameron Grant cc: multimedia@FreeBSD.org cc: "Simon L. Nielsen" cc: Seigo Tanimura cc: current@FreeBSD.org Subject: Re: [PATCH] sound(4) related manpages 5.3 TODO item X-BeenThere: freebsd-multimedia@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Multimedia discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Aug 2004 20:59:46 -0000 --M/SuVGWktc5uNpra Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Aug 29, 2004 at 03:08:33PM -0400, Mathew Kanner wrote: > On Aug 28, Ruslan Ermilov wrote: >=20 > Hello Ruslan, >=20 > > One and most important thing I'm not sure I understand, and > > that's causing a lot of confusion, is why "device pcm" was > > renamed to "device sound" in the first place? I believe the > > reason is that "device sound" is a generic sound driver, > > which has support for PCM playback, mixer, /dev/sndstat, > > eventually MIDI, sequencer, and so on. Individual sound > > drivers are free to implement either of these interfaces. > > Most of them implement "pcm" nowadays, so saying that > > "pcm was renamed to sound" is not quite correct. In other > > words, the sound.ko module provides the infrastructure for > > more than just PCM, and the sound(4) manpage should eventually > > document more than just PCM. Does that sound correct? >=20 > Sounds correct on all accounts. Also, the synopsis should > indicate that the preferred method to load sound is to set > sound_load=3D"YES" in loader.conf and barely mention kernel options, and > otherwise ignore ISA and PNP. >=20 Um, what's wrong with ISA and PnP hints, and what's wrong with "device sound"? OK, I've briefly read your midi2-patch-aug22.diff patch, and I see that it implements "device midi" and the midi.ko module, and they are not part of "device sound", as I thought they would be. So I wonder, if it's correct to rename the pcm(4) manpage to sound(4), or will the sound(4) manpage be updated to document midi(4) as well? Also, the pcm(4) manpage (whether it's renamed to sound(4) or not) is seriously outdated. First, it talks only about pcm(4), and unless there are plans to update it with more than PCM, it should probably stay pcm(4). Its SYNOPSIS still assumes that "device pcm" provides all sound drivers (like it does in 4.x). The whole manpage needs to be revised and updated. Are you willing to help? > > 3. After repo-copies and deletes, the attached patch should be > > applied. It's mostly mechanical (foo -> snd_foo, pcm -> sound), > > with the following notable exceptions: > >=20 > > - Note that non-PnP ISA cards, such as those handled by snd_mss(4) > > and snd_ad1816(4), still require hints of the form > >=20 > > hint.pcm.0.at=3D"isa" > > hint.pcm.0.irq=3D"5" > > hint.pcm.0.drq=3D"1" > > hint.pcm.0.flags=3D"0x0" > >=20 > > because they implement device "pcm". Granted, the difference > > between module and driver name is confusing enough that Seigo > > misspelled hints names in sys/conf/NOTES, and Simon misspelled > > them in the new snd_ad1816(4) manpage. The patch corrects the > > hints names in the snd_ad1816(4) manpage and NOTES. The patch > > removes the "hint.snd_mss" from NOTES because (like was said) > > the snd_mss(4) module implements the "pcm" device, hence the > > hints start with "hint.pcm", and this is already documented > > in the sound(4) manpage. Module snd_sbc(4) and snd_gusc(4) > > are special in that they implement PCM support through the > > bridge device ("sbc" and "gusc", respectively), with "pcm" > > device as a child. For them, ISA hints should be spelled > > "hint.sbc" and "hint.gusc", respectively. This is also fixed > > in NOTES. >=20 > This is a very good catch, I never noticed this. >=20 I wish there would be more consistency in naming. Previously, we had the csa(4) manpage, "device csa", and /dev/csa* entries. Now we will have the snd_csa(4) manpage, "device snd_csa", but still /dev/csaX entry. Also, in the old world, "midi" devices were created as children of "pcm" devices, so "hint.pcm.0" hints for non-PnP ISA devices looked correct. In new world with your updated midi(4), what will be the hints for the ISA device that implements PCM and MIDI? hint.pcm.0 and hint.midi.0? ;) All is so plain in the old good 4.x world: /sys/i386/isa/sound/sb_card.c /sys/i386/isa/sound/sb_dsp.c /sys/i386/isa/sound/sb_midi.c /sys/i386/isa/sound/sb_mixer.c Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --M/SuVGWktc5uNpra Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (FreeBSD) iD8DBQFBMkO+qRfpzJluFF4RAkDIAJ42JHH6V+Ocsh31XY0Bv0OlFhleeACfZuBL J3citDWqvci+h45zh6O+mBA= =U25R -----END PGP SIGNATURE----- --M/SuVGWktc5uNpra-- From owner-freebsd-multimedia@FreeBSD.ORG Mon Aug 30 01:20:27 2004 Return-Path: Delivered-To: freebsd-multimedia@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5C18C16A4D0; Mon, 30 Aug 2004 01:20:27 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4C0D143D4C; Mon, 30 Aug 2004 01:20:27 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 3E7EF72DD4; Sun, 29 Aug 2004 18:20:27 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 383DE72DCB; Sun, 29 Aug 2004 18:20:27 -0700 (PDT) Date: Sun, 29 Aug 2004 18:20:27 -0700 (PDT) From: Doug White To: Miguel Mendez In-Reply-To: <20040829191615.2f10acf0.flynn@energyhq.es.eu.org> Message-ID: <20040829181627.C69068@carver.gumbysoft.com> References: <20040829191615.2f10acf0.flynn@energyhq.es.eu.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-multimedia@freebsd.org cc: freebsd-ports@freebsd.org Subject: Re: Attention beep-media-player users on FreeBSD 5.x X-BeenThere: freebsd-multimedia@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Multimedia discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Aug 2004 01:20:27 -0000 On Sun, 29 Aug 2004, Miguel Mendez wrote: > Hi all, > > Because I've gotten about 5 e-mails so far about this. It's explained in > the pkg-message anyway. > > If bmp crashes upon start with a libpthread related error, modify your > /etc/libmap.conf and add this: Complaining about spin locks not initialized, I bet? > # Might crash if used with libpthread > [beep-media-player] > libc_r.so.5 libc_r.so.5 > libc_r.so libc_r.so This looks like an attempt to hack around the crossed-thread-libraries issue. I know how to fix this with KDE, but I'm not as experienced with gnome. Generally it involves rebuilding X and all ports in a particular order. With KDE you need to rebuild gmake fairly early since it encodes build options that get used for qt and dependants. There may be some information in the -current archives on this issue, particularly relating to gnome. If you want to go hunting, run 'ldd' on the beepmp binary and make sure libc_r and libpthread don't both show up. If they do, you need to hunt through the dependant libraries to find the one depending on libc_r and rebuild it. objdump -x is useful here; look for the NEEDED entries in the dynamic section. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org From owner-freebsd-multimedia@FreeBSD.ORG Mon Aug 30 08:54:49 2004 Return-Path: Delivered-To: freebsd-multimedia@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6E30016A4E8; Mon, 30 Aug 2004 08:54:49 +0000 (GMT) Received: from mindfields.energyhq.es.eu.org (73.Red-213-97-200.pooles.rima-tde.net [213.97.200.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8B0FE43D3F; Mon, 30 Aug 2004 08:54:47 +0000 (GMT) (envelope-from flynn@energyhq.es.eu.org) Received: from scienide (scienide.energyhq.es.eu.org [192.168.100.1]) by mindfields.energyhq.es.eu.org (Postfix) with SMTP id 4E44735731; Mon, 30 Aug 2004 10:54:46 +0200 (CEST) Date: Mon, 30 Aug 2004 10:54:27 +0200 From: Miguel Mendez To: Doug White Message-Id: <20040830105427.30e2297a.flynn@energyhq.es.eu.org> In-Reply-To: <20040829181627.C69068@carver.gumbysoft.com> References: <20040829191615.2f10acf0.flynn@energyhq.es.eu.org> <20040829181627.C69068@carver.gumbysoft.com> X-Mailer: Sylpheed version 0.9.12-gtk2-20040622 (GTK+ 2.4.9; i386-portbld-freebsd5.2.1) Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="pgp-sha1"; boundary="Signature=_Mon__30_Aug_2004_10_54_27_+0200_c19gMzO4+keVu8QQ" cc: freebsd-multimedia@freebsd.org cc: freebsd-ports@freebsd.org Subject: Re: Attention beep-media-player users on FreeBSD 5.x X-BeenThere: freebsd-multimedia@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Multimedia discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Aug 2004 08:54:49 -0000 --Signature=_Mon__30_Aug_2004_10_54_27_+0200_c19gMzO4+keVu8QQ Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Content-Transfer-Encoding: 7bit On Sun, 29 Aug 2004 18:20:27 -0700 (PDT) Doug White wrote: Hi, > > If bmp crashes upon start with a libpthread related error, modify > > your/etc/libmap.conf and add this: > > Complaining about spin locks not initialized, I bet? The exact error is this: flynn@scienide% beep-media-player GThread-ERROR **: file gthread-posix.c: line 188 (): error 'Resource deadlock avoided' during 'pthread_mutex_trylock' aborting... Abort (core dumped) It happens pretty early when the program is about to load the skin. > > # Might crash if used with libpthread > > [beep-media-player] > > libc_r.so.5 libc_r.so.5 > > libc_r.so libc_r.so > > This looks like an attempt to hack around the crossed-thread-libraries > issue. I know how to fix this with KDE, but I'm not as experienced The problem was that I was mapping libc_r.so to libpthread.so. beepmp crashes with libpthread, so I had to undo the mapping. However, it's still true that people who linked beepmp with libpthread need to remap the lib, e.g. [beep-media-player] libpthread.so.1 libc_r.so.5 libpthread.so libc_r.so ... and so on. > with gnome. Generally it involves rebuilding X and all ports in a > particular order. With KDE you need to rebuild gmake fairly early > since it encodes build options that get used for qt and dependants. Interesting, I haven't experienced problems with KDE, at least not in 5.2, I'm waiting for 3.3 to come out to try it again (now on 5.3). > There may be some information in the -current archives on this issue, > particularly relating to gnome. Thanks, I'll have a look. > If you want to go hunting, run 'ldd' on the beepmp binary and make > sure libc_r and libpthread don't both show up. If they do, you need to > hunt through the dependant libraries to find the one depending on > libc_r and rebuild it. objdump -x is useful here; look for the NEEDED > entries in the dynamic section. beepmp links with libgthread and libc_r. If libc_r is mapped to libpthread the program aborts, it works fine with libc_r. I'll have a look at the offending code when I have some spare time. Cheers, -- Miguel Mendez http://www.energyhq.es.eu.org PGP Key: 0xDC8514F1 Note: All HTML and non-english mail goes to /dev/null --Signature=_Mon__30_Aug_2004_10_54_27_+0200_c19gMzO4+keVu8QQ Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (FreeBSD) iD8DBQFBMutHnLctrNyFFPERAtSxAKC74Bc4kTom2eJE9rKyzVGDA5CHBACgiE9H RC4mwWtyD29Xb8za7DnUzq4= =QiLt -----END PGP SIGNATURE----- --Signature=_Mon__30_Aug_2004_10_54_27_+0200_c19gMzO4+keVu8QQ-- From owner-freebsd-multimedia@FreeBSD.ORG Mon Aug 30 15:28:52 2004 Return-Path: Delivered-To: freebsd-multimedia@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 26CDF16A4CE; Mon, 30 Aug 2004 15:28:52 +0000 (GMT) Received: from rt0-ext.kdcg.net (rt0-ext.kdcg.net [81.2.114.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id E3D6243D2F; Mon, 30 Aug 2004 15:28:50 +0000 (GMT) (envelope-from cg@ijcg.net) Received: from localhost (localhost [127.0.0.1]) by rt0-ext.kdcg.net (Postfix) with ESMTP id BF41E4AB901D; Mon, 30 Aug 2004 16:31:27 +0100 (BST) Received: from rt0-ext.kdcg.net ([127.0.0.1]) by localhost (alexandria.rings [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 48510-06; Mon, 30 Aug 2004 16:31:26 +0100 (BST) Received: from tacitblue3.rings (tacitblue.rings [10.1.0.2]) by rt0-ext.kdcg.net (Postfix) with ESMTP id A75EC4AB9018; Mon, 30 Aug 2004 16:31:26 +0100 (BST) Date: Mon, 30 Aug 2004 16:28:52 +0100 From: cg To: "Ruslan Ermilov" , "Mathew Kanner" References: <20040828142503.GA52613@ip.net.ua> <20040829190833.GA9796@cnd.mcgill.ca> <20040829205942.GC39813@ip.net.ua> Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-15 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-ID: In-Reply-To: <20040829205942.GC39813@ip.net.ua> User-Agent: Opera M2/7.54 (Win32, build 3869) X-Virus-Scanned: by amavisd-new at badexample.com cc: Cameron Grant cc: multimedia@freebsd.org cc: "Simon L. Nielsen" cc: Seigo Tanimura cc: current@freebsd.org Subject: Re: [PATCH] sound(4) related manpages 5.3 TODO item X-BeenThere: freebsd-multimedia@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Multimedia discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Aug 2004 15:28:52 -0000 On Sun, 29 Aug 2004 23:59:42 +0300, Ruslan Ermilov wrote: > I wish there would be more consistency in naming. Previously, > we had the csa(4) manpage, "device csa", and /dev/csa* entries. > Now we will have the snd_csa(4) manpage, "device snd_csa", but > still /dev/csaX entry. > > Also, in the old world, "midi" devices were created as children > of "pcm" devices, so "hint.pcm.0" hints for non-PnP ISA devices > looked correct. In new world with your updated midi(4), what > will be the hints for the ISA device that implements PCM and > MIDI? hint.pcm.0 and hint.midi.0? the intention behind the renaming was to simplify the naming scheme, and to glue pcm and midi together such that card drivers didn't have to separate out their pcm, midi and independant code. if you look at any of the current card drivers, you'll find that they make several calls into the pcm code. those supporting midi, likewise, call into midi code. having midi and pcm as seperate devices gives the impression that they're independant, but if we allowed that to be the case the drivers would have to become far more complex. ie, they each would require a separate module for their pcm, midi and general parts because if say, only midi was compiled into the kernel then the pcm code in the drivers would fail to link. likewise, drivers supporting midi would fail to link if only pcm was present. for modules, this problem can be solved with dependancies, but the only solution for a static kernel would be to declare that if you wish to compile a driver that supports pac and midi, both device pcm and device midi must be specified. rather than leave the situation that way, we elected to combine the pcm and midi devices into one, so the card drivers could assume both were present. renaming the card modules is a different story, and although i was in favour of it, i now feel it wasn't such a good idea in its current form. because pcm is just a framework rather than an actual device from the kernel's point of view, the driver name would show up in dmesg etc as snd_emu10k1 or whatever. while that in itself wouldn't cause a problem, it would result in each driver using a different devclass - and there are some fairly fundamental assumptions in the pcm code that is designed around being able to translate a unit number to a device_t. if the drivers were changed to register as snd_* rather than pcm, but remain sharing their devclass, there would be interesting results: either all sound devices would show up with the name of the one that attached first (eg an ich and emu10k1 as snd_ich0 and snd_ich1) or the unit numbers would be shared across devices (eg, snd_ich0, snd_maestro1, snd_cmi2...) both of those possible outcomes would be worse than the current situation, in my opinion. what we can - and should - do is rename the "pcm" devclass to "sound". this would make sound devices show up as sound0 etc, and make the hints/sysctls be hw.sound0.*. we also need to make sure that the sound.ko module contains both pcm and midi. it might be nice to have a meta device called sound_all which pulled in all the drivers plus the pcm and midi code, and a corresponding kld. i wonder if we still have the opportunity to rename snd* to sound*? or possibly sound to snd which would mesh better with /dev/sndstat. > ;) All is so plain in the old good 4.x world: heh. -cg From owner-freebsd-multimedia@FreeBSD.ORG Mon Aug 30 23:49:48 2004 Return-Path: Delivered-To: freebsd-multimedia@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2DE1416A4CE for ; Mon, 30 Aug 2004 23:49:48 +0000 (GMT) Received: from sccrmhc13.comcast.net (sccrmhc13.comcast.net [204.127.202.64]) by mx1.FreeBSD.org (Postfix) with ESMTP id CE73143D48 for ; Mon, 30 Aug 2004 23:49:47 +0000 (GMT) (envelope-from fdiprete@comcast.net) Received: from thurston.houselan.com (h00608c0009cb.ne.client2.attbi.com[24.128.129.105]) by comcast.net (sccrmhc13) with ESMTP id <2004083023494701600i407ae> (Authid: ); Mon, 30 Aug 2004 23:49:47 +0000 Date: Mon, 30 Aug 2004 19:49:21 -0400 From: Frank DiPrete To: normal1@gmail.com Message-ID: <20040830234921.GA940@thurston.houselan.com> Mime-Version: 1.0 Content-Type: text/plain; Format=Flowed; DelSp=Yes; charset=ISO-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit X-Mailer: Balsa 2.0.15 Lines: 11 cc: freebsd-multimedia@freebsd.org Subject: wintv card X-BeenThere: freebsd-multimedia@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Multimedia discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Aug 2004 23:49:48 -0000 http://news.gw.com/freebsd.multimedia/4953 I found your july post while searching on another problem. I fixed the no sound problem (play and record) by using the audio patch cable from line out (tv) to line in (sound card) then setting the mixer to not mute and up the levels on LINE and then fixed the recording issue by upping the levels on REC. Yep - turned out it was a mixer issue. Regards From owner-freebsd-multimedia@FreeBSD.ORG Tue Aug 31 13:36:57 2004 Return-Path: Delivered-To: freebsd-multimedia@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 55CE316A4CE; Tue, 31 Aug 2004 13:36:57 +0000 (GMT) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0BDF543D6E; Tue, 31 Aug 2004 13:36:56 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from heffalump.ip.net.ua (heffalump.ip.net.ua [82.193.96.213]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id i7VDaoTx093256 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 31 Aug 2004 16:36:51 +0300 (EEST) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.1/8.13.1) id i7VDat7N033180; Tue, 31 Aug 2004 16:36:55 +0300 (EEST) (envelope-from ru) Date: Tue, 31 Aug 2004 16:36:54 +0300 From: Ruslan Ermilov To: cg Message-ID: <20040831133654.GF31981@ip.net.ua> References: <20040828142503.GA52613@ip.net.ua> <20040829190833.GA9796@cnd.mcgill.ca> <20040829205942.GC39813@ip.net.ua> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="k3qmt+ucFURmlhDS" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new cc: Seigo Tanimura cc: Cameron Grant cc: "Simon L. Nielsen" cc: multimedia@FreeBSD.org cc: Mathew Kanner cc: current@FreeBSD.org Subject: Re: [PATCH] sound(4) related manpages 5.3 TODO item X-BeenThere: freebsd-multimedia@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Multimedia discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Aug 2004 13:36:57 -0000 --k3qmt+ucFURmlhDS Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable [ Please keep me Cc:ed when replying ] On Mon, Aug 30, 2004 at 04:28:52PM +0100, cg wrote: > On Sun, 29 Aug 2004 23:59:42 +0300, Ruslan Ermilov wrote: >=20 > >I wish there would be more consistency in naming. Previously, > >we had the csa(4) manpage, "device csa", and /dev/csa* entries. > >Now we will have the snd_csa(4) manpage, "device snd_csa", but > >still /dev/csaX entry. > > > >Also, in the old world, "midi" devices were created as children > >of "pcm" devices, so "hint.pcm.0" hints for non-PnP ISA devices > >looked correct. In new world with your updated midi(4), what > >will be the hints for the ISA device that implements PCM and > >MIDI? hint.pcm.0 and hint.midi.0? >=20 > the intention behind the renaming was to simplify the naming scheme, and = =20 > to glue pcm and midi together such that card drivers didn't have to =20 > separate out their pcm, midi and independant code. >=20 > if you look at any of the current card drivers, you'll find that they mak= e =20 > several calls into the pcm code. those supporting midi, likewise, call = =20 > into midi code. having midi and pcm as seperate devices gives the =20 > impression that they're independant, but if we allowed that to be the cas= e =20 > the drivers would have to become far more complex. ie, they each would = =20 > require a separate module for their pcm, midi and general parts because i= f =20 > say, only midi was compiled into the kernel then the pcm code in the =20 > drivers would fail to link. likewise, drivers supporting midi would fail= =20 > to link if only pcm was present. >=20 > for modules, this problem can be solved with dependancies, but the only = =20 > solution for a static kernel would be to declare that if you wish to =20 > compile a driver that supports pac and midi, both device pcm and device = =20 > midi must be specified. >=20 > rather than leave the situation that way, we elected to combine the pcm = =20 > and midi devices into one, so the card drivers could assume both were =20 > present. >=20 > renaming the card modules is a different story, and although i was in =20 > favour of it, i now feel it wasn't such a good idea in its current form. = =20 > because pcm is just a framework rather than an actual device from the =20 > kernel's point of view, the driver name would show up in dmesg etc as =20 > snd_emu10k1 or whatever. while that in itself wouldn't cause a problem, = =20 > it would result in each driver using a different devclass - and there are= =20 > some fairly fundamental assumptions in the pcm code that is designed =20 > around being able to translate a unit number to a device_t. >=20 > if the drivers were changed to register as snd_* rather than pcm, but =20 > remain sharing their devclass, there would be interesting results: either= =20 > all sound devices would show up with the name of the one that attached = =20 > first (eg an ich and emu10k1 as snd_ich0 and snd_ich1) or the unit number= s =20 > would be shared across devices (eg, snd_ich0, snd_maestro1, snd_cmi2...) >=20 > both of those possible outcomes would be worse than the current situation= , =20 > in my opinion. >=20 > what we can - and should - do is rename the "pcm" devclass to "sound". = =20 > this would make sound devices show up as sound0 etc, and make the =20 > hints/sysctls be hw.sound0.*. we also need to make sure that the sound.k= o =20 > module contains both pcm and midi. >=20 I agree that renaming the "pcm" devclass to "snd" or "sound" is a good idea, and I like the "snd" more for a couple of reasons (please see below). Let me now check if I got you right. Assuming it will be renamed to "snd", what about the /dev entries, will they be still /dev/pcm{unit}, /dev/mixer{unit}, and /dev/midi{unit}? If, for example, I have two sound cards installed, first without MIDI, and second with MIDI, what will I have in /dev? pcm0, mixer0, *no* midi0, pcm1, mixer1, and midi1? And these devices ("pcm", "mixer", and "midi") will be all children of the "snd" device. And for the ISA sound card with MIDI support, the following device hints and corresponding /dev entries? hint.snd.0.at=3D"isa" hint.snd.0.irq=3D"5" hint.snd.0.drq=3D"1" hint.snd.0.flags=3D"0x0" /dev/pcm0 /dev/mixer0 /dev/midi0 > it might be nice to have a meta device called sound_all which pulled in = =20 > all the drivers plus the pcm and midi code, and a corresponding kld. >=20 The snd_driver.ko module already provides this feature. Should we need such a "config(8) device" is another question. I don't personally see a fit in it -- the GENERIC kernel can already have all snd_* devices and the generic "snd" device. > i wonder if we still have the opportunity to rename snd* to sound*? or = =20 > possibly sound to snd which would mesh better with /dev/sndstat. >=20 Yes, please, the latter. ;) So, to summarize, I'd have liked to see the following happen: - "snd" is the generic sound device (module snd.ko) - "snd_foo" is the sound driver for foo (module snd_foo.ko) - "pcm" devclass renamed to "snd" - "pcm", "mixer", and "midi" devices are created as children of "snd" - ISA device hints become snd..{at,irq,drq,flags,...} - the hw.snd. sysctl tree stays unmodified, including the following convention: PCM-related sysctls will have the hw.snd.pcm prefix, and MIDI-related sysctls (should there be any) will have the hw.snd.midi prefix. And one final question: if the plan is as described here, it probably makes sense to do it now, before 5.3, or postpone the "manpage and handbook" sound related TODO items until it's actually done and merged into RELENG_5. I'd like to avoid repo-copying the pcm(4) manpage to sound(4) now, only to repo-copy it later to snd(4). If this doesn't happen in time for 5.3, I suggest the following emergency plan for now: - repo-copy (and tweak as necessary) all bridge drivers manpages, as shown in my patch; - do *not* repo-copy pcm(4) to sound(4) yet, just link it, possibly mentioning in the manpage that the generic driver will soon be renamed from "sound" to "snd", - fix hints in NOTES (as in my patch) to match reality. When "sound" -> "snd" conversion is actually done, repo-copy pcm(4) to sound(4), tweak as necessary, documenting what the "sound" device really is, mentioning "pcm", "mixer", and "midi" sub-devices, link sound(4) to pcm(4), mixer(4), and midi(4). Please let me know how to proceed... Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --k3qmt+ucFURmlhDS Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (FreeBSD) iD8DBQFBNH72qRfpzJluFF4RAqu0AJ4oyJ18J59CS5x9aXP4VZSOBe/p2wCePTMl ZJv5LomHgJ0dVtITkt/YIWo= =ZMN9 -----END PGP SIGNATURE----- --k3qmt+ucFURmlhDS-- From owner-freebsd-multimedia@FreeBSD.ORG Tue Aug 31 18:49:33 2004 Return-Path: Delivered-To: freebsd-multimedia@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 87FE116A4CE for ; Tue, 31 Aug 2004 18:49:33 +0000 (GMT) Received: from redtick.homeunix.com (adsl-67-67-15-5.dsl.okcyok.swbell.net [67.67.15.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2410243D45 for ; Tue, 31 Aug 2004 18:49:33 +0000 (GMT) (envelope-from boxend@redtick.homeunix.com) Received: from redtick.homeunix.com (localhost.homeunix.com [127.0.0.1]) i7VInWTW037699 for ; Tue, 31 Aug 2004 13:49:32 -0500 (CDT) (envelope-from boxend@redtick.homeunix.com) Received: (from boxend@localhost) by redtick.homeunix.com (8.12.10/8.12.10/Submit) id i7VInVBi037698 for freebsd-multimedia@freebsd.org; Tue, 31 Aug 2004 13:49:32 -0500 (CDT) (envelope-from boxend) Date: Tue, 31 Aug 2004 13:49:32 -0500 (CDT) From: Mark Message-Id: <200408311849.i7VInVBi037698@redtick.homeunix.com> To: freebsd-multimedia@freebsd.org Subject: launchcast X-BeenThere: freebsd-multimedia@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Multimedia discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Aug 2004 18:49:33 -0000 Has anyone been able to get launchcast to work on a freebsd or linux emmulator?? I've googled around and not found anything to help, other than it based on windowsmedia and active x. The Active x part being the main blocking point. Looking for a commandline solution to install on a jukebox setup. Thanks in Advance. From owner-freebsd-multimedia@FreeBSD.ORG Tue Aug 31 19:44:16 2004 Return-Path: Delivered-To: freebsd-multimedia@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5B1C416A4CE for ; Tue, 31 Aug 2004 19:44:16 +0000 (GMT) Received: from redtick.homeunix.com (adsl-67-67-15-5.dsl.okcyok.swbell.net [67.67.15.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id DB69043D46 for ; Tue, 31 Aug 2004 19:44:15 +0000 (GMT) (envelope-from boxend@redtick.homeunix.com) Received: from redtick.homeunix.com (localhost.homeunix.com [127.0.0.1]) i7VJiFTW037896 for ; Tue, 31 Aug 2004 14:44:15 -0500 (CDT) (envelope-from boxend@redtick.homeunix.com) Received: (from boxend@localhost) by redtick.homeunix.com (8.12.10/8.12.10/Submit) id i7VJiEck037895 for freebsd-multimedia@freebsd.org; Tue, 31 Aug 2004 14:44:14 -0500 (CDT) (envelope-from boxend) Date: Tue, 31 Aug 2004 14:44:14 -0500 (CDT) From: Mark Message-Id: <200408311944.i7VJiEck037895@redtick.homeunix.com> To: freebsd-multimedia@freebsd.org Subject: re:launchcast X-BeenThere: freebsd-multimedia@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Multimedia discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Aug 2004 19:44:16 -0000 more info on my own request: found this perl script on hacks.oreilly.com, but no joy #!/usr/bin/perl # Written by badfugu - October 2003 # I do claim some ownership, but please distribute freely. require LWP::UserAgent; require HTTP::Request; require HTTP::Response; # Get video ID from input my $vid_id = $ARGV[0]; print "Video ID: $vid_id\n"; ($vid_id <= 0) and die "Invalid video ID!\n"; # Build the first URL my $pri_url_head = "http://launchtoday.launch.yahoo.com/player/showasx.asp?cid=1&pid=4&csid=396500550&sx=g%2F4.xml&sgm=1&vid="; my $pri_url_tail = "&bw=300&pv=6&bp=Windows%209x&uid=1486187332&uguid=8bodoh10e6o4n&im=0&pls=&asp=&fcv=&z=y.asx"; my $pri_url = $pri_url_head . $vid_id . $pri_url_tail; # Attempt to fetch the playlist (asx) from that URL print "Attempting to fetch from showasx.asp...\n"; my %options = ( agent => 'Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)' ); my $ua = LWP::UserAgent->new( %options ); my $request = new HTTP::Request 'GET', $pri_url; my $response = $ua->request($request); if (!($response->is_success)) { die "Could not fetch!\n"; } # Extract second url from response my $sec_url = ""; if ($response->content =~ /(http:.+medialog.+$vid_id.+asx)/) { $sec_url = "$1"; } else { die "Could not extract medialog.asp url!\n"; } # Attempt to fetch the next playlist from the secondary URL print "Attempting to fetch from medialog.asp...\n"; my $mkpl_url = ""; $request->url($sec_url); $response = $ua->request($request); if (!($response->is_success)) { die "Could not fetch!\n"; } else { $mkpl_url = $response->content; } # Attempt to fetch the media stream URL print "Attempting to fetch from makeplaylist.dll...\n"; $request->url($mkpl_url); $response = $ua->request($request); if (!($response->is_success)) { die "Could not fetch!\n"; } else { $mms_url = $response->content; } # Play that stream!!! system("mplayer -bandwidth 99999999 $mms_url"); # eof ########################################################### This being the error msg : Can't locate LWP/UserAgent.pm in @INC (@INC contains: /usr/local/lib/perl5/site_perl/5.8.4/mach /usr/local/lib/perl5/site_perl/5.8.4 /usr/local/lib/perl5/site_perl /usr/local/lib/perl5/5.8.4/BSDPAN /usr/local/lib/perl5/5.8.4/mach /usr/local/lib/perl5/5.8.4 .) at ./launch.pl line 5. Are PAN mods not loaded with the perl5.8? or is this something diff?? From owner-freebsd-multimedia@FreeBSD.ORG Wed Sep 1 09:08:22 2004 Return-Path: Delivered-To: freebsd-multimedia@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7D2A016A4CE for ; Wed, 1 Sep 2004 09:08:22 +0000 (GMT) Received: from kayjay.xs4all.nl (kayjay.xs4all.nl [80.126.33.60]) by mx1.FreeBSD.org (Postfix) with ESMTP id CBE9143D45 for ; Wed, 1 Sep 2004 09:08:21 +0000 (GMT) (envelope-from karelj@kayjay.xs4all.nl) Received: from kayjay.xs4all.nl (localhost.kayjay.xs4all.nl [127.0.0.1]) by kayjay.xs4all.nl (8.12.11/8.12.11) with ESMTP id i8198Dhg029076 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO); Wed, 1 Sep 2004 11:08:14 +0200 (CEST) (envelope-from karelj@kayjay.xs4all.nl) Received: (from karelj@localhost) by kayjay.xs4all.nl (8.12.11/8.12.11/Submit) id i8198Du6029075; Wed, 1 Sep 2004 11:08:13 +0200 (CEST) (envelope-from karelj) Date: Wed, 1 Sep 2004 11:08:09 +0200 From: "Karel J. Bosschaart" To: Mark Message-ID: <20040901090809.GA29057@kayjay.xs4all.nl> References: <200408311944.i7VJiEck037895@redtick.homeunix.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200408311944.i7VJiEck037895@redtick.homeunix.com> User-Agent: Mutt/1.4.2.1i cc: freebsd-multimedia@freebsd.org Subject: Re: launchcast X-BeenThere: freebsd-multimedia@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Multimedia discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Sep 2004 09:08:22 -0000 On Tue, Aug 31, 2004 at 02:44:14PM -0500, Mark wrote: > more info on my own request: > > found this perl script on hacks.oreilly.com, but no joy A while back I used this script successfully on FreeBSD. > This being the error msg : > Can't locate LWP/UserAgent.pm in @INC (@INC contains: /usr/local/lib/perl5/site_perl/5.8.4/mach /usr/local/lib/perl5/site_perl/5.8.4 /usr/local/lib/perl5/site_perl /usr/local/lib/perl5/5.8.4/BSDPAN /usr/local/lib/perl5/5.8.4/mach /usr/local/lib/perl5/5.8.4 .) at ./launch.pl line 5. > > Are PAN mods not loaded with the perl5.8? or is this something diff?? You need to install the devel/p5-POE-Component-Client-UserAgent-0.05 port. It will install quite a bunch of p5- dependencies... However, trying the script now gives me a 'Could not extract medialog.asp url!'. I guess the launch site has changed and the script needs to be adapted accordingly. Karel. From owner-freebsd-multimedia@FreeBSD.ORG Wed Sep 1 13:22:31 2004 Return-Path: Delivered-To: freebsd-multimedia@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C4C7316A4CF for ; Wed, 1 Sep 2004 13:22:31 +0000 (GMT) Received: from redtick.homeunix.com (adsl-67-65-250-14.dsl.okcyok.swbell.net [67.65.250.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 714D543D54 for ; Wed, 1 Sep 2004 13:22:31 +0000 (GMT) (envelope-from boxend@redtick.homeunix.com) Received: from redtick.homeunix.com (localhost.homeunix.com [127.0.0.1]) i81DMTTW041008; Wed, 1 Sep 2004 08:22:30 -0500 (CDT) (envelope-from boxend@redtick.homeunix.com) Received: (from boxend@localhost) by redtick.homeunix.com (8.12.10/8.12.10/Submit) id i81DMTVC041007; Wed, 1 Sep 2004 08:22:29 -0500 (CDT) (envelope-from boxend) Date: Wed, 1 Sep 2004 08:22:29 -0500 From: Mark To: "Karel J. Bosschaart" Message-ID: <20040901132229.GA40978@redtick.homeunix.com> References: <200408311944.i7VJiEck037895@redtick.homeunix.com> <20040901090809.GA29057@kayjay.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040901090809.GA29057@kayjay.xs4all.nl> User-Agent: Mutt/1.4.2.1i cc: freebsd-multimedia@freebsd.org Subject: Re: launchcast X-BeenThere: freebsd-multimedia@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Multimedia discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Sep 2004 13:22:31 -0000 On Wed, Sep 01, 2004 at 11:08:09AM +0200, Karel J. Bosschaart wrote: > On Tue, Aug 31, 2004 at 02:44:14PM -0500, Mark wrote: > > more info on my own request: > > > > found this perl script on hacks.oreilly.com, but no joy > > A while back I used this script successfully on FreeBSD. > > > > This being the error msg : > > Can't locate LWP/UserAgent.pm in @INC (@INC contains: /usr/local/lib/perl5/site_perl/5.8.4/mach /usr/local/lib/perl5/site_perl/5.8.4 /usr/local/lib/perl5/site_perl /usr/local/lib/perl5/5.8.4/BSDPAN /usr/local/lib/perl5/5.8.4/mach /usr/local/lib/perl5/5.8.4 .) at ./launch.pl line 5. > > > > Are PAN mods not loaded with the perl5.8? or is this something diff?? > > You need to install the devel/p5-POE-Component-Client-UserAgent-0.05 port. > It will install quite a bunch of p5- dependencies... > > However, trying the script now gives me a > 'Could not extract medialog.asp url!'. I guess the launch site has changed > and the script needs to be adapted accordingly. > > Karel. Thanks for the point in the right direction. -- ============================================================================== The information contained in this communication is confidential, private, proprietary, or otherwise privileged and is intended only for the use of the addressee. Unauthorized use, disclosure, distribution or copying is strictly prohibited and may be unlawful. If you have received this communication in error, please notify the sender immediately. ============================================================================== From owner-freebsd-multimedia@FreeBSD.ORG Wed Sep 1 17:32:44 2004 Return-Path: Delivered-To: freebsd-multimedia@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1079F16A4CF for ; Wed, 1 Sep 2004 17:32:44 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0108543D2F for ; Wed, 1 Sep 2004 17:32:44 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id E7F5F72DD4; Wed, 1 Sep 2004 10:32:43 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id E211072DCB for ; Wed, 1 Sep 2004 10:32:43 -0700 (PDT) Date: Wed, 1 Sep 2004 10:32:43 -0700 (PDT) From: Doug White To: multimedia@freebsd.org Message-ID: <20040901102931.A6696@carver.gumbysoft.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: RELENG_5 build broken with BKTR_USE_FREEBSD_SMBUS and BKTR_NEW_MSP34XX_DRIVER enabled (fwd) X-BeenThere: freebsd-multimedia@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Multimedia discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Sep 2004 17:32:44 -0000 Hey folks, Here's a patch I whipped up to fix compiling the kernel with the options noted in the subject. I think this guy is the first one to actually try both options at once :) I'm told it works on the right hardware, which I don't have -- my ancient WinTV doesn't have the msp. http://people.freebsd.org/~dwhite/msp34xx.c.patch I can commit this if desired. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org ---------- Forwarded message ---------- Date: Sun, 29 Aug 2004 16:01:41 -0700 (PDT) From: Doug White To: Damian Gerow Cc: current@freebsd.org Subject: Re: RELENG_5 build broken with BKTR_USE_FREEBSD_SMBUS and BKTR_NEW_MSP34XX_DRIVER enabled On Tue, 24 Aug 2004, Damian Gerow wrote: > In trying to build a kernel with bktr support, I'm using both > BKTR_USE_FREEBSD_SMBUS and BKTR_NEW_MSP34XX_DRIVER. This is what I see on a > compile: > > cc -c -O -pipe -march=pentium4 -Wall -Wredundant-decls -Wnested-externs \ > -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline \ > -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. \ > -I/usr/src/sys -I/usr/src/sys/contrib/dev/acpica \ > -I/usr/src/sys/contrib/altq -I/usr/src/sys/contrib/ipfilter \ > -I/usr/src/sys/contrib/pf -I/usr/src/sys/contrib/dev/ath \ > -I/usr/src/sys/contrib/dev/ath/freebsd \ > -I/usr/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h \ > -fno-common -finline-limit=8000 --param inline-unit-growth=100 \ > --param large-function-growth=1000 -mno-align-long-strings \ > -mpreferred-stack-boundary=2 -ffreestanding -Werror \ > /usr/src/sys/dev/bktr/msp34xx.c > In file included from /usr/src/sys/dev/bktr/msp34xx.c:92: > /usr/src/sys/dev/bktr/bktr_reg.h:451: error: syntax error before "device_t" > *** Error code 1 Please try the patch at: http://people.freebsd.org/~dwhite/msp34xx.c.patch Seems to test out OK on my ancient Hauppauge WinTV card. These options must not be a frequently used combination since its been months since this stuff was touched last. There was a PR that fixed a compile bug in one file related to the smbus option but must not have been tested with the msp stuff too. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org From owner-freebsd-multimedia@FreeBSD.ORG Wed Sep 1 19:16:27 2004 Return-Path: Delivered-To: freebsd-multimedia@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B258716A4CE; Wed, 1 Sep 2004 19:16:27 +0000 (GMT) Received: from rt0-ext.kdcg.net (rt0-ext.kdcg.net [81.2.114.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id C631343D54; Wed, 1 Sep 2004 19:16:26 +0000 (GMT) (envelope-from cg@ijcg.net) Received: from localhost (localhost [127.0.0.1]) by rt0-ext.kdcg.net (Postfix) with ESMTP id CDC5F4AB9027; Wed, 1 Sep 2004 20:19:09 +0100 (BST) Received: from rt0-ext.kdcg.net ([127.0.0.1]) by localhost (alexandria.rings [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 57477-01-3; Wed, 1 Sep 2004 20:19:09 +0100 (BST) Received: from tacitblue3.rings (tacitblue.rings [10.1.0.2]) by rt0-ext.kdcg.net (Postfix) with ESMTP id B6F5D4AB9025; Wed, 1 Sep 2004 20:19:08 +0100 (BST) Date: Wed, 01 Sep 2004 20:16:33 +0100 From: cg To: "Ruslan Ermilov" References: <20040828142503.GA52613@ip.net.ua> <20040829190833.GA9796@cnd.mcgill.ca> <20040829205942.GC39813@ip.net.ua> <20040831133654.GF31981@ip.net.ua> Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-15 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-ID: In-Reply-To: <20040831133654.GF31981@ip.net.ua> User-Agent: Opera M2/7.54 (Win32, build 3869) X-Virus-Scanned: by amavisd-new at badexample.com cc: Seigo Tanimura cc: Cameron Grant cc: "Simon L. Nielsen" cc: multimedia@freebsd.org cc: Mathew Kanner cc: current@freebsd.org Subject: Re: [PATCH] sound(4) related manpages 5.3 TODO item X-BeenThere: freebsd-multimedia@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Multimedia discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Sep 2004 19:16:28 -0000 > I agree that renaming the "pcm" devclass to "snd" or "sound" is a good > idea, and I like the "snd" more for a couple of reasons (please see > below). Let me now check if I got you right. Assuming it will be > renamed to "snd", what about the /dev entries, will they be still > /dev/pcm{unit}, /dev/mixer{unit}, and /dev/midi{unit}? If, for example, > I have two sound cards installed, first without MIDI, and second with > MIDI, what will I have in /dev? pcm0, mixer0, *no* midi0, pcm1, mixer1, > and midi1? And these devices ("pcm", "mixer", and "midi") will be all > children of the "snd" device. And for the ISA sound card with MIDI > support, the following device hints and corresponding /dev entries? the /dev entries are /dev/dsp* and /dev/audio*, /dev/sndstat, /dev/mixer*, plus the midi ones: /dev/midi* and /dev/sequencer. all of these names are mandated by the oss spec. i'm not sure about midi device numbering; i believe some cards can implement multiple midi devices, eg an fm synth, io port and a wavetable synth simultaneously. pcm won't be a separate device as such; it won't appear in dmesg. this probably applies to midi too. > So, to summarize, I'd have liked to see the following happen: > > - "snd" is the generic sound device (module snd.ko) > - "snd_foo" is the sound driver for foo (module snd_foo.ko) > - "pcm" devclass renamed to "snd" > - "pcm", "mixer", and "midi" devices are created as children of "snd" no. pcm and midi will effectively be part of snd. making them separate newbus drivers would be tricky and require every driver to be modified. > - ISA device hints become snd..{at,irq,drq,flags,...} > - the hw.snd. sysctl tree stays unmodified, including the following > convention: PCM-related sysctls will have the hw.snd.pcm > prefix, and MIDI-related sysctls (should there be any) will have the > hw.snd.midi prefix. > > And one final question: if the plan is as described here, it probably > makes sense to do it now, before 5.3, or postpone the "manpage and > handbook" sound related TODO items until it's actually done and merged > into RELENG_5. I'd like to avoid repo-copying the pcm(4) manpage to > sound(4) now, only to repo-copy it later to snd(4). If this doesn't > happen in time for 5.3, I suggest the following emergency plan for > now: > > - repo-copy (and tweak as necessary) all bridge drivers manpages, > as shown in my patch; > > - do *not* repo-copy pcm(4) to sound(4) yet, just link it, possibly > mentioning in the manpage that the generic driver will soon be > renamed from "sound" to "snd", > > - fix hints in NOTES (as in my patch) to match reality. this sounds ok to me. > When "sound" -> "snd" conversion is actually done, repo-copy > pcm(4) to sound(4), tweak as necessary, documenting what the > "sound" device really is, mentioning "pcm", "mixer", and "midi" > sub-devices, link sound(4) to pcm(4), mixer(4), and midi(4). > > Please let me know how to proceed... i don't think i can cope with the pressure of getting it into 5.3, so it'd be better to postpone it until 5.4 i think. -cg From owner-freebsd-multimedia@FreeBSD.ORG Wed Sep 1 20:24:39 2004 Return-Path: Delivered-To: freebsd-multimedia@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B14ED16A4CE; Wed, 1 Sep 2004 20:24:39 +0000 (GMT) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 74B9443D53; Wed, 1 Sep 2004 20:24:38 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from heffalump.ip.net.ua (heffalump.ip.net.ua [82.193.96.213]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id i81KOWPK040215 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 1 Sep 2004 23:24:33 +0300 (EEST) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.1/8.13.1) id i81KOWvs000535; Wed, 1 Sep 2004 23:24:32 +0300 (EEST) (envelope-from ru) Date: Wed, 1 Sep 2004 23:24:32 +0300 From: Ruslan Ermilov To: cg Message-ID: <20040901202432.GB416@ip.net.ua> References: <20040828142503.GA52613@ip.net.ua> <20040829190833.GA9796@cnd.mcgill.ca> <20040829205942.GC39813@ip.net.ua> <20040831133654.GF31981@ip.net.ua> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="L6iaP+gRLNZHKoI4" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new cc: Seigo Tanimura cc: Cameron Grant cc: "Simon L. Nielsen" cc: multimedia@freebsd.org cc: Mathew Kanner cc: current@freebsd.org Subject: Re: [PATCH] sound(4) related manpages 5.3 TODO item X-BeenThere: freebsd-multimedia@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Multimedia discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Sep 2004 20:24:39 -0000 --L6iaP+gRLNZHKoI4 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Sep 01, 2004 at 08:16:33PM +0100, cg wrote: [...] > the /dev entries are /dev/dsp* and /dev/audio*, /dev/sndstat, /dev/mixer*= , =20 > plus the midi ones: /dev/midi* and /dev/sequencer. all of these names ar= e =20 > mandated by the oss spec. >=20 Oh, of course I meant /dev/dsp* when I wrote /dev/pcm*. ;) > i'm not sure about midi device numbering; i believe some cards can =20 > implement multiple midi devices, eg an fm synth, io port and a wavetable = =20 > synth simultaneously. >=20 > pcm won't be a separate device as such; it won't appear in dmesg. this = =20 > probably applies to midi too. >=20 OK. > >So, to summarize, I'd have liked to see the following happen: > > > >- "snd" is the generic sound device (module snd.ko) > >- "snd_foo" is the sound driver for foo (module snd_foo.ko) > >- "pcm" devclass renamed to "snd" > >- "pcm", "mixer", and "midi" devices are created as children of "snd" >=20 > no. pcm and midi will effectively be part of snd. making them separate = =20 > newbus drivers would be tricky and require every driver to be modified. >=20 OK, sounds very good. But what about PCM-related sysctls then? How will hw.snd.pcm0.vchans be represented, for example? hw.snd.0.vchans maybe? > >- repo-copy (and tweak as necessary) all bridge drivers manpages, > > as shown in my patch; > > > >- do *not* repo-copy pcm(4) to sound(4) yet, just link it, possibly > > mentioning in the manpage that the generic driver will soon be > > renamed from "sound" to "snd", > > > >- fix hints in NOTES (as in my patch) to match reality. >=20 > this sounds ok to me. >=20 OK, I will it then. > >When "sound" -> "snd" conversion is actually done, repo-copy > >pcm(4) to sound(4), tweak as necessary, documenting what the > >"sound" device really is, mentioning "pcm", "mixer", and "midi" > >sub-devices, link sound(4) to pcm(4), mixer(4), and midi(4). > > > >Please let me know how to proceed... >=20 > i don't think i can cope with the pressure of getting it into 5.3, so it'= d =20 > be better to postpone it until 5.4 i think. >=20 Sure, that's fine. ;) Can you please send me some plain text paragraph for the pcm(4) manpage that will be linked to the sound(4) manpage, documenting future plans like renaming "sound" to "snd", so people stay tuned? Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --L6iaP+gRLNZHKoI4 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (FreeBSD) iD8DBQFBNjAAqRfpzJluFF4RAonZAJwLgPFwLuUVr8NKDNdmbRqij/fDdgCgk7Sj 2O3Po8WlV2Aj45TPXMO67aE= =YKeJ -----END PGP SIGNATURE----- --L6iaP+gRLNZHKoI4-- From owner-freebsd-multimedia@FreeBSD.ORG Fri Sep 3 16:12:08 2004 Return-Path: Delivered-To: freebsd-multimedia@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 51BE016A4CE for ; Fri, 3 Sep 2004 16:12:08 +0000 (GMT) Received: from mail.jamesgrace.com (mail.jamesgrace.com [63.171.29.94]) by mx1.FreeBSD.org (Postfix) with SMTP id A875D43D55 for ; Fri, 3 Sep 2004 16:12:07 +0000 (GMT) (envelope-from jamesgrace@mail.jamesgrace.com) Received: from screwtape.tafford.com by mail.jamesgrace.com ESMTP; Fri, 3 Sep 2004 12:12:07 -0400 Received: (qmail 59148 invoked by uid 1001); 3 Sep 2004 16:12:06 -0000 Date: Fri, 3 Sep 2004 12:12:06 -0400 From: "James N. Grace" To: freebsd-multimedia@freebsd.org Message-ID: <20040903161206.GD55663@jamesgrace.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i cc: freebsd-mobile@freebsd.org Subject: ESS 1788 not working on my Compaq Presario 1080 notebook... X-BeenThere: freebsd-multimedia@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Multimedia discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Sep 2004 16:12:08 -0000 My kernel config is as follows: device pcm device sbc0 at isa? port 0x220 irq 5 drq 1 flags 0x15 "more /var/run/dmesg.boot" produces the following related output: sbc0: at port 0x220-0x22f irq 5 drq 1 flags 0x15 on isa0 pcm0: on sbc0 "cat /dev/sndstat" produces the following output: pcm0: at io 0x220 irq 5 drq 1:5 bufsz 4096 (1p/1r/0v channels duplex) "cat 11khz_test.au > /dev/dsp" produces almost recognizable sound. "cat 16khz_test.au > /dev/dsp" recognizable. "cat 22khz_test.au > /dev/dsp" fast, unrecognizable. Using "mpg123" to play an MP3 file produces no sound at all and produces the following error: pcm0:play:0: play interrupt timeout, channel dead Using "mpg123 --8bit" to play an MP3 file produces strange, garbled sound and produces the following error: pcm0:play:0: play interrupt timeout, channel dead Music CDs play fine and the "mixer" application seems to work properly. Any ideas? From owner-freebsd-multimedia@FreeBSD.ORG Fri Sep 3 19:29:15 2004 Return-Path: Delivered-To: freebsd-multimedia@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3D52016A4CF for ; Fri, 3 Sep 2004 19:29:15 +0000 (GMT) Received: from mail.jamesgrace.com (mail.jamesgrace.com [63.171.29.94]) by mx1.FreeBSD.org (Postfix) with SMTP id A0E2243D1F for ; Fri, 3 Sep 2004 19:29:14 +0000 (GMT) (envelope-from jamesgrace@mail.jamesgrace.com) Received: from screwtape.tafford.com by mail.jamesgrace.com ESMTP; Fri, 3 Sep 2004 15:29:14 -0400 Received: (qmail 63571 invoked by uid 1001); 3 Sep 2004 19:29:14 -0000 Date: Fri, 3 Sep 2004 15:29:14 -0400 From: "James N. Grace" To: freebsd-multimedia@freebsd.org Message-ID: <20040903192914.GG55663@jamesgrace.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i cc: freebsd-mobile@freebsd.org Subject: [ RELEASE 4.10 ] - ESS 1788 not working on my Compaq Presario 1080 notebook... X-BeenThere: freebsd-multimedia@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Multimedia discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Sep 2004 19:29:15 -0000 My kernel config is as follows: device pcm device sbc0 at isa? port 0x220 irq 5 drq 1 flags 0x15 "more /var/run/dmesg.boot" produces the following related output: sbc0: at port 0x220-0x22f irq 5 drq 1 flags 0x15 on isa0 pcm0: on sbc0 "cat /dev/sndstat" produces the following output: pcm0: at io 0x220 irq 5 drq 1:5 bufsz 4096 (1p/1r/0v channels duplex) "cat 11khz_test.au > /dev/dsp" produces almost recognizable sound. "cat 16khz_test.au > /dev/dsp" recognizable. "cat 22khz_test.au > /dev/dsp" fast, unrecognizable. Using "mpg123" to play an MP3 file produces no sound at all and produces the following error: pcm0:play:0: play interrupt timeout, channel dead Using "mpg123 --8bit" to play an MP3 file produces strange, garbled sound and produces the following error: pcm0:play:0: play interrupt timeout, channel dead Music CDs play fine and the "mixer" application seems to work properly. Any ideas? From owner-freebsd-multimedia@FreeBSD.ORG Sat Sep 4 15:40:42 2004 Return-Path: Delivered-To: freebsd-multimedia@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2E4E216A5AC for ; Sat, 4 Sep 2004 15:40:42 +0000 (GMT) Received: from mail.tinkerbox.org (adsl-64-168-139-138.dsl.snfc21.pacbell.net [64.168.139.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 32F7643D5E for ; Sat, 4 Sep 2004 15:40:27 +0000 (GMT) (envelope-from bruno@tinkerbox.org) Received: from localhost (unknown [127.0.0.1]) by mail.tinkerbox.org (Postfix) with ESMTP id 9F91E18E4 for ; Sat, 4 Sep 2004 15:40:26 +0000 (GMT) Received: from mail.tinkerbox.org ([127.0.0.1]) by localhost (router.bschwand.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 57430-08 for ; Sat, 4 Sep 2004 08:40:16 -0700 (PDT) Received: from duron (duron.bschwand.net [192.168.137.4]) by mail.tinkerbox.org (Postfix) with ESMTP id 4432C18E2 for ; Sat, 4 Sep 2004 08:40:16 -0700 (PDT) Date: Sat, 4 Sep 2004 08:40:16 -0700 (PDT) From: bruno schwander X-X-Sender: bruno@duron.bschwand.net To: freebsd-multimedia@freebsd.org Message-ID: <20040904083524.Q50649@duron.bschwand.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by amavisd-new at tinkerbox.org Subject: gphoto2 , usb X-BeenThere: freebsd-multimedia@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Multimedia discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Sep 2004 15:40:42 -0000 Hi, Has anybody managed to get gphoto2 working with a usb camera attached ? >gphoto2 --list-ports Devices found: 3 Path Description -------------------------------------------------------------- serial:/dev/cuaa0 Serial Port 0 serial:/dev/cuaa1 Serial Port 1 usb: Universal Serial Bus usbdevs shows the camera present. I have the ugen module loaded. I have an epson usb scanner hooked up that works fine, so usb is working on my machine. >gphoto2 --auto-detect Model Port ---------------------------------------------------------- >gphoto2 --port=/dev/ugen0 --list-files *** Error *** Could not detect any camera *** Error (-105: 'Unknown model') *** this is with libusb-0.1.7 Library giving userland programs access to USB devices gphoto2-2.1.4_1 A command-line frontend to libgphoto2 libgphoto2-2.1.4_3 A universal digital camera picture control tool on FreeBSD 4.8-STABLE Any help appreciated... bruno From owner-freebsd-multimedia@FreeBSD.ORG Sat Sep 4 15:43:30 2004 Return-Path: Delivered-To: freebsd-multimedia@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DE09916A4CE for ; Sat, 4 Sep 2004 15:43:30 +0000 (GMT) Received: from mproxy.gmail.com (rproxy.gmail.com [64.233.170.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 89F7A43D41 for ; Sat, 4 Sep 2004 15:43:30 +0000 (GMT) (envelope-from normal1@gmail.com) Received: by mproxy.gmail.com with SMTP id 76so50855rnl for ; Sat, 04 Sep 2004 08:43:28 -0700 (PDT) Received: by 10.38.171.2 with SMTP id t2mr549339rne; Sat, 04 Sep 2004 08:43:28 -0700 (PDT) Received: by 10.38.77.52 with HTTP; Sat, 4 Sep 2004 08:43:28 -0700 (PDT) Message-ID: <7df4e19b0409040843773454ef@mail.gmail.com> Date: Sat, 4 Sep 2004 08:43:28 -0700 From: Eddie Dandrades To: bruno schwander In-Reply-To: <20040904083524.Q50649@duron.bschwand.net> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <20040904083524.Q50649@duron.bschwand.net> cc: freebsd-multimedia@freebsd.org Subject: Re: gphoto2 , usb X-BeenThere: freebsd-multimedia@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Eddie Dandrades List-Id: Multimedia discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Sep 2004 15:43:31 -0000 I have, are you having a problem with it? Have you checked that your camera is supported? On Sat, 4 Sep 2004 08:40:16 -0700 (PDT), bruno schwander wrote: > Hi, > > Has anybody managed to get gphoto2 working with a usb camera attached ? > > >gphoto2 --list-ports > Devices found: 3 > Path Description > -------------------------------------------------------------- > serial:/dev/cuaa0 Serial Port 0 > serial:/dev/cuaa1 Serial Port 1 > usb: Universal Serial Bus > > usbdevs shows the camera present. I have the ugen module loaded. I have an > epson usb scanner hooked up that works fine, so usb is working on my > machine. > > >gphoto2 --auto-detect > Model Port > ---------------------------------------------------------- > > >gphoto2 --port=/dev/ugen0 --list-files > *** Error *** > Could not detect any camera > *** Error (-105: 'Unknown model') *** > > this is with > libusb-0.1.7 Library giving userland programs access to USB devices > gphoto2-2.1.4_1 A command-line frontend to libgphoto2 > libgphoto2-2.1.4_3 A universal digital camera picture control tool > > on FreeBSD 4.8-STABLE > > Any help appreciated... > > bruno > _______________________________________________ > freebsd-multimedia@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-multimedia > To unsubscribe, send any mail to "freebsd-multimedia-unsubscribe@freebsd.org" > -- -gabriel