Date: Mon, 18 Dec 2017 17:11:20 +0100 From: Alexander Leidinger <Alexander@leidinger.net> To: freebsd-ports@freebsd.org Subject: Re: OSS Audio Message-ID: <20171218171120.Horde.s5OngVFuRoftIluNHRvGOV6@webmail.leidinger.net> In-Reply-To: <trinity-ea77de16-0e84-44d5-91c2-e14cb14947ca-1513464797281@3c-app-mailcom-lxa15> References: <trinity-591c5f9d-357f-4ae9-88b2-d5d603fb8de4-1513379128533@3c-app-mailcom-lxa04> <CALM2mEmpWmOyrfHku3diWrpeHLd0To3szUrutSsMt0LF=%2BEDFA@mail.gmail.com> <trinity-ea77de16-0e84-44d5-91c2-e14cb14947ca-1513464797281@3c-app-mailcom-lxa15>
next in thread | previous in thread | raw e-mail | index | archive | help
This message is in MIME format and has been PGP signed. --=_g0ARV2vhdwQ-vwyuWy6-4GV Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Quoting Sid <sid@bsdmail.com> (from Sat, 16 Dec 2017 23:53:17 +0100): > I've had a few misconceptions. > > Bluebee Blubeeme said, 4Front has a modern OSS implementation that=20=20 >=20is under a FreeBSD license. > > The model of Sound on FreeBSD is, three layers: > 1. The API, where programs use libraries (of respective sound=20=20 >=20architecture) to access the sound server. > 2. The sound server: OSS, Sndio, Portaudio, JACK, ALSA, native, etc > 3. FreeBSD's base is always OSS (OpenBSD's driver is sndio); sound=20=20 >=20servers connect to and use this. It's a little bit different. From application to hardware it is like: 5) application 4) maybe some infrastructure layer (jack, portaudio) 3) the API (for linux: ALSA libs, for FreeBSD: opening the device=20=20 nodes=20and issues ioctls =3D the OSS API) 2) the kernel code 1) the hardware So FreeBSD is a target from layer 2 until layer 3. Everything above=20=20 depends=20100% on the application you are using. > The part of OSS in name, that is a mess, is the API structure, and=20=20 >=20various implementations. In FreeBSD for instance, when a program=20=20 >=20uses an OSS API, I hear that developers, need to write so many=20=20 >=20patches, because different OSS frontends are not standardized. Most FreeBSD implements the OSSv4 API. Maybe not in v4.2, but those are=20=20 extensions=20are not really that much important for this discussion. The=20= =20 important=20part is, that we support OSSv4 since about FreeBSD 8, and=20=20 that=20the main part of playing audio is not changed between 4.0 and=20=20 4.2,=20so it doesn't matter much if we talk about the FreeBSD=20=20 implementation=20of OSSv4 or the 4Front implementation of OSSv4.2. The issues which come at hand are so far either at layer 5 or 4. For=20=20 issues=20at layer 3 I have not seen any prove or procedure how to repeat=20= =20 the=20issue so far (and I'm interested to see a procedure so that we can=20= =20 repeat=20the issue(s) people talk about here). Bye, Alexander. --=20 http://www.Leidinger.net=20Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF --=_g0ARV2vhdwQ-vwyuWy6-4GV Content-Type: application/pgp-signature Content-Description: Digitale PGP-Signatur Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJaN+ioAAoJEKrxQhqFIICEp1IP/2HCKuuX4MMshl1i3+zpVdKG Wn5yZKvQEPhyj2wrBUGtlZdPOLnf9CeVWTg/ZuFbQlzf2hrOOp6o95H3j72shfDF NbyC+NF79YEI4BN3HMGQTyMOG50VCfHlz6dyzgOC1BULVxqJ9oheREbns5i7kt0a edMk1lON5zZ2+jPPTq9Kh2br+VhBCD3RGaJkwQ942j8jeSvRpqfBl/XlPvmMfeXm wF/B/9Ii6Og+TtwNhLq+/vxAM5WUfbh1UD3VW7JTQyOnElf7z93Af6nJu6c/Z08u 3Bbv8Om0Ig5OS57a/lkBYGVVV6WI+OyjyD2XqKCiBHI81A/vrAdtU7Cy6haHMu6g 8gF7frfutoq3H2zI+45nr/UjUcI1enuz8GkNyRDzG2zhtnbpQ6GXCSEQrWWTVPex Z2EZh7RukbFMzsUaSAJMmfkIjofkjdwNDh7lf5sPkGpKushrGs4roF8hYKUiZQVg /5QuxIx4PO5Q1NgJASr+QbFSFbBDC+JSH7RRK8kp/OwZF1hSV+88lV1joF8eIhPU 9jeyM/+dEPBBvH5M4ZVZvQbEvC/J7wXIFtng6wyA/gjUwgfEUCvTnnZeR8EJm3/N PtoxLJhjaJiklHHvF+xEXWxwFS2tAh8AOGsf+R3zrr76PNtOkNhl0uIQa5u8MYoH XkRTwtLC78XC4Tr9stsQ =od8+ -----END PGP SIGNATURE----- --=_g0ARV2vhdwQ-vwyuWy6-4GV--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20171218171120.Horde.s5OngVFuRoftIluNHRvGOV6>