(Sometimes) Stop the Voices, Please!
Feb 04, 2020
I have been working on a large project for several months. At one time I had contacted support with a question about stopping voiceover for slides on a conditional basis. I got help and thought I had the solution nailed, then proceded to apply that solution liberally to slides throughout my project.
Today I went back to testing and discovered the "fix" is no longer fixed: the conditional triggers I've set up everywhere are not holding back the voices as expected. I wonder if something changed in one of the many subsequent SL updates?
I have tried this from opposite approaches: PLAYING the voiceover when the opposite of the condition is FALSE (the solution from the Support Team; illustrated in 1st slide), as well as PAUSING the voiceover when the condition is TRUE (illustrated in 2nd slide). In the attached sample, one of the variables is manually triggered , simulating one of the 3 conditions where the voiceover would NOT play. This is crossreferenced in a TXT box on both slides, for easier troubleshooting.
I just cannot seem to crack this nut on my own. Does anyone see what I am missing here? It seems like this should be a simple deal with straightforward use of variables.
3 Replies
You have the condition set to "or" for three potential variables. Two of those are set to false so they meet the condition. If you set them all to true, the audio doesn't play.
I created a recording to show what's happening and a fix, assuming I understood what you're doing.
https://360.articulate.com/review/content/8a1b54dc-b676-4a06-838c-adb67f87bd71/review
Thanks, Tom - you correctly understood the scenario: stop the audio IF ANY of the 3 conditions are met (triggered by variables). I can implement the 4 trigger fix you recommend, but I have literally 100+ slides to which this would need to be applied, and that grind-it-out work is not fun to think about.
Your video explainer DID however give me some ideas about timeline, and how my earlier thinking was getting in the way. Because I am lazy (and tenacious!) I put in a little extra problem-solving effort, which resulted in a solution that will be 50% easier to implement. The trick is to BALANCE the two offsetting triggers:
This approach, in just 2 triggers, effectively PAUSES (or STOP) media IF any of the variables is already satisfied (which is always the case in my design).
CHEERS! Thanks for getting me a little further down the road! Always much appreciated!
~Brad
This discussion is closed. You can start a new discussion or contact Articulate Support.