WriteLog
[Top] [All Lists]

Re: [WriteLog] 2Tone

To: <writelog@contesting.com>
Subject: Re: [WriteLog] 2Tone
From: "Mark, G0MGX" <mark.g0mgx@gmail.com>
Date: Fri, 15 Feb 2013 05:39:00 -0000
List-post: <writelog@contesting.com">mailto:writelog@contesting.com>
Hi Gents

I'm new on the reflector so please excuse any Muppetry!

I run Writelog and Logger32 at the same time during RTTY contests. The
initial reason for wanting to do this was so I could use the Logger32 Radio
Control Panel - I have macros setup to control the radio contour, notch,
roofing filters and other settings. To get this to work correctly I have had
to set up a virtual serial port so that both applications can control the
radio through the same CAT port/cable. I ended up using an application from
www.eterlogic.com which is free for platforms other than Windows 7. I happen
to be running W7 64bit here...

The advantage of this setup now is that I can also turn on 2Tone from
Logger32 and have that as an alternate decoder for the RTTY signals, there
is no integration into Writelog (you cant click on the decodes in 2Tone and
have the calls and reports transfer into WriteLog), but you can easily
Eyeball the window and manually fix things on the fly. On my screen I have
the RTTYRite, MMTTY and 2Tone windows side by side.

Hope this is of interest.

Mark.
G0MGX

-----Original Message-----
From: Jerry Flanders [mailto:jeflanders@comcast.net] 
Sent: 15 February 2013 04:57
To: w0yk@msn.com; writelog@contesting.com
Subject: Re: [WriteLog] 2Tone

In the next contest I plan to use 2Tone standalone, without it being
"clickable" from WL. It should be straightforward to have logger32 running
but minimized and have 2Tone and its display panel somewhere on my screen so
I can eyeball it if my other WL decoders disagree.

It might be possible to record contest audio live, then play it back later
into multiple decoders to see which one wins.

Jerry W4UK

At 11:19 PM 2/14/2013, Ed Muns wrote:
>I've been wrestling with how to really evaluate 2Tone and concluded 
>that the only valid way is to have it fully integrated with the contest 
>logger and test it under fire in major RTTY contests.  Since the only 
>competitive RTTY contest logger that runs 2Tone right now is N1MM 
>Logger, I once again attempted to climb its learning after giving up four
years ago.
>
>Leading up to the CQ WPX RTTT Contest, I got into every RTTY contest 
>using N1MM Logger with MMTTY, DXP38 and 2Tone in parallel.  5-10% of 
>the time one of the three copied clearly while the other two did not.  
>In BARTG, each was best about the same amount of those times.  Of 
>course 90-95% of the time all three copied perfect and the same.  In FMRE,
2Tone was best far more often.
>This was from my CA QTH which is very different than Aruba, so I was 
>eager to see how the three decoders compared in the pileups down here.
>
>First some background.  I needed more than just to "run N1MM Logger".  
>I needed three networked PCs with SO2V running on each of two of them, 
>i.e., SO4V.  On each radio PC, 3-4 decoders ran on the main receiver 
>audio stream and a single instance of MMTTY ran on the sub-receiver 
>audio.  The third PC had no radio, but ran CC-Cluster and kept a third 
>copy of the log.  Callsign stacking had to work flawlessly on the two 
>radio PCs, along with ESM and a number key remappings.  There are more 
>details but that gives a notion of the complexity that I run with 
>WriteLog and needed to carry through to the N1MM Logger configuration.
>
>It seemed like I was making progress balancing all this complexity and 
>learning the idiosyncrasies of N1MM Logger.  During FMRE, the weekend 
>prior to WPX RTTY, I had pretty good confidence that all this would 
>work good enough.  However, as I evolved through the next week, I kept 
>running into unacceptable issues that I couldn't resolve well enough.  
>By late Thursday night I got cold feet and bailed.  Friday morning I 
>moved everything back to WriteLog.  As Don AA5AU and I discussed on 
>Thursday, I had to think about whether I wanted to risk having a 
>weekend of software application issues, as compared to having fun 
>contesting with WriteLog and its higher probability (for me) of running 
>smoothly.  I greatly regretted giving up 2Tone but I feel it was the 
>right decision for last weekend.  WriteLog ran the configuration 
>described above perfectly.  There were no glitches other than the usual 
>operator QLFs.  2Tone would have increased my rate by reducing the number
of repeats and allowing me to get more callsigns quicker.
>
>I have to say that K8UT, N2AMG, K6LL, W6SX and others were extremely 
>supportive as I struggled to re-learn and configure N1MM Logger for my 
>RTTY configuration.  It is the most used logger by far in the CQ RTTY 
>contests based on logs submitted.  A lot of top contesters use the 
>program and many of them use a lot of the advanced features.  So, there 
>is plenty of evidence that it should be able to measure up to the task.
>
>I plan to continue evaluating the feasibility of running N1MM Logger, 
>only because 2Tone is not available for WriteLog.  2Tone is the sole 
>reason I am considering using N1MM Logger.
>
>Ed P49X (W0YK)
>
>*******************************************************************
>
>Joe W4TV wrote;
>
>It's not likely that 2Tone can be used with Writelog.  2Tone emulates 
>the XMMT.ocx interface for MMTTY while the current MMTTY plug-in uses 
>the original shared memory interface in MMTTY.exe.  Using 2Tone would 
>require a completely new "plug-in" for WriteLog.
>
>
>On 2/12/2013 8:27 AM, Steve AI9T wrote:
> > Anyone figured out how to run 2Tone with Writelog yet?? It would be 
> > a nice addition.
>
>_______________________________________________
>WriteLog mailing list
>WriteLog@contesting.com
>http://lists.contesting.com/mailman/listinfo/writelog
>WriteLog on the web:  http://www.writelog.com/



_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web:  http://www.writelog.com/

<Prev in Thread] Current Thread [Next in Thread>