Personally it´s all about the workflow. Testing out a song in different BPMs and pitches and being able to write musical sketches fast and easy. That´s actually the reason I first started using Tracktion, leaving Cubase behind... But, there may be many good reasons why the timestretch (ACID-like) feature is high priority for many Tracktion users. And I think most users will agree that the timestretch already in there is not very inspiring to work with, except as maybe an effect...longimanus wrote:Well, even the best timestrech I've heard cannot stretch very far before sounding weird, no more than a few (very few) bpm higher or lower (depending on the instrument, of course).asha wrote:longimanus: You can actually "compose" your own loops you know? And for those of us who combine working with loops and "real" instruments it would be great to have a good native timestretch in Tracktion.
Exactly why I asked the question. If it's such an important features for so many, why not use a program that was built from the ground up for this single functionality like Acid. It took years to develop Acid, with this single purpose in mind, and to expect the same functionality from a program that wasn't built for that within a few weeks or months or years even is not very realistic imo.And by the number of votes I think we can see quite clearly it´s a feature many of us would like to see in the future...
Unless Mackie buys a ready made algo and integrate it, but then we can say goodbye to cheap upgrade...might as well buy Acid and rewire it.
Anyway, let´s not make Rock´s job even harder by debating our personal opinions on timestretch in this thread. I think people who vote have a clear opinion why they want it in Tracktion...
)
