Just started using the plugin and appreciate it.
I would like to have a chime sound before spoken announcements so have successfully done this as follows:
In each event with an announcement I have TWO speaking items; first is to play a chime file and second is the actual spoken announcement. This works fine with minimal delay to play the chime followed by the spoken announcement.
Now to get fancy and to avoid having two speaking items in each event I thought - why not use the "Event Before" option on the plugin so I did the following:
1) Setup an event called "Chimes" that only plays the file with the chime. This works fine when the event is executed by itself.
2) Set up my announcement events that only speak the specific announcement. These work fine when executed on their own.
3) Added the "Chimes" event in the "Event Before" option on the Airplay configuration page. - now is where it goes off the tracks...
After doing step 3 above - when an announcement event is run there is a very long delay followed by the announcement occurring first and the Chime playing after.
It seems that maybe I created some kind of recursive call with the method that really slows things down and that gets treated like a stack - where the last event pushed down is first event poped back up so that the execution is reverse of expected.
Any thoughts on accomplishing what I was aiming for or should I just give-in and go with the less elegant approach of two speak items in each event (chime and spoken announcement)?
I would like to have a chime sound before spoken announcements so have successfully done this as follows:
In each event with an announcement I have TWO speaking items; first is to play a chime file and second is the actual spoken announcement. This works fine with minimal delay to play the chime followed by the spoken announcement.
Now to get fancy and to avoid having two speaking items in each event I thought - why not use the "Event Before" option on the plugin so I did the following:
1) Setup an event called "Chimes" that only plays the file with the chime. This works fine when the event is executed by itself.
2) Set up my announcement events that only speak the specific announcement. These work fine when executed on their own.
3) Added the "Chimes" event in the "Event Before" option on the Airplay configuration page. - now is where it goes off the tracks...
After doing step 3 above - when an announcement event is run there is a very long delay followed by the announcement occurring first and the Chime playing after.
It seems that maybe I created some kind of recursive call with the method that really slows things down and that gets treated like a stack - where the last event pushed down is first event poped back up so that the execution is reverse of expected.
Any thoughts on accomplishing what I was aiming for or should I just give-in and go with the less elegant approach of two speak items in each event (chime and spoken announcement)?
Comment