Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 6 Dec 2012 08:14:27 -0800
From:      VDR User <user.vdr@gmail.com>
To:        Thomas Zander <thomas.e.zander@googlemail.com>
Cc:        freebsd-multimedia@freebsd.org
Subject:   Re: Why 24/192kHz sound is not a solution.
Message-ID:  <CAA7C2qgwiG6ELHqDov-1CpD=R7ZL=PP0G8hVrZAwu6a2L%2BSvPA@mail.gmail.com>
In-Reply-To: <CAFU734wQ0YikLwhCE5%2Bhri7W5V1pHhZWk1tVgbhgD299wvi9Mw@mail.gmail.com>
References:  <1354723094926-5766828.post@n5.nabble.com> <CAA7C2qjCbe_yJMCpKFj67aXtSBiWC%2BGwHMkACcerUGB3bWo1pg@mail.gmail.com> <CAFU734wQ0YikLwhCE5%2Bhri7W5V1pHhZWk1tVgbhgD299wvi9Mw@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Dec 6, 2012 at 1:19 AM, Thomas Zander
<thomas.e.zander@googlemail.com> wrote:
>>> http://people.xiph.org/~xiphmont/demo/neil-young.html
>>
>> I don't know that using the mailing list to post links to articles is
>> appropriate, but 24/192 does matter when it comes to processing.
>
> Why should this be inappropriate? The article has a clear focus on the
> 24/192 topic and freebsd-multimedia@ is a place to discuss how FreeBSD
> should deal with this. IMHO there is nothing wrong with that.
> In my opinion there is one answer: If the sound chip accepts 24/192,
> then our sound system should be able to use this capability.

I'm in several mailing lists and in all cases it's generally frowned
upon when people use them to post links to articles. Most people
consider it spam. Also, having a discussion about features/support in
a driver is on thing, but that is not the same as having a discussion
about the nature and technical aspects of sound. If you don't
understand why those conversations are completely different and not
relevant to a drivers lack of support, I'm not sure what to tell you.

I do agree with your opinion about capability support. If the hardware
supports it, so should the software.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAA7C2qgwiG6ELHqDov-1CpD=R7ZL=PP0G8hVrZAwu6a2L%2BSvPA>