Thanks Scot for that update to the group. I might add that I did beta
test the MMTTY Plug-in for WriteLog in last weekend's NAQP RTTY
contest and it performed extremely well. That is not to say that it is ready.
I'm not the one to determine that.
I used it in a 2nd RTTYrite window in parallel with my PK232 which I
ran in the 1st RTTYrite window by utilizing WriteLog's SO2R setup except
I used just one radio with paralleled receive from the rig going to the PK232
and soundcard. For transmit I used FSK from the PK232 in parallel with
FSK from COM 2 on my computer into the radio. This way I could transmit from
either
Entry window & from either RTTYrite screen. It was awesome.
The MMTTY receive outperformed the PK232 hands down. I saw the
difference despite most of the signals being strong from stateside. With the
pace of the contest so fast, I was not able to play with the many different
setups available with MMTTY. I used the basic, default setup and no AFC.
I made 560 QSO's in 10 hours with absolutely NO problems. I transmitted
several times from the MMTTY window but not nearly enough to tell
if it's 100% good.
Other than the outstanding receive MMTTY gives you, another great feature
is having three different and very useful tuning indicators - spectrum, scope
and waterfall. To me, the scope is the best.
Hopefully, Wayne and Ron will have it out soon. But it's their call.
73, Don AA5AU
----- Original Message -----
From: "Scot Herrick" <scot@k9jy.com>
To: "David Douglass" <vk2dpd@bigpond.com>; <writelog@contesting.com>
Sent: Monday, July 23, 2001 9:55 AM
Subject: RE: [WriteLog] MMTTYPluginforWritelog.Exe
>
> Hi David,
>
> MMTTY, in version 1.61B - in BETA testing, provides for an MMTTY 'engine'
> that can be used by other programs. You will note in the WL web site that
> the new version 10.27x - currently in BETA test - uses this engine as one of
> the TNC options in Rttyrite. WriteLog maintains the Rttyrite screen (where
> the printing is done) so that you can still click on calls and exchanges to
> automatically fill in your Log Entry window, but uses the MMTTY engine for
> decoding the RTTY signals (and it has that nice waterfall display that a lot
> of people like; it's really a sharp looking interface).
>
> The key words here are BETA TESTING. Both in MMTTY and in WriteLog. As a
> beta tester I can tell you that it will be very nice but it also needs a lot
> of work between the two programs to make sure it meets the stringent
> standards of the WriteLog users for programs. This one is a little more
> difficult in that two programs are in a beta testing mode, not just one. You
> don't want all the page faults where you have to shut down the PC and start
> over in the middle of the contest, trust me.
>
> But when it's done, it will be pretty slick. Have some patience, it looks
> like - if the two programs can fix the problems - that it's coming.
>
> CU...Scot, K9JY
>
> See WriteLog's complete user manual at
> K9JY's WriteLog site http://www.k9jy.com
>
> mailto:scot@k9jy.com
>
> > Hi All,
> >
> > Just discovered that there is MMTTY support for WriteLog.
> >
> > Can anybody point me in the right direction as to where I can get some
> > information on this!! Or if there has been any previous discussion on this
> > on the reflector.
> >
> > I'm one of the few people who have never been able to hit it off with
> > Rttyrite, and have always used other software in the RTTY contests (either
> > TrueTTY or MMTTY), although I use WriteLog in CW and SSB tests.
> >
> > Thanks in advance
> >
> > David
> >
> > vk2dpd@qsl.net
> > vk2dpd@bigpond.com
> >
> >
> >
> > --
> > WWW: http://www.writelog.com/
> > Submissions: writelog@contesting.com
> > Administrative requests: writelog-REQUEST@contesting.com
> > Problems: owner-writelog@contesting.com
> >
>
>
> --
> WWW: http://www.writelog.com/
> Submissions: writelog@contesting.com
> Administrative requests: writelog-REQUEST@contesting.com
> Problems: owner-writelog@contesting.com
>
>
--
WWW: http://www.writelog.com/
Submissions: writelog@contesting.com
Administrative requests: writelog-REQUEST@contesting.com
Problems: owner-writelog@contesting.com
|