Error when publishing or editing audio in Storyline

Hi Suzan,

Welcome to Heroes, thanks for reaching out here! Forgive me if I'm misunderstanding at all, is this something that is happening in any file you attempt to publish or edit audio in? Is it happening with any audio file or just one in particular? Is there a particular error that you're seeing? I see in your screenshot, that it says "loading", is that something that doesn't go away? 

You mentioned uninstalling and reinstalling, if this is an issue you're seeing happen across any storyline file you're working on in Storyline 2 and with any audio file, I would recommend first checking out our minimum system requirements here to verify that you meet them. If you do, I would recommend running this repair to fix erratic behavior in Storyline 2.

Keep me posted on how that goes! :)

Hi,

I did everything you said in this place but did not change the results, the computer I'm using i5 processor, 8GB  RAM, 2GB video card, writes audio files Loading and stays off, and when I did Publisher gives an error, I installed in today's new update on but the problem did not improve, please help 

Hi Suzan

do you want to upload your .story file - might be easier for someone to help you troubleshoot the issue.

Hi Wendy

Story File is working properly on other computers, only I have this problem. As an example: after creating test.story and adding Audio files everything is normal, but after saving and closing the test.story file when I reopen it it says audio Loading but can never load audio

:(

Hi Suzan,

If it's only not working on your set up, can you confirm that you and your colleagues are all using the same update of Storyline? We'd advise the latest update, Update 11 available here.

Next, are you working on the files by saving to your local drive? Lastly if again its just your set up you may want to look at conducting the repair of Storyline. 

Hi Ashley,

I did update, We all use the same version and I did Unexpected or Erratic Behavior in Articulate Storyline 2, but it did not change the results

Have you tried publishing the file from your PC - does it publish correctly?

publisher gives this error.

Try changing the file name in the publish window

I changed the name but gives an error.

Did you confirm Ashley's comment above that you are working locally with the storyline source file on you PC not on a network drive? 

How are you adding the audio - are the audio files saved locally as well?

Yes I confirm that I have done it but the result has not change, I still get the same error message. We use the same version on three pc's, audio files are wav, mp3 and wma. In my pc, the story files do not work but on other 2 pc's it works. This error occurs since one week, before that time it works on my pc properly

All windows updates been run? Perhaps you need to log a support ticket with Articulate Engineers to work with you

Hi Suzan,

Are you able to determine anything different about your set up vs. that of your colleagues? Are you all on the same version of Windows, Storyline, etc.? Are you sharing the .story and audio files back and forth? Did you look at a brand new .story file to see how that behaves? 

As Wendy mentioned it may be something best handled by our Support Engineers for some more one on one feedback. 

I'm having the same issue. I can't publish the file and I have done all of the fixes suggested. Was there any resolution?

Hi Tricia

nothing has been mentioned in Suzan's case - if you have done all the suggested checks you might need to log a support ticket with Articulate --> log

Hi Tricia

Unfortunately there is no solution now support teams are investigating, I will write here the solution

Thanks Suzan for following up.  I see your case (906507), so we'll follow along for updates as well.

Hi Tricia,

I took a look at Suzan's case (Case #00906507 for my reference) and see that our team was pulling some system and Windows event logs to dig a bit deeper, and if you'd like us to do the same with your set up we'd be happy to. You can reach out to our Support team here and feel free to mention this discussion in terms of the connection to  similar problem.