Hi everyone.
I hope you're doing well.
I recently reinstalled my Nebula third-party libraries and made sure to name them exactly as they are in my Logic Pro projects to avoid any compatibility issues or missing plugins. New projects with the same plugin versions and names are working fine.
However, when I open an older project from about a month ago, Logic Pro marks those plugins as unavailable. Could you please help me resolve this issue?
I'd like to point out that Logic Pro presets don't work as expected.
to see the problem I addressed
Watch the attached videos.
Thank you for your assistance!
MacOS Mojave 10.14.6
Logic Pro 10.5.1

https://mega.nz/file/X5sElIJK#PqeyuCb3VFUAFkcTbFqBkIa_RDI1HhbmKt4K5btu6TM
https://mega.nz/file/GhkSDJCb#OoPKI2ligwqmhV9uVuz2KyUVweJDKtYYvkK8CJKPRlE

 

Fallen into the update trap again. If you have projects open, you shouldn't do any updates at all.

Install the version you used in old projects. You can also save the preset settings with the old version either as FXP or take pictures of the settings so that you can restore your settings with the newer version.

 

Hey, I didn't update Logic Pro. I had to re-install Nebula 4 external libraries due to a crash. I used the same program version.

 

Did you remember to reinstall the framework? You are using the V.R. Nebula 4.5 for Third-party libraries? Are the presets in different file locations now? Does your external disk that you replaced have the same Volume name as before? I use Logic but not Nebula.

 

I've deleted and reinstalled V.R. Nebula 4.5 for Third-party libraries. As mentioned in my post, everything is the same. Thank you

 

Time Machine-Backups?

Open projects created with earlier versions of Logic Pro for Mac
If you open a project created with an earlier version of Logic Pro, it might have unexpected output routings and other issues which prevent proper playback.

This can happen if you try to open a project created originally in Logic 4, 5, or 6, which you subsequently opened and saved in Logic Pro 7, 8, or 9. Here’s how to work with these projects in the most recent versions of Logic Pro:

1. If you haven't done so already, open the project in Logic Pro 10 or later, save the project, then close it.
   
   
2. Create a new empty Logic Pro project.
   
   
3. Choose File > Import > Logic Projects, select the older project that you saved, then click Import. All the tracks in the older project appear in the browser on the right side of the Logic Pro main window.
   
   
4. For each audio or instrument track you want to add to the new project, select the Content checkbox. To select all tracks, including aux and output tracks, press Command–A, then select one track’s checkbox.
   
   
5. Click any other parameters you want to import into the new project except for I/O settings.
   
   
6. Click Add at the bottom of the browser.
   

Selected tracks are added to the Tracks area, along with the other parameters you selected in the browser.

 

Are the permissions on the drive/folders set to --rwx for read, write, execute so Nebula can access the content files? Try doing Get Info for the drive, click the lock icon, and set the drive to Ignore Ownership. Reset the permissions using Permission Reset 2 or BatChmod.

Or screenshot your Get Info popup for that disk. Did you Codesign Nebula? And it is working with some other. libraries, right? Can you move any controls on a Nebula instance and they stay where you put them? Or do they spring right back to 0?

 

As shown in the video links in my post. The libraries work, but I can't load the logic pro preset. When I click on them the knobs don't move. However, the worst thing happens when I open a project where I previously used the libraries. In that instance, logic doesn't recognize the plugin and the missing AU.Component pops up. It's hilarious. If I open the project ignoring the "missing plugin alert" I can find the so-called plugin and add it to the chain, but the previous settings are gone.
Although Logic Pro, nebula library, engine version, and create plugin name are the same. It looks like logic treats it like a different plugin.
Watch the videos in my post to see what I'm talking about. Thank you

 

I don't have any backup with the time machine.
Also, there's no need to Import the files as the Logic Pro version is the same as 10.5.1.
Thanks for your input.

 

Ok, so I almost never save presets the way you are doing them in your Nebula. When you save a preset the way you are doing it, that creates .aupreset files. Mine are here on High Sierra: /Users/my username/Library/Audio/Presets. There is a folder for every plugin you have loaded, but there are only .aupreset files in those folders if you save it the way you are.

I never save presets that way. I save the preset from within the plugin, in it's native file format. Like Serum .fxp, as an example. I save my project and it captures a saved state of every plugin without making an .aupreset file.

I would look at the entire drive using Find Any File for .aupreset files you may have saved and see what you can salvage.

 

Last edited: Jan 13, 2025

Yup the Nebula presets workflow seemed weird, that's why I used the Logic Pro browser.
Anyway, I know where those presets are.

 

The workflow in Nebula is the reason why I do not use it. There are others, but the workflow/content structure is #1, by far and away.
The only presets I ever really save to .aupreset files, are actually parts of Logic. As an example, if I have it auto-load to the Limiter at -3, or the "default" EQ being set already to high cut/low cut.

 

Thanks for the suggestion. I may have found a way to recover the presets. I'll explain it tomorrow

 

Hi, here we are.
To make the aupresets work again, I made a new preset with the plugin and saved it as Dummy.
You can give it any name.
It won't matter.
Then, I went into the folder containing the old and newly created presets and compared them in TextEdit.
The files begin with the plugin name and versions, and then there is a wall of written codes which, I believe are the preset settings.
Then, there are some data strings containing three serial numbers.
The first and third serial numbers are identical in both files.
I just copied the second serial number from the new to the older presets.
After that, I've been able to load the older presets in the plugin with no issues.
Now.
I'm wondering if the same process would work with the project files.