A remote playlist refresh replaces or reconciles data from its source. Edits made only to a downloaded copy may disappear when the player loads the original remote list again. Use local favorites, grouping or sorting features where available if you want personal organization alongside ongoing service updates.
Identify the source of truth
A remote URL points to the service-maintained catalogue. A personal file is a separate copy. Editing one does not update the other. Keep that distinction clear before spending time reorganizing a large list.
Separate service corrections from preferences
A wrong stream address or guide identifier may need a source-side correction. A preferred channel order is usually a household preference. Sending those as separate requests helps avoid a personal browsing choice being treated as a service-wide metadata error.
Back up organization rather than secrets
Where a player supports a settings export, find out what it includes before storing or sharing it. Backups can contain account values as well as favorites. Keep the export private and delete obsolete copies when they are no longer useful.
A practical sequence
- Check whether the profile uses a URL or a local file.
- Use local organization tools where supported.
- Keep source corrections separate from personal preferences.
An example
Renaming a group in a downloaded copy will not change the group returned by the service URL. Reimporting that URL can restore the original name.
Questions about this topic
Can I stop refreshes permanently?
Possibly, but you would also stop receiving source corrections and additions.
Will favorites always survive?
That depends on how the player stores and matches them.
