rubiTrack supports many kinds of devices via direct sync which imports activities directly from the device connected to your Mac. In addition rubiTrack supports activity file import for other devices that do not support direct sync.

^MTA Direct sync with MTP-devices requires rubiTrack PRO.

rubiTrack supports the following file formats. If you have a file format you would like to see supported by rubiTrack email us.

rubiTrack supports the following cloud services.

If you find a problem please do not hesitate to let us know and email us. We appreciate your feedback!

As of August 2022 the forum is no longer available.

That doesn't mean you are on your own! We remain at your disposal for any questions or problems you may have.

rubiTrack 6 is compatible with macOS 14 Sonoma, 13 Ventura, 12 Monterey, 11 Big Sur, 10.15 Catalina, 10.14 Mojave, 10.13 High Sierra. WiFi sync requires a Mac built 2012 or later.

rubiTrack 6 is available for iPhone running iOS 12 or later.

If you can't remember where your rubiTrack file is located on your hard disk:

rubiTrack 6, rubiTrack 5, rubiTrack 4

1. Start rubiTrack (your file will be opened automatically).
2. Select "File > Show In Finder" from the main menu.

Older Versions

1. Start rubiTrack (your file will be opened automatically).
2. Hold the COMMAND key and click into the filename in the title bar of the rubiTrack main window.
3. A menu will open that shows the full path.
4. Select the first folder in the menu to switch to Finder.

All you need to do is open your rubiTrack 5/4/3/2 file in rubiTrack 6 via "File > Open…" from the main menu.

First you need to know where your put your old file (see Where is my rubiTrack file?).

1. Start rubiTrack 6.
2. Select "File > Open…" from the main menu.
3. Select your old rubiTrack file.
4. rubiTrack 6 will offer to upgrade the data, click "Upgrade".
5. Select a new file name for the upgraded data, then continue.

Depending on the version you are upgrading from, the upgrade process may take some time to complete.

Your Garmin device may not show up as a volume when connected to your Mac. In that case, it uses a connection type known as Media Transfer Protocol. Since version 6.2.2, rubiTrack 6 PRO is able to access such devices.

Setup

1. Plug in your device into a USB socket (if you have more than one type of socket on your Mac, use USB-A).
2. Quit any apps on your Mac that connect to the device (Android File Transfer, Garmin Express).
3. Turn on "MTP Device Sync" in the application preferences via "rubiTrack > Preferences >> Advanced > MTP Device".
4. Wait until the device is ready, usually indicated by a charging message.
5. In the rubiTrack Sync Manager, sync using the "Connected Device" item.

Depending on the number of activities stored on the device, your first sync may take a long time. Subsequent syncs will be much faster.

Pro Tip: If you are using rubiTrack's "Cloud Backup" feature, it will automatically save a backup copy of any activity file downloaded from the device.

Troubleshooting

If rubiTrack doesn't download the data as expected, try this:

• Plug your Garmin device into a different USB port (prefer USB-A over USB-C).
• Make sure no other app is running that may use the device (Android File Transfer, Garmin Express).
• Unplug other non-essential hardware that is connected via USB (such as SSD, iPhone, USB stick)
• Connect your device directly to your Mac, instead of going through a USB-hub.

If no data gets transferred, you can verify that rubiTrack is able read the device's content:

1. Open the application preferences via "rubiTrack > Preferences >> Advanced".
2. Click the button labeled "MTP Device Info".
3. If rubiTrack can read the device, it will show a directory listing of the device after a short time. You can copy this information into an email and send it to us.
4. If rubiTrack cannot read the device, an error message will be displayed.
5. In either case please email us and tell us which device you were using.
   Email to rubiTrack support

Feedback appreciated!

This is an experimental feature! So, if it works (which it should, despite the experimental status), let us know - and let us know the device you were using.

If you have a Garmin device connected to your Mac via USB and direct device syncing does not work, go through the following checklist:

1. Does the device mount as a volume when connected to your Mac?
   • Beginning with version 6.2.2, rubiTrack 6 PRO is able to access devices that don't mount as volume, too.
   • Check out the FAQ entry above about MTP devices.
2. If it mounts as a volume, is the volume name "GARMIN"?
   • By default Garmin devices use the volume name "GARMIN" (all caps). rubiTrack 6 cannot access the device if it has been renamed because of restrictions by Apple for apps from the App Store.
3. Does rubiTrack 6 have permission to access the volume?
   • Check the System Preferences' "Privacy" section and verify that rubiTrack 6 is granted permission to access Removable Volumes.

If the answers to all of the above questions is "YES", you should have no problem direct-syncing your Garmin device. If you still have problems contact us.

Beginning with version 6.0, rubiTrack supports the official Garmin Connect API.

After authorizing with Garmin Connect, any new activities uploaded to Garmin Connect will become available for syncing with rubiTrack for a limited time. In order to fill gaps in your activities or import activities from the past, you may use the Backfill feature in rubiTrack's Sync Manager.

