Used to use WL 6, which had a “process” button that did the work (time stretch) immediately.
WL 12 has “apply” button in time stretch, but nothing happens on this button press, and saved files have no time stretch.
How to make it work?? What a strange redesign…
Tnx
Please describe precisely what you are doing, because this function works properly, and AFAIK, not much differently than how it did with WaveLab 6.
1 Like
Hi!
Check this…
regards S-EH
2 Likes
3 Likes
Thanks for replies everyone.
Yes I read FAQ and did similar to the video, but I get no result in the output file
I wonder if I should use “export” instead of “save as”, maybe? Еxport does not look very understandable to me so I did not try it yet.
Another thing that confuses me is that in Wavelab 6, once I applied the time stretch, Wavelab took a certain amount of time to process it. Wavelab 12 does not seem to do any processing at all. Or could it be just instant, even with “High Quality”? I work with short pieces, like a minute or so. They still took Wavelab 6 quite a time to process.
Save or Export is not needed to apply Time Stretching (just like any other processes under the Process tab). And unless you only try to stretch a few seconds or milliseconds (must be at least 100ms), there should be some time elapsing for the processing (depending on your hardware).
If you don’t even get any results with some extreme setting (like a 1000% rate) on a longer piece of audio (a few minutes), and if you don’t see a “Time Stretching” entry in the History window (see Tool Windows → History) after you hit “Apply”, then there seems to be something off.
2 Likes
Thanks.
Only, what’s the point of any stretching if I do not have the output file, afterward?
My problem is that those files remain identical to the original, after I save them, no matter what I apply.
What do you mean “output file”?
You can’t save the stretched file?
It works here.
Save As or Render, both allow you to create a new audio file with the applied stretch.
I just used Time Stretch for the first time in years.
It worked both flawlessly and was unexpectedly transparent. The client was super happy. Saving the resultant file worked as it should. I checked the resultant file in another app and the new bpm was as expected and correct.
When doing something destructive like this, I always like to save a duplicate file (calling xx bpm) and process that.
I’m on the latest WL 12 build Windows 10 current build.
Looks like the longer the chunk - the more stretch I get, even if I use same “stretch factor” like 110.
If I highlight the whole file and use 110 stretch factor - entire file does become slower.
But if I only want to edit the end of file, like the last minute, and apply the same 110 stretch factor - that last minute almost does not slow down.
But shouldn’t the result be the same speed (110), no matter how long part I try to stretch?? So weird…
So, it does work.?!
If you apply per Target Stretch Factor the processed part should always have the same ratio (using the same settings), regardless of the selection length. When you stretch a whole file of 5 minutes (300 seconds) by factor 110% you will get a result of 5 minutes 30 seconds (300 x 1.1 = 330). When you just select and stretch the last minute (60 seconds) by factor 110% the whole result will be 5 minutes 6 seconds (240 seconds unchanged + [60 x 1.1 = 66]).
Is this not the case for you?
Are you using the option Use Modulation Envelope by chance? Even then the processed part will always have the same average ratio (using the same settings), but time/speed will change differently depending on whether you process the whole file or just a small selection.
