Unfortunately there is no migration system from the old Rekord Buddy collection to the new format. The main reason is because the time a migration would take is the same as the time it will take a user to re-import their collection from another program like rekorbdox, Traktor or Serato.
The real 'sync' was part of the early 2.0 versions. Users pressed a button and ideally only things that had changed would get updated.
Problem is, it never worked properly because in some cases the modification time info was not even available. rekordbox for example, doesn't even store this info anywhere so there is no way to know what has changed when. Just looking for changes is not enough, you need to know when this happened so that the syncing is correct. So basically this was never really doable in the end.
In a 2.0.24 and after, the sync was replaced with an import/export method that would work better but be an all or nothing. Users had to import or export the whole collection. That wasn't ideal either.
Fast forward to 2.1 and yes, both sync and import/export are replaced by drag and drop but this is a great building block for future improvement. If the user can pick and choose what to copy from one collection to another (and without the need to go through the Rekord Buddy collection if you don't need to, which makes the process much faster) then we can imagine a feature that will show you what has changed, when it can, and allow you to only update all or some of those changes yourself..
Rekord Buddy collects anonymous statistical information while you use the app. This information is in no way connected to you and we have no way to identify you as the source of this information. In order to do this, the app will request from a third party server a random universal unique ID which is then use to identify you when sending statistics to us. Because the unique ID is generated by someone else, and because we never send any other identifying information, we do not know which user is behind which unique ID. While the event system we use (mixpanel) does look at your IP address when receiving events from you, in order to determine roughly your location (city and country), they do not store this IP address with your information which means we cannot connect IP address with unique IDs.
We currently collect the following information: OS name and version (i.e. macOS10.14.3), machine model (i.e. Macmini8,1), your rough location (i.e. Paris, France), the version of the app you are using (i.e. 2.1.14beta(672)), the time you sent the event (i.e. 23:43:22UTC), the names of the DJ apps you have installed (i.e. Serato,Traktor,rekordbox), the time you started and stopped using the app and the type of drag operations you perform in the app (i.e. Drag a Playlist from Serato to rekordbox). The list contained here will always be kept up to date as we add or remove events. We use this information for statistics (how many people are using the app or a certain feature of the app) and improve Rekord Buddy in the future (like prioritizing translations to other languages).
As stated in the EULA that you must agree to when purchasing the app:
You agree that Next Audio Labs may collect and use usage and technical data, and related information, including but not limited to statistical data on your music collection and its use, and technical information about your device, system application software, and peripherals to facilitate further development of the Licensed Application, new features, future products, and other services. Application Provider may use this information, as long as it is in a form that does not personally identify you, to improve and/or promote its products, to provide services or technologies to you, and/or for other business reasons.
Because this information is anonymous and non-critical, there is no opt-out option for the user as this would invalidate the statistical information.
When the app encounters an issue (Something wonderful...) or a crash, we send a crash log back to our servers. This log contains information provided by Apple about your machine but we also attach an identifier in this case so that we can contact you if necessary or, for example, find your specific issue after you make a post on the community forums.
If you have multiple monitors, even if one of them is switched off, right click on the app icon and select
Desktop on on Desktop 1 to make sure the app opens its windows on the main screen.
You can log into the website and then head over to your Purchase history page which will show your license key by clicking on the little key icon.
Some browsers may not display the entire number on screen so make sure to select the entire field and copy it to the clipboard to avoid typing mistakes.
The license key will be a 32 character alphanumeric string.
These Rekord Buddy 2.0 features have been put on hold in order to help ship 2.1 faster. This was a hard decision but is the right decision in the short term. The code for these features still exists and will be plugged back in, pending some further testing, in a future release.
This tongue-in-cheek message is inspired by the infamous SCA virus message from the Commodore Amiga (Damien was part of the Amiga demo-scene in Europe back in the days). It is part of the new 'unexpected issue' detection in Rekord Buddy.
Because Rekord Buddy is developed and supported by a single person, it is a tall order to test the app under every single configuration out there and especially to anticiapte all the different type of information found in all the different DJ collections around the world. Because of that, problems fall through the cracks and a call has to be made as to what to do when those problems occur.
Rekord Buddy is coded very defensively, to try to detect issues when they happen as much as possible. When an issue is detected, it's no longer possible to trust that your data is safe and therefore Rekord Buddy exits after this dialog in order to prevent data corruption.
At the same time, a detailed report is sent to Next Audio Labs with your license information so that we can take a look and firgure out what went wrong. We can even add custom code in future builds to debug the issue right on your machine which helps greatly in figuring out a fix if the issue can't be reproduced.
The bottom line is that if you get this message, you have found something we didn't know about and you are helping make Rekord Buddy better. Make sure to keep an eye out for future app updates and try the same action again to see if it is fixed or to provide further info for us to fix it. We do not ignore any issue we receive.