FLX-10 jog tension and backspin issue

Bug Reports
1

NOTE: Please use the search function above before posting to avoid creating duplicate topics.

  • Device model : Macbook M3 Max
  • Version of operating system : Sequoia 15.6.1
  • Version of djay : 5.4.3
  • Hardware/controllers used : DDJ FLX-10

Summary of the issue:
First of all, I am very much surprised as to how well the FLX-10 works with Djay! But, since we are here, I found a thing that annoys me… When performing a backspin on the FLX-10 it all sounds quite well when the tension adjust dial is sligthly tuned left of the ‘middle’. When I put it to the lightest setting and I do a backspin the platter keeps spinning but djay does not detect the scratch anymore. Instead it has switched to detecting pitch bend. Effectively this means that the jog wheel is still spinning backwards (in total I guess about 8 seconds) quite fast while the track is already moving in forward position again after about 3 to 4 seconds (although a lot slower because of the pitch bend detection). When I put the dial to the heaviest setting the opposite occurs when performing a backspin: the jog wheel has stopped moving a long time while djay is still backspinning the track. This means I only can use one setting for backspins properly while I would like to have the ability to make backspins as long or short as I want using the jog tension adjust. I have CDJ-3000’s as well and on those devices it works flawlessly (it’s just one setting in the mapping, ‘scratch mode’ I guess it’s called), just like using them as usual with a USB drive in. Is this some limitation that Pioneer puts on mapping their controllers to third party software? Or is it just a shortcoming in the mapping / implementation? Would love to hear your thoughts! Thanks in advance :slight_smile:

How to reproduce the issue:
Get your hands on a FLX-10, run it through algoriddim djay and mess around with backspins with different jog tension settings. You’ll see what I mean.

1 Like
2

Hi @caster25, welcome to the Community! Thanks for the details about the issue and your setup - this is very helpful. Since this sounds repeatable, can you please capture and share a short video of this? Thanks!

1 Like
5


Hey, I just went a little overboard on the ‘short’ in ‘short video’, but I think this captures it perfectly. I also made the comparison with how it should work as I have a CDJ-3000 hooked up, controlling the same deck.

2 Likes
6

The keen I may have noticed that the hot cues weren’t lighting up on the flx-10. This apparently happens when you have Rekordbox still running in the background :sweat_smile: . The jog issue still remains when Rekordbox is exited though, as is to be expected.

1 Like
7

Thanks for the video @caster25. I believe the main difference between the CDJ and the FLX10 is the CDJ uses HID mode. Either way, I have passed this onto our hardware team for further review and comment. I’ll report back when I have more news. Thanks!

3 Likes
8

Hi again @caster25, our team was able to replicate this and is investigating options for a potential fix. When I have more news, I’ll share it here. Thanks!

2 Likes
10

I would like to add that I’m also experiencing this issue.

It feels to me like as soon as you take your finger from the platter, the connection stops and the spinback slows down by a pre determined time. Regardless of how fast the platter is still spinning. The speed of the spinback is determined by the “launch velocity” of the spin back.

My thoughts are that when the platter is activated, it should “latch” on as long as there is movement in the jogwheel, it will release when the jogwheel movement = 0

1 Like
11

1 Like
12

Thanks for sharing @TomThePirate

1 Like
13

This is happening on my REV5 as well. It was noticeable before, but somewhere, an update really made it worse. I’m talking like 3 beats before it starts playing again, but really really slow like I am pitch bending hard. I have mapped backspins to my censor button, but it sounds really bad.

1 Like
14

Hi @SpEd, please provide full details for your setup. Did you recently update your Windows 11 OS by chance?

Device Model (ex. 2020 iPad Air 4th Gen):
Version of operating system (ex. iOS 17.3.1):
Version of djay (ex. 5.1.3):
Hardware/controllers used (ex. Reloop Ready):
Hardware Firmware Version:

1 Like
15

macbook air M4

mac os 26.1

djay 5.6.3

DDJREV5

