From: kcgen <kcgen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: dosbox-staging-0.77.0
Date: Wed, 02 Jun 2021 23:21:50 +0200 [thread overview]
Message-ID: <20210602212150.9N27XS1AF_QufJwl1nkFHPtqXjZD6ef7vXf29GVIQYw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31258@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1064 bytes --]
New comment by kcgen on void-packages repository
https://github.com/void-linux/void-packages/pull/31258#issuecomment-853391106
Comment:
> The enable-floats option could probably be added to Void's FluidSynth package (https://github.com/void-linux/void-packages/blob/master/srcpkgs/fluidsynth/template), but I do not know if it would be a suitable default outside of DosBox.
I highly recommend it across the board. Floats are already 32-bits - which gives you 2^16 times finer resolution to quantify an amplitude level versus CD-quality 16-bit sound.
Even 24-bit audio is considered sufficient for professional-grade studio work. Leaving this as a double means samples are a whopping 64-bit; which is.. vastly overkill.
The other benefit of 32-bit floats (versus full-doubles) is that SIMD'able operations can pack twice the data into a single operation, which can make difference on CPU limited hardware like the Pi 2 and 3. I make these two points in another thread and FluidSynth's author was also in agreement - but can't remember where now.
next prev parent reply other threads:[~2021-06-02 21:21 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-02 9:48 [PR PATCH] " joshuakraemer
2021-06-02 9:56 ` [PR PATCH] [Updated] " joshuakraemer
2021-06-02 11:51 ` joshuakraemer
2021-06-02 20:03 ` [PR PATCH] [Updated] " joshuakraemer
2021-06-02 21:21 ` kcgen [this message]
2021-06-02 21:22 ` kcgen
2021-07-15 20:56 ` [PR PATCH] [Updated] " joshuakraemer
2021-07-15 21:05 ` joshuakraemer
2021-07-16 15:28 ` [PR REVIEW] " ericonr
2021-07-16 15:28 ` ericonr
2021-07-16 15:28 ` ericonr
2021-07-16 15:28 ` ericonr
2021-07-16 17:00 ` [PR PATCH] [Updated] " joshuakraemer
2021-07-16 17:00 ` [PR REVIEW] " joshuakraemer
2021-07-16 17:01 ` joshuakraemer
2021-07-16 17:02 ` joshuakraemer
2021-07-16 17:03 ` joshuakraemer
2021-07-16 17:58 ` ericonr
2021-07-16 18:21 ` [PR PATCH] [Updated] " joshuakraemer
2021-07-16 20:15 ` [PR REVIEW] " ericonr
2021-07-16 20:16 ` ericonr
2021-07-16 20:41 ` [PR PATCH] [Updated] " joshuakraemer
2021-07-16 20:42 ` [PR REVIEW] " joshuakraemer
2021-07-16 20:42 ` joshuakraemer
2021-07-17 2:14 ` [PR PATCH] [Updated] " ericonr
2021-07-17 2:15 ` ericonr
2021-07-17 2:15 ` [PR PATCH] [Merged]: " ericonr
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210602212150.9N27XS1AF_QufJwl1nkFHPtqXjZD6ef7vXf29GVIQYw@z \
--to=kcgen@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).