Bug: Read aloud - multiple stream(s) of audio & out of control

LimJK
LimJK Member Posts: 1,068 ✭✭
edited November 20 in English Forum

Hi Logos,

How to re-create the the subject issue:

  • Open NICNT 1 Thessalonians 1 (I have set Columns format to NONE)
  • Start Read aloud ... reading as expected
  • While it is reading scroll down one or more times (competing read aloud audio(s) start)
  • Stop Read aloud ... does not stop Read aloud
  • The only way to stop Read aloud is to QUIT Logos

I am on Logos 6.0a SR-3 for Mac. Attached is the log.

6327.LogosLogs.LimJK.20141214-231746.zip

JK

MacBookPro Retina 15" Late 2013 2.6GHz RAM:16GB SSD:500GB macOS Sierra 10.12.3 | iPhone 7 Plus iOS 10.2.1

Comments

  • Dave Hooton
    Dave Hooton MVP Posts: 35,767

    I don't have that resource. Does it occur for ESV or any other resource?

    Dave
    ===

    Windows 11 & Android 13

  • LimJK
    LimJK Member Posts: 1,068 ✭✭

    I don't have that resource. Does it occur for ESV or any other resource?

    Dave,

    For ESV, if you switch to System Narrator, you get similar problem. However, for ESV if I do CMD+R it stops Read aloud after the verse is read.

    Interesting, now that you asked, I tried again ... if I do CMD+R to stop Read aloud of multiple audio streams of NICNT 1 Thess and if I am patient enough for the whatever that is left in the "buffer" to be completely read out ... it actually stop after that. But, still a bug, I think [:)]

    I suppose Commentaries has longer para to read, and ESV verses are shorter and thus stops when the verse is read.

    JK

    MacBookPro Retina 15" Late 2013 2.6GHz RAM:16GB SSD:500GB macOS Sierra 10.12.3 | iPhone 7 Plus iOS 10.2.1

  • Bob Soule
    Bob Soule Member Posts: 445

    LimJK said:

    • While it is reading scroll down one or more times (competing read aloud audio(s) start)

    I don't have the NICNT but the other resources which I do have that have read functions, scroll as the text is read. And they will have competing read aloud(s) if I manually scroll the resource.  On further testing this only happens with system narrator, as mentioned above.

    Does the NICNT scroll as it is read? If so, is this sufficient, if not I guess you will have to stop read aloud, scroll and start read aloud until such time it works like you want it to.

    I would also consider this a bug.

  • LimJK
    LimJK Member Posts: 1,068 ✭✭

    Bob Soule said:

    Does the NICNT scroll as it is read? If so, is this sufficient, if not I guess you will have to stop read aloud, scroll and start read aloud until such time it works like you want it to.

    I would also consider this a bug.

    Bob,

    Logos System Narrator Read aloud scrolls the text correctly most of the time. I discovered this issue accidentally when I found Read aloud continue to read the text below the Panel (not visible to me), so, I did what I thought is normal ... manual scroll to see the text :-)

    I hope someone from Logos see this, and hopefully it will be fixed some point down the road.

    JK

    MacBookPro Retina 15" Late 2013 2.6GHz RAM:16GB SSD:500GB macOS Sierra 10.12.3 | iPhone 7 Plus iOS 10.2.1

  • LimJK
    LimJK Member Posts: 1,068 ✭✭

    Bump ... hoping someone from Logos see this. The problem still exists in Logos 6a SR-5 for Mac.

    JK

    MacBookPro Retina 15" Late 2013 2.6GHz RAM:16GB SSD:500GB macOS Sierra 10.12.3 | iPhone 7 Plus iOS 10.2.1

  • Jonathan Haas
    Jonathan Haas Member, Logos Employee Posts: 31

    Hello,

    I will create a case for this and we will work on getting this fixed in an upcoming release. Thanks for pointing this out!

  • LimJK
    LimJK Member Posts: 1,068 ✭✭

    Hello,

    I will create a case for this and we will work on getting this fixed in an upcoming release. Thanks for pointing this out!

    Jonathan,

    Thank you[:)]

    JK

    MacBookPro Retina 15" Late 2013 2.6GHz RAM:16GB SSD:500GB macOS Sierra 10.12.3 | iPhone 7 Plus iOS 10.2.1

  • Angela Murashov
    Angela Murashov Member Posts: 1,532

    Hello,

    I will create a case for this and we will work on getting this fixed in an upcoming release. Thanks for pointing this out!

    This has been fixed in 5.2b SR9 and 6.0b SR-1.