Hi,
Version used: Virtual DJ 7.4.7
I've found an issue with smart_cue. I've been using it to trigger hot cues in the same way that smart_play is used to quantize play to the nearest beat. I've found that it seems to use a different method for choosing the nearest beat as smart_play. The method it seems to use is the nearest calculated beat point instead of using a fixed BPM based beat grid. It works well during kick drums but falls down when there is no beat to lock on to, breakdowns, outros etc.
In other words, smart_play works consistently throughout an entire song regardless of the audio signal as it keeps to the beat grid BUT smart_cue doesn't.
As Virtual DJ 7 is no longer under development, if simple, could the method of smart_cue be updated in a future release to use the same method as smart_play? Also, can anyone confirm that my findings are correct?
Many thanks
Version used: Virtual DJ 7.4.7
I've found an issue with smart_cue. I've been using it to trigger hot cues in the same way that smart_play is used to quantize play to the nearest beat. I've found that it seems to use a different method for choosing the nearest beat as smart_play. The method it seems to use is the nearest calculated beat point instead of using a fixed BPM based beat grid. It works well during kick drums but falls down when there is no beat to lock on to, breakdowns, outros etc.
In other words, smart_play works consistently throughout an entire song regardless of the audio signal as it keeps to the beat grid BUT smart_cue doesn't.
As Virtual DJ 7 is no longer under development, if simple, could the method of smart_cue be updated in a future release to use the same method as smart_play? Also, can anyone confirm that my findings are correct?
Many thanks
Posted Thu 04 Feb 16 @ 10:12 pm
The functionality of smart_cue in v7 is not going to be changed at this point.
In v8 smart_cue uses the beat grid in combination with your globalQuantize setting.
In v8 smart_cue uses the beat grid in combination with your globalQuantize setting.
Posted Fri 05 Feb 16 @ 12:06 pm