Where Data Is Saved

Your Settings

config.yaml holds all the app's settings, usually set from the settings screen.

It is read when TinePlayer starts, so restart it after any edits.

Video Saved Data

Video watched positions and track selections are saved in positions.json, unless Remember Where You Left Off is turned off.

Entries are keyed by the video's full path, so moving or renaming a file loses its saved settings. To clear it, you can delete the file manually or use Clear Saved Video Data in the settings.

Jellyfin Connection

When connected to a Jellyfin server, the connection details will be stored in jellyfin.json.

Keep this file private, do not share it.

Update Check

updates.json records when TinePlayer last looked for a new version and the latest version tag. It is not written at all with Check for Updates off.

No updates are downloaded or installed. The check asks GitHub which release is newest and the most it does is offer to open the releases page.

Log File

TinePlayer writes logs to tineplayer.log. It is the most useful thing to attach when reporting a problem.

Log files for the last three runs are kept. tineplayer.log is the run that just finished, tineplayer.1.log the one before it, and tineplayer.2.log the one before that.

Access tokens, account names, and any external server addresses are stripped before logging. File names are preserved, so read the file before attaching it to any issues if the names of your videos are something you would rather not share.

Plugin Cache

registry.bin is GStreamer's cached index of the plugins it can use. Deleting it is safe, it will be rebuilt on the next start.

Portable Installation

On Windows, the portable ZIP unpacks with a folder called user beside TinePlayer.exe. When that folder exists TinePlayer stores everything there rather than in your system's user profile folder. Deleting that user folder will result in a portable version reverting to the system user folder instead.