sox-devel@lists.sourceforge.net unofficial mirror
 help / color / mirror / code / Atom feed
From: SoX NG <sox_ng@fastmail.com>
To: sox-devel@lists.sourceforge.net, sox-ng@groups.io
Subject: SoX developments in sox_ng
Date: Fri, 27 Dec 2024 07:19:41 +0100	[thread overview]
Message-ID: <5ef75327-a0d1-4d08-a38c-5fe8a7415064@fastmail.com> (raw)

Hi

    Discussion of changes to SoX's functionality seem to happen most now 
in their issue comments so I though I'd summarize the active ones here 
in case anyone wants to follow how SoX is evolving or has input.


    One has already been resolved by Rob: a change in the Bit-depth 
figures to fix a couple of bugs: that positive values should include the 
0 sign bit as a significant digit of the right hand value and that 
negative values' leading 1s do not count as significant digits for the 
left hand value (if I've understood it properly) plus a couple of corner 
cases like -32768. Oddly enough, the issue was raised in the sox.sf.net 
ticket tracker by someone who thought that the Bit-depth values should 
be the same for a signal and for the inverted version of it, which isn't 
true because 8 has one more significant digit than -8. A "fix" was even 
committed there to address it, so there are now three different versions 
of Bit depth figures, two wrong and one right. At least I hope it's 
right now!

https://codeberg.org/sox_ng/sox_ng/issues/273


   One is still being investigated, that the "echos" effect says it does 
one thing in the manual, says it does something else in the header 
comments in stats.c but in reality seems to do something different from 
either of these in reality, apparently very similar to what "echo" does. 
We're trying to find out what it does do in reality and which of the 
claimed functionalities is more useful, as well as thinking of two new 
echo effects: one the same as traditional guitar effects that repeat the 
echo forever and the other the already well-known "tapped delay" DSP effect.

https://codeberg.org/sox_ng/sox_ng/issues/276


Feel free to discuss here of course and I'll import the gems into the 
issue tracker, as I don't think there's an easy way to interact with 
issue comments from the command line.


     M



_______________________________________________
SoX-devel mailing list
SoX-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sox-devel

                 reply	other threads:[~2024-12-27  6:20 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.sourceforge.net/lists/listinfo/sox-devel

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5ef75327-a0d1-4d08-a38c-5fe8a7415064@fastmail.com \
    --to=sox-devel@lists.sourceforge.net \
    --cc=sox-ng@groups.io \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/sox.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).