From: Jean Louis <bugs@gnu.support>
To: Nicolas Graner <nicolas@graner.name>
Cc: help-gnu-emacs@gnu.org
Subject: Re: sending data to an asynchronous process
Date: Fri, 2 Apr 2021 20:18:54 +0300 [thread overview]
Message-ID: <YGdR/h/Pq2jNQmUL@protected.localdomain> (raw)
In-Reply-To: <86v995t2c5.fsf@graner.name>
* 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.
It would be nice to show all the function you use there.
> 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. Using process-send-string
> instead of process-send-region makes no difference.
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?
--
Jean
Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns
Sign an open letter in support of Richard M. Stallman
https://rms-support-letter.github.io/
next prev parent reply other threads:[~2021-04-02 17:18 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 [this message]
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
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=YGdR/h/Pq2jNQmUL@protected.localdomain \
--to=bugs@gnu.support \
--cc=help-gnu-emacs@gnu.org \
--cc=nicolas@graner.name \
/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).