Time stretch downgraged - Can someone from CW confirm or deny?

There are better tools for time stretch. Why not use your mouse to stretch it? If that isn't good enough for you, then you should use Audio Snap or a non native program like Melodyne.

I agree with Ian, I never understood that change, those extra decimal places made a big difference for time stretching accuracy.

Bigdogs - I don't think that true.  If I timestretch to a target tempo in S8.5, at the end of the song it's still clicking along w/ the metrinome.  In X2 if I do the same thing, it's way off by the end of the song.  I think the displayed decimal points are what you get in X2.

I see that if you type in a value of 3 decimal points, it changes the length.  But when you play around with this, X2 does erratic computations-IE, it doesn't work.  It doesn't seem possible to stretch accurately to a target tempo in X2, even with trial and error.  I really think they've made timestretch less functional in X2!

Can someone from Cakewalk please confirm or deny this?

As you probably know, the Bakers don't watch the forum that closely. If you really want this fixed, you'll want to file a formal problem report. Even though one decimal point is probably "as intended" for this release, I suspect they would probably get it fixed sooner rather than later, since it was better in earlier versions.

I can check it, but it seems pretty clear you've confirmed it won't do 3-decimal place precision any more.

A workaround might be calculate the new end point yourself, and drag-stretch the clip it to that point.


EDIT: I checked it out. It seems Bigdogs is right... and then some. Not only can you enter a precision of three decimal places, you can enter as many as needed to get 1-sample precision, and it will stretch to that precision, even though it will only display 1 decimal place in the inspector when it's done. Slipstretching also works.

If you have an example of a particular  stretch scenario that didn't give you what you wanted, please post exact numbers (e.g. start end, new end, expected stretch percentage), and I'll try it.

John and brundlefly.

I'm playing around with the timestretch in a different song than before and it seems to work OK in this song.  So I think you both may be right.  X2 may have made some incorrect guesses before.  Or it might be a programming thing with the new release.  It definitely doesn't work correctly in the previous song though.  So now it's an intermittent problem... the worst kind.  But at least CW intends for it to work!

Thanks guys.  I'll update if I learn something more.

Ian

I'd really like to see an example that doesn't work, as I haven't been able to break it.

If my math is right, 5 decimal places will give you a sample-accurate stretch up to a stretched length of about 7.5 minutes (based on 44.1kHz). Above that, you'll need 6 decimals, and that will cover you up to 75 minutes (coincidentally right around CD-length), and 7 decimals will get you up to 12.5 hours (another factor of 10)!

Of course, I haven't tested anything above the 7.5 minute mark to see if SONAR will process more than 5 decimals. I would think it should, but I don't want to think about how long it will take to process a stretch that long!

true: http://snag.gy/QKjmO.jpg

brundlefly - I went back to the song that didn't work and it still doesn't time stretch properly - every time!  So it's really (probably) a corrupted file issue.  Or, more likely, an imperfection in the coding.  Something I did was a contingency X2 wasn't set up to handle.  These things happen as I'm sure you'd a agree?

Thanks for your insistence that X2 wasn't basically at fault.  It got me troubleshooting some more and helped me.

Thanks guys,

Ian

that's a good point and I agree. features should carry over from old versions, and they don't.


me, i'd like to have the OLD OLD timestretch quality (bad quality on purpose) and it seems that every time that checkbox moves and I cant find it. its like hide and seek.