Just reach out to me via support instead of a public forum for another app (I nearly missed this thread) and I'll be glad to help you out like I've helped many many people before you. So anyway, bottom line is, whatever problem you've had can be fixed. 2.1 which will go in beta next week will go back to the old import/export workflow. Ok, finally finally, you're not the only one who complained about the workflow in 2.0 and you'll be happy to know that I always listen. Given my resources (I do everything by myself) there is no way I could do any more in depth testing than what I did. If it works for them then they don't spend time finding more bugs. Version was in beta for a long period of time (and I got a lot of flack for that too) but toward the end, people just use the app instead of testing it I.e. Even if Rekord Buddy had no bugs, you could still make a mistake and cause problems if you didn't have backups.įinally, with regards to the 'not enough testing' you have to realize it's impossible to test everything pas a certain point. Not just for Rekord Buddy but for any unforeseen problem you may encounter.
Also, and it needs reminding all the time, you should have backups of your data at all time. It overwrite Traktor collection (which it has to) but Traktor keeps backups of the nml file in a sub folder. Secondly, in Traktor's case, RKB2 doesn't destroy anything. There are thousands of RKB2 happy users around the world so whatever problem you have I'm sure it can be fixed or any user error can be resolved. I personally help out everyone that reports issues to me, generally in the order of importance (how many people are seeing the same problem). First and foremost it will be easier to help you via support than in the Traktor forums. Click to expand.Many things to cover here.
0 kommentar(er)
