# Migrating between versions

When updating Nobe OmniScope between minor versions, for example from **1.10.x** to **1.11.x**, not every file is handled the same way.

## What stays shared and what changes

* Layout files in the `layouts` folder are shared across versions. In most cases you do not need to rename or copy them.
* Application settings use versioned config files such as `config_1_10.json` and `config_1_11.json`.
* Window, dock and panel positions use versioned UI files such as `ui_1_10.ini` and `ui_1_11.ini`.
* Some newer builds may offer a settings import prompt on first launch. If that prompt is not shown, you can migrate settings manually.

## Before you update

1. In OmniScope, choose **Options / Open Logs**.
2. Quit OmniScope.
3. Make a backup copy of the whole folder, especially:
   * `layouts/`
   * your current `config_*.json`
   * your current `ui_*.ini`

If you are moving layouts to another machine as well, see [Backup & transfer](https://docs.timeinpixels.com/nobe-omniscope/layouts/backup-and-transfer).

## Manual settings migration

If the new version starts with default settings and you want to bring your old settings forward:

1. Launch the new version once, then quit it. This creates the new versioned files if they do not exist yet.
2. In the OmniScope logs/settings folder, copy the old config file to the new version name.
3. Example: copy `config_1_10.json` to `config_1_11.json`.
4. If you also want the previous dock, panel and window layout, copy the old UI file to the new version name.
5. Example: copy `ui_1_10.ini` to `ui_1_11.ini`.
6. Start the new version again and verify your preferences, scopes and input slots.

It is safer to **copy** the old files and keep the originals as a backup.

If the new version behaves unexpectedly after the manual copy, close OmniScope, delete the new versioned files you created, and launch again so OmniScope can regenerate fresh defaults.

## Important note about layouts

A saved layout can store more than scope placement. It can also store:

* input slot assignments
* auto-connect state
* source-specific settings

Because of that, an older layout may still reference a specific saved input device id even if the visual layout itself loads correctly.

## Potential issue with DeckLink and UltraStudio devices

In some upgrades, especially from **1.10.x** to early **1.11.x** builds, a saved layout may contain an older DeckLink or UltraStudio device id that no longer matches the id used by the newer version.

Typical symptoms:

* the layout opens, but scopes stay black
* the status bar keeps showing the DeckLink device as connecting
* the input slot does not show a live signal, even though the same hardware still works in the older version

## How to fix a saved DeckLink device manually

1. Load the layout.
2. Open the **Connect To** dialog or use the **Input Strip**.
3. Re-select the correct DeckLink or UltraStudio device manually.
4. Confirm that the live signal is back.
5. Save the layout again.

Saving the layout again updates the stored device id for that layout.

If you use several saved layouts that remember DeckLink inputs, repeat this once for each layout.

## Recommended upgrade workflow

1. Back up the OmniScope folder first.
2. Let OmniScope import settings automatically if that option is offered.
3. If not, copy the config file manually and copy the UI file only if you want the old window and dock layout.
4. If a DeckLink or UltraStudio source does not reconnect after loading an older layout, reconnect it once and save that layout again.