IIDEEJAYII
wish to report unexpected change with:
setting 'pitchRange' 25.0
with VDJ 2023 (tested on 7759 & 7831) the above script changes the pitch range for ALL decks,
now with VDJ 24, (tested on 7921 & 8095) the above script changes only the implied (or specified) deck,
(though it still changes the setting in options correctly)
example w VDJ 2024, the above script, if on action deck 1, will change the pitch range of ONLY deck 1 to 25%,
but change the setting to 25.0. and say, leave decks 2, 3 & 4 at 12%. (and the setting > option > pitchRange will be changed to 25.0
Or deck 2 setting 'pitchRange' 25.0 would change only deck 2's pitch range.
NOTE: This could be useful, in some cases, (yet confusing since inconsistent with the what is showing in options)
all works as expected with VDJ 2023
(is a universal setting)
-------------------
PS
the script (verb): pitch_range works as expected changing the pitch range on ALL decks,
and the settings > option > pitchRange
and if one wanted deck specific control of pitch range.. would expect it to be with the verb.. (not the option)
as with: deck 1 pitch_range 50%
but the above script, acts on ALL decks, to 50%, not just deck 1.
just reporting the change.
Win 10
8095
setting 'pitchRange' 25.0
with VDJ 2023 (tested on 7759 & 7831) the above script changes the pitch range for ALL decks,
now with VDJ 24, (tested on 7921 & 8095) the above script changes only the implied (or specified) deck,
(though it still changes the setting in options correctly)
example w VDJ 2024, the above script, if on action deck 1, will change the pitch range of ONLY deck 1 to 25%,
but change the setting to 25.0. and say, leave decks 2, 3 & 4 at 12%. (and the setting > option > pitchRange will be changed to 25.0
Or deck 2 setting 'pitchRange' 25.0 would change only deck 2's pitch range.
NOTE: This could be useful, in some cases, (yet confusing since inconsistent with the what is showing in options)
all works as expected with VDJ 2023
(is a universal setting)
-------------------
PS
the script (verb): pitch_range works as expected changing the pitch range on ALL decks,
and the settings > option > pitchRange
and if one wanted deck specific control of pitch range.. would expect it to be with the verb.. (not the option)
as with: deck 1 pitch_range 50%
but the above script, acts on ALL decks, to 50%, not just deck 1.
just reporting the change.
Win 10
8095
Mensajes Sat 13 Apr 24 @ 7:43 am
Adion
That is correct. The default behavior is indeed also for pitch_range to remain deck independent, but you can add parameter "deck" in case you want it per deck
(So deck 2 pitch_range 20% 'deck' for example)
It was mainly required for some motorized controllers that allow setting different pitch ranges on both decks, but don't allow the other direction (computer to controller) to change the pitch range.
(So deck 2 pitch_range 20% 'deck' for example)
It was mainly required for some motorized controllers that allow setting different pitch ranges on both decks, but don't allow the other direction (computer to controller) to change the pitch range.
Mensajes Sat 13 Apr 24 @ 9:10 am
Adion
Not sure I understand.
If you want to change the pitch range to 25% for all decks, just use pitch_range 25%
If you really want to use setting, you could do deck all setting pitchRange 25.0, just not sure why since there is a dedicated pitch_range script
If you want to change the pitch range to 25% for all decks, just use pitch_range 25%
If you really want to use setting, you could do deck all setting pitchRange 25.0, just not sure why since there is a dedicated pitch_range script
Mensajes Fri 19 Apr 24 @ 10:22 am
IIDEEJAYII
yes since the change (VDJ 2024) I have converted the scripts, that were using setting 'pitchRange' XXX
to pitch_range XXX
since the former behavior has changed
was just posting that there was the change, with builds sometime after 7831 in that the verb setting was not working as expected to change the option, pitchRange
And agree not needed, since pitch_range is the better way to change the pitch range.
PS
done only wishing to point out a possible bug, if it may be of interest, in the spirit of being helpful.
to pitch_range XXX
since the former behavior has changed
was just posting that there was the change, with builds sometime after 7831 in that the verb setting was not working as expected to change the option, pitchRange
And agree not needed, since pitch_range is the better way to change the pitch range.
PS
done only wishing to point out a possible bug, if it may be of interest, in the spirit of being helpful.
Mensajes Fri 19 Apr 24 @ 10:37 am