Hey everyone, I wanted to share an updated introduction to something I’ve been building called PosterFlow. PosterFlow started as a personal home theater project. I wanted a cleaner way to manage digital poster screens without constantly juggling folders, images, slideshow tools, display windows, schedules, and manual updates. The goal was to make poster displays feel more like part of a real cinema/preshow setup instead of just a rotating image folder. PosterFlow is a Windows desktop app with an
Hello,
We’ve run into a portability issue when creating sequences in PreShow Experience on a desktop or non-media-server player.
Currently, PreShow stores all media references as absolute file paths tied to the original machine. This means that if we move a PreShow project folder to another server or workstation, the sequence breaks because the media paths still point to the original device location.
This creates unnecessary extra steps when deploying sequences for:
Short films
Theatre intros
Touring productions
Multi-server installations
Instead of simply moving the PreShow project folder and relinking a single base directory, we have to manually update or recreate paths due to the absolute references.
Requested Feature
It would be extremely helpful if PreShow could support relative file paths for media content.
For example:
When setting a content directory in PreShow, the software would treat that folder as the base path.
All media within the sequence would then be referenced relative to that base folder, rather than to an absolute system location.
When moving the project to a new machine, we would only need to update the base content directory once.
Benefits
Improved portability between systems
Easier deployment to media servers
Cleaner project structure
Reduced setup time for touring or distributed environments
Fewer broken media links
This enhancement would significantly streamline workflow and reduce errors when moving projects between machines.
Thank you for considering this request.
Edited by SVS