From: Nicolas Graner <nicolas@graner.name>
To: help-gnu-emacs@gnu.org
Subject: Re: sending data to an asynchronous process
Date: Fri, 02 Apr 2021 20:35:54 +0200 [thread overview]
Message-ID: <86im548rg5.fsf@graner.name> (raw)
In-Reply-To: <YGdR/h/Pq2jNQmUL@protected.localdomain> (message from Jean Louis on Fri, 2 Apr 2021 20:18:54 +0300)
Jean Louis <bugs@gnu.support> wrote on 2021-04-02 20:18:
> * Nicolas Graner <nicolas@graner.name> [2021-04-02 13:21]:
>> I am writing a program that creates audio samples in an emacs
>> buffer, then sends them to an external program (sox) to play in
>> the background while I continue working with emacs. Part of the
>> code is roughly as follows:
>>
> (setq process
> (let ((process-connection-type nil))
> (start-process "my-process" nil
> "sox" "-r" rate "-c" channels "-b" bits "-e" encoding "-q" "-d")))
> (process-send-region process start end)
> (process-send-eof process)
>
> For process-send-region, it says:
>
> If PROCESS is a non-blocking network process that hasn’t been fully
> set up yet, this function will block until socket setup has completed.
>
> Maybe that applies.
No. No network involved whatsoever. Just running /usr/bin/sox which is a
regular file.
> It would be nice to show all the function you use there.
No other function is needed. If you want to reproduce the problem, just
fill a buffer with 1 MB of random binary data and evaluate this slightly
modified version of the above code:
(setq process
(let ((process-connection-type nil))
(start-process "my-process" nil
"/usr/bin/sox" "-r" "44100" "-c" "2" "-b" "32"
"-e" "signed-integer" "-t" "raw" "-" "-q" "-d")))
(process-send-region process (point-min) (point-max))
(process-send-eof process)
If you have sox installed, be prepared to hear some horrible random noise :)
You will notice that the first expression above returns immediately as
expected, but the second (process-send-region ...) does not. That's the
problem I'm trying to solve.
> I would like to know if you play files or you feed data to sox to
> play files, where does that come from? Is it maybe an elevator
> music from an UDP port?
The data originally came from files that I read into a buffer and did
some processing on. At the time of calling the above code, all the data
is sitting quietly in an emacs buffer. No network, disk access or
anything else involved. Just sending the contents of a buffer through a
pipe to a program that was started as an asynchronous process.
Nicolas
next prev parent reply other threads:[~2021-04-02 18:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-02 10:20 sending data to an asynchronous process Nicolas Graner
2021-04-02 16:13 ` Jean Louis
2021-04-02 17:18 ` Jean Louis
2021-04-02 18:35 ` Nicolas Graner [this message]
2021-04-02 18:54 ` Jean Louis
2021-04-02 19:10 ` Jean Louis
2021-04-02 19:15 ` Eli Zaretskii
2021-04-02 23:03 ` Nicolas Graner
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86im548rg5.fsf@graner.name \
--to=nicolas@graner.name \
--cc=help-gnu-emacs@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).