Digital Workshop

I have been experimenting with autonarrate and have run into a snag. I know it should be a simple fix but obviously I am missing something. Here's the problem:

I have the text on the screen. Below it is a speaker icon and with a mouse over it tells you to double click to hear the text. When you double click the autonarrate begins. So far so good this works fine.

The problem is I cannot get the autonarrate to stop when I leave the page. I have tried the 'stop autonarrate' action with a hide trigger for when you leave the page. Then I tried putting the action on the "next" button but niether seems to work.

What am I missing?

Thanks
Dave
Opus Pro 4.5, Windows XP, Pentium 3

Have you selected the text item with the autonarration to stop in the Stop Autonarrate action? I've just done a quick test here and it works fine for me.

Hi Duncan

Yes, I did make sure that the appropriate text was selected but it didn't work. The text with the autonarrate does appear in the stop autonarrate action so Opus is recognizing it is there so I am confused as to why it would not work.

Thanks
Dave

I am still having trouble and was wondering if anyone else has had similar issues. I have tried simlifying the issue by attempting the same action with only audio and not autonarrate and still can not get it to work. Here is what I tried:

Created a button on the page with the action to play a sound file (an mp3).
In the page properties I set on hide stop wav file and selected the file from above.
When I test it out the sound plays when I click the button but it does not stop playing when I leave the page.

Am I missing something? Any help would be appreciated.

Thanks
Dave

Hi Dave,

I had the same problem with a sound that plays continu.
But there is also a checkbox.

Stop sound when page changes.
I tried that one and that works.

Kind regards,

Dave,

Where you have the action to change the page, put an action before it to stop the autonarrate.

If you have more than one action on a trigger and one of the actions is to go to next page, always make the go to page the last action.

Never set an on hide action on a page. Pages do not work in the same way as other objects. As soon as you move away from a page all it's actions will be lost.


Regards

Brenden Knifton

Hi Oscar

Thanks for the quick response. I had not seen the check box and it does fix the issue for the test page described with the button. Unfortunately, when I go back to my original problem, where I am using autonarrate, I can not find the same option. In other words the "play auto narrate" tab in the properties does not have a stop on page change click box that was available on the "play sound" tab.

We are so close. Any other place I might be able to find the option?

Thanks again
Dave

Hi Brenden

Thanks for the suggestion. I will try it out. The only issue will be that the action will have to be added to each button / object that allows the user to navigate out of the page (for example next, last, home etc). Is there a means of attaching the stop autonarrate to a single point that is triggered by leaving that page similar to the check box in the sound tab? Perhaps a script (I am a real rookie in that area)?

Thanks

Hi Dave,

The suggestion Brendon did works fine.
So if you create an action to stop the sound before navigating to another page you can stop the sound.

You can use script to stop autonarrate.
Then you can use a masterpage with stop next previous buttons etc. and use variable.StopAutonarrate() where variabble is the name of the textfile to stop autonarration.

If you need an example please let me know then I'll build a workaround for you.

I hope this helps.

Kind regards,

In my opinion the standard action is the way to go. There is no need to use script. In most cases the standard actions should be used, the scripts are there for when you want to create more complex sets of actions and programming. The big advantage of Opus is that most things can be done without the need for script.

If you have a lot of buttons then the master page suggestion would be a good way to reduce the number of actions you need to add to individual objects. If master pages are not an option then you can always copy and paste actions to save time.


Regards

Brenden Knifton

Try this: After your Stop Autonarrate Action, insert a Delay and set it for 1 second, THEN have your Go To Page.

Thanks for all of the help and sugestions. I tried the master page idea and it worked well and was suprisingly easy. It will also make additional autonarrates I develop a breeze!

Thanks again to all.
Dave