i dont think I have ever used the manual input for timestretch settings. I just set my project tempo, trim the clip, and ctrl+drag the clip length to the appropriate measure with snap setting turned on - bypassing the need for any calculation. Granted I dont use it too much, but its always worked fine that way for me.

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!

why not just enter a new duration?
also, try entering 100.75 and then 100.7 and then 100.8 and then 100.77 - you'll see the new duration change with each of the stretch amount % numbers so it's definitely rounding to one decimal place in the display but the new durations are different for each of the entries above.

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

great pic. :D

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

It fundamentally works under the hood, but it could do with a bit of an update to make it simpler to use, I think.

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.

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?

Yes, I agree. In the course of testing this, I was initially having the stretch fall short of the target end point by a few samples. Eventually I figured out that my punch-recorded test clip had fallen short of the punch out point by a few samples - an issue that's come up before. After I slip-edited it to end where it was supposed to, the subsequent stretch to 133.928571%  was right on the money.