

Eventually, I systematically deleted slides until it did publish and so I knew it was one particular slide.īut then, I went to work on another project and all the audio wouldn't load! Following advice, I have uninstalled and reinstalled Flash and Storyline multiple times and it still won't work. This is a dedicated computer I use for Storyline which I don't network. The project still wouldn't publish and after trying lots of things including importing into a new presentation, etc. I wrote to Articulate and they didn't have a problem publishing and so was advised to uninstall and then reinstall Storyline, which I did. The problem started with my project not publishing. I too am having a problem with my audio not loading. I'm just relating what we have experienced. I fear that you are going to have to do exactly what you do not want to do.īut I'm not an expert. I strongly suspect that your audio files are gone. We also, make sure that storyline is shut down when we quit for the day. We have learned, through hard experience, that with Storyline you MUST, MUST, MUST save often. I don't think that is causing the problem, as we had the same problem with keeping files on our local drives before we started saving them in Dropbox. I know that seems to be frowned upon, but it has saved our skins several times. Luckily for us, we keep the files on DropBox and we can easily roll back to an older version. Other times it would only be some of the audio files and some of the pictures. We had this happen with all recordings in a story along with many of the pictures in the story. But the info was gone, and the evidence for that was that the file size was suddenly drastically smaller. The slide still said that it existed, and that loading thing you see is the program trying to load something that isn't there anymore. It appeared to us that the audio files were gone. If the file was saved, the corrupted state would get saved.

Apparently the file had become corrupted while sitting there. Here is what we found: After sitting open for an extended period of time - like overnight - a storyline file would encounter problems when returning to the file and starting to do something. We had this exact same problem - i think - and it happened multiple times on three different machines.
