Tag Archives: reunion

Multimedia support in FTM for Mac – a bit lacking

Continuing my attempt to transition my family tree from Reunion to FTM for Mac, I wanted to discuss FTM’s handling of image listed in the GEDCOM file.

So first, I like the fact that FTM has a Media tab where you can view all images in your family tree file. That is something I’ve wanted from Reunion for a long time. That said, it seems FTM’s handling of the imported images is a bit sub-par. For starters, even though it has the correct path for each image file, it can’t seem to find them. Reunion exports the standard Mac (and UNIX) file path to each image, which in my case begins with a tilde (~) indicating that the file is in a sub-folder of my home folder. FTM doesn’t seem to know what that means. It lets you either search manually for the file or have FTM search for it. Either option works, but it would take forever for me to do this for each image.

Reunion has one very nice feature when a file goes missing (like if you move it to a different folder) where it lets you find the new location, and then it looks at all the other images that were in the same folder and updates them as well. This is a big timesaver and something FTM should emulate. THis in combination with the Media view that FTM offers would make a large task like changing all the image locations much easier to manage.

Truth be told, however, this task shouldn’t be needed at all by FTM – if it understood file paths properly this wouldn’t be an issue.

Taking a look at the GEDCOM file itself I can see that Reunion does something very nice – it exports the image cropping information. Frequently when using an image for a specific person you crop the image so it only shows that person. This is particularly true for the ‘primary’ image that one uses to represent the person in the tree. One can also use one group photo to crop out individual face shots of many different people. Showing the full image in a small window where you only want the head would be fairly useless. It’s not clear to me if the _CROP tag that Reunion uses is part of the GEDCOM standard or some kind of generally agreed-upon way to share that information, but it seems to me that FTM ignores the information. Worse, and the likely reason, I can’t figure out any way to crop photos in FTM at all.

I have a lot of complaints about Reunion’s handling of media. I think it should offer to keep a library of thumbnails or even web-resolution images itself, so that it doesn’t need to spend so much time doing image conversion when doing things like creating a web site based on your tree. I think it needs a central media view where you can manage all the images in your tree and make sure all the files can be located, etc. I think some integration with iPhoto would be nice. I think being able to tag photos with information on the people in them and the location information would be incredibly useful. Even with all of these complaints, FTM seems surprisingly inadequate when compared to Reunion in this area.

Launching Family Tree Maker for Mac and Importing a GEDCOM

I pre-ordered FTM for Mac when it was initially announced, and received it just recently. It comes on a single CD with a simple installer program on it. Launching the installer and running it, installs almost 500mb of stuff on your computer. Not exactly light-weight, but disk space is cheap these days, so that doesn’t bother me very much.

After installing it, I run the newly installed program and find it is a bit clunky when launching. It tells me that the program includes a free 2 week trial of Ancestry.com, and asks if I want to sign up, or if I already have an account to enter my login information. As I have an Ancestry.com account already, I enter my login details and continue. Things are a bit slow here, as I think it’s trying to communicate with Ancestry.com. I’m not sure how I feel about this connection from a privacy point of view. I certainly don’t like that it slows down the program.

The good side of the connection to Ancestry.com is that it allows the program to access Ancestry.com and try to find records connected to the people in your tree. This is a very nice feature, especially since it doesn’t require you to upload your whole tree to Ancestry.com where others can see it. If you want to publish your tree to Ancestry.com that is possible, but from what I understand syncing data between the online tree and the tree on your computer is not supported currently in the Mac version of FTM – but it is supported on the Windows version. A bit annoying.

The downside of Ancestry.com integration is the real question of how they protect your privacy. When you’re a member of their web site, you have ultimate control over what Ancestry has access to because they only know what you put on their site. Having access to the whole tree is a whole different issue, and not one I’m sure they’ve addressed. There’s no way to know what information is being sent back and forth. There’s also the issue that you need to have a paid account with Ancestry.com to use this feature, obviously. As I have an account already, this doesn’t affect me, but I wonder what features I will be missing if I decide to cancel my subscription to Ancestry.com?

So I exported a new GEDCOM from Reunion and told FTM to import it. The process was fairly quick, but it came up with over a hundred errors. I told it to load the error log, and something a bit bizarre happened – it launched the log in Notepad for Windows. Now you may be asking yourself how that is possible since I’m on a Mac – the answer being that I have a copy of Windows that runs in Parallels, an emulator. Even though Windows wasn’t running at that time, Parallels is ‘smart’ enough to know that a Windows filetype was launched and will try to launch it in Windows. Now, whether this is misconfiguration on my part with Parallels, or whether FTM actually created a file that is a Windows Notepad file, I’m not 100% sure, but I can say that this feature of Parallels has never before launched windows when the file wasn’t actually a Windows file, so I’m a bit confused. I think it would be nice of FTM to ask which text editor to use when launching text files (something Reunion does) to prevent this kind of mistake.

