![]() Specially things get quite notable with longer material like in your case. For this reason (and also in combination with the Cubase Engine and depending on the amount and size of the stretch factors) the resulting waveforms can not be sample accurate in most positions.' 'the élastique algorithm from zplane analyses larger “sample-blocks” internally, thus achieving very good tonal results. This is the explanation I got from Steinberg: locate the beginning of the first verse by using any of the navigation commands. ![]() ![]() When you are done, press enter to save your changes. I made a quick video comparing the latest to the older version 2.28 engine with some drums. Press shift plus tab about three times to enable the pre-roll before recording, and then tab twice to find an edit box that lets you specify the number of measures. Ive solved this with using the classic cut, quantize, timestretch(if necessary) annd crossfade workflow and havent come across the offset issue.īut its also somehow the nature of the beast- elastique isnt sample accurate but uses blocks of audio- there are similar 'issues' in Cubase and Reaper- the renderings of edits with quantize markers arent completely on par with edited audio. REAPER version 4.73 brought us the new Elastique V3 time stretching engine. Well the quality issues I was having were solved with 3.2.2 when they updated the Elastique to the last version.īut I also from time to time see this offset when using solo mode(with bend markers) with certain material.
0 Comments
Leave a Reply. |