1 Like
16

Thanks @SpEd. Since this sounds repeatable, can you please capture and share a short screen recording of the issue to help clarify what’s happening? Thanks!

1 Like
18

So I assume there is still no fix for this issue?
its been 7 months now
I just paid for subscription after a trial and was really happy with how the software was working, then when I tried to do a set and spin back I noticed this issue also (ddj flx 10)
It ruined the set
Tried to search for a fix online which led me here,
are we any closer to a fix on this issue?

1 Like
19

Hi @Billy_T, welcome to the Community! Our team is still working on this. I’ll share more news here when I have it.

1 Like
20

Experiencing this with my Rev5 as well. Love the software but the pitch bending thing when backspinning is a lingering annoyance. Any update on this?

1 Like
21

Hi @somerandomdj, thanks for the feedback. We don’t have any updates to share yet regarding this. When I have more news, I will post it here. Thanks!

1 Like
22

Title: Please add advanced jog-wheel inertia and backspin settings

The scratch response and overall jog-wheel feel in djay Pro are already excellent. I do not want to change the normal scratch sensitivity or response.

The problem appears when using traditional two-deck scratch techniques. When I lightly pull the track backward to return the cue marker to the 12 o’clock position, djay does not continue following the physical inertia of the jog wheel properly after I release the platter. I have to pull it much harder than I should.

What I want is very simple:

  • Keep the current scratch feel exactly as it is.

  • Let a light backward pull produce a clear response.

  • Continue following the physical jog-wheel movement after touch release.

  • Allow the track to return naturally to the 12 o’clock cue position through inertia.

I am also frustrated because these controllers are listed as supported on the official djay website. When a controller is officially listed as supported, I expect the physical behavior of its jog wheels to be properly translated into the software—not merely for the buttons, faders, and basic scratch movement to function.

At the moment, the jog wheel and the software do not behave like a truly native integration. The physical platter may still be moving, but djay stops following that movement correctly after the touch signal is released. For a performance-oriented controller, accurate jog-wheel behavior is not an optional extra. It is one of the most fundamental parts of the controller.

Calling a controller “supported” while an essential part of its jog-wheel behavior remains incomplete is extremely frustrating, especially when this limitation has already been reported and acknowledged.

I understand that automatically optimizing this behavior for every MIDI and HID controller may be difficult. However, VirtualDJ addresses this by exposing advanced parameters for jog behavior. Users can adjust scratch sensitivity, pitch-bend sensitivity, backspin after touch release, and the spin threshold separately.

Could djay Pro add an optional Advanced Jog Settings section with controls such as:

  • Backspin after touch release: On / Off

  • Backspin trigger threshold

  • Jog inertia gain

  • Inertia decay

  • Forward-spin continuation

  • Separate scratch and pitch-bend sensitivity

These options could be hidden under an Expert or Advanced menu, with a Reset to Default button. Beginners would never need to touch them, while advanced users could properly tune controllers such as the Beatpad 2, DDJ-REV5, and other performance-oriented hardware.

This does not require changing the excellent default scratch feel. It would simply allow users to adjust the behavior that occurs after the platter is released.

If universal automatic calibration is difficult, please give advanced users the tools to tune it themselves. A controller advertised as supported should deliver jog-wheel behavior that feels genuinely integrated with the software—not merely mapped well enough to perform basic operations.

1 Like
23

Hi @zdup, welcome to the Community! Thanks for the detailed feedback - I have shared this with our dev team.

1 Like
24

Thanks for sharing this with the development team—I appreciate it.

I have one question.

While reading other community posts over the past year, I’ve noticed that similar jog-wheel reports often receive the same reply: “I’ve shared this with our development team.”

However, I rarely see any follow-up after that.

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?

  • Will users be informed if the request is accepted, rejected, or considered technically impossible?

  • Or should we simply assume there will be no further response unless it appears in a future release?

I completely understand that not every request can be implemented. I’m simply hoping for a little more visibility into the process.

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.