The volume slider on my HTML5 build doesn't work properly. If you click anywhere on the slider it drops to 0 volume and there is no way to turn it back up.
The volume control works normal on other builds just the HTML5 build seems to have the issue.
I've tested it across several projects and the issue appears in all of them. Is anyone else experiencing similar?
You may find that the volume slider doesn't work on slides with video content when you view the HTML5 output in mobile Safari on an iPad/iPhone.
Apple has chosen to ignore volume settings for video content since iOS devices have built-in volume controls. (See Apple's developer documentation for details.) As a result, you'll need to use the volume controls on your iPad or iPhone to adjust the volume of video content in your course.
If you're only seeing this while testing the HTML5 content in Chrome, we'll want to know a bit more about how and where you're testing the course. You'll want to ensure you've loaded the output within the intended publish environment instead of viewing it locally as described here. If the behavior persists after confirming that you're testing it in the intended environment we'll want to take a look at the .story file.
The file I was using when I first found the issue was running locally with browser security disabled however after finding it I'm seeing the issue across all of my courses(live on LCMS). It is only on chrome/pc/html5 it seems to work fine in all other browsers. That build I'm guessing will only appear if the user is running chrome with flash disabled so it is not a major issue. I'm afraid I cannot share the content of the courses however I will try to make a test build/course and recreate the issue in a build I can send in.
I don't see a particular issue reported to our QA team, so if you're seeing it in all your courses we'd definitely like to take a look. If you're able to share privately our team can sign an NDA if needed and you can share here.
Sorry I'll submit it shortly. I can be more specific now now too. The issue is tied to the player scaling. If the player is set to scale with the window when you try to use the volume slider is uses the mouse position relative to where the slider would be at the published player size not the updated position based on the players scaled size.
Did you submit it here? You would have received an email from Support@articulate.com to confirm your submission and that would have the case number - I was able to find the case and it looks like my colleague Eloise replied on April 13th with the following:
We have reviewed your reported problem and we were able to duplicate your issue. I have submitted your case to our Quality Assurance team for their review. As a workaround you can try doing any of the following below:
1) Set the Player size to "Lock player at optimal size"
I cannot offer a time frame for when or if this issue will be resolved so please continue to take advantage of the workaround if you encounter this issue in the future.
I'll see if we can have the email resent to you - or you can check in your junk/spam folder to see if you can locate it.
I have the same issue with Volume slide controller only in Chrome (+Opera)!
The volume slider on my HTML5 build doesn't work properly. If you click anywhere on the slider it drops to 0 volume and there is no way to turn it back up.
Ashley already checks it but whatever you found out here, please inform me too!!!
Glad you reached out here too Chrysa - and you'll also want to message folks here directly using the "contact me" button on their profile, as this thread is a bit older and therefore they may no longer be subscribed.
I never got a response from before (i did submit it). We(my team not articulate) ruled that it was a non critical issue as anyone running chrome will likely have flash installed and would never see the HTML5 version of the content. So I never went further than submitting it in researching the issue.
Oh, I'm sorry I did narrow down the issue. it was a hitbox / scaling issue. if you click and hold on the slider and move the mouse around at some point you will find where storyline thinks the slider should be and will start adjusting the volume as if your mouse was over the slider even though it is 1/3 of the way across the screen. That lead me to believe that it has something to do with scaling as it's referencing the mouse position for where the scroll bar would be if the window was at it's default size.
You submitted it as a support case? I do see one associated with this issue, and it's the same that I also updated Chrysa on in her other thread, and the last reply from our team to you was as follows:
We have reviewed your reported problem and we were able to duplicate your issue. I have submitted your case to our Quality Assurance team for their review. As a workaround you can try doing any of the following below:
Set the Player size to "Lock player at optimal size"
I cannot offer a time frame for when or if this issue will be resolved so please continue to take advantage of the workaround if you encounter this issue in the future.
We'll keep you posted here and in the other thread, and also as a part of your support case if there is additional information to share.
The company I work for is experiencing this same issue on Chrome running on PCs. We've tested several courses and they all exhibit the same behavior. Is there any timeline on a fix for it?
The HTML5 code is not updating hitboxes on the volume slider after resize as the volume slider is not active when the player resizes.
As far as a fix I haven't been pushing it as once we analyzed it we found it is a negligible issue if you are using most lms'. In my case the only way a user will see the faulty HTML5 version of the content is if they are running on PC without flash. The issue doesn't appear in mobile which was our concern.
As for a work around as posted above is to "Set the Player size to 'Lock player at optimal size'". This will prevent the player from scaling and causing the issue. I'm not fond of that Fix as I want the scaling for UX.
I can report that the locking volume slider problem also occurs for me on a Mac, running Chrome. It occurs in the published version as well as the local version. I do not have the Player set to lock at the optimal size, since being able to scale the output is a more desirable way to view it. Any updates on this issue would be much appreciated — thanks!
This is still with our QA team for investigation, but you'll want to use the lock player at optimal size or disable the volume control within the player to allow the HTML5 output to work. We'll update you here if there is any other information to share.
The volume slider on my HTML5 build doesn't work properly. If you click anywhere on the slider it drops to 0 volume and there is no way to turn it back up.
The volume control works normal on other builds just the HTML5 build seems to have the issue.
I've tested it across several projects and the issue appears in all of them. Is anyone else experiencing similar?
same here guys - volume drops down w/o the option to turn it back on.
Hi, thanks for your prompt reply.
As the final project will be a software demo, and narration plays a major
part in this package, deactivate the volume control is almost impossible
as this will significantly damage its functionality.
Same goes with locking (or otherwise restrict) the slides navigation.
Letting the demo users navigate between the slides is an entry level
feature and cannot be compromised.
That all said, with all the sympathy and good will, $1300 should buy me a
fully functioning tool. Volume, navigation, that's all basic level
features.
If you disable the volume control from the Storyline player, then the user can utilize their system audio to determine how it plays and behaves in their particular environment. If there is a significant functionality piece I'm missing, please let me know and I can also ensure we share that fact with our QA team as they continue to investigate.
54 Replies
should clarify it only seems to occur in Chrome.
Hi Ryan,
You may find that the volume slider doesn't work on slides with video content when you view the HTML5 output in mobile Safari on an iPad/iPhone.
Apple has chosen to ignore volume settings for video content since iOS devices have built-in volume controls. (See Apple's developer documentation for details.) As a result, you'll need to use the volume controls on your iPad or iPhone to adjust the volume of video content in your course.
If you're only seeing this while testing the HTML5 content in Chrome, we'll want to know a bit more about how and where you're testing the course. You'll want to ensure you've loaded the output within the intended publish environment instead of viewing it locally as described here. If the behavior persists after confirming that you're testing it in the intended environment we'll want to take a look at the .story file.
The file I was using when I first found the issue was running locally with browser security disabled however after finding it I'm seeing the issue across all of my courses(live on LCMS). It is only on chrome/pc/html5 it seems to work fine in all other browsers. That build I'm guessing will only appear if the user is running chrome with flash disabled so it is not a major issue. I'm afraid I cannot share the content of the courses however I will try to make a test build/course and recreate the issue in a build I can send in.
Hi Ryan,
I don't see a particular issue reported to our QA team, so if you're seeing it in all your courses we'd definitely like to take a look. If you're able to share privately our team can sign an NDA if needed and you can share here.
Sorry I'll submit it shortly. I can be more specific now now too. The issue is tied to the player scaling. If the player is set to scale with the window when you try to use the volume slider is uses the mouse position relative to where the slider would be at the published player size not the updated position based on the players scaled size.
Thanks Ryan and if you share it as a part of a support case can you let me know the case number so that i can follow along?
I submitted it a few days ago I have yet to hear back or get a case number.
Hi Ryan,
Did you submit it here? You would have received an email from Support@articulate.com to confirm your submission and that would have the case number - I was able to find the case and it looks like my colleague Eloise replied on April 13th with the following:
We have reviewed your reported problem and we were able to duplicate your issue. I have submitted your case to our Quality Assurance team for their review. As a workaround you can try doing any of the following below:
1) Set the Player size to "Lock player at optimal size"
I cannot offer a time frame for when or if this issue will be resolved so please continue to take advantage of the workaround if you encounter this issue in the future.
I'll see if we can have the email resent to you - or you can check in your junk/spam folder to see if you can locate it.
I have the same issue with Volume slide controller only in Chrome (+Opera)!
The volume slider on my HTML5 build doesn't work properly. If you click anywhere on the slider it drops to 0 volume and there is no way to turn it back up.
Ashley already checks it but whatever you found out here, please inform me too!!!
Glad you reached out here too Chrysa - and you'll also want to message folks here directly using the "contact me" button on their profile, as this thread is a bit older and therefore they may no longer be subscribed.
I never got a response from before (i did submit it). We(my team not articulate) ruled that it was a non critical issue as anyone running chrome will likely have flash installed and would never see the HTML5 version of the content. So I never went further than submitting it in researching the issue.
Oh, I'm sorry I did narrow down the issue. it was a hitbox / scaling issue. if you click and hold on the slider and move the mouse around at some point you will find where storyline thinks the slider should be and will start adjusting the volume as if your mouse was over the slider even though it is 1/3 of the way across the screen. That lead me to believe that it has something to do with scaling as it's referencing the mouse position for where the scroll bar would be if the window was at it's default size.
Hi Ryan,
You submitted it as a support case? I do see one associated with this issue, and it's the same that I also updated Chrysa on in her other thread, and the last reply from our team to you was as follows:
We have reviewed your reported problem and we were able to duplicate your issue. I have submitted your case to our Quality Assurance team for their review. As a workaround you can try doing any of the following below:
Set the Player size to "Lock player at optimal size"
I cannot offer a time frame for when or if this issue will be resolved so please continue to take advantage of the workaround if you encounter this issue in the future.
We'll keep you posted here and in the other thread, and also as a part of your support case if there is additional information to share.
Hi,
The company I work for is experiencing this same issue on Chrome running on PCs. We've tested several courses and they all exhibit the same behavior. Is there any timeline on a fix for it?
The HTML5 code is not updating hitboxes on the volume slider after resize as the volume slider is not active when the player resizes.
As far as a fix I haven't been pushing it as once we analyzed it we found it is a negligible issue if you are using most lms'. In my case the only way a user will see the faulty HTML5 version of the content is if they are running on PC without flash. The issue doesn't appear in mobile which was our concern.
As for a work around as posted above is to "Set the Player size to 'Lock player at optimal size'". This will prevent the player from scaling and causing the issue. I'm not fond of that Fix as I want the scaling for UX.
Hi Tim,
I don't have an update from our team at this point in time, but this thread is tagged to be updated once there is additional information to share.
I am having a similar issue. In chrome on a mac, the audio mutes instead of adjusting, and appears to lock there.
Hi Sara,
This thread is a bit older, and since you mentioned Mac I wanted to find out a bit more about where and how you're viewing the course. Are you viewing it in Safari on your Mac or another browser? Are you testing the published course in the intended publish environment vs. testing it locally?
I can report that the locking volume slider problem also occurs for me on a Mac, running Chrome. It occurs in the published version as well as the local version. I do not have the Player set to lock at the optimal size, since being able to scale the output is a more desirable way to view it. Any updates on this issue would be much appreciated — thanks!
Hi Adele,
This is still with our QA team for investigation, but you'll want to use the lock player at optimal size or disable the volume control within the player to allow the HTML5 output to work. We'll update you here if there is any other information to share.
same here guys - volume drops down w/o the option to turn it back on.
Hi Orgad and welcome to E-Learning Heroes!
I do not have an update to share regarding this issue as it is still in the hands of our QA Team.
We do have some workarounds listed:
1. Disable the Volume Control
2. Set Player size to "Lock Player at optimal size"
Hi, thanks for your prompt reply.
As the final project will be a software demo, and narration plays a major
part in this package, deactivate the volume control is almost impossible
as this will significantly damage its functionality.
Same goes with locking (or otherwise restrict) the slides navigation.
Letting the demo users navigate between the slides is an entry level
feature and cannot be compromised.
That all said, with all the sympathy and good will, $1300 should buy me a
fully functioning tool. Volume, navigation, that's all basic level
features.
HI Orgad,
If you disable the volume control from the Storyline player, then the user can utilize their system audio to determine how it plays and behaves in their particular environment. If there is a significant functionality piece I'm missing, please let me know and I can also ensure we share that fact with our QA team as they continue to investigate.
Hi,
How is the fix for this issue coming along? It has been reported for well over a year and nothing has been done about it.
Or are you just too busy pushing Articulate360 to care about us perpetual licence holders?
Thanks
This discussion is closed. You can start a new discussion or contact Articulate Support.