Studio One can lose track of audio after a computer move, even when the actual WAV files still exist on the new drive. The fix is usually to reconnect the song to the media it referenced before the move, not to reinstall the whole DAW or start rebuilding tracks.
A .song file is not necessarily a suitcase containing every recording, sample, Sound Set, and plug-in used by the session. The difference between native project files and rendered stems matters here because Studio One project files can preserve the arrangement while some media still lives elsewhere.
If the old machine still works, the cleanest Studio One move to a new computer starts there. Collecting external media before copying the song is much easier than hunting for missing paths afterward.
Do not assume the Studio One Media folder contains everything just because the song opens far enough to show the timeline. Imported drum hits, loops, impulse responses, and recordings can remain referenced from outside the song folder. If you are trying to work out where Studio One stores audio files, the answer depends partly on where the file entered the session and whether it was later collected.
When the files still exist, point the missing-file search at the folder that contains them and save the repaired song after Studio One accepts the new locations. If Studio One files are not found even though the expected audio is present, check the original path shown in the Pool before copying random files into new folders. A correct relink is cleaner than creating duplicates with identical names.
One less obvious failure is stale song cache data. Studio One's support guidance recommends closing the application and removing the Cache folder inside the affected song folder when a song reports missing files unexpectedly, then reopening the song. Use that as a troubleshooting step after confirming the actual media has not been deleted or left on another drive.
Sound Sets must be installed where Studio One expects them, while third-party instruments and effects need compatible installations on the new system. Cross-platform moves need extra care because an AU instance used on macOS does not automatically become the VST version on Windows. Studio One can therefore report missing plug-ins even when a related product is installed.
If Studio One is not finding plug-ins after the move, treat scanning as a separate problem from audio relinking. Studio One plug-in scanner failures can happen even when plug-in files appear to be in the expected place, so repeatedly moving song media will not fix the scan state.
Large libraries deserve the same separation. Keeping external storage for large music libraries is perfectly workable, but the drive has to be mounted, and the library path has to remain available. A new computer can expose old assumptions about drive names, folder structure, and where sample content was installed.
Save to New Folder is even cleaner when you want a portable copy of one song. Studio One creates a new song folder and copies the media it needs there, which makes the Studio One file structure easier to verify before you transfer Studio One files again. Open the copied version and play it before deleting or reorganizing the original.
Studio One Pro+ Backup and Restore handles settings such as presets, templates, macros, I/O configurations, and plug-in thumbnails. It should not be mistaken for a complete archive of song media. A dependable migration still needs the actual songs, collected audio, required Sound Sets, third-party software, licenses, and any libraries those plug-ins depend on.
For future Studio One backup files, test the copy instead of trusting the folder size. Reopen a few important songs from the destination drive, confirm recordings and imported samples resolve, and check the instruments that matter most. A backup becomes useful when the restored session actually plays.
A .song file is not necessarily a suitcase containing every recording, sample, Sound Set, and plug-in used by the session. The difference between native project files and rendered stems matters here because Studio One project files can preserve the arrangement while some media still lives elsewhere.
If the old machine still works, the cleanest Studio One move to a new computer starts there. Collecting external media before copying the song is much easier than hunting for missing paths afterward.
Start with the path Studio One expected
Open the problem song and use the Pool to inspect where Studio One expected the missing audio to live. Sorting the Pool by location can expose an old drive letter, renamed folder, disconnected external disk, or another Studio One file location that no longer exists on the new machine. The Studio One Locate Missing Files window is useful once you know which folder actually contains the material.Do not assume the Studio One Media folder contains everything just because the song opens far enough to show the timeline. Imported drum hits, loops, impulse responses, and recordings can remain referenced from outside the song folder. If you are trying to work out where Studio One stores audio files, the answer depends partly on where the file entered the session and whether it was later collected.
When the files still exist, point the missing-file search at the folder that contains them and save the repaired song after Studio One accepts the new locations. If Studio One files are not found even though the expected audio is present, check the original path shown in the Pool before copying random files into new folders. A correct relink is cleaner than creating duplicates with identical names.
One less obvious failure is stale song cache data. Studio One's support guidance recommends closing the application and removing the Cache folder inside the affected song folder when a song reports missing files unexpectedly, then reopening the song. Use that as a troubleshooting step after confirming the actual media has not been deleted or left on another drive.
Audio, Sound Sets, and plug-ins fail differently
Missing audio, missing Sound Sets, and missing plug-ins are three different problems. Studio One file management gets confusing when all three appear after the same computer migration because reinstalling one category does nothing for the others. A song can find every WAV file and still load with instruments or effects unavailable.Sound Sets must be installed where Studio One expects them, while third-party instruments and effects need compatible installations on the new system. Cross-platform moves need extra care because an AU instance used on macOS does not automatically become the VST version on Windows. Studio One can therefore report missing plug-ins even when a related product is installed.
If Studio One is not finding plug-ins after the move, treat scanning as a separate problem from audio relinking. Studio One plug-in scanner failures can happen even when plug-in files appear to be in the expected place, so repeatedly moving song media will not fix the scan state.
Large libraries deserve the same separation. Keeping external storage for large music libraries is perfectly workable, but the drive has to be mounted, and the library path has to remain available. A new computer can expose old assumptions about drive names, folder structure, and where sample content was installed.
Rebuild the project so it stays portable
Once the song works again, use Copy External Files in Studio One so referenced audio is gathered into the song folder. You can also enable the option to ask about copying external files when saving. Both steps reduce the chance that a future Studio One backup file depends on a sample sitting in some forgotten Downloads folder.Save to New Folder is even cleaner when you want a portable copy of one song. Studio One creates a new song folder and copies the media it needs there, which makes the Studio One file structure easier to verify before you transfer Studio One files again. Open the copied version and play it before deleting or reorganizing the original.
Studio One Pro+ Backup and Restore handles settings such as presets, templates, macros, I/O configurations, and plug-in thumbnails. It should not be mistaken for a complete archive of song media. A dependable migration still needs the actual songs, collected audio, required Sound Sets, third-party software, licenses, and any libraries those plug-ins depend on.
For future Studio One backup files, test the copy instead of trusting the folder size. Reopen a few important songs from the destination drive, confirm recordings and imported samples resolve, and check the instruments that matter most. A backup becomes useful when the restored session actually plays.