So what were the errors? They fall into two categories: Non-strict dates and non-standard GEDCOM tags. So first, it seems FTM is being strict about date formatting on import, which is not a bad thing, but annoying in that they don’t give you a way to fix these mistakes as you import. Reunion is actually very good about keeping date formatting strict, and converts all dates you enter into a standard format, but the dates that FTM rejected seem to be dates that I imported from relatives in other GEDCOM files. They include things like:

END MAY 1936
1932 OR 1935

These are obviously problematic for a strict date system, but I think FTM should have asked me to correct them. Perhaps Reunion did the same thing when I originally imported the GEDCOM they came from, I don’t remember, but there were not so many dates like that and it would be nice to fix them from the beginning. I’ll leave it to the BetterGEDCOM group to come up with a way to support fuzzy dates in a standard fashion.

The second problem was unrecognized tags. Reunion lets you create custom fields and assign GEDCOM tags to them for export. FTM doesn’t know what to do with these custom tags and does something very bad in my mind – it ignores them. Reunion actually added two of the fields that were ignored, a web site (tag URL) and an e-mail address (tag EMAL) that at some point was added to the profile of the exporter. It’s perfectly normal to add an address and contact information to the information in the GEDCOM file about the person who created it, but I guess e-mail and web sites were not common enough when the GEDCOM standard was last updated for these to be standard tags, and thus FTM ignores them.

The other custom tag, which makes up the bulk of the errors recorded by FTM on import, was the NAMR tag. I may may have made that one up myself, but frankly I don’t remember as it was such a long time ago. The tag is for the custom field I created for Religious Name. In Jewish parlance, the Shem Kodesh or Hebrew Name. For those people whose Hebrew Name I know, I add that to the custom field. Reunion exports it like any other fact about the person, which frankly is what it should do. Maybe FTM doesn’t support custom fields at all, I don’t know yet. If FTM does support custom fields and doesn’t offer a way to create such a field on import, that would be pretty dumb. As you might imagine, going through the error log and figuring out which people had a NAMR tag (the log only shows the line # of the error in the GEDCOM file) and then adding this fact to each record in FTM would be a mind-numbing experience that I would hope is not necessary. As my knowledge of FTM at this point is fairly minimal, I’ll hold judgment on this, but it doesn’t look particularly good.

Should I switch from Reunion 9 to Family Tree Maker for Mac?


So I’ve been using Reunion on my Mac for a long time. More than ten years at least. Probably more than 15. I like Reunion. For the most part I like the way it works, and even if the user interface is hopelessly out-of-date, I still like the user interface compared to many other genealogy programs on the Mac. Being more modern isn’t always better if the paradigm doesn’t work for you. I like Reunion’s family paradigm.

One thing I’ve always disliked about Reunion is the fact that it’s upgraded so infrequently. It’s been about three and a half years since the last major update. Before that it was about four and half years between upgrades. It’s true that there are lots of little updates and bug-fixes in-between upgrades, but this is not the same thing. There’s no excuse for upgrades that take four years. There are plenty of people that defend this upgrade policy, and say they don’t want to upgrade every year since it costs so much, but that’s a silly argument since I’d rather upgrade for $20 a year then pay $80 every four years. Leister, the company that makes Reunion, also does something else a bit maddening, which is that they absolutely refuse to mention anything about future versions until they are already shipping. Now, this would be so bad if they shipped new versions every year, but when your upgrade cycle is over four years, people begin to wonder if the product is actually going to be upgraded, or if they should start looking elsewhere…

Over the years I’ve tried just about every Mac genealogy program out there, and while some are very powerful, and some have great user interfaces, none have worked the way I wanted them to, and in the end I’ve always ended up back with Reunion. One program which has always intrigued my inner-nerd is GEDitCOM II, which is more of a genealogy development system, allowing you to create your own user interfaces and features, using AppleScript, Python or Ruby as scripting languages. One day when I have more time to spend on it, I will probably look more closely at it, although for the time being I like my genealogy program to be easy to use and quick when entering data, and I don’t want to think about scripting languages.

It’s always bothered me a bit that none of the ‘big’ genealogy programs out there had versions for the Mac. One of the most popular genealogy programs on Windows is Family Tree Maker (FTM), which while it has gone through a number of owners over the years, is now part of Ancestry.com. I was happy to hear they finally came out with a Mac version of their product, even if it based on a year-out-of-date version of the product (FTM for Mac is based on FTM 2010 for Windows, not the current FTM 2011 for Windows). Some people reading this are saying to themselves that there was a Mac version of FTM in the past, but that was so many versions and owners ago, I don’t really consider that to be anywhere near the same product. So FTM now has a Mac version – how does it stack up against Reunion?

Let’s find out together. As I try to transition my 2000+ person family tree from Reunion to FTM for Mac, I’ll be posting my impressions on this blog. Next posting – launching FTM for Mac and importing a GEDCOM.