3 ms·
I always go straight for the prompt with this kind of thing - it's here: https://github.com/knowsuchagency/pdf-to-podcast/blob/512bfbdb4fd658ad4b301336020c4ea16
by simonw 2y ago
I always go straight for the prompt with this kind of thing - it's here: https://github.com/knowsuchagency/pdf-to-podcast/blob/512bfbdb4fd658ad4b301336020c4ea16cb69e18/main.py#L49-L80 https://github.com/knowsuchagency/pdf-to-podcast/blob/512bfb...
It starts like this:
Your task is to take the input text provided and turn it into
an engaging, informative podcast dialogue. The input text may
be messy or unstructured, as it could come from a variety of
sources like PDFs or web pages. Don't worry about the
formatting issues or any irrelevant information; your goal is
to extract the key points and interesting facts that could be
discussed in a podcast.
The way this uses different OpenAI TTS voices for the different roles is really neat!
- zachthewf 2y agoI wonder what (if anything) is the impact of the leading spaces on each line of the multiline string, which are an artifact of wanting to keep the prompt pretty within code. Hopefully not much, but I've heard horror stories about trailing spaces...
- simonw 2y agoAs far as I can tell that only really affects the smaller models - GPT-4 / Claude / Gemini all seem pretty much impervious to weird whitespace in my experience.
- cchance 2y agoI imagine you could force this even further by specifying the names of the researcher and interviewer, and giving details of the structure of the episode