| 2019-10-15 11:09:39 |
ronso0 |
description |
the effect beat syncronisation (quantize) is very helpful of course, but it's behaviour could be improved so that 'quantized' effects somehow result in the same absolute delay/period time for a wide range of track BPMs.
current situation:
the default 'time'/delay parameter works well for tracks up to like 130/140 BPM, though it fades to fast for 160 BPM tracks, and fades to long with a 55 BPM track respectively.
Adjusting the 'time' to match the BPM(*2 or /2) for every newly loaded track is annoying.
idea:
somehow consider the absolute 'time' default (0.5s?) which is used when no beatgrid is available, and make 'time' snap to the beat fraction (1/2, 1/4, 2, ...) that's closest to 0.5s with the track BPM when effect 'quantize' is enabled.
example:
If the default echo delay is 1 beat, it would be 2 beats for the 160 BPM track I guess, and 1/2 beat for the 55 BPM track.
related:
lp:1518185 (stepped) BPM Sync for effects |
the effect beat syncronisation (quantize) is very helpful of course, but it's behaviour could be improved so that 'quantized' effects somehow result in the same absolute delay/period time for a wide range of track BPMs.
current situation:
the default 'time'/delay parameter works well for tracks up to like 130/140 BPM, though it fades to fast for 160 BPM tracks, and fades to long with a 55 BPM track respectively.
Adjusting the 'time' to match the BPM(*2 or /2) for every newly loaded track is annoying.
idea:
somehow consider the absolute 'time' default (0.5s?) which is used when no beatgrid is available, and make 'time' snap to the beat fraction (1/2, 1/4, 2, ...) that's closest to 0.5s with the track BPM when effect 'quantize' is enabled.
example:
If the default echo delay is 1 beat, it would be 2 beats for the 160 BPM track I guess, and 1/2 beat for the 55 BPM track.
related:
lp:1518185 (stepped) BPM Sync for effects
lp:1656225 discretely valued effect parameter knobs
lp:1740372 show ControlPotmeter and EffectParameter values in skins |
|
| 2020-03-05 19:52:43 |
ronso0 |
description |
the effect beat syncronisation (quantize) is very helpful of course, but it's behaviour could be improved so that 'quantized' effects somehow result in the same absolute delay/period time for a wide range of track BPMs.
current situation:
the default 'time'/delay parameter works well for tracks up to like 130/140 BPM, though it fades to fast for 160 BPM tracks, and fades to long with a 55 BPM track respectively.
Adjusting the 'time' to match the BPM(*2 or /2) for every newly loaded track is annoying.
idea:
somehow consider the absolute 'time' default (0.5s?) which is used when no beatgrid is available, and make 'time' snap to the beat fraction (1/2, 1/4, 2, ...) that's closest to 0.5s with the track BPM when effect 'quantize' is enabled.
example:
If the default echo delay is 1 beat, it would be 2 beats for the 160 BPM track I guess, and 1/2 beat for the 55 BPM track.
related:
lp:1518185 (stepped) BPM Sync for effects
lp:1656225 discretely valued effect parameter knobs
lp:1740372 show ControlPotmeter and EffectParameter values in skins |
the effect beat syncronisation (quantize) is very helpful of course, but it's behaviour could be improved so that 'quantized' effects somehow result in the same absolute delay/period time for a wide range of track BPMs.
current situation:
the default 'time'/delay parameter works well for tracks up to like 130/140 BPM, though it fades to fast for 160 BPM tracks, and fades to long with a 55 BPM track respectively.
Adjusting the 'time' to match the BPM(*2 or /2) for every newly loaded track is annoying.
idea:
somehow consider the absolute 'time' default (0.5s?) which is used when no beatgrid is available, and make 'time' snap to the beat fraction (1/2, 1/4, 2, ...) that's closest to 0.5s with the track BPM when effect 'quantize' is enabled.
In Preferences > Effects, show Tempo Quantize Options to set the BPM range for which the default scaling should be used, for example 80-150 BPM.
Apply adjustment to file BPM (disregard rate slider), and do this only when a new track is loaded.
example:
If the default echo delay is 1 beat, it would be 2 beats as soon as a track faster than 150 BPM is loaded, likewise change it to 1/2 beat for tracks slower than 80 BPM track.
related:
lp:1518185 (stepped) BPM Sync for effects
lp:1656225 discretely valued effect parameter knobs
lp:1740372 show ControlPotmeter and EffectParameter values in skins |
|
