MACLOGGERDX CONTESTS FULL
MACLOGGERDX CONTESTS SOFTWARE
MACLOGGERDX CONTESTS LICENSE
MACLOGGERDX CONTESTS MAC

There are a lot of map options that are fun. There is a Stacking register that allows you to keep up with calls/frequencies and easily tune back to them which is nice. Just because some information is available doesn't mean you need to log it!īut I kept looking at the program, and while it did do some fairly stupid things, it did some other things very nicely indeed.

MACLOGGERDX CONTESTS LICENSE

But really, why would I want to put in my log when the other station's license is going to expire? Crazy. Whew! Now, there may be a flag in the preferences that allows me to turn this off, but I never did see it. For instance, the following was entered with no prompting from me in the last QSO I entered into MLDX:Ĭlass: E, efdate:, expdate:, GMT:-5, qrzloc:user, Uploaded to ClubLog 02:16 It is automatically populated with a bunch of needless 'stuff' when doing a lookup on a station. But I figured I could live with it - IMO though, it just detracts from the appearance of the log - a log whose main advantage is it's appearance.Īnother problematic item is the Notes or Comments field. That is very busy to look at and needlessly detailed for most purposes.

MACLOGGERDX CONTESTS FULL

Particularly, the Time fields are a full timestamp displayed as YYYY-MM-DD HH:MM:SS.

MLDX pretty much assumes the user will be using an online callsign lookup service such as QRZ.com.Īlso, the formatting of some items is fairly questionable as well. For example, in addition to 'normal', expected fields such as First Name, State, Frequency, Mode, Reports and Notes, there are questionable fields such as Last Name, Street, City, State, Email, IOTA, SOTA, 10/10, etc. There are fields that, IMO, just aren't necessary to display for average QSOs. I can see advantages to both schemes I suppose, but when actively evaluating, the 15 minute sessions are a PITA, but I sat down with the program, manual, and online forum to give it my best shot.Īfter importing my 5000+ QSO QRP-only log from the past three years, the first thing I noticed is that the QSO entry area is very busy on MLDX.

MACLOGGERDX CONTESTS SOFTWARE

The first thing I noticed is that 15 minutes is a very short time to spend with a complicated program when you don't know anything about how it works! Most software packages I've run across will do something similar, but give you a two-week to 30-day trial period. Fair enough, I can give it a try before buying. MLDX is $95, but has a trial scheme in that you can use the non-crippled program as much as you'd like prior to buying, with the only limitation being that the program times out after 15 minutes. It's not a bad program at all, but I had had many recommendations to try MLDX, so I decided I would. There are things about RUMLog that remind me of Logger32, and as freeware, the price is right, so I decided to give it a try. Both applications have user forums online in which the developers participate, but the MLDX forum seems to have the larger and more active user base of the two.

The two that seemed most interesting were RUMLog by Tom Lindner, DL2RUM and MacLoggerDX (MLDX) by Don Agro, VE3VRW. Keeping that as a fall-back solution, I wanted to run a native OSX application, so I began seriously looking for a logging program. I also knew based on personal experience and anecdotal reports that I could probably keep running Logger32 in a virtual machine on the Mac, but did not want to do it that way if I could help it.

MACLOGGERDX CONTESTS MAC

We converted to Macs at work about four years ago, so I'm fairly familiar with them, and have had my own Mac in my sights for a long time, so I'd done some research regarding logging software already, and knew there weren't nearly as many players as in the Windows world. As a DXer, it does everything I need a logging program to do.not as fancy as some of the programs out there, but the features it has are solid and useful. There is good documentation by a dedicated team of folks, as well as an active Yahoo group that includes regular participation by the program's originator Bob Furser, K4CY. Relatively complicated to set up, but once that is done, it works pretty flawlessly. I have used Logger32 for a long time, it has a decent feature set, and is highly configurable. With the acquisition of a Mac Mini to replace a very tired Windows XP laptop, came the need to convert my daily logging system from Logger32 to an OSX solution.

Macloggerdx contests