Date: Sun, 10 Sep 2006 20:09:54 -0500 From: "Z.C.B." <vvelox@vvelox.net> To: FreeBSD Hackers <freebsd-hackers@freebsd.org> Cc: ed@fxq.nl Subject: Re: ugen question Message-ID: <20060910200954.1a4a1e9f@vixen42> In-Reply-To: <20060908044351.GQ22564@hoeg.nl> References: <20060907204716.151d9ab9@vixen42> <20060908044351.GQ22564@hoeg.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_kALkpncL.ul9cPQWvXQKXLf Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Fri, 8 Sep 2006 06:43:51 +0200 Ed Schouten <ed@fxq.nl> wrote: > * Z.C.B. <vvelox@vvelox.net> wrote: > > Any suggestions on reading or the like for talking to a ugen > > device? >=20 > Well, I'm using ugen to test the workings of an Xbox 360 headset. I > just use this: >=20 > $ cat /dev/ugen0.3 > myvoice > ^C > $ cat myvoice > /dev/ugen0.4 >=20 > Gives me back my voice (well, at half the sample rate, as the > microphone is twice as accurate). Cool. It does not work here. I can read to it, but I am not getting any thing. The device generates a ugen0, ugen0.1, and a ugen0.2. I can cat stuff from ugen0.1, but not from the rest. If I read from ugen0 I get a operation not supported with cat. If I read from ugen0.2 I get a device not configured error. For writing with cat I get not supported for ugen0, not configured for ugen0.1, and i/o error for ugen0.2. --Sig_kALkpncL.ul9cPQWvXQKXLf Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFBLdkC1tfcMGJid4RAj7JAJ9ClUbr1t2D+ssd1sW2tdbdXPqipACcCHJM 5UKYLGTnF8okOR7nSB+OfhA= =D/tb -----END PGP SIGNATURE----- --Sig_kALkpncL.ul9cPQWvXQKXLf--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060910200954.1a4a1e9f>