A question for anyone. Does Sl10 use elastique for transform?
I’ve never tried transform in sl but typically respeed/repitch files exclusively via the current Elastique 3 algo…always in Sound Forge Pro as I like the gui Sound Forge uses for elastique. In fact, I don’t use SF for anything other than Elastique repitch/respeed
I use Wavelab for general editing.
My brain is such that I prefer to compartmentalize editing (in the following order) when restoring old tape recordings that will also be demixed…
Capstan for speed stabilization of the intact file
Elastique for preferred repitch/respeed
Spectralayers for any noise cleanup (if at all)
Spectralayers for hum cleanup
Spectralayers for demix
Cubase/Nuendo to load new multitrack splits, create edits.
Port to individual tracks of jh24 (sometimes)
Console mix
While I don’t envision using transform, I may try it soon as the current gui at least has somewhat the same control parameters in SF Elastique 3.
Here’s another tidbit of info I’ve gleaned from Robin…and now also…Zplane…
If I respeed old recordings after Capstan…it’s usually up a few semitones.
Over the past 8 or so years, I had begun to wonder if the “process” of respeeding on Elastique might be somehow better, potentially less-artifacty, less destructive on 192khz or 96khz files rather than 48khz. I operate at 48khz, 32bit float.
My own ears were inconclusive, but I did engage in several lively conversations around 6 years ago on other forums. At that time, I was respeeding/repitching with Elastique and demixing with Stephen Burnsee’s Prosoniq Isolate.
Robin recently commented that higher sample rates may be better…maybe…for respeeding to extremely slow tempos. Which I don’t do.
Zplane communicated with me a couple of weeks ago that they don’t see any advantage of higher sample rates in terms of any destructive component of repitch/respeed.
So for yet another year, I pretty much remain at 48khz/32bit float most of the time.