| |
EB2DVY > PSK31 24.12.99 15:16l 145 Lines 5197 Bytes #-9713 (0) @ WW.SYD.NSW.
BID : 770-EB2DVY
Read: OE1RRB GUEST
Subj: PSK31 Digest V1 #264
Path: OE1XAB<OE3XSR<OK0PPR<OK0PRG<OK0PAB<HA5OB<WU3V<WB0TAX<KP4IG<EA3RKU<
EA5AKC<EA5RKV<EA5DVS<EA5DV<EA5RCI<EA5VDR<EA3B<ED3ZAD<ED3ZAA<EA3AXS<
EA2C<EA2N<EA1URR<EA1URM<EA2RCF<EA2URV
Sent: 991223/2135Z @:EA2URV.EABI.ESP.EU #:32712 [URV-ABRA Bilbao] $:770-EB2DVY
From: EB2DVY@EA2URV.EABI.ESP.EU
To : PSK31@WW.SYD.NSW.AUS.OC
De: Psk31 Digest <owner-psk31@bipt106.bi.ehu.es>
Para: <psk31-digest@bipt106.bi.ehu.es>
Asunto: Psk31 Digest V1 #264
Fecha: martes 21 de diciembre de 1999 4:19
Psk31 Digest Tuesday, December 21 1999 Volume 01 : Number 264
In this issue:
[psk31] twpsk for Linux PSK31
[psk31] New WinPSK Home
Re: [psk31] New WinPSK Home
See the end of the digest for information about psk31-digest
----------------------------------------------------------------------
Date: Mon, 20 Dec 1999 11:09:31 -0500
From: "Williams, Ted" <ted@Bluestone.com>
Subject: [psk31] twpsk for Linux PSK31
Hi Guys,
Just uploaded twpsk-0.7 - PSK31 for Linux. It is at the metalab.unc.edu ftp
site
in the "/pub/Linux/incoming" directory, and will be moved to the
"/pub/Linux/apps/ham"
directory sometime soon.
Happy Holidays es 73
Ted - WA0EIR
Ted Williams - Bluestone Software
ted@bluestone.com
http://www.bluestone.com
Phone 609-727-4600 ext. 1180
Fax 609-778-4925
------------------------------
Date: Mon, 20 Dec 1999 18:37:37 -0500
From: Moe Wheatley <ae4jy@mindspring.com>
Subject: [psk31] New WinPSK Home
Winpsk now has a new home at:
http://ae4jy.virtualave.net/
I will put all the latest stuff there from now on. Thanks to all who have
helped in the meantime.
A new version is there which hopefully will resolve a few bugs and the
crashing problem but no guarantees since I could never get it to crater
here. The documentation package will not be updated until the non-beta
version is released hopefully soon after we all crawl out of our Y2K bunkers
Jan 1.
I will try to answer a few general questions/comments people have had.
1. WinPSK is too slow. Or the one I liked the best, "WinPSK is Lumpy!"
The program processes sound card data in much bigger chunks than the others.
This is to support the large appetite of the 4096 pt FFT spectral view.
Your PC has to wait .743 Seconds to get enough data to begin processing.
The actual processing doesn't take but 10's of milliseconds. The effect
though is that the display and text all change at once every .743 seconds
giving it the "lumpy" feel. The send/receive data rates are not slower.
There are much longer rx/tx turnaround times so this program probably isn't
much good for contesting.
2. Need a lot more macros.
I resist adding more macros for the following reason. I think Peter's
intent for this mode is for more human to human conversation rather than a
bunch of canned text exchanges between computers. Perhaps someone can give
a good reason for 40 or 50 macros. There's probably room for a couple more
on the current screen layout.
3. The CW ID does not have correct spacing.
Winpsk uses the same wave-shaping and timing rate as the PSK31 signals and
so the choice of code speed is fixed to multiples of the data rate( .032 Sec
) I compromised spacing integrity for a little faster speed. Unless there
are legal reasons for sending perfect code, I'd prefer not to wait so long
for the id. The alternative is to design a whole separate CW modulation
system which is not in the near future.
4. How about non-English support?
I am open to helping localize the program but being a dumb uni-lingual
person, I will need lots of help. Pauli, EA3BLQ, has offered to work on the
help file translation. Perhaps there is a UNICODE expert out there??
5. I will pre-empt this question before it is asked. When will you add rig
control, logging, more digital modes, callsign lookup, spell checker, word
processing, spreadsheet, email, autoCAD support, etc.
Not in my lifetime. I did this for fun/education, and spending the rest of
my life dinking with this thing would put an end to that in short order.
WinPSK future:
I will continue fixing problems as the are reported, improve the receiver a
bit, and add little things if they seem helpful. Since the source code will
be available, my hope is that someone will step forward and take this thing
over, rename it, and I'm out of the loop.
My reservation on giving out the source code is that some may modify it,
keep my name on it, distribute it, and then I will be chasing down other's
problems. If this happens then I will bail out real quick.
One way around this is that if someone modifies/improves something, send me
a well documented description of the change and I can incorporate it and
maintain it.
Sorry for the long post, Happy Holidays
73's
moe, ae4jy
------------------------------
Date: Mon, 20 Dec 1999 19:24:42 -0700
From: "WD7F" <wd7f@eiis.net>
Subject: Re: [psk31] New WinPSK Home
Hey, I downloaded it and about 10 minutes later I would say "I LIKE IT"!
Good job, but I do understand the "Lumpy" comments, however, I think I can
live with it. I'd say that you got a pretty intuitive program here. That's
one of my pet peeves with lots of software. Why don't the programmers make
it more easy to understand right out of the box? Oh, sure, I've done PSK
before so I know what to look for, but I still think it's pretty darned
good.
Thanks Moe.
de WD7F
John in Tucson
------------------------------
End of Psk31 Digest V1 #264
***************************
Read previous mail | Read next mail
| |
