SL 360 Previews correct audio on slide 2, plays another slides audio when published.

Submitted case 01039506 , no response. 

If you published, viewed, then changed the audio, it is possible that you are viewing a cached copy. Use a different browser, or start an incognito session.

Hi Sam,

I see that Robert is working on your case and responded with the following troubleshooting steps to start:

I understand that the audio on Slide 2 plays another slide's audio in the published version. 

May I know if the issue persists, if you remove the audio? 

How about if you do the following: 
1) Insert a new slide after Slide 2 
2) Copy all the contents from Slide 2 except for the audio 
3) Reinsert the audio into the new slide 

Please let me know how these tests goes. 

I'd also agree with Walt's suggestion that if you're viewing the published output and had updated the previous course it could be that you're seeing a cached copy of it. Take a look at testing it in a new browser or using the private/incognito mode so that it's not accessing that cached copy. 

Let us know how those tests go, and I'll also give Robert a heads up on the work you're doing in this forum discussion! 

This is not a cache copy  problem. We've tried this on multiple machines at multiple locations with multiple browsers. 

 Hi Ashley, I uploaded the story file so test could be run.  It is very repeatable. 

 I found a way to resolve the problem by creating a new project and importing all the slides. it works fine now. 

Nasty bug though. 

Thanks Sam - if it's resolved by importing it's a good indication that there was something that happened in the file, not the whole of Storyline. I see that Robert was able to test your initial file as well and didn't replicate the issue with the odd audio playing on other slides. With that in mind, we'd need a bit more information from you about how you're able to replicate this bug - was there anything specific that happened just before the behavior? I know I've seen you around the forums before, so my guess is you've already confirmed you're working off local files vs. a network/shared drive? Also are you on the latest update of your version of Storyline? 

I can demo this via WebEx if  anyone is interested.

.story projects don't corrupt themselves... some sequence of events in SL 360 led to the corruption.  We recently cut/paste several scenes to reorganize content.  It may have been too much for SL 360.

To whom it may concern: While this may be accurate technically, "some sequence of events" happens frequently to all versions of SL projects. Remember that a .story file is not a single file. Just like a .docx document, it is a complex web of many files. With so many moving parts, it is easy for "some sequence of events" to happen.

Loading, modifying, and saving a project  as well as network security settings and Windows OS's natural proclivity all play a part in project corruption. Enough of those are functions of SL to justify your thought that it  is too easy to overwhelm SL. But I think it is also justifiable  to say two additional things: "SL files will become corrupt", and "Frequent, incremental backups are best practice."

Hi Sam,

Our Support Engineers are happy to offer a gotoassist session if you can consistently replicate it and want to demonstrate those steps to us! Just respond to your latest case with Robert and he'll get you going from there. 

Sounds good.

I will get in touch soon.

Sam