| |
EB2DVY > PSK31 19.12.99 18:43l 148 Lines 6684 Bytes #-9718 (0) @ WW.SYD.NSW.
BID : 753-EB2DVY
Read: OE1BHS OE1RRB GUEST
Subj: PSK31 Digest V1 #256
Path: OE1XAB<OE3XPR<OE3XBS<OE3XSR<OK0PBX<OK0PRG<OK0PAB<HA5OB<HA5KDF<HG1PSO<
HG1KZC<9A0YDA<9A0YKZ<S50BOX<IW3GRX<I3KUH<IW2KTL<I1YLM<IK2QCA<IW5BFZ<
IK1MVX<TK5KP<F6KOE<F5IX<F6KED<F5KPO<F5KAT<EA3D<EA3B<ED3ZAD<ED3ZAA<
EA3AXS<EA2C<EA2N<EA1URR<EA1URM<EA2RCF<EA2G<EA2URV
Sent: 991218/1313Z @:EA2URV.EABI.ESP.EU #:31835 [URV-ABRA Bilbao] $:753-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 #256
Fecha: sßbado 11 de diciembre de 1999 4:18
Psk31 Digest Saturday, December 11 1999 Volume 01 : Number 256
In this issue:
[psk31] French PSK31 for SB 1.05 help file (in .pdf format)
Re: [psk31] Pictures by PSK31!
See the end of the digest for information about psk31-digest
----------------------------------------------------------------------
Date: Fri, 10 Dec 1999 16:36:31 +0100
From: Eduardo Jacob <jtpjatae@bicc00.bi.ehu.es>
Subject: [psk31] French PSK31 for SB 1.05 help file (in .pdf format)
There is a new .pdf file in french translated from the p31sbw105 help file by
Maurice F6IIE. It's available as:
ftp://det.bi.ehu.es/pub/ham/psk31/p31sbw105pdf-f.pdf
and
http://www.kender.es/~edu/download/p31sbw105pdf-f.pdf
Eduardo/EA2BAJ
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
to unsuscribe from the list send to majordomo@aintel.bi.ehu.es a message
with a text line as follow: unsubscribe psk31 or unsubscribe psk31-digest
More instructions on PSK31 Webpage: http://aintel.bi.ehu.es/psk31.html
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
------------------------------
Date: Fri, 10 Dec 1999 18:53:09 -0500
From: "Robert Lay" <w9dmk@crosslink.net>
Subject: Re: [psk31] Pictures by PSK31!
Dear Howard and ALL PSKers,
The initial message about sending pictures via PSK31 piqued my interest, so I
tried it.
Here are some comments about my first experiments.
I used the suggested program, IRFANVIEW32 as the image processing program and
created a 60 x 80 pixel image in JPG format.
I then encoded it using the recommended BINHEX ver 4.0 program, and that
produced a file "name.hqx" of 4096 bytes. The actual file produced is whatever
file name was assigned to the JPG file except with an HQX suffix.
My first experiment with PSK31 was to send the resulting file from my primary
PSK31 station to my secondary PSK31 station in order to guarantee a clean file
at the other end and to be sure that there were no characters that would not
pass through PSK31 processing properly. The file at the receiving end was
captured as "psk31.log" and then edited in an ASCII text editor to make certain
that there was no header or trailer garbage that might corrupt the decode
process. I then used BINHEX to decode the file instead of using the recommended
"decode shell extension". It worked fine and the decoded JPG file opened in
Paint Shop Pro, v 3.0, and looked fine.
I did not use the "decode shell extension" for decoding for two reasons. First,
I am wary of contaminating my Internet Explorer or my Outlook Express mail
system with any 3rd party add-ons. Second, the BINHEX program decodes as well as
it encodes, so why not use it? It may not be as slick as just clicking on the
file and having it automatically decoded, but I was in no hurry.
I then decided to evaluate the encode/decode system for vulnerability to
corruption, since Warren had warned that the transmission must be perfect.
I found that it is very difficult to characterize the process with respect to
the different types of corruption that may occur in normal transmissions.
Dropped characters, noise characters and bad characters are all possible. I
found that a character or two that is dropped or inserted or corrupted does not
usually cause the file to be completely trashed. In fact, a few bad characters
here or there do not seem to bother the BINHEX program at decode time. However,
any gross errors, such as an entire 64 character line being lost seems to trash
the file. It is possible to get swaths of garbage in the image and it is
possible to have the image viewing program decide that it cannot display the
image. But BINHEX seems to muddle through and produce something, even if it
grumbles about it. Whenever you get a message in BINHEX telling you that it
should be decoded with version 3.0 or version 5.0, you know that it is having
problems with the file.
I did not experiment with Monochrome pictures, nor did I experiment with sizes
other than 60x80 pixels. However, I did experiment with PSP v 3.0 as a picture
re-sizeing tool instead of the recommended IRFANVIEW32 program. I found PSP to
be a very simple tool to use for simply scaling a picture to a smaller size. All
you do is Image->Resize and then enter the height and width in pixels for the
new image and then save it.
If you use the Microsoft Paint applet that is part of Windows, you can cut and
paste a portion of an image and then crop it with Image->Attributes and produce
good results. You can use the KODAK Imaging program that comes with Windows 98,
also, but I find it difficult to use in comparison with the others.
There does not seem to be anything magic about JPG image files - you should be
able to use any image format - of course the receiving station has to have a
viewer for that format.
There does not seem to be anything magic about 60x80 pixels - it's only a
question of how much time do you burn up sending the image, and Warren is quite
correct in regard to the risks of transmissions exceeding 10 minutes.
The procedures outlined by Warren in his original post are very good -
especially since some sort of standardized and documented procedure is necessary
to reduce the initial confusion. However, there is a lot more flexibility in the
basic utilities and in the basic concept than what comes through from the first
reading. A little off-line experimentation will be very educational and will
make it clear that there are many ways to accomplish the same results - so long
as you know what you are doing and are careful. The one thing that MUST be
followed religiously, if the recipient is to be able to decode the image, is
that you MUST use BINHEX as the encoding method. Otherwise, the recipient will
have no idea what decoder to use to reconstitute the image, and you are on your
own in trying to set a new or different standard.
73 de Bob Lay, w9dmk@arrl.net, King George, VA
http://www.qsl.net/w9dmk
http://www.fortunecity.com/meltingpot/albania/784
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
to unsuscribe from the list send to majordomo@aintel.bi.ehu.es a message
with a text line as follow: unsubscribe psk31 or unsubscribe psk31-digest
More instructions on PSK31 Webpage: http://aintel.bi.ehu.es/psk31.html
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
------------------------------
End of Psk31 Digest V1 #256
***************************
Read previous mail | Read next mail
| |
