Explore the community Forums Lectora Lectora Questions & Answers Microsoft Surface Pro – Lectora course not working

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #373622 Score: 0
    Profile photo of Sophia K
    Sophia K
    Member
    beginner
    intermediate
    picture perfect
    friend finder
    curious george
    profile
    wise owl
    advanced
    contributor
    1 pt
    @skings5565

    Lectora version – 17
    LMS – Moodle
    SCORM 1.2

    We have tested the course (and other courses) on every browser and most devices (android and apple) and it works as expected.

    However, we are having a problem going through our Lectora courses using Microsoft Surface Pro using Microsoft Edge. The course works well on Google Chrome browser.

    We use audio in our courses, here is what happens for a standard page with interaction:
    1) The first audio plays well and text 1 is shown.
    2) The user clicks on an icon which reveals a popup and plays audio, once the audio has finished the user can click on the next icon
    3) The user clicks on icon 2 which reveals the popup but no audio plays, which means the user cannot complete the page or move onto the next icon as the course relies on the action in the audio

    This happens with every page with 3 or more audio, you can click on any icon and always the 2nd icon clicked doesn’t play sound.

    We have looked into figuring out the navigator.platform. Microsoft Surface uses Win32 which is the same as most standard Microsoft desktop/laptop computers. We don’t know how to detect if the user is using a Microsoft Surface Pro as it’s not a tablet but works differently to a computer.

    Has anyone come across this issue or know how to solve it?

    Thanks

    Sophia

    • This topic was modified 3 years ago by Profile photo of Sophia K Sophia K.
    #373685 Score: 0
    Profile photo of Math Notermans
    Math Notermans
    Member
    contributor
    intermediate
    advanced
    friend finder
    junior moderator
    advocate
    LUC16 Attendee
    LUC16
    wise owl
    curious george
    131 pts
    @mnotermans5114

    Although i cannot test it with Surface, you might try use another approach on the audio’s. Dont use the default audio player thats in Lectora, but add it with Javascript and a custom button/player.

    You could for example use Buzz

    Fade audio in Lectora

    http://buzz.jaysalvat.com/

    or Mediaelement, basically that is the same player as Lectora uses, but newer version and probably completer.

    http://www.mediaelementjs.com/

    Kind regards,
    Math

    #373828 Score: 0
    Profile photo of Math Notermans
    Math Notermans
    Member
    contributor
    intermediate
    advanced
    friend finder
    junior moderator
    advocate
    LUC16 Attendee
    LUC16
    wise owl
    curious george
    131 pts
    @mnotermans5114

    Also its good to know what Surface Pro you are testing on. 3 or 4 ?
    Cause today this caught my attention.

    Audio issues with the Microsoft Surface Pro 4


    Apparently the Surface Pro 4 has more issues with audio in different sectors too.
    Do google for ‘Audio stops not playing Surface Pro’ and you will get quite a lot of hits.
    A lot for Pro 4 , but i also found several on 3. And even 2. Can’t tell if this is a Surface Pro issue, or if my earlier workaround helps fix it, but really looks like Surface Pro is not stabile.

    #373835 Score: 0
    Profile photo of Sophia K
    Sophia K
    Member
    beginner
    intermediate
    picture perfect
    friend finder
    curious george
    profile
    wise owl
    advanced
    contributor
    1 pt
    @skings5565

    Thanks Math Notermans!

    I am testing on Microsoft Surface Pro 4 and also tested on 3. I will look into adding audio using javascript.

    #373844 Score: 0
    Profile photo of Math Notermans
    Math Notermans
    Member
    contributor
    intermediate
    advanced
    friend finder
    junior moderator
    advocate
    LUC16 Attendee
    LUC16
    wise owl
    curious george
    131 pts
    @mnotermans5114

    One extra tip. Add sufficient debug-code in your Javascripts so you can properly follow whats going on.

    For example:

    • at pageLoad -> console.log(“the page is Loaded”);
    • when clicking the audio buttons -> console.log(“now clicked audio 1”);
    • when the audio plays -> console.log(“audio 1 is playing”);
    • on specific events on the audio -> console.log(“now reached event Blabla on audio 1”);
    • on audioended -> console.log(“audio 1 has ended”);

    This way in your browser you can follow the complete process. If anything goes wrong you know exactly ( hopefully ) what and where…

Viewing 5 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic.