From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: sending data to an asynchronous process
Date: Fri, 02 Apr 2021 22:15:24 +0300 [thread overview]
Message-ID: <83zgygebw3.fsf@gnu.org> (raw)
In-Reply-To: <86v995t2c5.fsf@graner.name> (message from Nicolas Graner on Fri, 02 Apr 2021 12:20:26 +0200)
> From: Nicolas Graner <nicolas@graner.name>
> Date: Fri, 02 Apr 2021 12:20:26 +0200
>
> 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)
>
> The sound plays as expected, but process-send-region does not
> return until about half a second before the sound finishes
> playing. This means that if I send several minutes of audio,
> emacs is stuck during all that time, which completely defeats the
> purpose of an asynchronous process.
Asynchronous subprocesses mean that their processing and reading their
output are asynchronous. Writing to the subprocess is always
synchronous. It cannot be any other way, really, unless we start
additional threads to write to the subprocess (which then causes
problems because the Emacs Lisp machine cannot tolerate more than one
thread that has access to Lisp data). What Emacs does is read output
from subprocesses while it loops sending the data in chunks, so that
at least that part would work -- but that doesn't help in your case.
> The solution I found is to use a synchronous process:
> (call-process-region start end "sox" nil 0 nil ...
> where the fifth argument 0 means to discard process output and
> not wait for completion.
call-process-region writes the data to a temporary file, and then
invokes the subprocess. So if you do the same "by hand" and then call
start-process, you will have the best of all worlds. IOW, the
temporary file solution you didn't like is exactly what
call-process-region does under the hood, and so efficiency is not the
issue here. As for cleaning up the temporary files, that isn't really
a problem, is it?
next prev parent reply other threads:[~2021-04-02 19:15 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
2021-04-02 18:54 ` Jean Louis
2021-04-02 19:10 ` Jean Louis
2021-04-02 19:15 ` Eli Zaretskii [this message]
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=83zgygebw3.fsf@gnu.org \
--to=eliz@gnu.org \
--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).