[Bug 59582] New: TextAloud 3: custom NextUp/Acapela SAPI5 voice installs but is not enumerated under WoW64, while built-in voices work

[WineHQ Bugzilla]

http://bugs.winehq.org/show_bug.cgi?id=59582

            Bug ID: 59582
           Summary: TextAloud 3: custom NextUp/Acapela SAPI5 voice
                    installs but is not enumerated under WoW64, while
                    built-in voices work
           Product: Wine
           Version: 10.0
          Hardware: x86-64
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: -unknown
          Assignee: [e-mail]
          Reporter: [e-mail]
      Distribution: ---

TextAloud 3 starts under Wine WoW64 well enough to run, but an older
NextUp/Acapela SAPI5 voice does not become usable after installation.

This setup previously worked for me in an older real 32-bit Wine prefix. In a
newer WoW64 setup, I could not use speechsdk normally because winetricks
reported: "This package (speechsdk) does not work on a 64-bit installation. You
must use a prefix made with WINEARCH=win32." To continue testing, I had to
install speechsdk with winetricks --force.

After forcing speechsdk, TextAloud starts and the voices that come with the
Microsoft Speech SDK appear and work. However, newly installed third-party
SAPI5 voices do not work the same way. In my case, an old NextUp/Acapela voice
installer copies the voice files successfully, but the voice does not become
properly usable/enumerated in TextAloud.

What works:
- TextAloud 3 starts
- built-in Microsoft / Speech SDK voices are listed
- the third-party voice installer copies its files

What does not work:
- the newly installed third-party voice does not appear as a usable voice in
TextAloud
- comparing with my old working 32-bit prefix, the behavior is not the same
- manually copying registry entries from the old prefix did not restore full
functionality

I also tested manual registry fixes for the Acapela-related entries and CLSID
registration. That was not enough to make the custom voice usable.

So the practical result is: under WoW64, forcing speechsdk gives partial
functionality only. Built-in voices work, but newly installed third-party SAPI5
voices do not work correctly.

This looks like a WoW64 compatibility problem for older SAPI5/third-party voice
setups that previously worked in a real 32-bit Wine prefix.

Current workaround: I can still use the application through Lutris with Wine-GE
8-26 x86_64, but only by reusing my previously created and already-working
32-bit prefix. That prefix was set up before the newer WoW64 changes. I have
not tested whether the same setup can be reproduced from scratch under Wine-GE
8-26 x86_64.

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.