RE: https://mastodon.social/@JustinMac84/117564107356943617
Something in this post is causing the ReloqC Add-On to crash. Wonder how I can find out what part is causing it.
RE: https://mastodon.social/@JustinMac84/117564107356943617
Something in this post is causing the ReloqC Add-On to crash. Wonder how I can find out what part is causing it.
@GamingWithEars yeah I don't even have to listen to the whole post for it to crash, either lol. Here is the error log. Eloquence C queued speech: characters=1331, protected_tags=0, rate=48000 Hz, tags=False
INFO - external:synthDrivers.reloqC.SynthDriver.speak (17:48:48.700) - MainThread (49816):
Eloquence C queued speech: characters=3329, protected_tags=0, rate=48000 Hz, tags=False
ERROR - external:synthDrivers.reloqC._reloq_eci_direct.DirectEciEngine.speak (17:48:53.871) - reloq.eci-text (21824):
ECI could not clear cancelled input; native busy=1
ERROR - external:synthDrivers.reloqC._reloq_eci_direct.DirectEciEngine.speak (17:48:57.334) - reloq.eci-text (21824):
ECI could not clear cancelled input; native busy=1
ERROR - external:synthDrivers.reloqC.SynthDriver._on_error (17:48:57.376) - reloq.eci-text (21824):
Eloquence C synthesis failed
Traceback (most recent call last):
File "C:\Users\admin\AppData\Roaming\nvda\addons\reloqC\synthDrivers\reloqC\_reloq_eci_transport.py", line 602, in _run_job
completed = engine.speak(job.parts, on_pcm, on_index)
File "C:\Users\admin\AppData\Roaming\nvda\addons\reloqC\synthDrivers\reloqC\_reloq_languages.py", line 303, in speak
return flush()
File "C:\Users\admin\AppData\Roaming\nvda\addons\reloqC\synthDrivers\reloqC\_reloq_languages.py", line 280, in flush
result = engine.speak(tuple(pending), on_pcm, on_index)
File "C:\Users\admin\AppData\Roaming\nvda\addons\reloqC\synthDrivers\reloqC\_reloq_eci_direct.py", line 382, in speak
raise RuntimeError(f"{operation} rejected input (code {ok}; native busy={busy})")
RuntimeError: eciAddTextUtf8 rejected input (code 0; native busy=1)
ERROR - external:synthDrivers.reloqC._reloq_eci_direct.DirectEciEngine.speak (17:48:58.071) - reloq.eci-text (21824):
ECI could not clear cancelled input; native busy=1
ERROR - external:synthDrivers.reloqC.SynthDriver._on_error (17:48:58.088) - reloq.eci-text (21824):
Eloquence C synthesis failed
Traceback (most recent call last):
File "C:\Users\admin\AppData\Roaming\nvda\addons\reloqC\synthDrivers\reloqC\_reloq_eci_transport.py", line 602, in _run_job
completed = engine.speak(job.parts, on_pcm, on_index)
File "C:\Users\admin\AppData\Roaming\nvda\addons\reloqC\synthDrivers\reloqC\_reloq_languages.py", line 303, in speak
return flush()
File "C:\Users\admin\AppData\Roaming\nvda\addons\reloqC\synthDrivers\reloqC\_reloq_languages.py", line 280, in flush
result = engine.speak(tuple(pending), on_pcm, on_index)
File "C:\Users\admin\AppData\Roaming\nvda\addons\reloqC\synthDrivers\reloqC\_reloq_eci_direct.py", line 382, in speak
raise RuntimeError(f"{operation} rejected input (code {ok}; native busy={busy})")
RuntimeError: eciAddTextUtf8 rejected input (code 0; native busy=1)
INFO - synthDrivers.espeak.SynthDriver.__init__ (17:48:59.593) - MainThread (49816):
Using eSpeak NG version 1.52.0
INFO - synthDriverHandler.setSynth (17:48:59.708) - MainThread (49816):
Loaded synthDriver espeak
@serrebi Cool, are you willing to submit that as a PR since you found the right part of the log?
@GamingWithEars Not until next week unfortunetly.
@GamingWithEars I have muse code still, so I"m getting it to look into it, and if I manually test and it's fixed I"ll submit.
@serrebi @GamingWithEars Is Muse Code good? I find that Opus 5.5 is the best at understanding intent.
@Orinks I agree with that for sure. Claude is the one I won't let go of right now. @GamingWithEars
@GamingWithEars That’s so crazy because I never needed to do that. I just signed in with Google @serrebi @Orinks
@technocounselor @serrebi @Orinks It's something they added a few months ago now, i'd imagine. I tried to sign up for it a couple months ago now and I bet it had already been there for a bit.
@serrebi @GamingWithEars I actually ran into that bug and crashed it to. I didn't make it to the link either. that is just crazy.
@JamminJerry submitted a fix, but if you can't wait for it to murge, https://github.com/serrebidev/Reloq-C/releases/tag/v1.1.2-pausefix1 @GamingWithEars
@serrebi that log is absolutely useful to have. You could always ping @HOzosch with it for now. That dev is a star at really prompt work, and great at getting fixes in not long after. So I'm sure it could be picked up on his own time, and if he doesn't get to it before next week you can submit it as a PR instead. I can confirm though with 1.1.1, it's a strange crash. Thankfully NVDA just boots you back into Windows Onecore voices. @GamingWithEars
@Tamasg @serrebi @HOzosch @GamingWithEars Could be a crash word character sequence which couldn't be identified by the poster? I mean I don't know if he is aware of eloquence crash words and I know there is one like have with an apostrophe in it.
@TomGrant91 @Tamasg @serrebi @GamingWithEars Well, I made sure that every case declared in text_preprocessing.py in eloquence_64 is fixed. Well, at least most of them. And then, there is the fix from 1.1.3 as well.
@HOzosch Thanks, I'm sure it worked out better than my fix. @TomGrant91 @Tamasg @GamingWithEars
@TomGrant91 Nope. That was a different situation, fixed in the latest 1.1.3 release. @Tamasg @serrebi @HOzosch @GamingWithEars
@serrebi @GamingWithEars So, folks, should I submit it as a bug on the project's repository?
@GamingWithEars @serrebi Sure thing. I'm submitting the issue. It seems that something in the URL triggers it as copying the link and attempting to listen to the clipboard contents generates the crash.
@GamingWithEars Well, no. As you reach the URL in, say, Mastodon in continuous reading, the crash occurs. So it's not necessarily copying it which brings about the crash. Rather, the add-on's attempt to process it at once does it. But the easiest way to duplicate it is copying it to the clipboard and pressing NVDA+C to listen to it. @serrebi
@GamingWithEars I fixed it with muse code. After I manually tested it to make sure, I"m submitting it to the repo, and linking it in the issue. Edit: Then amir who I shared my addon changes with clued me into a bug I'm trying to fix on it.
@serrebi @GamingWithEars Great.
@serrebi Yo! That's awesome!
@GamingWithEars Yes it is awesome.