Packaging and Distribution
Build standalone Windows distributions and keep runtime dependencies intact.
Package Roneat Studio Pro for Windows without breaking runtime features.
Packaging goals
A good build should:
start without missing imports
keep audio features working
include all runtime assets required by the app
Before you package
Confirm these items first:
Python dependencies install cleanly
ffmpeg.exe exists in the project root
export features work in development mode
Runtime dependency checklist
Python packages
Your package process must include everything from requirements.txt.
Missing scientific or audio packages usually fail at startup.
Video export depends on ffmpeg.exe.
Copy it into the packaged output.
If the final build lacks that file, MP4 export will fail even if the UI opens correctly.
Recommended validation flow
Validate source mode
Run the app locally and confirm core features work.
Create the packaged build
Use your preferred Windows packaging flow.
Copy runtime binaries
Make sure ffmpeg.exe is present in the final output.
Test the packaged app
Verify launch, playback, PDF export, and MP4 export.
Post-build smoke test
After packaging, test at least these actions:
plugin loading if plugins are part of the build
Common packaging failures
App starts, but MP4 export fails
ffmpeg.exe is missing from the final distribution.
App fails during import
One or more dependencies were not bundled correctly.
Features work in development, but not in the build
The packaged output is missing data files, binaries, or runtime assumptions from the source tree.
Do not treat a successful launch as a successful package. Export and playback must also be tested.
