-
Notifications
You must be signed in to change notification settings - Fork 4
we really need some kind of 64 bit bridge #1
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
Comments
This is planned for the next release, but I haven't found a way to do it yet. |
Assume something like this resource in Microsoft Docs has been seen by you already? |
Hello. JAWS have both profiles e.g sappi5x and sappi5x64. I tried in sappi5x, but there's no new voice is showing. So i can't use it with that too. |
@datajake1999, perhaps go to build menu and select configurations and mey bee add release x64 and debug x64? |
Hello,
While it could be possible to compile it for 64-bit, I think we'd need to write a bridge, since the IBM TTS files aren't 64-bit.
I do agree though that if this could happen you could reach more users.
Thanks,
Brandon
…Sent from my iPhone
On Aug 30, 2021, at 2:33 AM, bhanuponguru ***@***.***> wrote:
@datajake1999, perhaps go to build menu and select configurations and mey bee add release x64 and debug x64?
and, please adapt this to latest vc. because it's confertble to edit form vs and build. and latest vs is quite good in my openion. that way we can make configurations for debug x64 and release x64.
i was trying to convert that dsp file to latest sln file, or i tryed to export the makefile from vc6 and tryed to compile using that makefile using latest vc, but din't work.
of course, i will send a pr if once my atempt is successfull, that is if i compiled to 64 bit, that is when i get it working with latest vs2019
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
|
Basically the way you'd have to do this is create a 64-bit DLL that exports the same functions, but just runs a 32-bit executable with command line parameters that specifies what DLL function to call, and somehow pipes the speech back to the host. |
For an example of software that's done this, JAWS for Windows' FSSynth32.exe is a bridge for the Eloquence support. |
Hello,
As for that, I think FSSynth32.exe is not only responsible for Eloquence, but also powers the SAPI5X (32-bit) SAPI support.
I believe you could confirm this by having JAWS use the SAPI5 IBMTTS and restarting JAWS, but I could be wrong.
Thanks,
Brandon
…Sent from my iPhone
On Feb 4, 2022, at 10:32 AM, Quin ***@***.***> wrote:
For an example of software that's done this, JAWS for Windows' FSSynth32.exe is a bridge for the Eloquence support.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you commented.
|
This is incorrect. JAWS does SAPI5 through raw COM objects. |
Hi,
Is that for 32 bit?
Wouldn't it somehow have to bridge if you use the 64 bit JAWS?
Thanks,
Brandon
…Sent from my iPhone
On Feb 15, 2022, at 5:09 PM, Quin ***@***.***> wrote:
This is incorrect. JAWS does SAPI5 through raw COM objects.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you commented.
|
hello. Do you have any update? You have left this project abandoned for 3 years and it should be time to get new updates. |
Great job for making this happen! It's stable unlike the other tries I've tried before.
One problem, though: a lot of modern 64 bit games and things can use only 64 bit voices, so we really need to brainstorm some kind of way to bridge it. Perhaps make a generic forwarder SAPI voice (kinda like NVDA SAPI) that will then call a 32bit executable to call the 32bit ibmeci.dll or something. It sucks not being able to use it in 64 bit things.
The text was updated successfully, but these errors were encountered: