Rotem Dan

Thanks for the information! This is really helpful. It seems that the `sox-14.4.1-macosx-20230718` doesn't seem work with ARM64 - which is expected, that's why I've set to use it only...

It's good to hear it works with `14.4.2`. You can also try a `wav` file with longer duration (more than a minute, to ensure that it never stops in the...

This should be normal behavior: * Each individual segment is synthesized and then played back (before any merging occurs). * `Merge and postprocess segments` happens after all segments have been...

Thank you. At least now I know that Echogarden runs under macOS, on a basic level. And from what I see, that `ffmpeg`, at least, works, and that `sox` is...

`Echogarden` simply calls the `sox` command line executable, like you do, only it streams the audio input to the executable's `stdin`. There is no difference otherwise. **So**: It's possible that...

On `0.11.5`, when running on macOS, SoX playback now first writes the audio to a temporary `wav` file, and plays the file, instead of using stdin. [Here is the relevant...

`auto-editor` has a CLI option called `ffmpeg-location`: ``` --ffmpeg-location Set a custom path to the ffmpeg location ``` In general, I would rather not to require the user to specify...

I can look for `ffmpeg` and `sox` executables in the current directory, if they are not found in path. This doesn't require adding new configuration options. It would only take...

On `v2.0.0`, SoX has been replaced by the newly developed [`audio-io`](https://github.com/echogarden-project/audio-io) package, which uses a direct native interface to the Core Audio driver on macOS. I'm closing this issue.

I'm not familiar with NestJS. Based on the error message, it seems like it is trying to import the module using `require`, under the hood? Echogarden is a complex application...