What does the Podcasts say about the Podcast episode?
The episode is downloaded in the Podcasts app: the Download button under the episode itself. The engine reads the English speech of the Podcast episode and writes the blog post from that text.
Podcast episode to a blog post in English: send the file and get the text with the timecodes. One file may be up to 30 minutes on the free plan, no minute limit on Pro.
The Podcast episode from the Podcasts becomes the blog post: the engine reads the English speech and the sections Headline and lead, Outline, Draft are written from the transcript. The free plan gives 3 files a day of up to 30 minutes.
The app can save the episode in a higher or in a lower quality, and the choice changes the size of the file
The file of the Podcast episode is sent as an attachment; the language of the speech is English, and the blog post comes back in the export of the service.
The text of the Podcast episode is given to the instruction of the blog post, and the answer is written in the sections Headline and lead, Outline, Draft, one after another.
The recording of the Podcast episode is in English, and that is one of the 99+ languages the engine reads; the setting of the widget says English and the blog post follows.
The downloaded episode is an MP3 file, and the app can offer it in a higher or in a lower quality
One segment per line, the way a person wrote it down. It is the format to paste into a ticket, a chat or a document.
The start and the end time of every segment, and the speakers named separately when you ask for it.
SRT and VTT with the time of every line, so the recording can carry its own subtitles.
The transcript is edited through the API and exported as Markdown for a wiki, or as DOCX for a review.
| What | What the platform says |
|---|---|
| Where the file is | The episode is downloaded in the Podcasts app: the Download button under the episode itself. |
| What the file is | The downloaded episode is an MP3 file, and the app can offer it in a higher or in a lower quality. |
| What can go wrong | By default the app takes the audio of the episode, not the video of it. |
| Length of one file | up to 30 minutes on the free plan, no minute limit on Pro |
| Free plan | $0: 3 files a day, up to 30 minutes per file, no card |
| Pro plan | $10 a month when you pay yearly ($120 a year), or $20 a month |
The episode is downloaded in the Podcasts app: the Download button under the episode itself. The Podcast episode is read by the engine in English, and the blog post is written from the text, not from a guess.
Send the transcript to the instruction only once.
The language of the widget is the language of the Podcast episode.
A file over 30 minutes has to be cut into parts; the Pro plan takes a recording of any length.
By default the app takes the audio of the episode, not the video of it.
The episode is downloaded in the Podcasts app: the Download button under the episode itself. The engine reads the English speech of the Podcast episode and writes the blog post from that text.
By default the app takes the audio of the episode, not the video of it. The file of the Podcast episode is the input of the engine, and the blog post is written from it.
the author of the post. The transcript of the Podcast episode is read first, and the blog post comes out of it in the sections Headline and lead, Outline, Draft.
3 files a day of up to 30 minutes every day, and the export of the text in the formats of the service, so the blog post comes back in every one of them.
The file of the Podcast episode and the widget are enough: the engine reads the English speech and writes the blog post.
The same task on another recording, with the same steps and the same sections.
Video to a blog postThe page of the task: the instruction that is written for it and an example of the answer.
Transcribe audio to textWhat the service does with a file: the formats of the export, the limits and the plans.
Podcast episode to textWhere Podcasts keeps the file, what it holds and what the engine does with it.
Speakers by name, a time on every line, export to TXT, SRT, VTT, CSV and Markdown.