Quick Sign In:  

Forum: VirtualDJ Technical Support

Topic: How to script, get_bpm, to show more decimals
How can one see more significant decimals, for say the BPM ?

have tired below, and get the same as what is displayed in the deck's song info (and skin's jog) the BPM with 2 decimals.
get_bpm absolute & param_cast 'float' '000000000' & debug


have tired
get_bpm absolute & param_cast 'frac' '0000000000' & debug

and get, it seems the rounded number of 3 decimal places.
(that is when setting browserBPMDigits to say 9 one sees 3 decimal places in the browser (NOT 9)

(BPM column, and above script outputs:
RESULT...............Browser Col BPM
0.99....................144.994
1.00....................144.995 ................... << should this be outputting 0.99 since asking only for the frac (can trunc work with frac ?)
.
.
1.00....................144.999 ................... << should this be outputting 0.99 since asking only for the frac
0.00.....................145.000
0.00.....................145.001
.
.
0.00.....................145.004
0.01.....................145.005


Summary:
How can one see more decimal accuracy of anything, and in this case, the BPM ?
(cannot get script to show even the 3 decimal places, that can be displayed in the browser column)

VDJ is storing the BPM with more accuracy then the 3 decimal places.
How can one display that additional accuracy?

would like a script to output, say ... 145.00127
or to the limit of the stored VDJ accuracy, if less then 6 decimals.



learning how to work with: param_cast
 

Posted Sun 24 Mar 24 @ 10:28 pm
locoDogPRO InfinityModeratorMember since 2013
param_cast '0.000'
3 decimal places, Accuracy is a good thing but chasing anything smaller than 1000ths seems pretty pointless.
 

Posted Sun 24 Mar 24 @ 11:04 pm
locoDogPRO InfinityModeratorMember since 2013
in skins there's
format="%Pbpmexx"
see textzone format stuff
 

Posted Sun 24 Mar 24 @ 11:11 pm
thanks so much for the quick reply, locodog..

I was going to ask if you had checked since:
get_bpm absolute & param_cast '0.000' & debug

still gave a result of only 2 decimals..



then checked running the script:
`get_bpm absolute & param_cast '0.000' `  

in name field and it outputs the 3 decimal place BPM

WOOT !

thanks again..



PS
must be something related to debug.. that limits output to 2 decimal accuracy.

 

Posted Mon 25 Mar 24 @ 2:25 am