* arecord --max-file-time behavior [not found] <182ef4f0bc499e00-webhooks-bot@alsa-project.org> @ 2025-03-21 23:23 ` GitHub issues - opened 0 siblings, 0 replies; only message in thread From: GitHub issues - opened @ 2025-03-21 23:23 UTC (permalink / raw) To: alsa-devel alsa-project/alsa-utils issue #296 was opened from thk686: I do environmental sound recordings where arecord runs for months to years with --max-file-time set to something like 15 minutes. It is very nice to have this feature, yet there is one aspect that is problematic. It is not simple to know which file is currently being written. One can time stamp the file names and ignore the most recent, which is probably the simplest. Nonetheless, I wonder if it could be the case that the current write file could be named something else, such as the file name but preceded by a . or other indicator, and have it renamed to its intended name once it is closed and arecord has moved on to another file. Issue URL : https://github.com/alsa-project/alsa-utils/issues/296 Repository URL: https://github.com/alsa-project/alsa-utils ^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2025-03-21 23:24 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <182ef4f0bc499e00-webhooks-bot@alsa-project.org>
2025-03-21 23:23 ` arecord --max-file-time behavior GitHub issues - opened
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.