It messes the whole thing instead of rendering it, see video
#Render Speed and Tempo is bugged
burnt mauve
abstract sluice
yes, this is expected
the time stretching and pitch shifting are phase vocoded
so the waveform can change drastically
burnt mauve
So the preview is just lying?
abstract sluice
pretty much, yes. In some sense the preview is always lying, as we don't show sample interpolation either
burnt mauve
So how is someone meant to stretch audio clips so they sync with another?
The preview whole job was to tell me what it will be like after stretching
Heck, I want to render the samples exactly as the preview shows
Just use whatever algoriithm was used for the preview and apply to the clip
abstract sluice
The entire point of the non-destructive stretching is that it's non-destructive - we don't store the change in speed until you render (or play) it
To time-stretch while keeping the phase intact, you need to use Effect -> Pitch and Tempo -> Change Speed and Pitch. This does change the pitch though.
You also can use the Change Tempo effect from the same menu, which instead of a phase vocoder uses a "Waveform Similarity and Overlap Add" approach or, in the case of the "high quality" option in that effect, "Subband Sinusoidal Modeling Synthesis". They have other qualities which may be more desirable to your use case, though we believe our phase vocoder implementation sounds the best across a wide range of content, even if it messes up the phase
burnt mauve
sounds like putting the cart before the horse. I need to make very specific modifications to the files and the program straight up lies to me about the results for the sake of 'non destructiveness'
heck, add a 'render destructively' option that applies it exactly as the preview shows it to be
abstract sluice
non-destructive edits are majorly useful for any sort of music making as it allows you to adjust the pitch and speed without generation loss. To always use destructive effects, use the effects menu only, not the non-destructive time stretching