No search box on the explorer node no midi mapping with modifiers, multiple actions and CFX selector Ĭannot physically delete files inside RB. Issues of the V6 Rekordbox migration - Minor ¶īesides the XML export and the v5 licenses problems, there are additional smaller issues: After the RB6 database encryption story last week, and all this years of Traktor workarounds, it looks the best way forward." "We would recommend that users who wish to move their Rekordbox collections to other DJ Software avoid updating to Rekordbox 6"."I’ve always done things by the book with Rekord Buddy and so my first reaction is to make we stay within the law here."."It could be different: In case Pioneer reads this: do the right thing and open up Rekordbox."."Call to arms: I ask all DJs regardless if they use my tools or not, ask Pioneer DJ to bring the export to XML function back, and while at it, ask them to fix the XML import.(issue was not specifically covered AFAIK)."What about this Rekordbox 6 issue? none of the conversion apps out there old or new except Rekordcloud works with Rekordbox 6 exporting, because your data is locked down inside Rekordbox 6 in a way it wasn’t in previous versions."."This alone tells me that this is a totally pointless method on Pioneer DJ’s part and that they need to change, or ideally ditch encryption completely."."will only last as long as Pioneer DJ doesn’t change the encryption key, which could be tomorrow or could be never."."as each manufacturer continues to build higher walls around their ecosystems to keep you trapped inside.How did the industry commenters reacted to the v6 XML export issue? ¶ The dead V5 license is quite annoying (there will be no V5 improvements and I don't expect any support moving forward). The XML vendor lock is a deal breaker for me.\
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |