Rotem Dan

I believe this was resolved. Closing.

Hi, thanks for your interest in trying to make a standalone executable! That is something I'd eventually want to have. I tried running `pkg` and got the same error messages....

I tested this and it seems to work (assuming you're using Windows, but it should be similar with other platforms): 1. Download https://nodejs.org/dist/v18.17.0/node-v18.17.0-win-x64.zip (or whatever is right for the platform)...

Turns out there's a simpler method to start the CLI, using the auto-generated batch files that are created in the `node_modules/.bin` directory when `npm install echogarden` is run: ``` .\node_modules\.bin\echogarden.cmd...

After asking Claude 2 about the batch file `.\node_modules\.bin\echogarden.cmd`: ```bat @ECHO off GOTO start :find_dp0 SET dp0=%~dp0 EXIT /b :start SETLOCAL CALL :find_dp0 IF EXIST "%dp0%\node.exe" ( SET "_prog=%dp0%\node.exe" )...

I managed to get a working single executable in Linux using [makeself](https://makeself.io/). (I used WSL2): 1. I downloaded and extracted https://nodejs.org/dist/v18.17.0/node-v18.17.0-linux-x64.tar.xz and renamed the directory to `echogarden-portable`. 2. I `npm...

Thanks, but it turns out this solution doesn't really work properly. `makeself` seemed to work at the beginning, but then coming back to test it again I realized it doesn't...

Yes, I noticed that was mentioned in the repository. But also, the way it performs the packaging would also require adding many special files, like binary files and modules (such...

Never seen it before. Could be a lot of things, including an ONNX runtime issue. Can you send the audio and transcript that produces it?

The error looks like it has to do with some issue with an input tensor or its dimensions. * Are you using `cpu` provider (there can be all sorts of...