Cozy is a modern audiobook player for Linux
github.com
github.com
I don't use mac though, so haven't confirmed what I've heard.
Why cannot pressing play in this instance be like a reverse snooze??
As others have mentioned, some kind of 'stay awake' feature would probably solve the issue too. I'm thinking a non-intrusive beep or shake the indicate that the phone is about to go into 'sleep mode', which can be dealt with by some feedback. the interval could then be set in the app or OS settings.
The nice thing about doing this system-wide is that it could do all sorts of other stuff: turn off notifications (I sometimes forget and get rudely awakened at night), go into low-battery mode, turn off the screen (in case I forget to put it facing down), etc.
It also has bookmarks but I never use them.
https://play.google.com/store/apps/details?id=com.acmeandroi...
I was surprised when I saw the Apple Books app didn't have that feature. Seems like a no-brainer to include.
In their library I did find most of the titles I was interested in, selection is good, content is high quality, so I've been enjoying it.
docker run -v $(pwd):/data ryanfb/inaudible@sha256:b66738d235be1007797e3a0a0ead115fa227e81e2ab5b7befb97d43f7712fac5
The resulting m4b file has proper chapters, so works everywhere, but I tend to split it further[0],[1][0]: https://github.com/captn3m0/Scripts/blob/master/split-by-aud...
[1]: https://github.com/captn3m0/Scripts/blob/master/split-audio-...
1. This tool can be used to extract your encryption keys: https://github.com/inAudible-NG/audible-activator
2. ffmpeg -activation_bytes XXXXXXXX -i name.AAX name.mp3
-i in.aax -c copy out.m4b
1. does not transcode 2. captures and retains all of the metadata
It lacks Audible exclusive titles (which are shockingly many!), though.
Before that, I used to strip the DRM from my audible books (easily doen using ffmpeg)
[0]: https://libro.fm
The size of the app is quite large for its functionality: 244.1 MB (Resources folder and MacOS folder take majority of application size.) which is puzzling. Given it uses GTK+, I don't think that it would look great on other systems if it is applying the GNOME theming / decorators to its windows. (Remember gedit on macOS / Windows?).
Given its still in beta and primarily uses GTK, I'd rather use this on Linux than on macOS. From what I have seen from other GTK+ apps, they just standout like a sore thumb on any other platform other than Linux. For cross-platform, I would use Qt5 instead.
Comparing to an Electron app, the bundle is likely smaller and resource usage lower, with little difference in theming.
Offtopic, but this reminds me of how Audible in general (website, purchasing UX, etc) always feels half broken. It mostly works but small bizarre things ruin it (most recently a purchased book disappearing while marked as purchased in the store requiring manual support intervention). I often wonder if it's half abandon ware since they now have a monopoly and it's using some ancient Java backend.
Even syncing progress b/w ebook readers is a pain point for me right now[1], but I'd love to see solutions for this.
- Speech-to-text. It has to be good, or the text you get back is unusable. Google's and Amazon's services for that will quickly become expensive for large volumes. And you need to mark text with time/position if you want ebook-to-audiobok sync.
- Diff algorithm between generated text and ebook text. Audiobooks are not produced from the same source material as ebooks, and they will have differences. On top of that you get errors and changes by narrators, and errors from speech-to-text. Not trivial if you want high fidelity.
- Figuring out the position in ebook from the diff. Relatively simple.
For ebook-to-audiobook you need to find the position in the speech-to-text conversion, and rewind to the time/position marking in that.
Storytel (disclaimer: I work at Storytel) has quite a few ebooks and audiobooks connected, but doesn't allow you to ingest your own ebooks and audiobooks.
that guy thinks you are going to be very big
all the best. We sure need more people doing ebooks and audiobooks. Amazon is @#$#$ authors with all their exclusivity requirements and insanely high cut that they take
The whole audiobook landscape isn't clear cut yet. In music and video you have a few well-established (entrenched?) players: Amazon, Google, Apple, Spotify (music). In audiobooks there are still a bunch of smaller players alongside Amazon (Apple doesn't do much about audiobooks, other big players are only just starting, see Spotify). There are at least three in every country, I think :)
And the whole thing is further fractured by whether or not publishers and rights holders want to provide their audiobook, and ebooks, or only one or the other. And there are way more publishers and rights holders than there are in music (in music they are also mostly consolidated into a few megamonsters [1]).
And the market is still growing, as more and more people discover and listen audiobooks (and related material like podcasts) during commute, in the car, during daily routines and so on.
So yeah, it's stressful, but interesting :)
To establish synchronisation you need to have, well, two texts and a way to compare them ;)
> where you don’t have synchronization you could assume that the speaker is carrying on at their normal words per minute.
What is their normal WPM and how would you calculate that? ;)
I've been putting off looking for an audiobook reader for linux to improve my german. HN makes life easier ;)
As an aside: does anyone know of an audiobook organiser? Essentially Calibra for audiobooks. Preferably with a web interface for running in my home server. I’ve tried booksonic, and found it very clunky and lacking proper organisational features.
>Hey, I'm the developer of Cozy and I just noticed that Cozy got posted here and people are trying it on macOS. The version linked in the README was a very old version of Cozy which I tested on macOS 10.14. It was quite a hassle to build and it was not stable. Sadly it's a lot of work to package a GTK app for macOS, therefore I discontinued building it but I didn't update the readme. Sorry for anyone who tried it and got disappointed!
Which probably wouldn't have been such an issue with electron.
For a user-specific application like a player, I would rather use a desktop app developed exclusively for a specific OS or set of OSes that works well with those. There are millions of Mac apps that have no equivalent on Linux, so I'm glad to see a developer focusing exclusively on Linux.
Electron for cross-platform apps works well when you are going to be forced into using it as a web client anyway due to proprietary platform lock-in, e.g. Slack.
Currently the best way to build something for Apple devices (outside of owning Apple hardware) seems to be usage of CI.
EDIT: I've just found https://community.spotify.com/t5/Content-Questions/Audiobook... which says
> In Browse > GENRES& MOODS > WORD you can now find these options.
Which should be available through their API using https://developer.spotify.com/documentation/web-api/referenc... It's not immediately obvious how I get to the Browse section through the awful interface at https://play.spotify.com but you can jump straight to https://open.spotify.com/genre/word-page
#!@PYTHON@
this is different of what I know about shebangs in Python
(I know, gtk is a pain in virtualenvs)
gstreamer1.0-plugins-good
gstreamer1.0-plugins-bad
gstreamer1.0-plugins-uglyIgnore below
---
the suffixes are related to codec licencing afaik
For example, foss purists might like to install `-good` whereas those who prefer all video sources to "just work" will also want `-ugly`
- "Good" plugins/codecs are ones that are freely distributable, FOSS and well maintained.
- "Bad" are ones that are not up to par quality wise (messy code, no code reviews, no documentation, ugly hacks, etc.)
- "Ugly" are the ones that might not be legally distributable in some world countries due to patents or licenses.
Free, open source, cross platform including mobile and remembers where I stopped listening.