-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Device detection bug. #32
Comments
@IvanScheers Was able to repro :) The problem is actually a permission's issue. You can't enumerate the audio playback devices from Instead, you can put your files in Thx again for reporting this, keep em coming! XD |
Thanks for investigating. I thought it would boil down to something like
that.
I'll decide later where to put my stuff when release is imminent. I'll be
spending some time porting from Nim (www.nim-lang.org) to C++. I love the
language, but I had no idea my executables would be false flagged by so
many virus scanners, just because it's Nim code. Apparently it is/was
popular among virus creators, so a lot of anti-virus software flags
software if it detects Nim features.
ChatGPT is helping, but it's going to be quite a task. Being false flagged
by 48 out of 72 virus scanners doesn't make a happy day :-(
Anyway, wsay to generate the TTS as .wav, combined with miniaudio to play
them, proves to be a great asset. I had to rewrite some of the code.
Initially I was threading playback (it has waits for the right instant,
background noise, filtering...) but it ate up over 20% of processor
resources. Looping over everything in the main thread only uses 1 to 3%.
Kind of important as an addon for a resources heavy simulator.
Thanks again for creating wsay. I'm very glad I stumbled onto it.
Oh, maybe one remark. It's of no importance to me, but in interactive
mode, it might be interesting that if -o is given, there would be one wav
per sentence passed to wsay. Like out0001.wav out0002.wav ... instead of
one big out.wav file at the end.
Kind regards,
Ivan
…On Fri, 17 May 2024 at 18:21, p-groarke ***@***.***> wrote:
@IvanScheers <https://github.com/IvanScheers> Was able to repro :)
The problem is actually a permission's issue. You can't enumerate the
audio playback devices from LocalLow, at least not without futzing around
with permissions.
Instead, you can put your files in Local (Local\Icarus\ReVoice\bin).
Which is the expected location anyways (LocalLow is for web "safe mode"
things). That should fix your issue. I'll add a better warning in the
future whenever no devices are detected.
Thx again for reporting this, keep em coming! XD
—
Reply to this email directly, view it on GitHub
<#32 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ASQMO4OJSGM7LIS2W65WABDZCY375AVCNFSM6AAAAABH2OZ72WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMJYGA2TCMRXGY>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Ugh antivirus false-positives -___- Microsoft enabled machine learning on Windows 11 and there's not one release of mine it won't false detect. I have to send every Had never heard of nim, looks interesting. Sucks to have to port like that :( But I'm glad my little tool is saving you some time. Take care! |
Report :
There's one peculiar issue. In my test version, with everything local to
my exe everything worked like a charm. Now that the speech & sound module
is completely rewritten from using MS SAPI, and then Sox (
https://sourceforge.net/projects/sox/) to apply filters, I moved this
module over to Codeblocks. After further editing of my code wsay suddenly
stopped working. It gave exit code -1073740791.
According to chatGPT: "An exit code of -1073740791 in Windows typically
corresponds to the hexadecimal value 0xC0000409, which indicates an
"Unknown Exception" or "STATUS_STACK_BUFFER_OVERRUN".
Testing further, I found that it only happens when starting wsay from a
subfolder (in the user %AppData% folder) I was intending to use in release
versions. The idea is to have my main program run in a working directory
with subfolders like bin, data, sound, etc.
Running it from the command line I got this :
So it may be Windows related, maybe it doesn't like executables being there
? Anyway I can work around that and place wsay.exe in "Program Files" or a
bin folder in the user's home directory and use that AppData subfolder as a
working directory. However, in the long run, for compability and a clean
setup it might be better to have wsay in that AppData/../ReVoice/bin folder.
The text was updated successfully, but these errors were encountered: