Detect Silence problem

Hi Everybody,

I use “detect silence” a lot but in N13 I found a problem that is really annoying me. In N12 and previous versions, if detect silence finds a “blank audio” , it erases it and continues to detect the dialogues untill it finishes. In N13 it stops when it finds a blank audio . Then a window pops up saying that nothing is recorded, I click okay and it continues “detecting”…but if right after the blank audio there is another blank audio , this same window pops up and when you click okay, it closes the window and the function shuts down and you can’t continue. I have to erase manually the blank audios.
Is there a setting or workaround for this?
Thanks

We also use “detect silence” a lot to separate the titles on digitized recordings. But for us it works the same way in N13 as in N12 and the empty spaces are deleted. It never stopped when it finds “blank audio”. Instead it will be deleted. And no window has ever popped up.
However, we have not made any such settings.
In any case it works. Something is set incorrectly in your N13 or in the dialog window of “detect silence”.

Same Problem here. When it finds blank audio an error message pops up.
Windows 10 / Nuendo 13.0.2

Are you on Mac or Windows?

I’m on Windows 11.

Thanks for reporting, i can confirm this issue. I’ve created a ticket.
Cheers
Dirk

Interesting because it works for us with Windows 11 Pro.
On three differnet PCs N13.0.20
Maybe someone else will confirm this regarding the Windows version.

There should be no os dependency. I have it always reproducible when i select multiple completely silent events and process “detect silence” on them.

Hi DSabath,
It was not fixed in this update(13.0.30). Do you know if it will be fixed on the next update?
Thanks

Hi, sorry, it didn’t make it into .30 update. Fix will be included in the next update.
Cheers
Dirk

Hi DsAbath…I just found out that when you check the “apply fades” box , no fades are applied at all. Could you please check this problem too ?

Thanks

Roberto

Hi Roberto,
i just checked, but cannot reproduce. Can you post your exact settings in the detect silence dialog (or a screenshot)? Is there anything special about your audio events?
Cheers
Dirk

Hi Dirk,
I found out what happened. The fades don´t apply if the event was already trimmered . When the process doesn´t have anything to trimm, it will not apply any fades.
Sorry to bother you.

Roberto

Hi Dirk,
I´m sorry to bother you again but detect silence was not corrected well. I´m sending a link from a .xml with 1 track and 2 dialogues.
https://drive.google.com/drive/folders/1xrs9guU-lgT5LLsUGrxqFWdAvKiQEBA6?usp=sharing
You can see that both events are recorded but when you use detect silence(Nuendo 13.0.40, both (or one) audio are(is) deleted. Its intermitent and should not happen. Could you take a look please?
Thanks

Roberto

Hi DSabath,
I made some tests with detect silence and I think the problem is with the preroll. When its at minimun, it doesn’t delete the files I sent (last message).
Thanks.

Roberto

Hi Roberto,
i just took some time to import your track archive and detect silence on the events. But i did not get incorrect results so far. I’d need your settings in the detect silence dialog.
Cheers
Dirk

Hi DSabath,
I recorded a video doing and undoing detect silence with various preroll settings. Please see if you can reproduce the problem.
Here is the link to download it:

I usually use the preroll in 30 with Nuendo 12 and works fine.

Thanks

Roberto

I confirm. I use this alot on recorded drums. especially on Toms. I record top and bottom of every drum. Usually the drums are a wild beast but after running detect silence, the drums are tighter than act as a single instrument where I have total control over EQ, Compression, etc.

In Nuendo 13 the detelect silence error on a tom track that has no hits. To get around this , close the error then mute the track.

Its a non issue in Nuendo 12

Thank you very much, Roberto! Just found out, it’s the threshold. If there’s nothing to strip, detect silence deletes the event. I can confirm this was ok in N12 and is now broken.
Looks like no problem for single selection (just cancel the dialog), but i can imagine this is a real issue for multi-selection case.
I’ll work on a fix to be included in the next maintenance update. Sorry for the inconvenience caused by this.

Thank You!!!