unofficial mirror
 help / color / mirror / code / Atom feed
From: Jan Stary <>
Subject: Re: better sndio support in SoX
Date: Tue, 20 Sep 2016 23:36:28 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <> <20160920193945.GA6738@starla>

> Seems reasonable; but I have little experience with using sndio
> with Måns sox, much less the API.  Perhaps Måns has an opinion,
> too.
> Fwiw, it would be helpful if example files could be
> provided/generated showing where the improvement is.

Any 24bit PCM file will exemplify this.

> Thanks.   Sorry for the late response; I've been mostly
> unplugged lately :)

No problem :-)

> I'm not familiar with sndio, but it looks like it changes how 24-bit
> samples are passed, packed rather than padded to 32 bits.

Yes, that's the point. With this patch,
SoX asks the underlying audio subsystem
to actually use the paramaters of the audio format.

(Whether the audio subsytem supports those parameters
is another question of course; the sndio sytem, as many other
sound daemons, will convert to and from almost anything.)

> The patch looks sane, and if OpenBSD is anyway building with this, it's
> probably good to pick it up.

Yes, the OpenBSD port of SoX is using this.
(I am not sure whether Alex actually commited yet.)

Changes to sndio.c should not affect anything else in SoX I believe.



  parent reply	other threads:[~2016-09-20 21:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-15 11:29 better sndio support in SoX Jan Stary
2016-09-20 19:39 ` Eric Wong
2016-09-20 20:06   ` Måns Rullgård
2016-09-20 21:36   ` Jan Stary [this message]
2016-09-20 22:24     ` Eric Wong
2016-09-21  5:45       ` Jan Stary
2016-09-21  6:58         ` Eric Wong
2016-09-21  7:19           ` Jan Stary
2016-09-21 11:42             ` Alexandre Ratchov
2016-09-21 11:19         ` Måns Rullgård
2016-09-21 11:42           ` Alexandre Ratchov

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:

  List information:

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

  git send-email \ \ \

* 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

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).