Sign In:     


Forum: VirtualDJ Technical Support

Topic: Inconsistent JOG Values When Debugging - Same Code Different Output Compared to PLAY_PAUSE
I am trying to scale the jogwheel sensitivity depending on the bpm of the current song such that one 360 revolution is exactly 4 beats/1 bar. I've run into inconsistencies when debugging with the PLAY_PAUSE button and the JOG mappings. The code I have mapped to both is identical:

get_bpm & param_1_x & param_cast & param_multiply 100 & param_cast & param_multiply 1.222225 & param_cast & debug

The math here is: (1 / BPM) * 100 * 1.22225

Essentially, I'm trying to normalize the BPM, then scale it by a magic number which I hope will scale the sensitivity such that 1 revolution = 1 bar. This code prints what I expect it to when I map it to the PLAY_PAUSE button: 1.22, which is the exact value I found when manually finding the perfect sensitivity for a song with 100 bpm.



The problem is, when I paste the same code into the JOG mapping, the value completely changes to +/- 88000.20.



Can someone help me out here? I feel like I'm so close, is it some sort of type error? Should I be casting the value to something else? By the way, I made a related post about what I'm trying to achieve here: http://www.virtualdj.com/forums/262291/VirtualDJ_Technical_Support/How_to_Achieve_Uniform_Jogwheel_Sensitivity_%28360_degrees_%3D_1_bar%2C_regardless_of_BPM%29.html

Many thanks, especially to LocoDog for creating the Script School posts, I would not have been able to make it as far as I have without it.
 

Posted Sat 18 Jan 25 @ 10:47 pm