Import

Use Tools → Import to create Streams or Movies from M3U/M3U8 or migrate supported Codec data.

Supported Files

Import a Playlist

1. Select M3U / M3U8 Playlist and choose the file.
2. Choose Import As → Streams (default) and a Stream Profile, or Movies and a Target Server.
3. Run Dry Run.
4. Review every Ready, Skipped, and Failed row. Correct problems and run Dry Run again.
5. Select Import. Test new Movies and keep new Streams stopped until tested.

Import As applies to every entry in the file. Split mixed lists before importing. Movies use the entry’s name, category, source URL, and logo as the poster. Movie imports follow your license limits and do not require a Stream Profile.

Engine 1.0.1+

Duplicate source URLs are skipped within the selected media type. Existing names are not overwritten; a conflicting name is reported as failed.

Dry Run saves no records and keeps your file and selections on the page. Results show failed items first. Close the results to correct your selections or select Import without choosing the file again.

Changed in Engine 1.0.1+

Import a Codec Backup

Start with an initialized Engine database and import Codec backups through Tools → Import. Directly restoring a Codec backup as the Engine database is not supported.

Both Dry Run and Import check that the file contains Codec database records and version information. Engine backups, unrecognized files, and damaged archives are rejected. Restore Engine backups from Database Settings.

Changed in Engine 1.0.1+

1. Download an Engine database backup.
2. Check license capacity and record existing server names.
3. Select the Codec .gz backup and run Dry Run.
4. Resolve unexpected mappings, skipped items, and failures.
5. Import with the same file and selections.
6. Verify Servers, Categories, Profiles, DVB, VOD, Streams, Bouquets, Packages, Accounts, and Users.

The current Master stays in place. Matching names or duplicates may reuse existing Engine items. Check imported outputs and license limits.

IDs and Relationships

New records keep their original Codec IDs when those IDs are available in the corresponding Engine tables. Only conflicting IDs receive replacements. Replacements also avoid IDs belonging to other records in the same backup. This applies to supported records and their configuration and output rows.

References follow the imported or reused Engine IDs, including Stream → Profile, Stream/Profile/Adapter → Server, DVB input server and adapter IDs, Bouquets, Packages, account ownership, and user access. In a multi-server backup, each Stream stays associated with its mapped server. A Stream fails to import if its Profile is unavailable or belongs to a different mapped server.

Existing items matched by name or username are reused with their Engine IDs. The source Master maps to the current Engine Master, and the source full administrator maps to account 1; their existing settings and credentials are retained.

Changed in Engine 1.0.1+

Keep the source system and backups until administration and production playback have been verified.