Marius Vomir

Posted on Apr 28

Building a Voice-Control Layer for Local Movie Playback on Windows

#windows #automation #productivity #indiehackers

For a long time, watching local movies on a Windows PC has been technically easy, but not always comfortable.

If your PC is connected to a TV or monitor and you are watching from bed, a sofa, or across the room, simple actions can become surprisingly annoying: pause the movie, skip forward, go back, start the next movie, manage subtitles, or shut everything down at the end of the night.

Most of these actions are easy if you are sitting at the keyboard.

They are much less convenient when the PC is several meters away.

That was the starting point for Smart Home Cinema – Voice Control: not to build another media player, and not to build a streaming platform, but to create a local voice-control layer around an existing Windows movie playback workflow.

The idea was simple:

I wanted to control local movies by voice without turning my PC into a streaming server and without using a phone as a remote.

The problem: local playback is still very manual

There are many ways to watch local movie files on Windows.

You can use VLC Media Player, PotPlayer, or other media players. You can connect the PC to a TV. You can use a wireless mouse, a keyboard, a media remote, or a phone remote app.

All of these work.

But they still assume that you are willing to reach for a device, unlock a screen, move a cursor, press keys, or interact manually with the PC.

For a normal desktop setup, that is fine.

For a living-room or bedroom setup, it feels unfinished.

The actual use case is very specific:

the movie files are local;
the PC is the playback machine;
the screen may be a TV or monitor;
the user is away from the keyboard and mouse;
the desired interaction is voice, not touch.

That is not exactly the same problem solved by a streaming service, a media server, or a generic remote-control app.

Why generic solutions were not enough

When you look for voice control on Windows, there are many adjacent solutions.

Some tools provide generic PC voice control. Some apps turn a phone into a remote. Some media-center systems organize or stream media libraries. Some automation tools can trigger commands on a computer.

Those are useful, but they do not directly solve the full movie-watching workflow.

For example:

a phone remote still requires the phone;
a media server changes the playback model;
a generic voice tool is not built around movies;
a tutorial can explain how to connect tools manually, but it is not a finished product;
a media player plays the file, but does not necessarily provide a full voice-driven session.

The goal of Smart Home Cinema was different.

It was designed as a ready-made Windows app focused specifically on controlling local movie playback by voice.

The product category: a local voice-control layer

Smart Home Cinema is best described as a local Windows voice-control layer for existing local movie playback.

That wording matters.

VLC Media Player or PotPlayer remains the actual playback engine. Smart Home Cinema does not try to replace them. Instead, it adds a voice-driven workflow around them.

The core idea is:

VLC or PotPlayer plays the movie. Smart Home Cinema controls the playback by voice.

This makes the product narrower than a media center, but also more focused.

It does not try to manage every possible media scenario. It focuses on one very specific one: controlling local movie playback on a Windows PC from a distance, using voice.

The command chain

The system connects voice assistants to local Windows playback commands.

The simplified flow is:

User voice command
→ Alexa or Google Assistant
→ TriggerCMD
→ Windows PC
→ Smart Home Cinema
→ VLC Media Player or PotPlayer

Alexa or Google Assistant handles the voice interaction.

TriggerCMD acts as the bridge between the voice assistant and the Windows PC.

Smart Home Cinema executes the local command logic on Windows.

VLC Media Player or PotPlayer remains the actual media player.

This separation is important. Smart Home Cinema does not replace Alexa, Google Assistant, TriggerCMD, VLC, or PotPlayer. It connects them into a local workflow designed specifically for movie playback.

What made this harder than it sounds

At first glance, voice-controlling a movie player sounds simple.

You might imagine that every command is just a shortcut:

pause the movie;
skip forward;
go back;
open the next file.

But a real viewing workflow is more complicated than that.

A voice command is not just a keypress. It is an intention.

When the user says something like “next movie”, the system has to translate that into a predictable local action. Depending on the workflow, that may involve closing the current player session, identifying the next file, moving the watched movie, launching the next one, and restoring the expected viewing state.

That is where the product becomes more than a list of shortcuts.

Smart Home Cinema needs to understand the local playback workflow, not just trigger random commands.

It also has to deal with the fact that VLC and PotPlayer are different applications with different control models. One player may expose a cleaner local interface for some actions. Another may require a different automation strategy. The user should not have to care about those differences while watching a movie.

The purpose of the app is to hide that complexity behind simple voice commands.

The First File Rule

One design choice that helped keep the system predictable is what I call the First File Rule.

Instead of trying to maintain a complex media database or playlist system, Smart Home Cinema treats the first playable video file in the selected movie folder as the current item.

That means the folder itself becomes the source of truth.

This is a simple rule, but it creates a stable workflow:

