Silence detection

[AladnaFm]

Hi Bernd.

We have a silence detection set up.
It always works for a while and then I need to change the date in the startprogram script line.

Screenshot_2015-03-26-19-32-15.png (229.4 KiB) Viewed 8556 times

If I changed the date to a more recent date is works fine again.
but that is not all, lately forwarding a program is taking a lot of time.
When the silence detection is kicking in it is generating a new playlist and it says: forwarding program.
Normally it should take a few seconds to add some songs and starts playing.
Lately it is not loading any songs more.

When I tested the command line:
PROGRAM_STARTSCRIPT |Automaat|2015-03-22 16:00:00|true
it says the command line is 'ok', it opens a playlist but adds no songs to it.
It says please wait, program forwarded. For about 30 till 60 seconds! And then it adds some tracks.
Before it was taking a few seconds to do that!

What is the best way to create a silence detection?
We want to open a new playlist anf execute a script.
Why do we need to enter a date for that script line?

Greetz Jesper

[radio42]

That more sounds like a history issue!

Since v3.0.13.5 the script-processing logic was change!
If a script-line violates all history-checks that script-line will be now be skipped (if all entries are contained in the history!)
Previously the last found track would be used regardless. Therefore a new “UseLastTrackOnFinalFail” script option was added.

So the question is how big are the media libs and how big is your global history (or media lib history).

See also here:
viewtopic.php?f=4&t=1000&hilit=UseLastTrackOnFinalFail
viewtopic.php?f=9&t=620

To check, if it is the history, temporarily either add the “UseLastTrackOnFinalFail” option or specify the ‘SuppressHistoryCheck’ option with all script-lines.

[AladnaFm]

Uselasttrackonfinalfail option is already on.
It is loading tracks but it takes up to 60 secs before it add tracks and starts to play.

It is the same script that is during the day every hour is generating a playlist within seconds.
So if it is history related it would have the same issues during nonstop right?

Is there also a command for openening a pre made playlist?

[radio42]

Try to set the global and ALL your media histories to 0 and see what is happening.

During the day the script wouldn't roll forward. It only rolls forward if the script is started late. That's why you might not recognize it during the day. I am pretty sure it is a history issue!
What is the size of your histories?
And how many tracks does your different media line contain?

[AladnaFm]

Tried your advice: changed the script to 'suppresshistorycheck' and set global history '0'
Tried the 'uselasttrackonfinalfail' also
Still the same problem, so no history problem i guess?

Normally the media lib history is 0 and the global history is 750.

I got it working half now and found the problem.
I was using this line before: PROGRAM_STARTSCRIPT |Automaat|2015-03-22 16:00:00|true

NOTICE I'm using a date from the past 2015-03-22 and that is what you said a script that started late.

But when I use this command line: PROGRAM_STARTSCRIPT |Automaat|2015-12-31 16:00:00|true
I used 2015-12-31 as a date. A date in the future and I tested the command line.

Result: It was working smooth and was adding tracks directly.

HOWEVER: Now it is loading tracks quickly and good it won't start!? The autoplay is on and even if I manually toggle it on it ain't starting the playlist because the start date now is in the future and it waits till that date/time, right?

So my question: why do you need to enter a date in that command line? Because you never know when a silence detection kicks in, right?
Only thing it needs to do is open a new playlist and add some tracks from a script that is not marked with a date/time.

Something like this: PROGRAM_STARTSCRIPT |scriptname|duration|

[radio42]

I didn't notice, that you used a date that far in the past.
Eg using that date today would mean, the script needs to be rolled forward for 6 days, this effectively might take some time!

The date and time is needed to start the program on time.
If you always want to start it NOW, you can use the ${now} macro instead of a real date. For example:
PROGRAM_STARTSCRIPT |Automaat|${now}|true

[AladnaFm]

Ok thank you for your help.
I will try the ${now} macro code instead of date.