It’s an old issue but still there. When using detect silence on multiple events some parts are vanishing completely. According to Steinberg this Bug should have been repaired since N13 vs 55…. but nope….
My suggestion to Steinberg: I think that this issue has to do with the speed of processing the events. When you open detect silence it first analyzes the content (it needs a fraction of a second) to get the preview ready according to the parameters. If you have multiple events selected and you have “process all selected events“ checked, it seems that detect silence doesn’t give the enough amount of time to itself to analyze the content. Therefore is cutting out some of the parts, even if they have content.
Does this still happen if you uncheck ‘process all selected events’ and do the processing one event at a time, making sure that the settings suit each event? Could it be that the processing cuts out certain events because their level is below the open / close thresholds?
It haven’t happened at our end, (we are on apple M1 by the way)
Sometimes the AI interrupts slightly cutting down the tail, but we’ve shared a few useful tricks you may already be familiar with. The algorithm feels a little dated, and we hope Fraunhofer updates them
Unfortunately SB cannot do much here but reach out to them.
i also wish this feature would work better and more reliable. To me i never really understood how it operates as tweaking the parameters don’t result in what i would think they should do. I’d expect the parameters to be those of a gate but they simply aren’t. I also had clips vanish completely which at some point i decided to not use the function anymore.
Also when having clips that are completely empty (flat line) which you want to “filter” from those with sample information you’d expect detect silence should do the job, but no. Setting the threshold to e.g. -60 just doesn’t work