From: Cary Lewis <cary.lewis@gmail.com>
To: sox-devel@lists.sourceforge.net
Subject: Re: Jack Driver
Date: Sat, 14 Nov 2020 18:54:26 -0500 [thread overview]
Message-ID: <CD7EA8A9-3100-4E0B-976B-0B3553211646@gmail.com> (raw)
In-Reply-To: <CAOQrJk7vCepm-CLAomobfad5jaktOgBsuHktGDykWPHf714rOQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1232 bytes --]
Can’t you just use cat or dd to read from the input source and tee to sox and the output device? Or do you need to Sox to decode the stream so that it plays?
> On Nov 14, 2020, at 4:52 PM, Claude Warren <claude@xenei.com> wrote:
>
>
> I think I need a Jack device driver and I don't see one available, so I think I have to write one. So is there any documentation about how to write a SoX device driver?
>
> To back up a bit, I think I need a Jack device driver because I want to take the audio input and record it while also sending it to the output. I don't want SoX to modify the signal going to output. So something like:
>
> Input ----+---- output
> |
> SoX ---- disk
>
> Put differently: Tee the input with one going to output and one going to sox to record to disk.
>
> Anybody have either documentation for how to write the device driver or a solution for the problem?
>
> Claude
>
> --
> I like: Like Like - The likeliest place on the web
> LinkedIn: http://www.linkedin.com/in/claudewarren
> _______________________________________________
> SoX-devel mailing list
> SoX-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/sox-devel
[-- Attachment #1.2: Type: text/html, Size: 2417 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
[-- Attachment #3: Type: text/plain, Size: 158 bytes --]
_______________________________________________
SoX-devel mailing list
SoX-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sox-devel
prev parent reply other threads:[~2020-11-14 23:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-14 21:26 Jack Driver Claude Warren
2020-11-14 23:54 ` Cary Lewis [this message]
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=CD7EA8A9-3100-4E0B-976B-0B3553211646@gmail.com \
--to=sox-devel@lists.sourceforge.net \
/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).