Plugins in empty inside rack

[JordiTR]

Hi you all, I've realized that in some projectes if I open the "CPU usage" window (see attached image) it looks there are lots of plugins on the "Inside rack" (which I interpret as the master track). The point is that those plugins are not accessible anywhere on my project and my master track is empty. If I double click on one of them to open it, Waveform (12) quits unexpectedly.

There is a lot of plugins instances and I would like to clean that list, but it's no possible from that "CPU usage" window. Is there any other place to clean that list ?? Thanks !!

[Peter Widdicombe]

Do you have a rack defined for every track? From the above, it looks like many tracks have a rack with multiple plugins within that rack - like 8 within Keys-Atmospheric alone ? It doesn't appear they are consuming much CPU, though.

[JordiTR]

Hi Peter, and thanks for your answer.

I've prepared another screenshot where you can see that if I delete all the tracks and all the master insertions all this stuff is still there...

I'm not sure if that "Inside rack" expression is related with "racks", since every time I add a FX plugin on the master track it's on that list under the "Inside rack" group.

Also, I see that all of them looks as if they were just using "0%" of CPU, but it's annoying having all this on this window...

[jabe]

Strange. I don't know how they got there, but I believe I've found a way to clear them out.

You'll need to make the Properties Panel fully visible.

After that, get the CPU Usage display up. Click to highlight one of the plug-ins, then click on Show selection in Edit (lower right of CPU Usage display) and it will appear in the Properties Panel. There is an option in the lower right corner of the panel to delete the plug-in.

[JordiTR]

Hi jabe and thanks for your answer. I've applied your proposal step by step exactly as you say and when I click the "show selections as Edit" button on the CPU usage window Waveform just crashes. Something is seriously wrong with these file... Weird, weird, I've never had those pluigns on the master track or a rack... Thanks anyway for your help.

[jabe]

Stranger and stranger. If you start a new project, are these plug-ins in that as well? Did you perhaps load a template into your project? Let me know what happens with these, and if the problem is still there, I'll give you my email address via PM and you can send me your tracktionedit file and I'll see if there's anything within it causing the problems (though if you understand XML files you could open the file in a text editor and take a look yourself).

[pough]

lots of plugins on the "Inside rack" (which I interpret as the master track)

At first I thought this was a strange thing to say, but then I started to do some tests and discovered that the plugin I have on my Master Track is listed in the CPU Usage window as being "(Inside Rack)". That's weird.

One thing to consider, and I don't recall seeing it mentioned here, is that when a Rack is removed from a track you get the choice of removing it or leaving it still existing in the Edit but floating in some kind of limbo. When I do that, the Rack disappears from the CPU Usage window but the plugin I had added to is remains.

[jabe]

So that could mean that adding the plug-ins to the master track then could allow them to be removed properly...?

[asprog]

Hello,

if you have a rack

floating in some kind of limbo

you should be able to see it when you use the menu to add a rack ("3rd Below Echo" here).
The only way to remove it seems to add it one more time by choosing it in this menu, and then remove it (be careful to choose well "Remove Rack").

It's a bug that I didn't know and that could be very annoying given the latency that this can introduce...

(Test made on a track, not the master track)

[fde101]

When you delete the last instance of a rack from a track, you are asked if you want to delete the rack itself or leave it. If you leave it, the plugins remain in the CPU window. Double-clicking on such a plugin in the CPU window, or choosing Show Selection in Edit, crashes Waveform (at least it does on macOS).

The crash is obviously a bug. The fact that the plugin stays behind is obviously intentional, since it asked and we told it to keep the rack.

If you manage to not crash waveform, you can create a new instance of the rack by selecting it in the plugin list (your existing racks are listed under Plugin Racks, whether they are on a track or not). If you then delete it from the track and respond that you want the rack to be removed, the plugin will disappear from the CPU window.