Read aloud doesn't read aloud; it just jumps around with indictators but no audio

With the new toolbar (or cmd-R) on the beta in Mac (running MacOS public beta), read aloud does not read aloud (except with Bible that has a recorded voice). When it is supposed to use the system reader, it just begins to jump through the text quickly flipping pages showing indicators but no audio playing. 

Jacob Hantla
Pastor/Elder, Grace Bible Church
gbcaz.org

Comments

  • Adam Borries (Logos)
    Adam Borries (Logos) Community Manager, Logos Employee Posts: 947

    We've seen scattered reports of this, and we have had trouble determining the conditions needed to reproduce the issue. We are actively looking into it, though. 

  • Michael Cooley
    Michael Cooley Unconfirmed, Member Posts: 2

    I tried to use read-aloud this morning and have the same issue here. It just begins to jump through the text, quickly flipping pages, showing indicators but no audio playing. All versions are running on a MacBook Pro.

  • PL
    PL Member Posts: 2,158 ✭✭✭

    Usually this happens when the book's language doesn't match the default reading voice's language (e.g. English voice trying to read a Chinese-character book).

  • Michael Cooley
    Michael Cooley Unconfirmed, Member Posts: 2

    All English. Same issue for any Bible version

  • stephen corbett
    stephen corbett Member Posts: 1 ✭✭

    I only had the issue for any version of NASB but switching to ESV, the read aloud then worked fine.

  • Timothy J Lacock
    Timothy J Lacock Member Posts: 1

    Tried the reader this morning and it is still jumping instead of reading. My logos runs on Mac. I hope they are still looking into this issue

  • Adam Borries (Logos)
    Adam Borries (Logos) Community Manager, Logos Employee Posts: 947

    Quick update: This continues to be an intermittent issue, with scatter reports. Our previous investigation didn't turn up the cause, or the exact conditions needed to reproduce it, so we added some logging to help us determine the issue.

    It's on our backlog to revisit this issue soon; posting your logs here would help. Thanks.