Messages from TRAKTOR

Dear TRAKTOR Community, thanks for your engagement in this thread, and on behalf of the whole team, we’re sorry for the radio silence since the first message I posted here. We’ve been busy analyzing your survey responses and deriving plans, and most importantly we have been exploring the potential implications for TRAKTOR coming from our close relationship with Izotope - our new sister company.

Let me try to answer the questions you’ve been asking and discussing here. Hope this will cover most of your thoughts.

1. The survey: The response was again overwhelming as for all of our past surveys - we received a total of 1551 reponses. Big thanks to everyone who participated - we appreciate each and every response as well as the time, passion and loyalty that you invested. Some of you were asking why we’ve been conducting one survey per year. Given the various changes and trends in our industry, we believe that engaging with you frequently is crucial because we want to make sure that what we’re working on is what you actually need. To be clear, we are working on the top requested features that have been mentioned. We hope you understand that we can’t publish the full ranking of the requested features, but we want to share with you that you can expect news soon on FX and a drum machine module. All other requests, such as flexible beatgrids, browser improvements, or further streaming services have been heard as well and they are on our midterm roadmap too.  

2. Subscription: Telling from the discussion in this thread, the fact that we asked about your preference regarding payment plans made some of you assume that we’ve decided to switch TRAKTOR Software to a subscription only model. This is not the case. Our research has shown that 9.1% of responders would switch to a TRAKTOR subscription, and 18.4% would be interested in an Add-On Subscription unlocking special features, while 72.5% would prefer to keep the status quo. Apparently there is interest in various scenarios, which is why we are working on an attractive offering for all needs. More specifically, this means that we are committed to respect the status quo and in near future will offer new, additional options to engage with TRAKTOR at different price points and for different needs.

3. Codebase: As there are some codebase related comments, let me assure you that we’re continuing working on a future-proof, modern and flexible codebase. Part of the perceived silence around TRAKTOR is due to the fact that relevant parts of our development capacities are currently dedicated to this renewal and merger of the codebase, which will enable user facing benefits, such as native M1 support, a new user interface and ultimately: faster development cycles. Don’t expect that one ‘big bang’ though. We’re migrating to the future codebase in increments while working on several aspects behind the scenes that may not be immediately visible. With every quarter though, we’re moving closer to the UI based updates that many of you have been waiting for.

4. Hardware: As mentioned before, we’re working on an exciting piece of hardware as we speak. We have to ask you for your understanding that we cannot provide any further details, but you should know that the future of TRAKTOR hardware is being worked on. There has also been the question about integrating more 3rd party controllers. We just want to say that we have heard you and that we agree with you. We definitely want more of these integrations to see the light of day, especially once we’ve made more progress around our codebase (see 3.).

Last but not least, we want to re-emphasize that we want to engage more frequently with you: a quarterly roadmap update and more frequent responses to your burning questions.

Please rest assured we continue working hard every day to build the products we all are so excited and passionate about. Once again, a warm thank you from Berlin - and looking forward to reading your thoughts!