Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 16 Dec 2017 01:16:14 +0100
From:      Alexander Leidinger <Alexander@leidinger.net>
To:        blubee blubeeme <gurenchan@gmail.com>
Cc:        Hans Petter Selasky <hps@selasky.org>, freebsd-multimedia@freebsd.org
Subject:   Re: FreeBSD amd64 GENERIC kernel
Message-ID:  <20171216011614.Horde.Uitm74qhBEwh_NRo9RgDgu3@webmail.leidinger.net>
In-Reply-To: <CALM2mEmnxsdwy5rr9ApC3q7kZ2-EK2YYBqMAibd9nA3XRfhKhQ@mail.gmail.com>
References:  <CALM2mEnnXKAyF_ti_zKYt=1m-ZTfjH5di1cayYjGM4hi9dOxRQ@mail.gmail.com> <aa346744-94c9-98a4-4de6-c5e956bf096c@ShaneWare.Biz> <CALM2mE=88_a-9FF3-e49TMPm1pGzwQn1h_wx2gofHK-NRKOpZA@mail.gmail.com> <cf0b39a9-8059-06c2-a033-109c626de225@selasky.org> <CALM2mEnfdv6R4YuSMSnR-SEtR1ief5uSg4qYWFb49dVQsRMw6A@mail.gmail.com> <ad2778be-a601-b825-1195-134dd02b04d9@selasky.org> <CALM2mEkKUr%2BrbMtS_ObXq0SYvZgFUKN9VXwqV-bxFrWVfizx1Q@mail.gmail.com> <4c3ae20e-b6dd-d5db-0b93-2e1225daa658@selasky.org> <CALM2mEkedLN%2Br2fk4YX3_Y01ENgvqo4s9yoyfBKTkBJkH56dcQ@mail.gmail.com> <4eb0c57e-96fa-b75a-17f8-750154aa247a@selasky.org> <CALM2mEn=9eNHzezpkKSBydKzedqagLwtfMopuDQb9Xem7=OGUA@mail.gmail.com> <d92eae76-831b-3a6f-a7a6-4f4d7e66df99@selasky.org> <CALM2mEmnxsdwy5rr9ApC3q7kZ2-EK2YYBqMAibd9nA3XRfhKhQ@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help

[-- Attachment #1 --]
Quoting blubee blubeeme <gurenchan@gmail.com> (from Fri, 15 Dec 2017  
22:39:25 +0800):

> What's with the stuck up attitude? Stay focused on the issue at hand which
> is FreeBSD's fork of OSS makes it a challenge to implement software that
> sticks to the OSS standard.
>
> There's nobody actively working on improving the audio situation on
> FreeBSD. You have a user/developer who wants to do the work and you react

Can you please describe in features / bullet-points what is missing  
instead of saying "X is better than Y"?

> like it's some personal attack on your person to update the underlying code.
>
> Guess what, most of the clever features you talk about are in OSS4 and if
> they are not, they can still be added.

What I understand what you say is:
  - I want to replace X by Y, because Y is better.
  - Anything what is better in X can be added to Y.

So basically I understand that you want to replace incomplete  
feature-set in X by an incomplete feature-set from Y (without knowing  
what the incompleteness in either X or Y is).

> I'd really appreciate it if you refrained from your continued attempts at
> ad hominem against me and stick to code and a discussion around ideas and
> implementations.

I understand HPS as asking you to explain in different words what you  
want to tell, as he is not understanding what you want to tell. To my  
knowledge HPS is not a native english speaker (neither am I). I don't  
know if you are a native english speaker or not.
As a person working in a multi-language (at least 10, with english  
being the common one) environment I suggest not getting upset about  
phrases like "I don't understand your english", it doesn't necessarily  
mean a deficit on the receiver side of this phrase, but most often  
just means both ends don't share the same language background. Often  
it helps in such situations to switch from implicit ("it") references  
to explicitly mention an item/feature/object/... and to use short  
phrases.


And to bring in some technical info (parts of "AFAIR", I may misremember...):
  - The OSS code in FreeBSD was at some point in time the 4Front OSS code.
  - At some point 4Front closed-source their implementation and  
FreeBSD deviated.
  - At some point Ariff put in an effort to advance the OSS code in  
FreeBSD which made it the best in various aspects (one of them  
latency) when compared to 4Front code, Windows, MacOS and Linux ALSA.
  - Then in 2006 Ryan was adding OSSv4-API compatibility to the  
FreeBSD sound code as part of the Google Summer of Code, mentored by  
Ariff and me.
  - Since then I don't remember big API changes/improvements... HPS  
worked a lot on USB audio support, userland drivers and AFAIK some  
MIDI stuff as part of the userland drivers, but all that is more or  
less drivers, not API... please correct me if I got this wrong; and  
mav(?) worked on HDA support (also driver, not API).

Note, various aspects of the FreeBSD sound code can be tweaked by  
sysctls, e.g. latency, virtual channels, direct physical access  
("bitperfect"), automatic resampling, equilizer, ... (see "sysctl  
hw.snd dev.pcm dev.hdaa dev.hdac" and "man sound snd_hda snd_uaudio"  
and the SOUND_4.TXT of Ariff you mentioned).

And regarding your comment about SOUND4.TXT: if you read this document  
carefully, you will notice that the part you quoted as being bad can  
be disabled.

Bye,
Alexander.

-- 
http://www.Leidinger.net Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF
http://www.FreeBSD.org    netchild@FreeBSD.org  : PGP 0x8F31830F9F2772BF

[-- Attachment #2 --]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAABAgAGBQJaNGXOAAoJEKrxQhqFIICEodAP/j/Uy6P9XFb3Z1vVhQmGddiG
uUgmSKbsSFT+651BGR+QysLzqvSTs7S0B8fSgA6AcX31t2ckP8pJh95Osh36VPSK
xs70BumL39Li/io2AxRYw5zw2JAt4i4Sxv6L7/m5JsKJGhSxKK6jlMAI3n0PA/Dm
w5+6oSmTqe/24gNmKRzDUMqGaDv2XACEXJhusLNNVQn+B8aSzGpRJNuLOSxX7vLG
VSAd1fYpP8MnHdKCpPoyyOpXGI8BmAtQzQlYU39mG9hQ3oyf36J6pw+3TXUhPE5I
L6S4SJAzucDkEIAddV9zKegpZybWhbkR6kt2iuWu9ASCCqDJtKSohla1H+bnsTS0
x7fYrj73FGBFUyc40YmyXNg/nbvZsRTgb5xaldfBWwCphFE2oMRwnRndCcZz4a5A
b5eLwps5LjCRKhg5ci175ncBGdp+1CxmDTgf/3iPgDeHOz+pCFU+CJfrluIWlGKb
2usOm99eiatBDOHh3/OzBXyEt8OGKH/Wlhrg2I7Lltbj0o1JXnsANvrsZcf2gKsB
t1dVPKAHQyNmOdjMv/Rhfo4EpIZcfDgfOD0bC3UvUI+Ls7EeAoTeqz8XYmjNfNEo
51O4aiftmRse8o61ttZUNnNqau5eT0pspx/XireOjrWVaIVUBzMc65h7OLMOaEt1
bcM1LpIfIsxUEO00EnMB
=PzLH
-----END PGP SIGNATURE-----

Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20171216011614.Horde.Uitm74qhBEwh_NRo9RgDgu3>