Stoermelder Modules not in Library anymore

Plugins & Modules
1

Hi,

I have this problem for a while now. The complete Stoermelder modules are gone from my library. Some time ago i looked for a solution and found a thread with some tips for removing the complete pack, deleting some folder(s) and reinstalling the modules.

I tried that, but it did not solve the problem. I can’t find the thread anymore, so i finally made a thread myself. Sorry if this belongs somewhere else.

I tried to live without the Stoermelder modules, but always come back to a point, where i realize, that i can’t. =D

Can anyone direct me to mentioned thread or to a solution?

2

Hmm.. I am sure others will chime in and give a better answer. But, in hopes that this will work:

1-Check on VCV website in your plugins, and make sure you are subscribed rather than only adding specific plugins.

2-Open Rack. In the ‘Help’ menu, select ‘Open user folder’

3-Open the plugins folder inside your Rack2 folder and delete Stoermelder

4-Open Rack again, and update your library

I think this usually works.. otherwise I suggest contacting VCV - Support

3

Can you provide a log.txt?

4

@codyge

Ok i did this, but after update and restart the pack still isn’t there. and strangly it still shows “packOne” (and “Pachde One”) in the update List and when i click on update, it updates to 100% and i have to restart again.

But the “PackOne” shows up every time in the Update list again and will update.

@stoermelder Here is the log.txt from the folder

C:\Users\MyName\AppData\Local\Rack2

log.txt (111.7 KB)

5

You are using Rack 2.5.1, which is pretty old. This is the reason why you can’t load PackOne.

3 Likes
6

@stoermelder

Oh wow… that’s embarrassing. :see_no_evil_monkey:
I feel so stupid. :joy:

I guess i am so used to everything updates automatically nowadays… I better won’t mention what an amount of time i spent on this problem.

THANK YOU!!

1 Like
7

I think it would be a good idea to add the minRackVersion key to the manifest, e.g. "minRackVersion": "2.6.0" to avoid this in the future. Described here in the manual, it’s designed to express the minimum Rack version that the plugin needs, and I presume there’s a bit of UI in Rack around it, to warn the user that their version of Rack doesn’t support this plugin. See e.g. the Fundamental manifest using it.

You shouldn’t because you could not have known about this incompatibility, although, for reasons like this example, it’s generally a good idea to upgrade Rack to the latest version, when the red dot appears in the Help menu, from which you can directly get it and upgrade.

4 Likes
8

I did not know about this, thank you.

4 Likes
9

@LarsBjerregaard

Yes, but i am old enough to at least Take this possibility into consideration. Especially before making a Forum thread.:laughing:

And because i really hate it that Everthing on any device does so much automatically in the Background without me knowing it. And that i Got used to it nontheless.

Anyway, maybe there was some good in my question, If there was some information Missing in regards of specifying the compatibillity. So my question maybe Had an added value for Others. And thats nice.

But… actually i Just wanted to say a really big thank you to all of you! I can use the stoermelder modules again and that is fantastic! :blush:

3 Likes