If you guys know anything about me and about Rekord Buddy it’s that I listen to users and use that feedback to make the app better. Next Audio‘s motto ‘By DJs for DJs®‘ is not a gimmick, it’s what I live by.
Rekord Buddy 2.0 was a vision on how to improve on the old version 1 and how to make the workflow better. Some of this worked and some of this didn’t. Version 2.1 aims to fix what didn’t and set up Rekord Buddy for future functionality.
In order to make the 2.1 release as bug free as possible, I need your help to beta test it and report any issues you find. There is something in it for you if you can find something and help me find it. Read on.
What is new in the 2.1 update?
- Database back-end is now the Windows/Cross Platform one.
This is a major step in shipping Rekord Buddy on Windows. The Windows version is a major rewrite of the app and 2.1 includes a huge chunk of the new Windows codebase. Testing this and making sure it works will help ship Windows faster.
- Syncing has been replaced by a simpler import/export workflow.
Many people had problems understanding how syncing worked in 2.0. As a result, they weren’t able to predict what a sync would do and what would get modified and why. This is a huge problem as users need to be able to trust their tools and be confident they won’t destroy information due to a user-error. By popular demand, the workflow is now a much simper ‘import from this/export to that‘ system. This is similar to how 1.0 worked and should be a lot more straightforward and less error-prone.
- Hotcues can be duplicated as memory cues on export to rekordbox from any program, not just Serato.
This was another highly requested feature. You can now duplicate your hotcues as memory cues in rekordbox, no matter where the data came from.
- User can now select if Traktor grid markers are merged with hotcues on export.
Traktor can store beat markers as hotcues and users that took advantage of this could loose this information as Rekord Buddy would always separate grid markers and hotcues. You can now merge those back together when exporting to Traktor.
- Traktor parser can now parse the comment2 field.
This field can me merged with the regular comment. A future version of the beta will probably allow users to specify a separator to use between each field.
- Users can now change the Traktor library location at any time.
The previous version would only let you change the location on init. Because of the new workflow, you can now change it at anytime.
What is missing?
The beta is a work in progress and some features will be added as we progress in stabilizing the features that are already there. Unfortunately features like Mixed-In-Key support and iTunes support that were initially planned for 2.1 that will now most likely make it in 2.2. This is because I need to ship 2.1 as quickly as possible to help the Windows port and therefore want to focus on making it stable first.
There is currently no way to import your 2.0 database into 2.1. This should be available upon release but in the meantime you will need to re-import your collection from somewhere else in order to use the beta. It’s also not recommended to continue using the regular 2.0 build when you start using the beta as it might get confusing and lead to user-errors.
Finally, keep in mind that the database format will probably change during the beta period which will force you to re-init every now and then. If you’re not wiling to do this then do not give the beta a try or do it on a separate computer.
How can I help?
I need to find and fix any issues that the beta has with your collection. Anything that doesn’t get imported correctly or anything that doesn’t get exported properly. Any wonderful things that you see while using the app, any suggestions for last minute tweaks to usability.
I want to make it worth your while and so, as part of the 2.1 beta, I’m introducing a new bug bounty program for Rekord Buddy. Ive been doing this in the past with people reporting big issues but this will now be official and available to all. Here’s how it works:
- Find and report an issue that I do not already know about (only bugs reported via firstname.lastname@example.org will be eligible).
- Send one email per issue and preface your email subject for each issue with “[2.1 Beta]“.
- Get confirmation from me that the issue is eligible for the bug bounty program.
- Help me fix the issue.
- Get a partial refund on your Rekord Buddy purchase (usually $5, could be more if the bug is a big one).
Where is the beta?
You can download the public beta here. Of course you need to be a current Rekord Buddy user and have a valid license in order to use the beta. Any updates for the beta will be available via the regular in-app update method after that.
Do not use the beta on a computer where your main collection is (unless you have backups). Do not use the beta for anything else but help test and report issue. Don’t get stuck 2 hours before a gig before the beta caused an issue and you’ve lost data. Be smart.