Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

How much episode recap is necessary in a tv-focused podcast?

+1
−0

I'm planning for my next podcast to do an episode-by-episode tv show analysis. (Actually two are in development, but they'll be about different shows.)

I'll be the main researcher/outline-assembler for these, and I'll have a co-host to bring in their background info.

One show is mega-popular and perennial -- but often people think they remember more about the show than they do -- they have a bit of a "Flanderized" image of some characters, especially. The other show has a smaller but more devoted fanbase, and is extremely serialized.

I can get lost in research, especially since the internet as a whole has a ton about Popular Show, and I personally have a ton on Devoted Fanbase show (including scripts).

Obviously the synopsis should be done mostly to jog the audience's memory and to pull out points for discussion, but how much is enough or too much?

Also, besides beat-by-beat (or scene-by-scene -- basically the order everything appears in the show) - are there other strong ways to organize the synopsis?

TLDR: How much episode recap is necessary in a tv-focused podcast? And what other organizing strategies work?


I was inspired by this question: How do I record information when planning to write a recap of events?
History
Why does this post require moderator attention?
You might want to add some details to your flag.
Why should this post be closed?

0 comment threads

2 answers

+0
−0

You said in a comment that this is for an existing, old show, presumably one with a fanbase. While your listeners have presumably seen it (they're listening to your podcast about it, after all), they might not have done so recently and even hardcore fans might not always remember episode sequencing (when things happened relative to other things). Therefore, you probably want a brief summary of points that are important for what you're going to talk about.

For example, suppose you were going to talk about the Babylon 5 season-2 opener, Points of Departure, which aired about 20 years ago. And suppose you're specifically going to be talking about Minbari politics and not much about the fact that there's a new commander on the station. You might open with something like:

When last we saw Ambassador Delenn she was disappearing into a cocoon. Apparently this was a possibility her government foresaw, as they've sent an emissary to the station, and apparently they're not happy -- look at that guy's face! But wait, didn't a Gray Council member give her the device she needed to build it? In today's episode of "As the Station Turns", we'll delve into the secrets and internal struggles of the race that nearly destroyed Earth not long ago.

During this episode a hostile Minbari warship arrives. I didn't mention that in my synopsis because (in this hypothetical podcast I'm planning for you :-) ) either you're going to talk quite a bit about it -- and can bring it up then -- or it's not going to be central to what you talk about.

To summarize, then:

  • Include key points that are important to the timeline (someone remembering this episode years later might think Delenn has already emerged).

  • Include smaller points, things that would be more easily forgotten, if they're important context for your cast. (The presence of that Gray Council member could be easily forgotten.)

  • It's ok to provide context in an "oh by the way" manner. (Fans of the show already know that the Minbari almost destroyed Earth; you're dropping in a casual reminder that it was recent.)

  • If it's important to the episode but not to your podcast, skip it. (This podcast episode isn't about Earth politics and the sudden change in station commander. Well, not directly; to the extent it intersects with what you're going to talk about, you can cover it then.)

History
Why does this post require moderator attention?
You might want to add some details to your flag.

0 comment threads

+0
−0

I think you see this all the time in "Previously on XYZ" segments of shows that have long plotlines (i.e. episodes are not self-contained).

The only thing they recap is what you need to know for THIS episode, and then not the whole subplot, just the last thing that happened in that subplot. e.g. The Breakup, not the romance before it. Or the woman seeing her ex with a new woman; and not the The Breakup before it.

As for organizing the elements; I'd go with explaining first what they will see first; i.e. if the first "new thing" or "reveal" in the current episode is we find out Mary is doing some serious spying on Cindy, recap first *why Mary is spying on Cindy.

I think you can presume your listeners watch the show; so all you need to do is remind them of what was the LAST thing that happened in each subplot, you don't have to recap the whole subplot.

As for NEW subplots, I wouldn't recap anything for them, unless some decision is critical to how the new subplot develops, you might want to tease that.

Remember how proud Josh was to get his promotion? I'm just saying, remember that.

History
Why does this post require moderator attention?
You might want to add some details to your flag.

0 comment threads

Sign up to answer this question »