Wayne,

I'd agree with everything you said, except that at least in my setup, 
JAWS reads character by character without repeats.

I'm familiar with what you describe, I've seen it in Digipan and other 
psk programs.  To get the single word "hello" you get something like:
H  He  Hell hello

That gets real old real fast.  For whatever reason, MMTTY doesn't behave 
that way  over several computers, several operating systems, and several 
versions of jaws.   I suppose that spelling by letter isn't the way God 
intended things, but since all my RTTY work is either contests or DX 
chasing, where it's just a call and exchange, it works well for me.

73 and tnx for your input,
Steve KW3A



On 2/16/2011 2:08 PM, Wayne wrote:
> Well you have to get the signal tuned correctly.   The mark tone at 2125hz
> and space at 2295hz or about that.  the level should be set so that noise
> isn't to high.   There a couple of test files with the documentation you
> could play in to your sound card to test the computer program decoding
> without the radio.
> The trouble with most of these things is the way the screen reader reads the
> characters as they scroll on the screen.   As the first character appears it
> reads it then the second is read along with the first and then the third
> making it real confusing.   You might just have to use the mouse cursor
> after the line is printed to read it.
> The test files would eliminate the problem of tuning the signal and let you
> check if the screen reader and program are working properly without having
> to deal with tuning the signal.   You would still have to get the correct
> level by adjusting the line-in which shouldn't be much.
> You would also could hear how the mark and space tones should sound when a
> signal is properly tuned.
>
> Wayne
>
> ----- Original Message -----
> From: "Michael Ryan"<[log in to unmask]>
> To:<[log in to unmask]>
> Sent: Wednesday, February 16, 2011 8:07 AM
> Subject: Didn't think RTTY was Rocket Science LOL
>
>
>> Hi all:=20
>> I'm still struggling with decoding RTTY signals and its not going
>> well.=20=
>>
>> I've got everything narrowed down as tight as I can get it and I'm =
>> slowly tuning across RTTY signals, some of which are vary strong, 59 and =
>> higher.=20
>> I tried both Jaws and Window Eyes and didn't find a difference in how =
>> the scrolling text was presented and as I'm more acquainted with WE, =
>> decided to stick with that and set the reader to speak all to listen to =
>> the scrolling gibberish. =20
>> I did manage to hit pieces of QSOs in english and when I did, =
>> immediately stopped tuning. However, once the text was read and a new =
>> piece of data was received, it would be back to gibberish and I wouldn't =
>> try and fine tune.=20
>> I use MTTY and I don't know if I'm supposed to have the scope on the =
>> screen, didn't make a difference in the gibberish when turned it off and =
>> as well, I got my XYL to assist me and she didn't know what to look for =
>> while I was tuning except the english of course. Are there supposed to =
>> be any indicators that I could tell my XYL to line up for me?=20
>> As well, are there any spoken clews to listen out for?  I mainly fine =
>> tune across the signals and the gibberish doesn't change to english for =
>> the most part.=20
>> Mostly fluke that I managed to get pieces thus far. Example: I'd tune =
>> from 14.085 to 14.086 in probably .05 increments. IE: one tap of my up =
>> arrow would give me a freq of 14.08505. =20
>> I do have my interface set properly for receive, no overflows.  Filter =
>> setting of my rig: Narrows filter engaged, about 2.4KHZ I'm guessing, IF =
>> Shift 2 -1000 which I'm thinking takes 1000 from that thus give me 1.4.
>> =20=
>>
>>
>> 73:=20
>>
>> Michael De VO1RYN=20
>>
>