The following rules apply to Garmin Connect access:

• There is a download window of 60 calendar days for new and backfilled activities.
• Once an activity is downloaded from Garmin Connect, you cannot download it a second time.
• You cannot authorize your Garmin Connect account on multiple computers at the same time.
• You may backfill up to 90 days in one request. You can request dates up to 5 years in the past. You may make one backfill request every 15 minutes.
• Any backfill day may only be requested once per user. This is a global limit that applies to your user account. You cannot request to backfill a day twice even if you de-authorize and re-authorize rubiTrack from scratch.

In order to protect your privacy these policies are in place:

• If you never download any activities after authorizing rubiTrack to receive activities from Garmin, we will deauthorize rubiTrack after 30 days.
• Activities will be removed from temporary storage 60 days after receiving them from Garmin.
• If you do not download activities via rubiTrack for more than 90 days, we will deauthorize rubiTrack.
• Any deauthorization removes all activities from temporary storage.

You can use tabular CSV data to import both activity summary data (activities without track or GPS data) and athlete log records.

Activity Summary CSV

• The field separators are either semicolon ";" or tab, comma cannot be used as a separator.
• The order of columns is arbitrary.
• All fields except date are optional.
• Some values like distance and temperature are interpreted according to the current unit setup in rubiTrack's Unit preferences.
• If country code, division and city are given and they are contained in the rubiTrack database, weather information will be looked up automatically.
• All numbers with decimal digits use the dot "." as decimal separator.

Activity Summary CSV Example File

Athlete Log CSV

• The field separators are either comma ",", semicolon ";" or tab.
• The order of columns is arbitrary.
• All fields except date are optional.
• Fields can be filled in one line and not in another, it doesn't have to be consistent (except for date which has to be filled in every line).
• For all weight related columns there are 3 versions, for example weight, weight_kg and weight_lbs. If the first version is used, rubiTrack determines the unit of the value based on the setting in the preferences. The other two versions pre-set the unit for the import. Only one of the three variants should be used in one single CSV file.
• All numbers with decimal digits use the dot "." as decimal separator.

Athlete Log CSV Example File

If you have a lot of activities in Garmin Connect dating back a long time, the usual backfill mechanism might take some time to download them all. Backfill also only works only 5 years into the past, so older activities are not accessible.

However, Garmin provides a way to retrieve ALL data on your account through the following service:

https://www.garmin.com/en-US/account/datamanagement/
You will have to log into your account using the Garmin Connect login. Garmin will notify you when your data is ready for collection.

The data comes compressed in a ZIP file (named something like "db8ab0ba-0603-4ea5-a5a3-85972ea46238_1.zip") that contains various bits of information. It includes the original data uploads your Garmin device or software made to your Garmin Connect account.

Extract the activity data as follows:

1. Place the downloaded ZIP file in a temporary folder.
2. Extract the files and folders it contains by double-clicking it in the Finder.
3. Inside the expanded folder hierarchy, find the folder "DI_CONNECT/DI-Connect-Fitness-Uploaded-Files".
4. This folder contains other ZIP files named like "UploadedFiles_0-_Part1.zip". There may be more than one of these ZIP files, depending on how many activities you have.
5. These ZIP files contain your activity data.
6. Expand each file and you have access to the original data you recorded.

You can now go ahead and import those activity files into a rubiTrack file (using "File > Import…" from the main menu or by dragging the containing folder into rubiTrack).

We recommend to first import into a new, temporary rubiTrack file and only import into your production rubiTrack file after you are satisfied with the outcome.

Yes, absolutely!

First you need to upgrade your old file(s) to rubiTrack 6, if the file(s) are not yet upgraded. Upgrading creates new files, your old data will remain as is.

We recommend to create a backup of your rubiTrack file you would like to add other files to:

1. Find your file in the Finder and select it.
2. Select "File > Compress" from the main menu.
3. You now have a compressed backup copy of your complete data, just in case.

Once all files are prepared, start rubiTrack:

1. Select "File > Open…" from the main menu to open the file you want to merge INTO.
2. Press and hold the SHIFT + OPTION + COMMAND keys.
3. Select "File > Integrate…" from the main menu.
4. Select the old data file you just upgraded.
5. Select "File > Save".

If you have more than one old data file, repeat steps 2-5 with every additional rubiTrack file you want to add to your file.

Data from rt2go can be upgraded to rubiTrack 6 by copying the data file:

1. Install rubiTrack 6 on the device you have rt2go running on.
2. Go to the home screen on the iPhone.
3. Terminate both apps via the Task Manager (if they are running).
4. Open the "Files" app.
   1. Find the folder called "rt2go".
   2. Long-press the file with the .rubitrack5 file extension (there should be only one).
   3. Select "Copy".
   4. Go back to the root level, find the folder called "rubiTrack 6".
   5. Inside "rubiTrack 6", long-press the file with the .rubitrack6 file extension (there should be only one).
   6. Select "Delete".
   7. Long-press the empty area and select "Paste" from the menu.
