From: "Måns Rullgård" <mans@mansr.com>
To: "Close, Kacey" <Kacey.Close@unt.edu>
Cc: sox-users@lists.sourceforge.net
Subject: Re: [EXT] Re: SoX Quits Unexpectedly
Date: Sat, 06 Aug 2022 15:09:12 +0100 [thread overview]
Message-ID: <yw1xfsi95urb.fsf@mansr.com> (raw)
In-Reply-To: <SA0PR01MB61051E4674DD7EEC8E8200B2E28F9@SA0PR01MB6105.prod.exchangelabs.com> (Kacey Close's message of "Tue, 19 Jul 2022 16:45:07 +0000")
"Close, Kacey" <Kacey.Close@unt.edu> writes:
> Subject: [EXT] Re: SoX Quits Unexpectedly "Close, Kacey" <Kacey.Close@unt.edu> writes:
>>
>>> I am trying to configure SoX to run at startup and stay operational
>>> indefinitely on a remote access computer. I have a series of LaunchAgents
>>> and Scripts that successfully launch SoX with no user interaction, but I
>>> have discovered that SoX will not run indefinitely. Instead it runs for
>>> ***exactly*** 1 hour, 41 mintues, and 27 seconds. I’ve repeated the process
>>> several times, and the run time is always 1:41:27. This seems an oddly
>>> specific number, but I’m not sure what is causing SoX to shut down. Any
>>> input would be appreciated.
>>
>> What operating system are you running, and what is the full sox command?
>
> I am on macOS 12.4 and I am initiating SoX with the following command:
>
> sox -d -t wav - | paplay --latency=10 --volume=28000
You're probably hitting the size limit for WAV files.
--
Måns Rullgård
_______________________________________________
Sox-users mailing list
Sox-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sox-users
prev parent reply other threads:[~2022-08-06 14:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-14 15:44 SoX Quits Unexpectedly Close, Kacey
2022-07-15 12:52 ` garra
2022-07-15 13:13 ` Måns Rullgård
2022-07-19 16:45 ` [EXT] " Close, Kacey
2022-08-06 14:09 ` Måns Rullgård [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-users
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=yw1xfsi95urb.fsf@mansr.com \
--to=sox-users@lists.sourceforge.net \
--cc=Kacey.Close@unt.edu \
/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).