transcript.fish VS pls

I have been working on this podcast transcription project for a couple months and it's been super rewarding.

I listen to a podcast called No Such Thing As A Fish, where some researchers talk about their favorite facts they learned that week. Then they riff on it and are generally smart and funny. I listened to the series so many times that I decided I wanted to listen to the show on shuffle, not at the episode level, but at the fact level.

Since I have been playing around with whisper.cpp in python this seemed like a perfect way to combine some technologies I've been wanting to play with.

I ran whisper over the entire podcast and transcribed all the episodes. I had to do this multiple times because I kept messing up. It eventually took like 7 straight days of my M1 processing to get through ~490 episodes.

4 million words, and an 800Mb SQLite database later, I got the transcriptions done and have put up a nice site for searching through the data.

https://transcript.fish

Now I just need to figure out the rest. Breaking it up into facts. Getting the audio working. Highlighting and linking to words, phrases, etc.

Some cool info about the process so far:

1. The SQLite database is chunked up and stored as static files, and the frontend queries the static files directly using HTTP range requests, so it only downloads a couple hundreds kbs when querying.

2. I've been proper using ChatGPT 3.5 free version to help me write python and SQL. It's been pretty game changing as I feel basically no pain from not knowing what I'm doing.

The code is here: https://github.com/noman-land/transcript.fish

Please help if you know how to get whisper speaker diarization working!! I would really appreciate the help.

Interesting, thanks for the tip! I've never heard of lockdown mode. Unfortunately I don't own an iPhone. Any chance you could post an issue with steps to repro?

https://github.com/noman-land/transcript.fish/issues

Thank you!

Many PR about typos fixing or installing GitHub actions to validate spellchecking on various repositories fix typos #4 ccoVeille posted on Apr 15, 2024 Fix typos and style Format README.md file View on GitHub Add Typos GitHub Action #37 ccoVeille posted on Apr 19, 2024 https://github.com/marketplace/actions/typos-action Fixes #28 View on GitHub fix typos #113 ccoVeille posted on Apr 13, 2024 Fix typos in code and tests Fix acronyms and brand names View on GitHub fix typos, brands and acronyms #21 ccoVeille posted on Apr 01, 2024 fix typos in code, test and documentation Fix registered trademark and other acronyms View on GitHub Fix typos in the documentation and code comments #99 ccoVeille posted on Apr 21, 2024 View on GitHub typos suggestion #390 ccoVeille posted on Apr 22, 2024 Check list [X] I have performed a self-review of my code [ ] I have commented my code in hard-to-understand areas [X] I have made corresponding changes to the documentation Description Fix some typos and wordings in README.md Fix headers style Fix exemplī grātiā usage (Latin) Type of change [ ] Bug fix [ ] New feature [ ] Refactor [ ] Breaking change [X] Documentation change Test environment Shell [ ] bash [ ] zsh [ ] fish OS [ ] Linux [ ] Mac OS X [ ] Windows [ ] Others: View on GitHub Fix typo and style #3 ccoVeille posted on Apr 25, 2024 View on GitHub

I'm working on pls (https://github.com/dhruvkb/pls/), a prettier and more powerful alternative to ls(1) that adds a lot of customisation and provides a very fluent command-line interface. It aims to be a superset of exa in terms of the features, while being more actively maintained and targeting a smaller subset of pro-users.

It works quite well and is very usable as a daily driver. I'm adding more features to it and making it available to install it via platform-native package managers.

I made a small CLI tool called pls (repo). It's a FOSS app for listing the contents of your directory (similar to ls) but it has lots of nifty features geared towards professionals/programmers (hence the 'p' in the name) that make the output prettier and easier to visually parse.