flackbash / AudioAnchor

Android audio player that tracks the listening progress of your audio books and podcasts
GNU General Public License v3.0
216 stars 41 forks source link

Feature suggestion: log of listened/played files (quantified self) #31

Open eternalbit opened 4 years ago

eternalbit commented 4 years ago

Having a log of the played books/files would be neat. Simply a CSV style file containing date/time and filename.

flackbash commented 4 years ago

To be honest I doubt that this is a feature many people would use.

Do I understand you correctly: You would like a log entry for every time you start the playback? Probably plus the duration of the playback? So you would get an entry for every time you hit the play (or pause) button...

eternalbit commented 4 years ago

You might be right, that not many people would actually use it.

I like the idea of being able to check what files I've listened to at a certain time.

Maybe there could be some kind of heuristic that determines whether I've actually played back a certain file .. it could check whether I've played more than 30 % of the file and then create the respective entry in the log. Then there would only be one entry for each file in most cases. So it wouldn't be just a raw list of play/pause events.

Sulter commented 4 years ago

You might be right, that not many people would actually use it.

I like the idea of being able to check what files I've listened to at a certain time.

Maybe there could be some kind of heuristic that determines whether I've actually played back a certain file .. it could check whether I've played more than 30 % of the file and then create the respective entry in the log. Then there would only be one entry for each file in most cases. So it wouldn't be just a raw list of play/pause events.

So a database with <file, stats>?

eternalbit commented 4 years ago

So a database with <file, stats>?

I don't understand what's meant by that syntax.

Self-Perfection commented 4 years ago

I'd say universal solution would be broadcasting of playback events. I don't know how this works in android terms, but surely it has something similar to D-Bus. Then user might setup any reaction to playback events, for instance logging to file. Widely known Tasker app might handle that.

Najrim commented 3 years ago

I'd love to have this functionality. The csv could look something like:

playback_start playback_end audiobook_title book_author
unix timestamp unix timestamp A book title Jonh Doe

Or the filename instead of the last two columns, as @eternalbit suggests.

flackbash commented 3 years ago

Ok, implementing this as @Najrim suggested would be quite straight forward. Still, I don't believe there is a high demand for such a feature but if it turns out more people would find this useful, I might implement this.

bhankas commented 3 years ago

+1 for interest in this feature.

bhankas commented 3 years ago

Just one suggestion : File should only be logged if it was played for more than certain duration. Otherwise just checking which file/episode was played last will populate log and the whole purpose will be defeated. I propose 30-60s, considering most audiobook chapters are 10+ minutes.