I have to split recordings from DAT cassettes into several clips. (50 hours of audio into about 1500 clips)
Background effects and music (Wickie, Popeye, I dream of Jeannie ...) for filmindustry (analog recording into digital archiv).
SONAR has a function to automatically split audioclips.
Each clip must have 750 ms befor it begins.
But it does no matter which value of "Look ahead" is used. 100 ms splits the clip just like 2000 ms. So the clip is always cut about 50 ms befor the audio starts. I cannot do anything with this function.
I have a background noise of -86 dB. It does no matter if the Openlevel is set to -82 dB or -40 dB. And it does no matter if the "Look ahead" is set to 100 or 2000 ms. The clip is always cut about 50 ms befor the audio starts
This function is broken since SONAR exists. Will this ever be repaired?
 
 

Yes it has been broken for more than a decade, I think.

From my perspective, failing to remove it when they know it doesn't work is surprising negligence.

Fixing it would obviously be preferred.

Some years back, Craig Anderton acknowledged the bug. I have submitted numerous bug reports.

Yes, I bring it up from time to time as well. Still awaiting a fix.

gswitz
Some years back, Craig Anderton acknowledged the bug. I have submitted numerous bug reports.

 
It always ends in double work. SONAR cuts the clips ONLY 50 ms before audio starts. Then Wavelab injects 700ms of silence before each file. A superfluos step.
It would be nice if integrated functions would work as expected. Especially when there are a lot of bug reports since light years.

Knowing Noel, there might be some benefit to leaving it in this state over removing it. Noel is a thoughtful and reasonable person.

This sounds like a logical and productive request that makes Users money in time and lost opportunity cost (IE other things that can be done rather than time spent on actions that could be automated).

On the other hand I can see Cakewalk's side... the must be a reason Cakewalk hasn't done it besides it obviously must be a major action.. either it can cause new problems; they know will take an unknown amount of time; they don't know how (doubtful), other problems are higher in que; etc.

I'm just trying to see both sides. But I'm on the User's side. All in all it's probably not like falling off a log. But needs to be done.😊😊

In my opinion "Detecting Silence" or splitting the beginning- and endtails of audio is a "must have" in every DAW.
In my case it helps to split digitized audio - in other case it helps to clean and shorten vocal or instrument tracks.
I make this job since 2005 - and at least since 2005 "remove silence" has never done right.
 
Possibly that CAKEWALK plans for the future new audiofeatures and waites therefore for a revision.
It would often better for me when Cakewalk would sometimes improve some basic functions like:
- normalizing left and right seperate
- detecting highest peak in a clip (without hearing it)
- normalizing a group of clips (detecting loudest peak in one of the clips), so that the ratio remains one to the other.
- And of course Removing Silence with splitting clips and repaired "look ahead".
Also: for 15 years we had an amazing CAL-script-language. It was never expanded for audio-objects. That would certainly be great for a lot of users.

+1 for audio-objects in CAL
 

I've run into this issue as well.
Any batch function/repetitive process that requires the user to circle back and fix the errors saves zero time and becomes useless. Another vote for fixing this.