5. Now that the data is copied, launch rubiTrack 6.
6. An alert at the end of the loading process will confirm the data upgrade.

Yes! You can export existing activities from SportTracks to the FITLOG format which you can then import into rubiTrack.

In order to direct sync with your TomTom device, you need to set up the TomTom MySports Connect software appropriately.

1. Install the TomTom MySports Connect software.
2. Set up TomTom MySports Connect to export FIT files on the "UPLOAD & EXPORT" page (Click "ADD" and select "FIT-format for training applications").
3. Make sure you're not exporting multiple file formats as this will lead to duplicates in rubiTrack.
4. If you changed the name of your TomTom watch, go to rubiTrack's advanced import preferences and enter the name of your watch (via "rubiTrack > Preferences >> Advanced" from the main menu).
5. Download activities from your TomTom device using the TomTom MySports Connect software.
6. When finished, you can use rubiTrack 6 to sync the data.

rubiTrack 6 is available as a cross-platform subscription for your Mac and iPhone. When subscribed, all features are available for both the macOS and the iOS version. rubiTrack 6 is available as a yearly subscription.

Subscriptions can be canceled from your App Store settings. Click here to read more on the Apple support pages.

Yes. When you subscribe for the first time, you can test rubiTrack PRO for 7 days. You will not be charged, if you cancel the subscription at least one day before the end of the trial.

The trial version is functionally identical to the full version.

There is no trial for the base functionality.

Yes. If you use rubiTrack without active subscription, there is a limited feature set available, depending on the device you are using.

rubiTrack 6 comes in two parts:

1. The app download (aka base version), charged once.
2. The optional PRO subscription, charged annually.

Neither of them is free.

The base version is meant as a fallback for you, should you one day decide to stop ponying up for the PRO subscription. It enables you to access and view the activity data you have in rubiTrack, you can even export activities using it.

The base version does not expire, so your data will be accessible always.

When you ask Apple to refund the app download purchase (base version), updates will no longer be available to you. The app will be deleted from your Mac eventually.

Your rubiTrack file will get damaged if you do!

Dropbox does not handle Mac package files (which is a folder containing other files and folders) correctly when you put them into the Dropbox sync folder. rubiTrack for Mac uses such a package file format. Under certain circumstances, Dropbox will corrupt such files, which can cause some or all data to be lost or become unreadable. This is a problem known to Dropbox for many years and it affects not just rubiTrack but hundreds of Mac apps that use a package file format.

Do NOT use Dropbox or similar sync service with your rubiTrack for Mac file. If you want to sync multiple Macs using Dropbox, create a ZIP'd copy of your rubiTrack for Mac data file and put that into your Dropbox instead.

Whenever possible rubiTrack calculates all values it displays based on the data the device reports for the workout. The data usually consists of a stream of GPS data and heart rate, cadence, power values, and so on.

Garmin Training Center (and others) use the device-calculated averages and absolute values (like distance, duration and average heart rate) unverified. This often leads to a displayed distance that does not agree with the GPS data.

rubiTrack allows the display of calculated data or original device data. You can easily switch between the two at any time (Activity > Update Activity > Using Original Device Data).

In many cases the distance the device calculates is slightly different from what rubiTrack calculates. rubiTrack uses a high-precision algorithm that works very reliably, more reliable than what a device could possibly calculate given its very limited computing power. Also, in some cases the distance can differ significantly because - like any other computer - GPS devices have bugs. And those cause rather big errors in distance calculations on the device from time to time.

In both cases a difference in calculated distance will cause a - possibly significant - discrepancy in average speed, pace and other values.

There are also other reasons for values being different. Those are not necessarily errors in calculations, instead they are caused by different methods of how they are calculated.

One example is maximum speed. Largely because of the very coarse time base GPS coordinates are timestamped with, calculating a maximum speed value between 2 points only leads to incorrect results. Values calculated this way would be unrealistically high if the timestamp induced error is large enough - which tests show they are.

This is why we use a running average over a couple of points to calculate the maximum speed. Garmin also does this on the device. You can verify this by watching the speed measure on the device when you stop. You will notice that the speed reported by the device will not jump to zero instantly, instead speed will drop to zero gradually. This is because it's an average over the last couple of points recorded by the device.

The reason why the values differ between rubiTrack and your device is that the way these running averages are build differ. They are calculated in different ways, both are correct.

One other popular example is the calorie calculation. If you are using a heart rate monitor, chances are that the number rubiTrack calculates is different from the number your device calculated. Again, this is because the device uses a different algorithm than rubiTrack in order to calculate the calories burned. Unlike in the above maximum speed example though, there is a very high probability that both rubiTrack and the device got it wrong. This is because it's incredibly difficult to calculate burned calories with only a handful of data that is available for the calculation. Regardless of where the value is coming from, always know that this is only an estimation and it's very likely not what the real calorie expenditure was.

So, while rubiTrack does not agree with the device on the burned calorie value, neither of the calculations give you an accurate number, both are estimations.