Xml export is really important indeed
Comment actions
Post
Follow
Rekordbox 6 export xml, sequence save, recording, midi
Hi,
So since upgrading to Rekordbox 6, I've noticed a range of Rekordbox 5 features were removed in 6.
From what I can surmise, the following features have been removed or hindered in Rekordbox 6:
- XML export was part of the standalone Rekordbox 5 licence, but is not available in 6 at all - clearly this is very bad. People invest huge time into their library and to not offer a means to export that (should they want to import their library into other software, etc) is akin to Microsoft Excel not offering the ability to save excel documents outside of their app.
- Sequence Save was part of the standalone Rekordbox 5 licence, but is now only available via subscription. Not even unlock devices unlock it.
- Recording was part of the standalone Rekordbox 5 licence, but now can only be accessed in 6 via unlock devices or subscription.
- Midi mapping was part of the standalone Rekordbox 5 licence, but now can only be accessed in 6 via unlock devices or subscription.
Now, I make a clear distinction here between unlock device and standalone RB5 licence, because I purchased a DDJ-400, which included a standalone RB5 licence for 2 devices (only one can be used at a time), and the DDJ-400 acts as an unlock device for Rekordbox 5 on other computers that do not have a standalone licence.
That standalone licence gave two of my computers (and still does in 5) access to the features mentioned above without needing to connect my DDJ-400. This was useful for many reasons that I shouldn't need to go into (but if you must ask, examples include setting up midi mapping with other software, prepping sequences, and recording automix sets for later listening), and it is a real shame these decisions were made to remove, reduce or hinder that functionality in Rekordbox 6 in the ways I've mentioned.
I should reiterate that the single biggest issue is clearly the lack of XML export, but all the other decisions also add to the unpleasant taste this update gives me.
If anything I've said is incorrect, please let me know, but otherwise, could you pass this onto the Rekordbox team, so further feedback about these poor decisions can be considered. Thanks.
Post is closed for comments.
Date
Votes
8 comments
XML export won't be back. It was the way people were importing into Engine Prime(Denon). That's really sad.
Comment actions
I don't think this will stopp Denon as they can import probably from an rekordbox exported stick like they do on their players. To change that I assume PioneerDJ would need to change that format as well which would require firmware updates to all supported devices which could be even impossible.
So it makes it more difficult for users to do a switch but I doubt it will stopp it. However if the process is more cumbersome lots of people my be more hesitent to make the move...
We will see. There are a lot of developers out there who are depending on this. It might be a matter of time until we see work arounds - but this is speculation.
Comment actions
Yeah I use multiple ecosystems. And exporting to XML had a number of good uses. And you;re right devs could make great use of it.
Bums me out.
Comment actions
If you check out the rekordcloud developer's blog, he goes into some detail already about having found the decryption key to access the new sqlite backend database. The reality is, people want access to their data, so will find ways to get it no matter what the rekordbox developers do. If the application that runs on the computer can access the database, then there will always be ways to get the decryption key. To make it more convoluted or difficult to get, only serves to alienate the customer base.
Just as an side, I've been developing software for over 10 years, so this is an area I know pretty well. Basically, by the rekordbox team taking away xml export, they're motivating developers to really dive deep into the internals of their software like never before.
Comment actions
Yeah I saw that. A new DB made sense for 6.0 as DeviceSQL is old and lacking. But the encryption was just gross. Really disappointed in Pioneer and their decision that because they don't like 3rd party integration you shouldn't have access to your own data.
Comment actions
Indeed Andre. It seems to be a kind of knee-jerk reaction, probably from upper management, that will clearly have the opposite effect of what they intend. Make it harder for 3rd parties to use the data? How about actually motivating many customers to move entirely because they don't want to be locked in?
However, as far as I can see, there is no official word about whether xml export will come back or not. So basically, the best approach imo, is to let it be known far and wide what pioneer has done, so it does impact their bottom line, which is the best way to get a clearly terrible decision reversed.
Comment actions
Hi folks,
Please see my response here: https://forums.pioneerdj.com/hc/en-us/community/posts/360061283351/comments/360010259892
If anyone is interested in making a petition, please get in touch.
Thanks,
Alex.
Comment actions