As reported by forum user BRUCE, the ESV audiobook ("David Cochran Heath") stops playing at the beginning of new chapters and the computerized macOS (or windows) takes over. I have no idea if this is related, but am wondering if it is related to the new smaller "Bible Indexing" command.
EDIT: I haven't had a chance to confirm, but it may be specific to certain books. My test case was between 1 John 1 & 2. See OP for more.
OSX & iOS | Logs | Install
Interesting, I can confirm the same thing with the ESV but the LEB audio works perfectly so it seems it wouldn't have to do with the indexing in that case I think?
Teacher, Ministry Leader, Student, Author, Husband
How to upload logs
Visit My Site: Reformed Truths
David Taylor Jr:it seems it wouldn't have to do with the indexing in that case I think?
It was just a stab in the dark. It may still be related... the ESV streams from the servers, while the LEB plays locally.
JT,
Some input ...
JK
MacBookPro Retina 15" Mid 2014 2.5GHz RAM:16GB SSD:512GB macOS Mojave 10.14.1 | iPhone X iOS 12.1
Hi Alabama and Bruce,
We have a case open for this. I've added these threads to the case.
Diagnostic Logging
Philana R. Crouch: We have a case open for this. I've added these threads to the case.
While the faithful rejoice at Faithlife's diligence in opening a case for the ESV Read Aloud bug, It is beyond frustrating that the bug persists for a quarter of a year without resolution. I'm not saying that the issue is languishing in a dusty corner under Bob's office credenza, but we have zero insight into the progress (or lack thereof) to date.
Faithlife, please be more proactive in letting your users (some of whom rely on the ESV Read Aloud feature due to limited visual acuity) know what's going on. If anything. Having run software development teams for years, I can state with a degree of certainty that I'd have been sacked (and rightly so) for allowing a feature bug to persist this long. Unacceptable, my friends. Please do better.
"I read dead people..."
Brother Mark:Having run software development teams for years, I can state with a degree of certainty that I'd have been sacked (and rightly so) for allowing a feature bug to persist this long.
I can appreciate your frustration... I share it too! It should be noted, however, that we are talking about a free feature and resource. I would be more concerned if I had paid for it!
Its odd but I too had this issue.. But then on Jan 01 I started a new 1 year Bible reading plan using the ESV and the read aloud has worked perfect.. I even thought maybe they fixed it. If they did not, I am not sure why all the sudden its working for me.
Rodney Phillips: .... I even thought maybe they fixed it. If they did not, I am not sure why all the sudden its working for me.
.... I even thought maybe they fixed it. If they did not, I am not sure why all the sudden its working for me.
Rodney, Congratulations on being one of the fortunate ones.... but to ensure that you are "fixed", why not try a few chapters in the NT vs. OT (which is where I'm currently having difficulty). It is common with software bugs where everything works fine on some hardware/software combinations and configurations.... yet, fails miserably on others. I am one of the unfortunate ones (apparently) and my ESV Read Aloud fails miserably by switching back to the system narrator voice between chapters... and, occasionally, just for fun, it skips backwards and repeats the last verse. Because, you know, why not confuse us even more? (/sarcasm)
I'm really hoping that Faithlife will give us a status here. BTW, chatting with support online yields the expected response of: Yes, yes, its a known issue. How quaint. And trite. And completely unhelpful. (Okay, this time I'm really turning off the sarcasm. For now.)
Our testing indicated that the problem (with reverting to the system narrator) starts in 1 Cor 11.
Someone is looking into resolving the problem but it turned out to be more complicated than we expected.
can anyone update on the mobile apps ability to read aloud any book in library? I know that used to be available, then was "broken" after an update some time back. With the recent Domino's app lawsuit (mobile app not useable by visually impaired people), wondering if this is something FL needs to put on front burner.
I like Apples. Especially Honeycrisp.
For clarification: this is an iOS accessibility feature, not a Logos one. I just tried it and it appears to work fine in paged view.
JT (alabama24): For clarification: this is an iOS accessibility feature, not a Logos one. I just tried it and it appears to work fine in paged view.
Thanks JT, I'll take a look.
This should be fixed with an update to the ESVAUDIO resource that was shipped recently.
Excellent.. Thank you for letting us know..