[issue] Glitch on clip start transposed w elastique!

Hello!

I’ve discovered a rather annoying bug when cutting up transposed audio using the elastique (pro) time algorithm (using C6.5).

Repro:

  • New Project
  • Import or record some audio. A 440hz sine will expose the issue very obviously.
  • Make sure the audio-file algorithm is set to an Elastique Time algorithm in the audio pool.
  • Transpose the clip 12 semitones (or any other amount)
  • Notice smooth playback!
  • Split the clip using the scissor tool into a few segments.
  • Notice “pitchbend” glitch on split-points of the clip.

This is really annoying when doing leveling of individual sections on a transposed piece of audio. I could of course flatten or print the transposed audio, but i like to work as non-destructive as possible, so i would appreciate this bug fixed.

Best,
Rune Borup / FishCorp
Copenhagen, DK

your right ive reproduced your elastique behavior , the transpose seems to be delayed at each start and starts with the original value.
The only cure is to glue the slices back together after editing !

This has been a problem ever since elastique was added to Cubase - I submitted this issue along with problems with disk access on time stretched audio as a bug. They fixed the access one but this one hasn’t been acknowledged.

Switching the algo will fix it (at the cost of possibly making the audio worse) or alternatively do as filterfreak suggested and bounce down an extended bit of audio and trim back the start point.

I constantly have this issue and it drives me mad!

I can confirm that this appears to affect Elasique Tape most of all - ie. it’s the most obvious. Even when flattening the file, the effect can be heard. Yuck.

Steinberg, please acknowledge this issue at least?

BUMP!

I cannot accept that a bug with such an obvious repro goes unrecognized by Steinberg!

+1

Do you still experience the problem if you set the clip to élastique Pro - Pitch?
[EDIT: yes, it is still there, but no where near as bad].
Filterfreak’s workaround is the way to go :wink:.

Hi, :slight_smile:
I couldn’t reproduce. Here a clip that is divided into segments sounds the same as a clip that is not cut into segments.

This will do:

  • New Project
  • Import or record some audio. A 440hz sine will expose the issue very obviously.
  • Make sure the audio-file algorithm is set to an Elastique Time algorithm in the audio pool.
  • Transpose the clip 12 semitones (or any other amount)
  • Notice smooth playback!
    Duplicated the track and reveresed the phase
  • Split one of the clips using the scissor tool into a few segments.
  • Notice “pitchbend” glitch on split-points of the clip.

Still the two clips cancel each other out.

Now uncheck and then check musical mode again.
The two clips do not cancel eachother out anymore.

I cannot confirm this as a bug. Be aware that elastique is a realtime process. This could also be a more or less unavoidable artifact when applying this real-time effect to the segments. However I will report this as a story and it will be investigated by the respective specialists.

Thank you :slight_smile:
Gr,
JHP

Sorry, Jan, but no! Here, I can distinctly hear the test tone “hoop up” the octave at the start of playback…
Test Tone A440_transp.wav.zip (775 KB)
This audio is the bounce of the Cubase test tone, at A440, transposed up one octave (no split), using élastique Pro - Time. Just listen to the start of it!

Hi,
It is also a difference if you position the cursor to the beginning of the clip and then hit space to play or if you position the curser to the beginning of the clip during play mode for instance by hitting Num 1 to jump the cursor back to the clip during play mode. You can also test this by duplicating your testone and then positioning the curser at the beginning of the first clip. When you then press play and you let the cursor run over both clips, the start of the first clip will sound different then the start of the second clip.

Anyway you’re absolutely right. This artifact is in the mixdown you have attached.
I have pasted the link to this thread in the report. Any further observations and aspects are welcome.

Thank you, :slight_smile:
Greetings,
JHP

Hi Jan,
I suspect there’s something else at play here (buffer size? settings in Device Setup>VST Audio System?)
I have just tried all the alternative start methods you suggested, and it “hoops” every time… including the start of the duplicated clip.
However, if I simply split the file, it plays across the split without problem.
It is also o.k. if I start playback after the start of the clip.

So the topic’s starter’s header does sum it up perfectly… “Glitch on clip start” :wink:

Hi,

Yes, this same bug is driving me crazy. I love the new algo’s and it’s a real shame that this bug just makes it really difficult to get exact results. I hope that SB sort it out on the next release.

Thanks

Erin

I just thought I’d mention this bug is at play whether or not any transposition is involved or not. It will “hoop” at the top of the clip using time stretching only. It just ruins a perfectly good tool. This really needs to be prioritized for C7.

Has this been addressed in C7?

I would like to know if this has been addressed in C7 too…

???

It’s driving me mad on a project at the moment.

To be honost, I think this should be fixed in 6.5.5 too. This is a reproducable and confirmed flaw in the program, reported 7 months ago.

The same pitchbend “hoop” seems to be happening when looping back to the Left Locator. This is on a pitch-shifted single event of an entire file of several minutes looping around a short section in the middle.

If I start at or before the Left Locator it doesn’t happen, just when it loops back.

7.0.2, Windows 7 HP, all 64-bit

Just trying to pitch shift some brass samples to make musical phrases… it is now impossible using elastique, which causes a pitch bend at the start of every single segment; the “solo” algorithms all sound like complete and utter sh1te on this sound source, they are all warbly and grainy. There are too many bits of audio to use the workaround of bouncing extra silence on the front.

Bottom line: This tool is completely ruined :frowning:

Please please please sort this out for 6.55 !

Does this problem exist on 6.0 versions of Cubase as well?

When will this be fixed?