RE: Announcing availability of SSIP for Windows 1.3 beta
- From: "Macarty, Jay {PBSG}" <Jay.Macarty@xxxxxxxx>
- To: <programmingblind@xxxxxxxxxxxxx>
- Date: Mon, 11 Feb 2008 11:37:20 -0600
TJ,
Thanks for the feedback. I'll post the following on the website later today
(can't get to it from where I am). However, here's an overview of how remote
connection would work.
NOTE: I am experiencing firewall issues from my current location; so, the
sample program below is getting an error. However, I will confirm that it works
and make any adjustments before posting it to the documentation later today.
1. When you create an instance of the SSIP Client object, the default is to
look for the server on the local machine using localhost as the host name and
port 3891. If you want to override this behavior, you follow the steps below.
2. Install the SSIP software on the remote machine you wish to use and start it
running.
3. In the program on your local machine, Use either the GetInstance method for
the singleton or the regular constructor for the instance object and specify
false on the argument so that the client doesn't try to automatically connect
to the server.
4. If the SSIP server on the remote machine is running in its default mode, the
port will still be 3891. Therefore, you can use the client method call of the
form Connect(hostName) to connect to the remote SSIP server.
That's it. After the small change in your connect logic, everything else looks
the same. Any say method calls or any properties you get or set will actually
be routed to the remote SSIP server for handling.
I am including an altered version of the C# example program below showing how
one might use it to access SSIP on a remote machine:
using System;
using System.Collections;
using SSIP.Client;
namespace SSIP.Demo
{
public class SSIPClientRemoteDemo
{
public static void Main(string[] args)
{
SSIPClient voice = SSIPClient.GetInstance(false); // do not auto-connect
string sampleText = "";
// Connect to a remote SSIP server
voice.Connect("SomeRemoteServer");
if (voice.IsConnected)
{
voice.SayImportant("Welcome to the SSIP voice remote server demo");
}
else
{
Console.WriteLine("Could not contact remote host");
return;
}
string currentAPI = voice.SpeechAPI;
voice.SayMessage("The current speech API is " + currentAPI);
voice.SayText("press enter to here a list of the current speech APIs");
Console.ReadLine();
ArrayList APIList = voice.APIs;
foreach (string APIName in APIList)
{
voice.SayMessage(APIName);
} // end foreach loop
voice.SayMessage("Please enter a string to be spoken.");
sampleText = Console.ReadLine();
voice.SayText("You enter the string " + sampleText);
voice.SayNotify("thank You. Press enter to end the demo program.");
Console.ReadLine();
voice.PlaySoundIcon("complete");
voice.Close();
} // end main method
} // end class
} // end
________________________________
From: programmingblind-bounce@xxxxxxxxxxxxx
[mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of TJ McElroy
Sent: Monday, February 11, 2008 10:50 AM
To: programmingblind@xxxxxxxxxxxxx
Subject: Re: Announcing availability of SSIP for Windows 1.3 beta
Hello Jay,
If you get a chance, would you please explain how to set up your SSIP
so it can pass speech to a remote computer.
That is so f$$$ing cool!
Thanks for writing your SSIP.
TJ
----- Original Message -----
From: Macarty, Jay {PBSG} <mailto:Jay.Macarty@xxxxxxxx>
To: programmingblind@xxxxxxxxxxxxx
Sent: Monday, February 11, 2008 10:42 AM
Subject: RE: Announcing availability of SSIP for Windows 1.3
beta
Marlon,
I think I see what you are getting at. The easiest answer is
that once the COM interface to SSIP is available, there shouldn't be any reason
you couldn't call it from within a Jaws script; although, this is sort of the
reverse of its normal usage. The COM interface is to the client object, not
directly to the server; so, you could still use the COM calls to send speech
output to a remote machine.
-----Original Message-----
From: programmingblind-bounce@xxxxxxxxxxxxx
[mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Marlon Brandão de
Sousa
Sent: Monday, February 11, 2008 6:40 AM
To: programmingblind@xxxxxxxxxxxxx
Subject: Re: Announcing availability of SSIP for Windows 1.3
beta
Hello Jay,
I don't know if it is possible, or if it is legal, or if it is
documented, but is it possible to do a synthezizer driver for
jaws
which uses SSIP to output sound? This way one can set the jfw
synthezizer to send sounds to a SSIP server running remotely
and one
can have output speech from a remote machine this way ..
Marlon
2008/2/11, tribble <lauraeaves@xxxxxxxxx>:
> Hi -- not a comment on SSIP per se, but when I tried
following that link
> from the email IE7 failed to launch -- I had to call it and
paste the link
> in order to get to your page, which is fine, albeit a few
keystrokes extra.
> Anyone know why the link wouldn't activate from the email
(using OE)? Other
> links in other mails work fine.
> Cheers.
> --le
>
> ----- Original Message -----
> From: "Macarty, Jay {PBSG}" <Jay.Macarty@xxxxxxxx>
> To: <programmingblind@xxxxxxxxxxxxx>
> Sent: Sunday, February 10, 2008 10:09 PM
> Subject: Announcing availability of SSIP for Windows 1.3 beta
>
>
> Now available at
> http://www.remoteaccessbridge.com/ssip/
> is the first beta release of the SSIP for Windows server. The
link above
> is the SSIP page on the RemoteAccessBridge website. The page
has the
> following sections:
>
> Introduction to SSIP for Windows
> Simplifying SSIP usage through client wrappers
> Downloading the SSIP for Windows software
> Providing feedback or reporting bugs
>
> Please keep the following in mind as you install and try out
this
> product:
>
> 1. If you have suggestions or comments regarding this product
which are
> appropriate for a public forum, feel free to post them here.
However, I
> would encourage you to use the mailto link provided on the
web page.
> This will go to my RemoteAccessBridge mailbox and I will
compile a list
> of recommendations and bug reports to use in future releases.
>
> 2. The current installer does not have the ability to detect
whether the
> SSIP server is already running. If it is and you try to
re-install, the
> installer will error out because required files can't be
overwritten.
> Therefore, if you already have an installed and running copy
of the
> server, make sure you shut down the server before running the
install.
>
> 3. The client wrappers for both DotNet and java are included
with the
> installation. If you allow the installer to use the default
install
> directory, these will be located in c:\Program
> files\SSIP4Windows\Clients in the dotnet and java
subdirectories
> respectively.
>
> 4. The DotNet directory under Clients contains the
SSIPClient.dll
> assembly, a copy of the web documentation file, and both
source and
> executable code for a sample program called SSIPClientDemo.
>
> 5. While the java directory under Clients contains the
wrapper,
> SSIPClient1.0.jar, the sample class SSIPClientDemo.java is
not included
> with this release. You can, however, read the java client API
> documentation on the web page and can include the jar in your
projects
> with little difficulty; especially, if you use the source for
the C#
> class as a starting point. Keep in mind that the SSIPClient
for java
> makes use of some collections objects. It is suggested that
the client
> be used with java 1.4 or higher.
>
> 6. The server can run in 2 different modes; normal and debug.
In normal
> mode, there is no SSIP server window initially opened and
only a system
> tray icon is shown. Selecting the tray icon allows you to
either open
> the SSIP monitor console window or shut down the server. When
started in
> debug mode, another option on the SSIP for windows group
added to
> Start/All Programs, the monitor window is opened
automatically. This
> window allows you to see when client applications connect to
the server
> and what request/response strings are passed. Within the
monitor window,
> you have buttons to clear the console text or shut down the
SSIP server.
>
>
> 7. I have noticed that, from time to time, I have lost the
system tray
> icon even though the server continues to execute. When this
occurs in
> normal mode, there is no way of accessing the server to shut
it down
> aside from going to task manager and killing the process. Am
working on
> that little bug.
>
> So that's it for the initial release. I look forward to your
comments
> and suggestions. Also, now that the initial effort of setting
up the web
> page and getting the installer loaded out is done, making
updates should
> be a little simpler.
>
>
>
> ------------------------------------------------------------
> Jay Macarty - Masterfiles Technical Lead - PBSG
> Phone: 972-963-1387
> Cell: 214-549-3421
> __________
> View the list's information and change your settings at
> //www.freelists.org/list/programmingblind
>
> __________
> View the list's information and change your settings at
> //www.freelists.org/list/programmingblind
>
>
--
When you say "I wrote a program that crashed Windows," people
just
stare at you blankly and say "Hey, I got those with the system,
for
free."
Linus Torvalds
__________
View the list's information and change your settings at
//www.freelists.org/list/programmingblind
__________
View the list's information and change your settings at
//www.freelists.org/list/programmingblind
Other related posts:
