The threat to Rigel gives him the opportunity to justify his obsession enough to take command. By saying that destroying it now is the best option, he’s reinforcing his mania with this argument. Decker isn’t totally unlikeable. His stated reasons – saving Rigel by destroying the machine – gives him a solid motivation to take command beyond simple rank. It’s still a decision based on revenge, guilt and obsession. Spock, on the other hand, reasons that since they can’t destroy it, Rigel is doomed. Decker won’t accept that. If he wasn’t so fixated on his quest, he might have moved off and consulted with Kirk and Spock about their best course of action. What a dull episode that might have been.
The episode was plenty fun as is. I don’t feel removing the ticking clock would make it more so.
That would be a sound editor, not a Foley artist. Foley artists record sound effects that must be precisely synced to the action onscreen, using various physical devices to create appropriate sounds (the way they did in old-time radio).. . . After Kirk toggles that improvised "self destruct" rocker switch, on can hear the "clicks" of a mechanism sounding rather mechanical. Please, that's not a complaint, merely an observation. For an audience of 1967, it's a sound they would immediately associate with a "time bomb". If done today, the Foley artist would probably dub in electronic "beeps".
Spock: “Illogical. We cannot destroy it, therefore we cannot save Rigel.”Yes Decker isn't totally wrong.
You know except where he beamed down everyone to a planet just after he saw the doomsday machine destroy another planet.
Didn't Spock just want to get Kirk then get out of range then tell Starfleet what was going on so they could defend Rigel? He wasn't giving up on Rigel.
Is there much difference between Deckers actions here and Kirk's actions in Obsession?
Kirk endangered his ship, his crew, kept sending redshirts down to the planet after he knew there was trouble.
r
Yes, it’s not very clear why he did that.Yes Decker isn't totally wrong.
You know except where he beamed down everyone to a planet just after he saw the doomsday machine destroy another planet.
This was my impression as well.Didn't Spock just want to get Kirk then get out of range then tell Starfleet what was going on so they could defend Rigel? He wasn't giving up on Rigel.
very good point. The only great difference is that Kirk hasn’t been totally emotionally crushed by his experience: while he feels guilty for the death of his companions he wasn’t true captain and, more importantly, he has had several years to work on his feelings.Is there much difference between Deckers actions here and Kirk's actions in Obsession?
Kirk endangered his ship, his crew, kept sending redshirts down to the planet after he knew there was trouble.
But 53 years ago, the average Joe in their living room or den would have expected a mechanically ticking "clock".
How do you figure that?Didn't fighting it cause it to feed more? Best coarse of action is leave it alone so it only needs to feed on one or two planets per system. Based on System L-374, it would not have eaten planet 3 if Decker would have left the DDM alone. His own action to fight it, caused the Constellation destruction and crew evacuation to planet 3, reduced the energy reserves of the DDM which then caused it to feed on planet 3 killing his own crew.
And it literally had a ticking "timer". After Kirk toggles that improvised "self destruct" rocker switch, on can hear the "clicks" of a mechanism sounding rather mechanical. Please, that's not a complaint, merely an observation. For an audience of 1967, it's a sound they would immediately associate with a "time bomb". If done today, the Foley artist would probably dub in electronic "beeps". But 53 years ago, the average Joe in their living room or den would have expected a mechanically ticking "clock".
Correct, the timer is not in line with what we actually see.
Spock: “Illogical. We cannot destroy it, therefore we cannot save Rigel.”
Now he could have meant “Cannot save Rigel ourselves“ but the Planet Killer was probably too close to the system to be stopped before the fleet could be gathered. However perhaps an evacuation could have been attempted. Spock seemed to be looking ahead to trying to stop the machine before it reached “the most densely populated section of our galaxy.”
I timed the 30 second clock taking ~80 seconds on screen. One half minute on Enterprise plus one half minute on Constellation sequentially only equals one minute. Maybe the extra 20 seconds was sequentially spent following the DDM, too?On the ticking-clock show 24, they often packed multiple screens in at once to show various things happening simultaneously. Maybe scenes on the two ships are happening at the same time, but shown sequentially.
You gotta consider that maybe some of the shots are happening in parallel.I timed the 30 second clock taking ~80 seconds on screen. One half minute on Enterprise plus one half minute on Constellation sequentially only equals one minute. Maybe the extra 20 seconds was sequentially spent following the DDM, too?![]()
I timed it from Sulu's countdown; And Kirk was beamed off 9 seconds after the Constellation's impulse engines should have exploded.If you can get any ringtone today, including a 1950s-sounding electro-mechanical bell, I'm sure Scotty could select any sound he wanted for his timer. The episode didn't know that, but it still counts.
I timed my audio cassette once as a kid, and the 30-second interval was more like a minute and a half if I recall correctly.
I timed it from Sulu's countdown; And Kirk was beamed off 9 seconds after the Constellation's impulse engines should have exploded.![]()
Exactly!You gotta consider that maybe some of the shots are happening in parallel.![]()
![]()
We use essential cookies to make this site work, and optional cookies to enhance your experience.