Who Is Behind Smart Home Cinema
Smart Home Cinema was created by Marius Eugen Vomir, an independent creator who wanted local movie playback on Windows to feel easier, more natural, and controllable by voice.
The project began from a very practical frustration: local movie playback on a Windows PC still required too much manual interaction. Pausing a film, resuming playback, skipping forward, starting the next file, or adjusting subtitles often meant reaching again for a keyboard, mouse, or remote.
Over time, that friction started to feel unnecessary. The goal became simple: make local movie playback feel easier, more natural, and controllable by voice from a distance.
Marius Eugen Vomir was also featured in HackerNoon’s Meet the Writer interview series, where he spoke about Smart Home Cinema, local-first design, and the real frustrations that led to the project.
Why This Project Exists
Smart Home Cinema exists because local playback deserved a better interface.
Streaming platforms made people familiar with convenient, low-friction viewing. But local movie playback on Windows often remained awkward by comparison, especially when using a TV, lying in bed, sitting on a couch, or trying to stay immersed in a film without interruption.
This project was built to close that gap: to bring more comfort and continuity to local playback without giving up direct ownership of files, player choice, or control over the system.
What Smart Home Cinema Is
Smart Home Cinema is a voice-controlled movie playback system for Windows.
It allows local playback to be controlled through simple voice commands in two ways: through the Local Voice Edition with a PC microphone, or through the Voice Assistant Edition with Amazon Alexa / Google Assistant and TriggerCMD.
The system supports VLC Media Player and PotPlayer and is designed to make playback feel like one coherent product rather than a loose collection of scripts, shortcuts, and separate tools.
The Philosophy Behind It
Smart Home Cinema follows a local-first philosophy.
Playback remains local. Movie files remain local. Player control remains local. The system is designed around direct interaction with the user's own Windows machine, not around a cloud playback backend or a remote streaming service.
In the Voice Assistant Edition, Alexa / Google Assistant still use their own cloud infrastructure to receive spoken input. In the Local Voice Edition, supported voice commands are recognized locally through the user's PC microphone. In both cases, the playback system itself is centered on local execution, local files, and direct control.
The result is a setup built around privacy, predictability, and real ownership of the viewing experience.
What You Will Find on This Site
This site exists to explain the product clearly and to document how it works.
Here you can find product pages, installation guides, the Local Voice Edition page, beginner guides for Alexa, Google Assistant, and TriggerCMD, technical articles, and supporting material related to subtitles, playback behavior, and system architecture.
The goal is not just to present a product, but to make the whole system understandable for people who want practical, local, voice-controlled movie playback on Windows.
The Core Idea
Local movie playback should feel simple, comfortable, and voice-controlled without giving up privacy, ownership, or direct system control.