It would actually be very helpful if WaveLab offered workflow support for this kind of correction.
At the beginning and end of the recordings there is a click. That’s where you place markers.
One track is the reference track. All other tracks are manually aligned precisely to the beginning or end using these markers.
Then the missing markers will be added to the tracks whose length will be modified so that the program can calculate the time offset.
(A new marker type in an Audio Montage would be needed for this — a marker that is anchored to a specific track, but whose marker line still spans all tracks so you can compare them accurately.)
After that, a function like “Match Lengths” could be executed, and WaveLab would calculate everything automatically within the Audio Montage.
(Or alternatively in a dedicated batch process, where the markers have been set beforehand for each file.)
This is just an initial idea …
Up to now the workflow has been very cumbersome, and as of now it doesn’t work anymore.
As a WaveLab user, however, you only set the markers for “MarkerStart ---- MarkerEnd” and can read this out precisely.
However, the files in the recording devices have different lengths. And in the dialog, you only ever refer to the file length.
You would have to calculate all of that yourself. But that’s what the computer is for. And no, I don’t want to cut the files. They have to stay as they are.
The program has all the information and could make it user-friendly, I think. So, enter the “target duration” between two specific markers. The program calculates the rest.
Have put some hours in it and with the help of … have a solution with ffmpeg and ruberband … With WaveLab I only measure and put all aligned together again.
For Windows in the PowerShell-ISE and with the help of ffmpeg:
What would help if one can copy with Strg + C the red marked sampleValue. But I get other values and have to type every number by myself. (I try to set the focus in the red marked field and press CTRL + C and copy the result in the editor-window … the result is in the edit window picture.)
And in Nuendo … as an unexperienced user myself in Cubase and Nuendo … I had no idea what to do and how to handle the situation. … and was overwhelmed and afraid of pressing the wrong things.
When you do such a little time stretching, you have of course to select time accuracy and not pitch accuracy. I don’t read German well, but according to your picture, it seems that you did not select the correct option.
Yes… but I want both — time and pitch correction at the highest quality. With the script, there is now a way to achieve this, so I do have a working solution using the Rubber Band algorithm.
I’ve read that WaveLab 9 used different algorithms, and that they were quietly replaced in later versions. But why were they changed?
If there is an option, it’s because you can’t have both at the same time. An audio algorithm always has to make some compromise. Especially one which is complex as time correction is.