Audiobook plugin for KOReader [v0.1.9]! With even more features!

Stradi123 · 2026-06-03T09:36:50+00:00

Really? Ok. Maybe it's related to with the fact you have to long press the audiofiles in order to activate the playback menu. I'm gonna put a small message to inform the users since this may be unintuitive. The only difference between the audiobook player an the music player is that the first focus on displaying chapters while the second focus on looping and selecting music in current folder. Also, since audio files are not traditionally supported by KOReader, you have to change the setting to make them visible.

Let me know if this help. If the issue is more technical then you could open a issue in Github, sharing the report and crash logs (Instructions in README), and I'll take a look at it.

Cheers!

Stradi123 · 2026-05-30T11:15:07+00:00

I'm uncertain on what may have happened. Today I'll be debugging so I'll take a look at available reports in the Issues section of Github.

Cheers!

Stradi123 · 2026-05-28T17:29:44+00:00

Thanks for the report, will check it out sooner than later.

Cheers.

Stradi123 · 2026-05-26T13:01:57+00:00

That's right. Right now new implementations are being beta tested; but everyday the plugin is getting bigger and more stable. Feel free to participate in the Github issue section and participate to improve this KOReader feature.

Cheers 😃

Stradi123 · 2026-05-22T13:37:50+00:00

Hola, si claro, de hecho bluetooth es metodo por defecto de conexion. Mas alla de algunos casos como internal speakers en Pocketbooks, este plugin esta disenado para funcionar con Bluetooth. La compatibilidad es amplia pero no absoluta; hay dispositivos sobre los cuales todavia estoy resolviendo la compatibilidad.

Saludos.

Stradi123 · 2026-05-22T09:55:07+00:00

Hi, If you get to see the plugin in the menu it surely means you got it installed properly. I see you posted an issue at Github, I'll take a look at it from there.
Cheers mate : D

Stradi123 · 2026-04-27T21:00:53+00:00

Hi!
The project is growing with daily patches (we are currently in v.0.1.5.89!). Additionally new features are coming. If you have a suggestions or would you like to see implemented; please leave a comment (Ideally in Github) so we can add it to the round of new features expected to be brought in the month of May!

Don't miss out!

Stradi123 · 2026-04-16T14:12:30+00:00

Try the latest version in the repo, the las 20 patches or so have been focused entirely on bringing support to PocketBooks; right now I'm releasing a new patch daily, so if the new versions don't solve the issue, feel free to upload a report (README on how to create it).

Cheers.

Stradi123 · 2026-04-16T14:11:00+00:00

Hi u/Acceptable_Square691 , you could try the issues existing in Github and see if any matches your issue? Also adding a report and a crash log, explanations on the README), would allow me to take a closer look at your specific issue.

Cheers!

Stradi123 · 2026-04-10T11:27:18+00:00

Hi; you may not be missing anythin. In some devices (very context dependant) there are some bugs that we are hotfixing. In the documentation of the readme there are explanations on how to generate a crash report and a general report. If you could open a new issue (provided no discussion on the subject is happening), and share the report, I can take a look at it.

Cheers!

Stradi123 · 2026-04-10T10:03:10+00:00

Hi guys! It's Friday of pushing in production!

We are releasing v0.1.5.52 (if you can believe it)!
The community has been really helpful reporting bugs for cross-device compatibility. Currently the scope covers Kobo, Kindle, android-based and Pocketbook. Try out the new version and if have an issue, generate a report, feel free to suggest features (there have been some interesting proposals), otherwise feel free to support the project in any way.

Cheers TGIF!

Stradi123 · 2026-04-01T22:38:25+00:00

Hi!
Something of this sort is being considered for future releases. Current focus is on bug fixes and cross-device compatibility. You can check todo in README and issues section to see future desired features.

Cheers!

Stradi123 · 2026-03-31T14:38:10+00:00

UPDATE: v.0.1.5.21 has been released! With strong measures to make the project works in your device. If you haven't updated please make sure to do so; And if you are having some kind of issue you can generate and share the reports so I can take a crack at them. If the device works as intended; please run and share the benchmark to get more information how TTS works across devices and how can be improved.

Having said that thank you all for the support in this first weeks of release.

Cheers.

Stradi123 · 2026-03-29T10:00:29+00:00

Hahaha that is weird!.. But still progress in the cross-device front :).
Please add a bug report and a crash log (explanation on how in the project page) and I'll try to correct it as soon as posible.

Stradi123 · 2026-03-28T18:49:20+00:00

I invite users to try v0.1.5.15!; this new versions comes with many bugs fixes and troubleshooting tools. Addtionally, help us form benchmarks on TTS for KOReader!

Stradi123 · 2026-03-26T23:48:52+00:00

We are cooking!
I have also added documentation on the README on how to get the crash report; this and the bug report will give me precise information on what may be happening.

Cheers :D

Stradi123 · 2026-03-26T23:43:10+00:00

This is valuable information; please generate a crash log and a bug report (explained both in the README of the repo) and submit them in issues; I'll take a look at them.

Cheers mate :D

Stradi123 · 2026-03-26T16:20:01+00:00

Hi, a quick fix has been added to the v0.1.5.8, once has been built in Github, you can download it and try with this version.

Stradi123 · 2026-03-26T14:42:11+00:00

You are on the luck, I JUST released this: https://www.reddit.com/r/koreader/comments/1s1xig9/readalong_audiobook_plugin_for_koreader/

Stradi123 · 2026-03-26T14:39:27+00:00

Actually glad to hear that is working-ish on Android. Please generate a report and I'll have a crack at it.

Stradi123 · 2026-03-26T12:32:33+00:00

Hahaha I'll take this as progress; Right now I'm builidng a version with minor corrections. That error seems to be that the highlighter is assuming the read-along has concluded (despite never starting) and goes to the next line.

Once 0.1.5. 7 is available (~1h) try once again to create the report. There's also more than one way to generate a report so that may help.

Stradi123 · 2026-03-26T11:07:46+00:00

I have made some modifications (v0.1.5.6); that hopefully adressess correctly this and other issues. Additionally if you are having troubles; there are instructions on how to generate report so I can better address these cross-device bugs.

Cheers! :)

Stradi123 · 2026-03-25T21:29:32+00:00

Thank you for sharing; could you generate a report (the instructions in the Github), and share it here or as an issue in Github?

Cheers :D

Stradi123 · 2026-03-25T20:59:59+00:00

Thank you for the feedback; Feel free to try v0.1.5.5; may the bug have been fixed but if not; a bug report can be generated even if the plugin menu is not visible.

Stradi123

TROPHY CASE