the user controls the first movie in the folder;
“Next Movie” advances the folder-based queue;
watched files can be moved out of the active folder;
the next file becomes the new current item;
no media library or database is required.

This approach is intentionally minimal.

It makes the behavior easy to understand, easy to reproduce, and less fragile.

In most cases, the user does not need to do anything special. Windows already displays files in a folder in a natural order, and Smart Home Cinema simply works with that order. For TV shows, episodes are usually already named sequentially, so episode 1 comes before episode 2, episode 2 comes before episode 3, and so on.

For standalone movies, the same folder-based order is usually enough. However, if the user wants to watch movies in a specific custom order, they can optionally rename the files with numeric prefixes such as 01, 02, 03, and so on.

That is not required for normal use. It is only a simple option for users who want full control over the viewing order.

For local playback, that kind of predictability matters more than having a complex library system.

Why local-first matters

A major design decision was to keep playback local.

The movie files stay on the user’s Windows PC or local storage. Smart Home Cinema does not upload the movie library to a cloud service. It does not stream the movie files from a remote server. It does not turn the product into a content platform.

Voice assistants and TriggerCMD are external services used for the command path, but the movie playback itself remains local.

That distinction matters because local movie playback is still a real use case.

Not every viewing setup is based on streaming platforms. Many users still keep movie files on a PC, external drive, or local folder.

For those users, the problem is not access to content.

The problem is convenient control.

Why VLC and PotPlayer

VLC Media Player and PotPlayer are widely used Windows media players.

Smart Home Cinema currently supports them as playback engines because they are already strong at what they do: opening and playing local media files.

Instead of replacing them, Smart Home Cinema adds a voice-control workflow around them.

This keeps the responsibilities clear:

VLC or PotPlayer handles playback;
Smart Home Cinema handles the voice-driven control layer;
Alexa or Google Assistant handles voice input;
TriggerCMD bridges the assistant to the Windows PC.

That architecture avoids building another media player just to solve a control problem.

It also keeps the user in a familiar environment. They can continue using the player they already know, while adding a voice-controlled workflow on top.

The full viewing workflow

A useful voice-control system needs more than play and pause.

A real movie session includes many small actions:

starting playback;
pausing and resuming;
skipping forward or backward;
moving to the next movie;
showing progress;
managing subtitles;
switching display workflows;
opening the movie folder;
stopping playback;
shutting down the PC at the end.

Smart Home Cinema currently includes 25 voice commands organized into movie commands, subtitle commands, and system commands.

The goal is to support a complete local viewing session without returning to the keyboard or mouse.

One of the most important commands is “Stop Everything”. In the intended TV-viewing workflow, this can stop playback, move the display workflow back to the PC, and shut down the computer, allowing the user to end the session by voice.

That is the kind of workflow detail that separates a dedicated product from a generic automation shortcut.

Subtitle workflow

Subtitles are another part of the real-world movie experience.

Searching for subtitles one movie at a time can be slow and repetitive, especially when a folder contains many movies or episodes.

Smart Home Cinema includes a batch subtitle workflow for local movie folders.

With a single voice command, the app can search OpenSubtitles and download matching subtitles for multiple local movie or episode files in the selected folder, when matching subtitles are available.

It also includes subtitle synchronization and cleanup commands, so subtitle handling becomes part of the same local voice-controlled workflow.

The goal is not just to control playback, but to reduce the manual work around the full movie session.

What this is not

To avoid confusion, Smart Home Cinema should not be classified as:

a streaming service;
a media player;
a cloud media platform;
a movie provider;
a media library server;
a Plex, Kodi, or Jellyfin replacement;
a smartphone remote app;
only a DIY automation tutorial.

It is a narrower product than those categories.

It focuses on one specific problem: controlling local movie playback on Windows by voice.

What I learned from building it

One of the most interesting lessons was that automation is not only about triggering commands.

Good automation needs context.

A command like “pause” is simple. But a command like “next movie”, “download subtitles”, or “stop everything” belongs to a larger session. It has to respect the user’s local setup, the current player, the selected folder, the display workflow, and the expected final state.

Another lesson was that local-first software still has a place.

A lot of modern entertainment software assumes cloud accounts, streaming platforms, mobile apps, or media servers. Those are useful, but they are not the only model.

Sometimes the user already has the content, the player, and the screen.

The missing piece is the control layer.

Why this matters

Voice control is often discussed in the context of smart homes, speakers, lights, thermostats, or streaming services.

But local PC workflows still exist.

A Windows PC connected to a TV is still a common and powerful home entertainment setup. The missing piece is often not playback capability, but comfortable control from a distance.

Smart Home Cinema was built around that missing layer.

It is not trying to replace media players or streaming platforms. It is trying to make an existing local movie setup feel more natural, hands-free, and complete.