Konstantin

That `-otxt` parameter in the command-line app is a switch. It does not accept path of the output file. The output text file is always placed in the same folder...

The UX issue is fixed in version 1.10.1. Specifically, the error message now includes path to the input file it’s trying to decode.

The current version of the library only supports modern .NET. I don’t have guides, but I have an example you can rework into a .NET 4 library. The example is...

@User1231300 Added in the API, command-line examples, and power shell. However, I don’t know how that thing should affect the output, haven’t tested much.

@juntaosun Implemented in version 1.11 for command-line and power shell.

@adamreed90 I like the idea of integer index in that string, it’s simple and it works. Will be fixed in the next version. In the meantime, update from master and...

@kiron111 I think you can do that with the new PowerShell wrapper. Here’s how. 1. Create the folder `%USERPROFILE%\Documents\WindowsPowerShell\Modules` 2. Download `WhisperPS.zip` from releases, extract ZIP into that folder 3....

@kiron111 You’re getting English because it’s the default. For Chinese, you need another parameter to the `Transcribe-File` cmdlet: `-language zh` So the complete line becomes that: ``` dir * -include...

@kiron111 The PowerShell module version 1.10.1 supports human-readable names for the languages, such as Chinese, in addition to the codes defined by 1988 version of ISO 639-1 which are used...

@DK013 The C# API allows to run real-time capture, see the [MicrophoneCS example](https://github.com/Const-me/Whisper/tree/master/Examples/MicrophoneCS). The logic for the microphone capture is in [Capture::run()](https://github.com/Const-me/Whisper/blob/1.10.0/Whisper/Whisper/ContextImpl.capture.cpp#L211-L212) C++ method. As you see, it’s currently hard...