Hi, I noticed when stretching samples and changing the stretch parameter from 1.000 to say 1.012 this value is changed to 0.734 after reloading the project. Looks like a bug.
I'm using Speedrum with Reaper on Linux. Thanks!
Speedrum wrong stretch value after reload
-
- KVRist
- 354 posts since 19 Aug, 2020 from Earth
I can't reproduce it...
Did you change the host tempo after stretching that layer? Because when the host tempo changes, the stretching also changes because it is linked to the beats, i.e. bpm.
Did you change the host tempo after stretching that layer? Because when the host tempo changes, the stretching also changes because it is linked to the beats, i.e. bpm.
-
- KVRist
- 354 posts since 19 Aug, 2020 from Earth
Does it always happen or only sometimes? On all samples or only certain ones?
-
- KVRer
- 2 posts since 3 Oct, 2019
Let me give you an example of the issue I am having.
I start a project that has host @ 120bpm
I load a kit where each sample was created @ 120bpm.
I enable Stretching for each pad , and the stretch ratio at 120bpm is 1.000.
That's correct---the sound is exactly as the original samples as is the duration of the sample.
While the project is open I change to 130bpm, the ratio goes to .922.
That's correct.
I change to 110bpm. the ratio goes to 1.090
That's correct.
The issue comes when you load a project with the very same kit that has a different host bpm than the original.
I start a project that has host @ 110bpm
I load the very same kit as above where each sample was created @ 120bpm.
The stretch ratio shown for each pad is 1.000.
This is not correct--the stretch ratio @110bpm with very same kit when the host was started @120bpm was 1.090! As a result, the samples are stretched differently and when you play the samples, they sound different than they did with the above example even when using the same BPM--and the duration of the samples are shorter than they were in the first example also.
That happens because you are resetting the baseline of the stretch ratio upon loading a new project with a different BPM. That baseline needs to remain locked to the samples on the kit itself, not the host bpm at project load time. If a 16 beat sample was created at 120bpm, that needs to remain the baseline, or 1.000, for the stretching. If a new project loads at 110bpm, the stretch ratio for those very same samples in that very same kit needs to be 1.090, not 1.000. Otherwise, that 16 beat sample is now reduced to a 14.75 beat sample.
-
- KVRist
- 354 posts since 19 Aug, 2020 from Earth
It's a bug, thanks for the report and explanation.