Update from 1.0 to 2.0

Updating from version 1.0 of Sounds Good to version 2.0 is a complex process, but not impossible. Below, you'll find all the necessary steps for a successful migration.

Sounds Good is no longer distributed as a traditional UnityPackage and is now offered as a UPM (Unity Package Manager) package. This change significantly enhances plugin quality, but also means there is no backward compatibility. Therefore, it's strongly recommended to fully delete the previous version before installing 2.0.

However, by following these steps, you can update and preserve your entire sound and music database.

---

Step 0 - Detect Incorrect Installation

Before importing the 2.0 package, carefully review Unity's import window. If you notice files are divided between these two paths:

• Assets/Plugins

• Packages/com.melenitasdev.sounds-good

it means the installation is incorrect, as both systems will mix, causing serious compilation errors.

If you detect this, DO NOT yet import version 2.0 and proceed to the next step. If you have already imported it and files are mixed, continue anyway.

---

Step 1 - Remove the Previous Version

Before importing version 2.0, completely delete this folder from your project: Assets/Plugins/Melenitas Dev/Sounds Good. Don't worry about losing your customized data; your sound database is stored in a different location: Assets/Resources/Melenitas Dev/Sounds Good.

If you've already installed version 2.0 on top of 1.0 by accident, you must also remove it from the Package Manager: Package Manager ► In Project ► Sounds Good - Easy & Optimized... ► Remove.

Delete 1.0

Delete 2.0 (if installed by accident)

---

Step 2 - Import Sounds Good 2.0

Now you can cleanly import version 2.0. Upon doing this, you'll notice all files will be installed at: Packages/com.melenitasdev.sounds-good.

You might see some files related to TextMeshPro installed outside the package; this is entirely normal.

---

Step 3 - Solve Initial Compilation Errors

This is the most time-consuming step. After installation, you'll encounter compilation errors because old references to SFX, Track, and Output are no longer compatible.

You have two temporary ways to resolve this:

• Comment out the lines that cause errors. Later, after everything is solved, you can uncomment and manually correct them.

• Replace enumerator references directly with strings. You won't need to revert this later, as Sounds Good now supports string calls for sounds/music. Example:

  SFX.jump   →   "jump"
  Track.main →   "main"

This temporarily enables compilation, granting you access to the new migration tools.

---

Step 4 - Migrate Your Database

Once you compile without critical errors, you will have access to the specific tools of Sounds Good 2.0.

• Open the window named Version Upgrader from the Sounds Good menu: Tools ► Melenitas Dev ► Sounds Good ► Version Upgrader (1.0 → 2.0).

• Click the "Upgrade" button. This automatically migrates your 1.0 database to the new 2.0 format.

• After migrating, click "borrar antigua base de datos" ("delete old database") to remove the old data and keep your project clean.

---

In conclusion, while this update process is more complex than usual, carefully following these steps ensures a safe and complete migration. You're now ready to fully leverage all new features and improvements offered by Sounds Good 2.0.