Frequently Asked Questions
Which devices are supported?
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.
|Device||Model||Direct Sync||File Import|
|Garmin Forerunner||910XT, 620, 610, 220, 210, 310XT, 410, 405, 405CX, 110, 70, 60, 50, 205, 305, 201, 301||•|
|Garmin Edge||810, 510, 800, 500, 200, 705, 605, 305, 205||•|
|Garmin||fēnix, SWIM, GPSMap 62, Dakota, Oregon, Colorado, eTrex||•|
|Suunto||Ambit, Ambit 2, Ambit 2s with Moveslink2||•|
|Suunto||T6, T6c, T6d (*)||•|
|Suunto||X9i, X9Mi, X10 (*)||•|
|Polar||RC3 GPS via HRM/GPX||•|
|Polar||RCX5, CS500, FT40, FT60, FT80, RS300X via HRM/GPX, polarpersonaltrainer.com XML||•|
|Polar||RS800, RS800CX, S610, S610i, S625X, S710, S710i, S720i, S725, S725X, S810, S810i, CS600, E600, AXN500, AXN700, Sport Tester, Vantage XL, Vantage NV, Accurex Plus, XTrainer Plus, Coach||•|
|Amod||3080 GPS Tracker||•|
|Timex||GPS Global Trainer||•|
|Withings||WiFi Body Scale||•|
Which file formats are supported?
rubiTrack supports the following file formats. If you have a file format you would like to see supported by rubiTrack email us.
|File Format||Import||Export (Mac)|
|TCX (Garmin Training Center)||•||•|
|FIT (Activity, Weight)||•|
|Sporttracks FITLOG (Activities)||•|
|Sporttracks LOGBOOK (Athlete Log)||•|
|NMEA GPS Log||•|
|Polar polarpersonaltrainer.com XML||•|
|Suunto Movescount XML||•|
Which cloud services are supported?
rubiTrack supports the following cloud services.
|Dropbox (rubiTrack for iOS only)||•|
|Withings (Body weight and health data)||•|
|Fitbit (Body weight and health data)||•|
Can I import activities I have stored in SportTracks?
Yes! You can export existing activities from SportTracks to the FITLOG format which you can then import into rubiTrack.
Can I import activities I have stored in Ascent?
Yes! You can export existing activities from Ascent to TCX format which you can then import into rubiTrack.
Can I import more than one activity into rubiTrack at a time?
Yes! Just drag all activities you would like to import into the document or use the "File > Import" menu.
Where is my rubiTrack file?
If you can't remember where your rubiTrack file is located on your hard disk:
- Start rubiTrack (your file will be opened automatically).
- Hold the COMMAND key and click into the filename in the title bar of the rubiTrack main window.
- A menu will open that shows the full path.
- Select the first folder in the menu to switch to Finder.
What if I find a bug?
If you find a problem please do not hesitate to let us know and email us. We appreciate your feedback!
rubiTrack for Mac is compatible with Mac OS X Mavericks, Mac OS X Mountain Lion and Mac OS X Lion (10.9, 10.8, 10.7, 64 bit). rubiTrack works with Intel Macs.
The version of rubiTrack for Mac available on the Mac App Store is compatible with Mac OS X Mavericks 10.9 - 64 bit, only.
rubiTrack for iOS is requires iOS 7.0 or later.
How can I use Dropbox in rubiTrack for iOS?
On rubiTrack for iOS you can use Dropbox to import files in one of the supported file formats.
- Make sure your file does not exceed 20MB, Dropbox import limited to files with 20MB at most.
- Optionally create a folder named "incoming" and put your files there. If the "incoming" folder exists, rubiTrack will look only there for new files.
- Once a file is processed, it will be moved to the "processed" folder.
- If a file can't be processed because the file extension is unknown or because it's bigger than 20MB it will be moved to "unprocessed". rubiTrack creates both folders automatically, if needed.
How can I import a rubiTrack for Mac data into iOS using Dropbox?
Use WiFi sync to get your data from the Mac into your iPad or iPhone. Dropbox import for rubiTrack for Mac data files is not supported.
Should I use Dropbox to sync multiple Macs?
NO! 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.
Does any of this affect rubiTrack for iOS?
No, you can safely use Dropbox in rubiTrack for iOS.
What is the difference between rubiTrack basic and rubiTrack [+]?
rubiTrack [+] adds an incredible amount of features, click here for details.
What do I get when I upgrade to rubiTrack [+]?
rubiTrack [+] adds an incredible amount of features, click here for details.
A rubiTrack [+] license does not expire and is yours forever. You may use your license on multiple computers for example on your Mac Pro at work and your MacBook at home. The license is for you and you only, you may not share the license with other users.
Do I get updates for free?
Yes, all updates to 3.x.x versions are free.
Do I get a discount on new major versions?
Yes, you will receive a discount for upgrading to a new release when it becomes available.
I'd prefer to buy from a US based store…
Not a problem, please use our US Store powered by Kagi.
Upgrading to rubiTrack 3
How does it work?
rubiTrack Store: Customers who purchased rubiTrack 2 from our store are entitled to a 50% upgrade discount when purchasing a license for rubiTrack 3. When you upgrade to rubiTrack [+] from within rubiTrack 3 basic and a license for version 2 is installed on your Mac, the discount will be applied automatically.
Mac App Store: Apple makes it impossible to offer upgrade pricing. If you missed the upgrade window in the Mac App Store, you can still upgrade at 50% by switching to our store. Email your receipt for your Mac App Store purchase of rubiTrack 2 to rubiTrack support, we will send you a coupon code for our store.
Upgrading from within rubiTrack 2 (rubiTrack Store Licenses)?
To get your upgrade discount coupon all you need is rubiTrack v2.5.2 with your current license installed. Follow these steps:
- Make sure you are connected to the internet
- Start rubiTrack v2.5.2 (it is important to start the old version!)
- If the upgrade window does not show up automatically, choose "rubiTrack > Upgrade Information…" from the main menu
- The screen displays your discount coupon in the lower-right corner.
- You can go to the store at any time and use the coupon (*).
- Alternatively you can click "Purchase…" to go to the store immediately.
(*) Note that the coupon is valid for one purchase.
Where can I download rubiTrack 2.5.2?
You can download rubiTrack 2.5.2 here.
Why are rubiTrack's measurements different from my device's measurements?
rubiTrack calculated measures are not necessarily wrong, they're just different from what the device shows you (which sometimes is definitely wrong).
Differences part 1: Calculation vs. Copying
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).
Differences part 2: Calculation errors
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.
Differences part 3: Different Algorithms
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.
Differences part 4: Too many unknowns
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.
Note that the procedure below is not required for Suunto devices that use Moveslink 2 like the Suunto Ambit. In that case you only need to set up Moveslink 2 to sync your device.
Syncing with a compatible Suunto device requires the Suunto Moveslink application and a Suunto Movescount account (both are free). If you do not have Moveslink.app installed you can get it here: www.movescount.com/connect/Moveslink. You also have to sign up for a Movescount account which is free (www.movescount.com).
Syncing your Suunto device works like this: First Moveslink.app downloads the data from the device. It then uploads it to your Suunto Movescount account and saves a copy of the workout on your Mac. When Movesline.app is finished, rubiTrack can access the data from your Mac.
After installation of Movelink.app and the Movescount account setup follow this procedure:
- Start Moveslink.app, make sure you enter your Movescount account data when requested, then quit it.
- Start rubiTrack (version 2.4 or newer).
- If everything worked correctly, rubiTrack will request to make a change to Moveslink's settings. This is necessary so that new workouts will be available to rubiTrack once downloaded from the device.
- Once rubiTrack recognizes Moveslink, rubiTrack will offer to make a change to a setting, do it. Click "Apply Change" when requested. Syncing will NOT work unless you see this message and approve the change.
- Start Moveslink.app again and connect your watch.
- The data download from the device will start automatically, wait till it reports success.
- Now you can sync with rubiTrack, it will read new workouts. Note that only new workouts will be available for syncing with rubiTrack, those that have been uploaded to Movescount prior to setting this up are not accessible for rubiTrack.
Important: If rubiTrack doesn't recognize Moveslink.app, it will startup at step (3) without requesting to make a change to Movelink.app's settings. It means something went wrong with the setup of Moveslink.app and syncing will not work. To fix this, quit rubiTrack and start over at step (1) - note you may have to repeat this sequence 2-3 times.