Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. General Programming
  3. C / C++ / MFC
  4. SAPI and 3rd Party Voice Engines

SAPI and 3rd Party Voice Engines

Scheduled Pinned Locked Moved C / C++ / MFC
windows-adminquestion
1 Posts 1 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • M Offline
    M Offline
    Mangesh Sardesai
    wrote on last edited by
    #1

    I have installed SAPI5.1 on win2k machine. I also have L & H German language engine installed. I am trying to access the L&H voices programatically. However the ISPVoice Interface is unable to use L&H voices. I checked out the registry keys HKLM\\Microsoft\Speech\Voices\Token\ but didnt found any entry for L&H voice. Strangely enough when installed on another machine the entries were found along with extra files installed at C:\Program Files\Common Files\L&H\SpeechEngines\1031\TTS\TTS3000\ I tried installing installing the same downloads on different machine but in vain. None of them showed these required entries and these extra files... Can anyone throw some light on this weird behavior???? :confused::confused::confused: M$

    1 Reply Last reply
    0
    Reply
    • Reply as topic
    Log in to reply
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes


    • Login

    • Don't have an account? Register

    • Login or register to search.
    • First post
      Last post
    0
    • Categories
    • Recent
    • Tags
    • Popular
    • World
    • Users
    • Groups