5 ms·
I built summarize.tech Yes it's a great idea and I have a version that is basically a convolution over the transcript. It works much better than the current ve
by peterhunt 3y ago
I built summarize.tech
Yes it's a great idea and I have a version that is basically a convolution over the transcript. It works much better than the current version - it can automatically create cohesive chapters and summaries of those chapters - however, it consumes an order of magnitude more ChatGPT API calls making it uneconomical (for now!)
- e1g 3y agoI'm inspired that this is a side project, given everything you run. Kudos.
- peterhunt 3y agoThanks for the kind words. I built it on a few cross-country plane rides and now I mostly just leave it alone. The infrastructure and tooling we have these days is so incredible.
- moneywoes 3y agoCan you please eli5 the difference of old and new?
- peterhunt 3y agoSure. The old one just splits the transcript into 5 minute chunks and summarizes those. The reason this sucks is because each 5 minute chunk could contain multiple topics, or the same topic could be repeated across multiple chunks. This dumb technique is actually pretty useful for a lot of people though, and has the advantages of being super easy to parallelize and requiring only 1 pass through the data. The more advanced technique does a pass through large chunks of the transcript to create lists of chapters in each chunk. Then it combines them to a single canonical chapter list with timestamps (it usually takes a few tries for the model to get it right). Then it does a second pass through the transcript, summarizing the content for each chapter. The end result is a lot more useful, but is way slower and more expensive.