FLX-10 jog tension and backspin issue

[Slak_Jaw]

You’re welcome @zdup, the linked topic below provides more info on how Suggestions in this Community work.

Update to Our Voting System Guidelines [Suggestions]

As a user, it’s essential to grasp the significance of your vote and how it influences our development roadmap. When you vote for a specific feature request or general suggestion: Your vote signals your interest and support for the proposed feature/suggestion. We consider the cumulative votes alongside other factors such as feasibility, resource availability, and alignment with our product vision. While high-voted features are more likely to be prioritized, they are not automatically im…

@zdup

Could you let us know what users should expect after a report has been forwarded?

For example:

• Will there be a follow-up if the development team reviews it? Nothing that will be shared publicly here.
• Will users be informed if the request is accepted, rejected, or considered technically impossible? Not normally, unless it is clearly technically impossible.
• Or should we simply assume there will be no further response unless it appears in a future release? Yes, this is essentially how it works.

@zdup

Since this issue has already been reported by multiple users, it would be helpful to know whether it is actively being investigated or whether the current behavior is considered expected.

The current behaviour is considered expected, but the team is actively investigating other possibilities. Unfortunately, changing the current behaviour is less straight forward than it seems on the surface. Our dev team has a lot priorities to balance and they do not share timelines or roadmaps as these priorities often need to be adjusted. I hope that helps!

[zdup]

Thank you for your reply. I appreciate the explanation, and I understand that this is currently considered the intended behaviour. I also understand that it is entirely up to Algoriddim whether to change this behaviour or keep it as it is.

However, if this behaviour is considered “expected” rather than a bug, I believe it should be clearly documented on the controller compatibility page.

The page already lists unsupported features such as jog displays, screens, and FX functions for various controllers. However, there is no indication that the jog wheel response itself differs from what users would reasonably expect from a natively supported controller.

Since this behaviour is officially considered expected, not mentioning it before purchase is misleading. Users choosing high-end controllers such as the REV5 or FLX10 naturally expect accurate jog wheel performance for two-deck mixing and scratching. At the very least, this limitation deserves the same level of disclosure as the other documented unsupported features.

I hope you will consider either documenting this behaviour more clearly or continuing to investigate possible improvements in the future.

[Slak_Jaw]

You’re welcome @zdup. Thanks for the additional feedback. I will share it with the team.

[caster25]

Yeah so my subscription was up for renewal… Didn’t go for it. Biggest reason was that after nearly 11 months this issue still isn’t fixed. They are probably not able to fix this without some proprietary piece of code from Pioneer / AT. Just switch back to rekordbox guys, then your controller works perfectly fine.

[Slak_Jaw]

Thanks for the feedback @caster25. Sorry to see you go…

[Brown_bkp]

This is not cool and not happy about that should everyone facing this issue go before solutions are found?

[Slak_Jaw]

Thanks for the input @Brown_bkp. Our team is working on it…