Please make sure you are using the latest PowerPac version (v14.054.2) and see if it works for you.I ran a simple test with a single audio file playing on the first page of book and it works in Chrome, at least when run from the hard drive using the PowerPac server. We have other courses working in Chrome using this version of the PowerPac. The latest PowerPac version contains some fixes designed satisfy the Google autoplay issues. These are not guaranteed to work for the long haul though, but they seem to be working for now.
If it still doesn't work for you in Chrome:This indicates that even if the sound is able to play, it will not send events until the user has clicked on at least one item in the opening window (e.g.: it can be a button or even just the main window itself). This will satisfy the Chrome policy for autoplay and allow all features of the sound controller to work.
NOTE: You may need to start making an opening splash screen for your courses that satisfy the "user click" policy. We are in the process of encouraging our clients to consider the opening splash screen method as it will guarantee that autoplay works. Once user interaction is satisfied on page one, media autoplay should work no matter how many pages are in your course. And this is true whether the media is audo or video.
Please keep us informed regarding issues which affect your particular scenario as we can review if further adjustments are required.
UPDATE:Just tried by uploading my test content to another server and the autoplay failed. What Chrome is doing is tracking the
MEI (Media Engagement Index) which is determined by how times a user clicks the window to interact with the web content. Once satisfied, the autoplay will always work for that user, but not necessarily for another user from a different computer. They must satisfy the
MEI as well. However, the splash screen method will just always work because, you just need to make the screen with a simple button to enter the course. Clicking the button always satisfies the autoplay mechanism.
While this a Chrome-only issue, don't be surprised if ALL the browser manufacturers start adopting this. The idea behind this is to prevent advertisers from unduly messing wth a user's experience when visiting web locations with ads, etc. Unfortunately, it does not take into consideration that courseware developers are trying to provide education, not advertising. In our case, the
MEI is actually messing with a user's positive experience by not being very intelligent. Uggh!!