Help! I broke NLS auto-increment with "Save Default Preset"

Support
1

Hello! I’ve come to rely on Waves NLS but my favorite console is Nevo and it defaults to Spike.

So I clicked “Nevo” and chose “Save as default preset.”

Now the auto-increment when I add NLS to a bunch of tracks at once is broken! Is there a way to restore the original behavior? (To be clear, I’m referring to how it used to choose the next preset automatically when adding to many tracks at once: Spike01, Spike02, Spike03, etc. After setting the default preset it no longer does that.)

I realize I made a big mistake because I should have just changed the console in the NLS Bus but I didn’t. I need to remove my “default preset” which broke the original functionality!

Thanks in advance!

2

Whew! I figured out the solution. I’m responding here to help anyone else that runs into the same issue.

If you ever change the default preset in Waves NLS and need to restore the original behavior, simply delete this file:

C:\Users\Public\Waves Audio\Plug-In Settings\NLS Startup Preset.xps

While the ability to “Set Default Preset” is very helpful in most Waves plugins, I do NOT recommend it for NLS because you’ll lose the feature that automatically increments the channel number when applying the plugin to many tracks at once.

2 Likes
3

Yeah I did the same a number of years back, though I used Logic’s press system. After deleting it’s default press I was able to return the status back to normal.

I just found it hard to “reset” the incremental system. What you have to do, though, is remove every instance including the Buss plugins. It turns out that was the buss plugins was causing me the issues there.

4

Thanks Simon.

Just to confirm, for me – deleting C:\Users\Public\Waves Audio\Plug-In Settings\NLS Startup Preset.xps returned the incremental system! (WHEW.)

Now if only I could get it to default to Nevo instead of Spike…

1 Like
5

The only quick and fast way I can think of is to assign them all to a group and adjust the group settings. Even if you disable the group setting after that is done.

1 Like
6

Hello, please how do I solve this problem on a MacBook Pro intel 2019?

7

Good question, Edriver3…

Unfortunately I’m on Windows, but my guess is there is some consistency to their product behavior on Mac.

If so, I would search your drive for “NLS Startup Preset” and see if anything comes up. I found a Gearspace thread discussing a similar issue but according to someone there it appears Waves plugins put their presets in various locations. (I’m guessing he had multiple versions installed, because I would think Waves would be consistent.)

I don’t think I’m allowed to link directly, but search “Gearspace Where does Waves save its Factory Presets?” and that should get you there, although I don’t know if it will actually be helpful.

One issue though is that apparently after the Lion version of the OS, Apple started hiding the folder where presets are saved. So when you do that search, you need to do a search that includes hidden files.

If you have an active Waves Update Plan I would reach out to support, although they’ll probably tell you to reinstall… And TBH, that might be the first thing you should try.

If you get an answer though be sure to follow up here and I’ll delete this response. But try that search and see – I bet SOMEWHERE the preset is saved on your drive and you can delete it.

That is what fixed it for me, on Windows.

PS. I’m not familiar with how search works on Mac, but on Windows I would need to search for “NLS Startup Preset.*” with a wildcard at the end – because I don’t know what the extension will be on Apple’s OS.

PS #2. Maybe this will help, look here:
System HD > Users > Shared > Waves > Plug-In Settings > Plug-In name
from https://www.waves.com/support/how-to-use-waves-plugin-presets

If it works the way I suspect it does, by default there is no “startup preset” but if it detects one there, it will use it… So look there and see if you have an NLS Startup Preset and delete it.

And again, if (any of) that works – follow up with the specifics so I can clean up this dodgy advice! :slight_smile:

8

If you still need any assistance, please Contact Technical Support directly.