Investigate Silent detection
Re: Investigate Silent detection
Hi Bernd,
Thanks for your reply.
Herewith my feedback:
Mixerchannel Silence detection: -35 dB - Silence for at least 30 sec.
Condition: Only on scheduler, action: Auto play
Routing:
DJ player(s) Rout -> no sounddevice Virtual subbus 44,1 Khz (out2)
stand by -> no sounddevice Virtual subbus 44,1 Khz (out2)
Full duplex -> no sounddevice Virtual subbus 44,1 Khz (out2)
PFL -> no sounddevice Virtual subbus 44,1 Khz (out2)
Cartwall 1 + 2 -> no sounddevice Virtual subbus 44,1 Khz (out2)
Overlay -> no sounddevice Virtual subbus 44,1 Khz (out2)
Output device config:
ROUT
Samplerate 44,1 Khz
Driver model: None
Output mixer channel: out2 Wave out 2 (orban optimod)
Mute/unmute Output
Enable silence detection
OUT2
Output samplerate 48 Khz
Drivermodel: WDM
Wave out 2 (orban optimod)
Speakerpair: Default
Copy to: None
Output in 32 Bit
Apply master volume (checked on)
Enable silence detection
Cuepoints are automaticly done by de ACPD option, which i have chosen to be re-calc every time he loads a song / programm, etc.
The schedule is been setup as follow:
xx:59:40 Overlay player News starts
xx:02:30 soft start scheduler with early start of 70 sec, and late start of max 120 sec.
Thanks for your reply.
Herewith my feedback:
Mixerchannel Silence detection: -35 dB - Silence for at least 30 sec.
Condition: Only on scheduler, action: Auto play
Routing:
DJ player(s) Rout -> no sounddevice Virtual subbus 44,1 Khz (out2)
stand by -> no sounddevice Virtual subbus 44,1 Khz (out2)
Full duplex -> no sounddevice Virtual subbus 44,1 Khz (out2)
PFL -> no sounddevice Virtual subbus 44,1 Khz (out2)
Cartwall 1 + 2 -> no sounddevice Virtual subbus 44,1 Khz (out2)
Overlay -> no sounddevice Virtual subbus 44,1 Khz (out2)
Output device config:
ROUT
Samplerate 44,1 Khz
Driver model: None
Output mixer channel: out2 Wave out 2 (orban optimod)
Mute/unmute Output
Enable silence detection
OUT2
Output samplerate 48 Khz
Drivermodel: WDM
Wave out 2 (orban optimod)
Speakerpair: Default
Copy to: None
Output in 32 Bit
Apply master volume (checked on)
Enable silence detection
Cuepoints are automaticly done by de ACPD option, which i have chosen to be re-calc every time he loads a song / programm, etc.
The schedule is been setup as follow:
xx:59:40 Overlay player News starts
xx:02:30 soft start scheduler with early start of 70 sec, and late start of max 120 sec.
Re: Investigate Silent detection
Hi Bernd,
thanks for your prompt reply, as well the suggestions.
I will change the silence detection as suggested to a lower dB.
According the scheduler i will change the time to xx:00:00 - as well the ending at xx:59:59
I assume that the overlay player will be prior, so even when i use the max early / late start the overlay has to be finished before the regular schedule will start...
once again thanks for your support!
thanks for your prompt reply, as well the suggestions.
I will change the silence detection as suggested to a lower dB.
According the scheduler i will change the time to xx:00:00 - as well the ending at xx:59:59
I assume that the overlay player will be prior, so even when i use the max early / late start the overlay has to be finished before the regular schedule will start...
once again thanks for your support!
Re: Investigate Silent detection
yes, correctly - when an overlay is running it has prio and a next program will only start once the overlay has finished.
Bernd - radio42
ProppFrexx ONAIR - The Playout and Broadcast Automation Solution
ProppFrexx ONAIR - The Playout and Broadcast Automation Solution
Re: Investigate Silent detection
Thanks for the additional info. I see a couple off smaller issues with this config!
a) Silence Detection:
- the dB value of -35 dB is quite high, ie. you might want to lower it to at least -60 dB
- as you route all strems/players to your OUT2 mixer channel, please disable the silence detection for the ROUT mixer channel
b) Program Scheduling:
Please change the start time of your next program from xx:02:30 to xx:00:00 or even xx:59:41!
In your current setup you would only start the next program at earliest at xx:01:20. E.g. in case the News are shorter than 2 minutes or even unavailable for whatever reason, you will have a break/silence by definition.
I guess exactly this is what might effectively cause your current trouble!
a) Silence Detection:
- the dB value of -35 dB is quite high, ie. you might want to lower it to at least -60 dB
- as you route all strems/players to your OUT2 mixer channel, please disable the silence detection for the ROUT mixer channel
b) Program Scheduling:
Please change the start time of your next program from xx:02:30 to xx:00:00 or even xx:59:41!
In your current setup you would only start the next program at earliest at xx:01:20. E.g. in case the News are shorter than 2 minutes or even unavailable for whatever reason, you will have a break/silence by definition.
I guess exactly this is what might effectively cause your current trouble!
Bernd - radio42
ProppFrexx ONAIR - The Playout and Broadcast Automation Solution
ProppFrexx ONAIR - The Playout and Broadcast Automation Solution