I am currently runing storyline 1. I have all the animation and text displaying correctly in line with the audio narration. When I publish to the web the content becomes out of time with the audio?
Is there any way to fix this easily?
I am currently increasing the time duration between the end of the audio and the progress buttons appearing with limited success. Even with clearing all of the browser history before rerunning. I have tried this in both Fire fox and chrome (IE does not work at all).
Any help or suggestions would be greatly recieved.
Hi, Sam - There are a few thing we can try first to rule out some common issues: Please make sure you are working locally as described here, and you may want to try importing the file into a new file before publishing. If you are still having issues, you might want to try to repairStoryline. If issues persist, please feel free to share your file or a sample here and we'll take a look.
I have tried all that you have suggested, saving and publishing to my C drive, different folders and running a reinstall of story line. But alas the problem still persists.
I have uploaded one slide for you to look at. The problem is most evident on the third layer. The next button should not appear untill my narrative has finished. As you will see in the program there is a couple of seconds gap between the end of the audio and the apperance of the next button. This works nicely in the program, but once it is published to web (HTML5 file) the timings get out of sink. This is the case in both fire fox and chrome, with cleared history, cookies and chashe.
I have tried to over come this but increasing the time gap and republishing but this seems to have no effect.
Hi, Sam - Thanks for providing your file, and myself and a colleague both tested your file, and did not see a difference in the timing in the Flash/HTML5 version. Please note that Firefox isn't supported for HTML5 (see System Requirements), and could you please test this output link from Tempshare in Chrome only to see how it functions for you?
I've got a video of 94 secs, but need the project to show a layer at 35secs. When I publish this to our LMS, it's hit and miss when the layer appears (either at 28sec, 35 secs or 48 secs). This problem seems to have become more pronounced now I've allowed the user to pause/play the video at their request. Do you have your video playing automatically, or via user interaction?
I'm watching this discussion thread in the hope we both find a resolution for this.
The only user interaction I have gived is to progress onto the next slide/layer once all my narrative and text information has completed (that is the idea but the progression button appears on some slides before that has finished)
Then, like you, I've no clue why we are both having this issue.
I reckon our e-Learning Heroes will come to the rescue on this one. Alternatively, I've let my Storyline provider's support function know I'm struggling with this. When I get a response from them, I will post it here for you :)
I hope the Heroes are able to solve this, as well all know once a candidate sees that progression button they will click it, regardless of the content finishing or not!
I have a feeling that this may turn out to be a problem with servers and differing timing devices on them. You would have thought, that time being a standard unit of measurment, would be consistant accross the board! Maybe some advice from Dr Who!
Yet I cant understand why it works in the program on my laptop but doesn't when it is run on a browser installed on my laptop using the same timing chip!
I had tested your file, and I do see the Next button appearing about 2 seconds after the Guidance part of the Audio is completed. Is this supposed to come in at a different time? Could you can see this here, and could you also test the published version here?
If you would like to take a screen recording of what you are seeing, if it is different, could you share that here? Or you could send it directly to support.
The delay on the first screen is not the issue I am trying to resolve. There is that gap in the timings in articulate.
The problem is on the following layers. If you go on to the next layer you will see that the next button appears before the audio finishes. It is even more evident on the third layer.
In articulate the text appears in time with my narrative and the next button does not appear untill the audio has finished. As an attempt to over come this I added 2-4seconds after my audio had finished before the next button was due to appear. As you can see from the published version this does not happen (asuming your computer is doing the same thing).
I'm still a relative novice on Storyline, but I do have a suggestion for you.
First of all, on Storyline 1, do you have a trigger for MEDIA COMPLETES? If so, why not simply set your NEXT buttons to appear after the media/audio completes its run?
13 Replies
Hi, Sam - There are a few thing we can try first to rule out some common issues: Please make sure you are working locally as described here, and you may want to try importing the file into a new file before publishing. If you are still having issues, you might want to try to repair Storyline. If issues persist, please feel free to share your file or a sample here and we'll take a look.
Hi Christie.
Thank you for your reply.
I have tried all that you have suggested, saving and publishing to my C drive, different folders and running a reinstall of story line. But alas the problem still persists.
I have uploaded one slide for you to look at. The problem is most evident on the third layer. The next button should not appear untill my narrative has finished. As you will see in the program there is a couple of seconds gap between the end of the audio and the apperance of the next button. This works nicely in the program, but once it is published to web (HTML5 file) the timings get out of sink. This is the case in both fire fox and chrome, with cleared history, cookies and chashe.
I have tried to over come this but increasing the time gap and republishing but this seems to have no effect.
Regards.
Sam.
Hi, Sam - Thanks for providing your file, and myself and a colleague both tested your file, and did not see a difference in the timing in the Flash/HTML5 version. Please note that Firefox isn't supported for HTML5 (see System Requirements), and could you please test this output link from Tempshare in Chrome only to see how it functions for you?
Hi Christie.
Tried your link in Chrome and still get the same issue, text and buttons appearing before they should!!
Regards.
Sam.
I feel your pain, Sam!
I've got a video of 94 secs, but need the project to show a layer at 35secs. When I publish this to our LMS, it's hit and miss when the layer appears (either at 28sec, 35 secs or 48 secs). This problem seems to have become more pronounced now I've allowed the user to pause/play the video at their request. Do you have your video playing automatically, or via user interaction?
I'm watching this discussion thread in the hope we both find a resolution for this.
Hi Jo.
The only user interaction I have gived is to progress onto the next slide/layer once all my narrative and text information has completed (that is the idea but the progression button appears on some slides before that has finished)
Sam.
Then, like you, I've no clue why we are both having this issue.
I reckon our e-Learning Heroes will come to the rescue on this one. Alternatively, I've let my Storyline provider's support function know I'm struggling with this. When I get a response from them, I will post it here for you :)
I hope the Heroes are able to solve this, as well all know once a candidate sees that progression button they will click it, regardless of the content finishing or not!
I have a feeling that this may turn out to be a problem with servers and differing timing devices on them. You would have thought, that time being a standard unit of measurment, would be consistant accross the board! Maybe some advice from Dr Who!
Yet I cant understand why it works in the program on my laptop but doesn't when it is run on a browser installed on my laptop using the same timing chip!
I look forward to seeing what they suggest!
Hi Sam!
I had tested your file, and I do see the Next button appearing about 2 seconds after the Guidance part of the Audio is completed. Is this supposed to come in at a different time? Could you can see this here, and could you also test the published version here?
If you would like to take a screen recording of what you are seeing, if it is different, could you share that here? Or you could send it directly to support.
Hi Emily.
The delay on the first screen is not the issue I am trying to resolve. There is that gap in the timings in articulate.
The problem is on the following layers. If you go on to the next layer you will see that the next button appears before the audio finishes. It is even more evident on the third layer.
In articulate the text appears in time with my narrative and the next button does not appear untill the audio has finished. As an attempt to over come this I added 2-4seconds after my audio had finished before the next button was due to appear. As you can see from the published version this does not happen (asuming your computer is doing the same thing).
Regards.
Sam
Hi Sam
I'm still a relative novice on Storyline, but I do have a suggestion for you.
First of all, on Storyline 1, do you have a trigger for MEDIA COMPLETES? If so, why not simply set your NEXT buttons to appear after the media/audio completes its run?
jo
Jo!
Your a Geneious! In one fowel swoop the issue is sorted!
I think articulate should employ you as a hero!
I had looked to see if there was that function previously but could not see it in the main list of functions.
However when I tried the change state command it had, as you said, when media completes as an option.
If you have something i can help you with then let me know!
Thanks again Jo!
Regards.
Sam.
Glad that Jo was able to assist you here Sam :) Thanks for sharing.
This discussion is closed. You can start a new discussion or contact Articulate Support.