Smart Home Cinema Now Has Two Editions: Voice Assistant and Local Voice
Smart Home Cinema started as a way to control local movies on a Windows PC through Alexa or Google Assistant. Now it has evolved into two editions: one for smart assistant control, and one for direct local microphone control.
Smart Home Cinema was originally built around a simple idea:
watching local movies on a Windows PC should not require reaching for the mouse, keyboard, or remote every time you want to pause, skip, continue, or stop playback.
The first version of Smart Home Cinema solved that problem through smart assistants.
A user could say a command to Alexa or Google Assistant, the command would reach the Windows PC through TriggerCMD, and Smart Home Cinema would control VLC Media Player or PotPlayer locally.
That version still exists.
It is now called the Voice Assistant Edition.
But Smart Home Cinema has grown beyond that first workflow.
There is now a second edition:
Smart Home Cinema – Local Voice Edition.
Instead of using Alexa, Google Assistant, or TriggerCMD, Local Voice Edition lets the user speak directly to the Windows PC through a local microphone.
This does not change what Smart Home Cinema is.
Smart Home Cinema is still not a media player, not a streaming service, and not a media library system. It remains a local voice-control and automation layer for people who watch their own movie files on Windows using VLC or PotPlayer.
What changed is the way voice commands enter the system.
The original path: Voice Assistant Edition
The original Smart Home Cinema workflow was designed for people who already used Alexa or Google Assistant.
The basic flow looked like this:
Alexa or Google Assistant → TriggerCMD → Windows PC → Smart Home Cinema → VLC or PotPlayer
This approach made sense for smart home users.
If someone already had an Echo device, Google Assistant, or a smart speaker in the room, Smart Home Cinema could become part of that voice-control environment.
The user did not need to touch the PC during playback. The assistant handled the voice input, TriggerCMD delivered the command to the Windows computer, and Smart Home Cinema performed the local action.
This edition is still useful today.
For users who like smart home workflows, assistant routines, or voice control through an existing speaker, Voice Assistant Edition remains a valid way to use Smart Home Cinema.
But it also has more moving parts.
It requires an assistant, a command bridge, account setup, and external services that must be configured correctly.
That is why a second edition became necessary.
The new path: Local Voice Edition
Local Voice Edition was created for users who want a more direct setup.
Instead of sending the command through a smart speaker and an external bridge, the user speaks directly to the PC.
The basic flow becomes:
PC microphone → Local Voice Engine → Smart Home Cinema → VLC or PotPlayer
This removes the smart assistant layer completely.
There is no Alexa requirement.
There is no Google Assistant requirement.
There is no TriggerCMD requirement.
There is no smart speaker requirement.
The Windows PC itself becomes the voice-control point.
This is the biggest practical difference between the two editions. Local Voice Edition does not create a different product. It creates a different input path for the same core idea: controlling local movie playback on Windows by voice.
Same product, different voice input
This distinction is important.
Smart Home Cinema did not become two unrelated products.
Both editions are built around the same purpose:
voice-controlled local movie playback on Windows.
Both editions are designed for users who watch local video files with VLC Media Player or PotPlayer.
Both editions are focused on practical playback actions: play, pause, skip, next movie, subtitles, Command Center, progress display, local folder actions, and end-of-session control.
The difference is not the movie experience.
The difference is the voice input layer.
Voice Assistant Edition uses an external assistant as the voice entry point.
Local Voice Edition uses a microphone connected to the PC.
That is why the two editions can exist side by side without replacing each other.
They serve different users and different setups.
Why Local Voice Edition matters
Local Voice Edition matters because it lowers the barrier to entry.
A user no longer has to build a smart assistant workflow just to control movies by voice.
There is no need to create assistant routines, configure TriggerCMD commands, or depend on a smart speaker being available in the room.
For many people, this is easier to understand:
install the app, use a microphone, speak to the PC.
That makes Smart Home Cinema more accessible to users who do not have a smart home setup, do not want one, or simply prefer a local-first approach.
It also makes the product easier to explain.
Voice Assistant Edition is powerful for users who already live inside Alexa or Google Assistant ecosystems.
Local Voice Edition is more direct for users who simply want their Windows PC to respond to movie commands.
Offline after activation
This is one of the most important parts of Local Voice Edition.
Local Voice Edition still needs internet access for specific activation-related actions, such as trial activation, license activation, or license rebinding.
But once the trial or license is activated, normal movie control can work without an internet connection.
That means the core experience is offline after activation.
Voice command recognition, command handling, playback automation, CommandHub actions, visual overlays, Command Center behavior, VLC or PotPlayer control, and local file handling run on the user’s Windows PC.
For normal movie playback and normal movie commands, Local Voice Edition does not need Alexa, Google Assistant, TriggerCMD, or cloud-based command routing.
This makes it especially useful for local setups where internet access is unreliable, unavailable, intentionally disabled, or simply not something the user wants to depend on while watching movies.
There are still clear exceptions.
Internet may be needed for:
- trial activation;
- license activation;
- license rebinding;
- optional subtitle downloads through OpenSubtitles;
But those are specific online actions.
They are not required for the normal local playback-control experience after activation.
In practical terms:
if the trial or license is already activated, and the user is not downloading subtitles, Local Voice Edition can control local movies offline.
That is a major difference from voice-assistant-based control.
Why Voice Assistant Edition still exists
Local Voice Edition does not make Voice Assistant Edition obsolete.
Some users prefer smart assistants.
Some already have Alexa or Google Assistant in the room.
Some like saying commands to a smart speaker instead of speaking toward a PC microphone.
Some want Smart Home Cinema to feel like part of a broader smart home environment.
For those users, Voice Assistant Edition still makes sense.
The point of having two editions is not to declare one “right” and the other “wrong.”
The point is choice.
A user can choose the assistant-based path if they want Smart Home Cinema inside their smart home workflow.
Or they can choose the local microphone path if they want a simpler and more offline-friendly setup.
Both paths lead to the same core result:
voice control for local movies on a Windows PC.
What this means for older blog articles
Some older articles on this blog were written before Local Voice Edition existed.
At that time, Smart Home Cinema only had the Voice Assistant Edition.
That is why those articles naturally focus on Alexa, Google Assistant, TriggerCMD, assistant routines, or smart speaker workflows.
They reflect the original Smart Home Cinema workflow, which is still available today as the Voice Assistant Edition.
But now they should be read with the current product structure in mind:
Smart Home Cinema has two editions.
Some articles explain the Voice Assistant Edition.
Some newer pages explain Local Voice Edition.
And some general concepts, such as the First File Rule, local playback, subtitles, Command Center, or controlling movies from bed, apply to the Smart Home Cinema experience more broadly.
This article exists to make that distinction clear.
Where to learn more
For the full explanation of the microphone-based edition, including setup details, Local Voice states, privacy behavior, microphone recommendations, and offline use, see the dedicated Local Voice Edition page.
For installation and download options, use the Download & Installation page.
For users who prefer the assistant-based setup, the existing articles about Alexa, Google Assistant, TriggerCMD, VLC, and PotPlayer remain relevant to the Voice Assistant Edition.
Final thought
Smart Home Cinema began with one way to control local movies by voice:
use Alexa or Google Assistant to send commands to a Windows PC.
That idea is still useful.
But the product has now grown into something more flexible.
With Local Voice Edition, users can skip the smart assistant layer entirely and speak directly to their PC through a local microphone.
The result is still Smart Home Cinema:
local movie playback, controlled by voice, on Windows.
The difference is that users now have a choice.
They can connect Smart Home Cinema to a smart assistant, or they can keep the experience more direct, more local, and offline after activation.