Cosmi Player - playback library source and replacement instructions What these materials cover -------------------------- Cosmi Player uses LibVLCSharp and LibVLCSharp.WPF 3.10.1, a custom LibVLC 3.0.23 native build, FFmpeg 4.4.5, LIVE555 2026.08.25 and other libraries. The covered libraries retain their own licences. Cosmi Player's application source is separate and is not part of the library source kit. Source materials for Cosmi Player 1.1.0.0 --------------------------------------- Matching native library sources, patches, dependency recipes and build instructions are retained in the native source-build archive. The wrapper source is pinned to commit 4896d0e06d19ac40b46802cf7dc167d432f3fd63 in VideoLAN's LibVLCSharp repository, covering both managed assemblies. The combined library source kit is distributed separately from the app: https://cosmisan.com/apps/cosmi-player/downloads/ Select the source kit and checksums matching your application version. Support: support@cosmisan.com. The supplied source kit contains the original library sources, modifications, build instructions and component provenance. A link to an upstream project's current homepage alone is not a substitute for this matching source material. Library sources can be modified and redistributed under their own licences; the paid application does not need to be given away to exercise those rights. Preparing a compatible replacement ---------------------------------- 1. Obtain the source kit matching the installed release and read its build instructions and component licences. Modify and compile the library you want to change. A source ZIP is not itself a loadable playback library. 2. Start with a copy of the app's complete bundled libvlc folder, in a writable folder on a local drive outside WindowsApps. The installed app location can be found with this read-only PowerShell command for the Store release: (Get-AppxPackage -Name Cosmisan.CosmiPlayer).InstallLocation Copy the libvlc subfolder; do not alter WindowsApps. 3. Replace the compiled component and any matching dependencies in your copy. Keep compatible Windows x64 native libraries, LibVLC 3 APIs and managed wrapper APIs. The set's root must contain: managed/LibVLCSharp.dll managed/LibVLCSharp.WPF.dll win-x64/libvlc.dll win-x64/libvlccore.dll win-x64/ win-x64/plugins/ For LIVE555 changes, rebuild the VLC RTSP plugin containing that code using the native source kit; merely adding a separate LIVE555 DLL does not replace the code incorporated into that plugin. 4. In Settings, under Playback libraries, choose that set's root folder, then Save and restart. Existing recording confirmation still applies. Playback libraries cannot be exchanged inside a running player. The chooser checks compatibility and runs selected code during its check; use code you trust. 5. To restore the supplied set, choose Use bundled libraries, then Save and restart. If a custom set cannot start, use the recovery screen's bundled option. The app also accepts --restore-bundled-libraries at startup. The application does not require replacement libraries to have our original hashes or signing key. Both managed wrappers and the native set are replaceable; compatible replacements do not require modifying or re-signing the app package. Windows security or organisation policy can independently block a DLL. These instructions do not ask you to disable Windows protection or bypass such policy. The Library rights document preserves the applicable modification and debugging permissions. Original component licence texts are included in the app's Legal Information viewer and the complete notices archive.