You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, can someone explain why this is necessary? Why making the song faster or slower causes clipping and then need gain reduction which is most of the time at the maximum at 0.75?
When I use --ignore-clipping and then check the file inside Cubase, then there is no clipping visible. So I don't understand this behaviour.
Thank you :)
The text was updated successfully, but these errors were encountered:
Because the stretcher works by adjusting phases of the frequency components separately from one another, it can easily end up adjusting some components for an additive effect in the output (or the opposite - the output signal level can vary both up and down somewhat independent of the perceived volume).
The stretcher itself doesn't do anything about this - it just leaves it up to the caller to decide whether it matters and, if so, what to do about it. But in the command-line tool, when the input and output are both encoded into a fixed range (as with PCM WAV files), this can result in clipping, so the tool takes the simplistic approach of reducing the gain and restarting.
Because the command-line tool exports to a fixed-range (PCM24) WAV, the exported file will already be clipped - any values out of range will be clamped into range on export. So on inspection you may see "flat tops" but you won't see any out-of-range values.
Hi, can someone explain why this is necessary? Why making the song faster or slower causes clipping and then need gain reduction which is most of the time at the maximum at 0.75?
When I use
--ignore-clipping
and then check the file inside Cubase, then there is no clipping visible. So I don't understand this behaviour.Thank you :)
The text was updated successfully, but these errors were encountered: