However the fact that I'm using an Apple MacBook Pro M1 always seems to get lost in translation. But I totally do appreciate the initial help. Because sometimes there are PC methods that I figure out to help me on Mac. For sometimes the problem may translate across both platforms.
Once again

-Thanx in Advance
-Big Pluck

 

Asking for help in these big product general discussion topic threads is an easy way to have your post buried by unrelated posts.

You are probably trying to use the Team Guiseppe releases of Studio one and Omnisphere 3 right? And then with Sonic Extensions. If you think that Mac configuration help is sparse on here, with the majority of users being on Windows; narrow the Mac users down by quite a considerable additional percentage who are actually using the combination of those three+ products.... and i'm not one of them either.

Make sure everything is firewalled in correctly. The first thing I would try would be to rule out the DAW. Use Bluecat Audio's Patchwork standalone application version and just load Omnisphere. If still not working, use Terminal commands, Permissions Reset 2, or BatChmod on the Sonic Extensions and make sure they are read/write/execute allowed for all users. After that check and/or dequarantine them, clear xattrs, codesign the extensions, even if you did it previously. If you have them on an external drive, MacOS Tahoe is even more bitchy than ever about that because external volumes are being preferred over internal paths for resource resolution. It might actually be easier to redirect the plugin to look at the Macs internal default disk location, and then symlink to the external. You are tricking it into thinking it is perfectly fine to open since it is pseudo-located on the local disk.

And if Spectrasonics took any action to block shared Sonic Extensions, thats another layer to deal with somehow.

 

Last edited: May 25, 2026 at 10:51 AM

Thank you clone for the major High School Homework project I have ahead of me to learn now. And Mom is gone so I don't know if that's good or bad. For she would surely be up my ass to find the sources to figure it out.

-Thanx in Advance "Clone"
-Big Pluck

 

You've already been here for 6 years. Time to push a little further into the IT aspects of Audio Production using warez. What I told you to do would take me about a half an hour and you have been asking about this for days. You are rocking an M1 and I've only had an M4 for about 5 days after an upgrade from a 2010 Mac Pro and I could solve your problem without even looking at it. But that is likely because I got my invitation to all this stuff from a college professor I asked about an educational discount on Protools and ended up at a russian Radium dump site and Efnet. So yeah, your high school comment has a lot of traction but it's not about me. That's why you are asking Windows users about Mac software here, and your reply only confirms why you still are.

 

I just noticed this too. Most probably the patches that were in these files were redistributed at different directories for Omnisphere 3. But in order to make sure, we should open Omnisphere 1-2 and look at the patches, then search for them in Omnisphere 3 and see if they have the same configurations, effects, etc.

 

In the past (reply #53) I have talked about the issue of Omnisphere 3 with duplicated names and how it hides tons of patches and soundsources.

I have been waiting for Spectrasonics to do something about it, but so far they haven't fixed it, so I am forced to rename the duplicated patches manually.
Fortunately we have scripts (and AI for those like me who don't know programming language). So I got this one:

Spoiler: Powershell Script

# ==================== SETTINGS ====================
$Path = 'C:\ProgramData\Spectrasonics\STEAM\Omnisphere\Settings Library\Patches'

# Change $false when you want to apply the changes for real
$DryRun = $false

# =======================================================

Get-ChildItem -Path $Path -Filter "*.prt_omn" -Recurse -File |
Group-Object -Property BaseName |
Where-Object Count -gt 1 |
ForEach-Object {

$files = $_.Group | Sort-Object FullName
$originalName = $_.Name
$counter = 1

Write-Host "`nProcesando duplicados de: $originalName.prt_omn" -ForegroundColor Yellow

foreach ($file in $files) {
$newName = "$originalName [$counter].prt_omn"
$newFullPath = Join-Path $file.DirectoryName $newName

Write-Host " $($file.Name) → $newName" -ForegroundColor Gray

if (-not $DryRun) {
try {
# Verificar si ya existe el nuevo nombre para evitar conflicto
if (Test-Path $newFullPath) {
Write-Host " ⚠ Conflicto: $newName ya existe. Saltando..." -ForegroundColor Red
}
else {
Rename-Item -Path $file.FullName -NewName $newName -ErrorAction Stop
Write-Host " ✓ Renombrado correctamente" -ForegroundColor Green
}
}
catch {
Write-Host " ❌ Error: $_" -ForegroundColor Red
}
}
$counter++
}
}

Write-Host "`n=== Proceso finalizado ===" -ForegroundColor Magenta

if ($DryRun) {
Write-Host "Modo DryRun activado. Cambia `$DryRun = `$false para aplicar los cambios reales." -ForegroundColor Yellow
}

With this, every single duplicated patch has been renamed to "Nameofpatch [1]", [2], etc. So now they appear in Omnisphere 3.

However, there are still tons of patches from the Factory files that are compressed so the script can't see the name of those patches. For example, one of the duplicated patch names was "Broken Record", and the first one comes from the Moog Tribute library, so this patch is inside the big compressed file "Moog Tribute Library.db" which only Omnisphere 3 can open and read. So, the patch of a 3rd party library that also has the name "Broken Record" will still hide the patch of the Moog Library.

Now the next step is to rewrite ALL the patches outside of the factory ones, that would be the only way to be 100% sure that there won't be more duplicated patch names, a big pain in the butt to do and a fix for an issue that only Omnisphere 3 has but Omnisphere 2 didn't....

 

Last edited: May 26, 2026 at 12:48 PM

Plus I thought this was the place for this. Where should I have posted it?

 

No need to open Omni 1-2. Just go to \STEAM\Omnisphere\Settings Library\Patches\Factory and open them in notepad, it lists all the patches.