Hi, sorry for posting here but not sure if this should go on github or here. Anyway, in V1.0.0 and V1.1.0 I have the Autodafe plugins selected in the plugin manager.
But each time I start rack I get an update every time for those plugins. I let the system Update All but they reappear at the next startup.
This is all I see in my library.
And this is all the Autodafe plugins installed.
Something weird happening?
Thanks,
Chris.
Try deleting the Autodafe folders in ~/Rack/plugins-v1 and restart Rack and let them download and install again.
Did that. No change. I even deselected in the plugin manager, start/stop rack and re-selected them in the manager.
Are you on Linux? (I don’t recognise your terminal).
If so (this may be way off the mark) there are issues apparently:
Yes, I’m on linux openSUSE 15.0.
Had a quick read of Dave’s comment. That libm is a bit of a vague library name???
I’m not on Linux and out of my depth there I’m afraid.
thanks anyway.
Greetings ! libm is an essential library:
LIBM is the standard C library of basic mathematical functions, such as sin(x), cos(x), exp(x), etc.
Open a terminal, go to your Rack Autodafe plugins directory (not the drums, btw) and run this command:
ldd plugin.so
The chances are good you’ll see something like this:
$ ldd plugin.so
./plugin.so: /lib64/libm.so.6: version `GLIBC_2.27' not found (required by ./plugin.so)
linux-vdso.so.1 (0x00007ffed540a000)
libstdc++.so.6 => /lib64/libstdc++.so.6 (0x00007f6e562af000)
libm.so.6 => /lib64/libm.so.6 (0x00007f6e55fa7000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f6e55d8f000)
libc.so.6 => /lib64/libc.so.6 (0x00007f6e559c7000)
/lib64/ld-linux-x86-64.so.2 (0x0000556ec49d1000)
That “version not found” message is the key. My system needs an upgrade. As far as I can tell, there’s no other way to spoof the plugin into finding an alternate version of the library. (Still working on that here though.)
Send Antonio my blog post about compiling Linux plugins.
Brilliant - thank you so much @dlphillips !
My GLIBC was only v2.26 (thought I had updated it???)
Autodafe all ok now.
The Hora modules have the same issue.
hi!
Just installed VCV and I’m so glad to be able to learn modular virtually!!!
But it also seems that I have the same problem with Autodafe, which keeps updating itself. Even after trashing the folder the update still pops up. I’m on Mac OS 10.8. Any help?
@antonio.grazioli Hi Antonio
When you changed this :
{
"version": "0.6.2c",
"modules": [
{
"plugin": "Autodafe-Drum Kit",
"version": "0.6.0",
"model": "Drums - Kick",
"params": [
{
"paramId": 0,
"value": 0.0
}
],
"data": {
"sampletype": 1
},
"pos": [
93,
1
]
},
{
"plugin": "Autodafe-Drum Kit",
"version": "0.6.0",
"model": "Drums - Snare",
"params": [
{
"paramId": 0,
"value": 0.0
}
],
"data": {
"sampletype": 1
},
"pos": [
97,
1
]
},
{
"plugin": "Autodafe-Drum Kit",
"version": "0.6.0",
"model": "Drums - Closed Hats",
"params": [
{
"paramId": 0,
"value": 0.0
}
],
"data": {
"sampletype": 1
},
"pos": [
101,
1
]
},
{
"plugin": "Autodafe-Drum Kit",
"version": "0.6.0",
"model": "Drums - Open Hats",
"params": [
{
"paramId": 0,
"value": 0.0
}
],
"data": {
"sampletype": 1
},
"pos": [
81,
1
]
},
{
"plugin": "Autodafe-Drum Kit",
"version": "0.6.0",
"model": "Drums - Claps",
"params": [
{
"paramId": 0,
"value": 0.0
}
],
"data": {
"sampletype": 1
},
"pos": [
85,
1
]
},
{
"plugin": "Autodafe-Drum Kit",
"version": "0.6.0",
"model": "Drums - Cymbals",
"params": [
{
"paramId": 0,
"value": 0.0
}
],
"data": {
"sampletype": 1
},
"pos": [
77,
1
]
},
{
"plugin": "Autodafe-Drum Kit",
"version": "0.6.0",
"model": "Drums - Ride",
"params": [
{
"paramId": 0,
"value": 0.0
}
],
"data": {
"sampletype": 1
},
"pos": [
89,
1
]
},
{
"plugin": "Autodafe-Drum Kit",
"version": "0.6.0",
"model": "Drums - Rim/Claves",
"params": [
{
"paramId": 0,
"value": 0.0
}
],
"data": {
"sampletype": 1
},
"pos": [
73,
1
]
}
],
"wires": []
}
to this :
{
"version": "1.1.1",
"modules": [
{
"id": 384,
"plugin": "Autodafe-DrumKit",
"version": "1.0.0",
"model": "DrumsClaps",
"params": [
{
"id": 0,
"value": 0.0
}
],
"rightModuleId": 385,
"data": {
"sampletype": 1
},
"pos": [
0,
0
]
},
{
"id": 385,
"plugin": "Autodafe-DrumKit",
"version": "1.0.0",
"model": "DrumsHiHatClosed",
"params": [
{
"id": 0,
"value": 0.0
}
],
"leftModuleId": 384,
"rightModuleId": 386,
"data": {
"sampletype": 1
},
"pos": [
4,
0
]
},
{
"id": 386,
"plugin": "Autodafe-DrumKit",
"version": "1.0.0",
"model": "DrumsCymbals",
"params": [
{
"id": 0,
"value": 0.0
}
],
"leftModuleId": 385,
"rightModuleId": 387,
"data": {
"sampletype": 1
},
"pos": [
8,
0
]
},
{
"id": 387,
"plugin": "Autodafe-DrumKit",
"version": "1.0.0",
"model": "DrumsHiHatOpen",
"params": [
{
"id": 0,
"value": 0.0
}
],
"leftModuleId": 386,
"rightModuleId": 388,
"data": {
"sampletype": 1
},
"pos": [
12,
0
]
},
{
"id": 388,
"plugin": "Autodafe-DrumKit",
"version": "1.0.0",
"model": "DrumsKick",
"params": [
{
"id": 0,
"value": 0.0
}
],
"leftModuleId": 387,
"rightModuleId": 389,
"data": {
"sampletype": 1
},
"pos": [
16,
0
]
},
{
"id": 389,
"plugin": "Autodafe-DrumKit",
"version": "1.0.0",
"model": "DrumsRide",
"params": [
{
"id": 0,
"value": 0.0
}
],
"leftModuleId": 388,
"rightModuleId": 390,
"data": {
"sampletype": 1
},
"pos": [
20,
0
]
},
{
"id": 390,
"plugin": "Autodafe-DrumKit",
"version": "1.0.0",
"model": "DrumsRimClaves",
"params": [
{
"id": 0,
"value": 0.0
}
],
"leftModuleId": 389,
"rightModuleId": 391,
"data": {
"sampletype": 1
},
"pos": [
24,
0
]
},
{
"id": 391,
"plugin": "Autodafe-DrumKit",
"version": "1.0.0",
"model": "DrumsSnare",
"params": [
{
"id": 0,
"value": 0.0
}
],
"leftModuleId": 390,
"data": {
"sampletype": 1
},
"pos": [
28,
0
]
}
],
"cables": []
}
It changed the slug or whatever it is called, so I/we are no longer able to load a v0.62 patch into V1 without the warning that all modules are missing which they are NOT they just have a different/wrong name.
Can you do something to prevent this, or not.
Greetings Peter
We try to catch these issues at the VCV Library, but this one slipped by us. What Antonio should have done is used Drums-Claps as the slug in v1, which is the "normalized version of Drums - Claps and would have preserved patch compatibility. The problem we have now is that probably around 50% of people are trying to load patches with the slug Drums - Claps and 50% are loading patches with the slug DrumsClaps. There’s not much that can be done at this point, because if Antonio changes it to Drums-Claps, patches you created >1 month ago would work, but patches you created <=13 days ago would not. At this point, I would recommend “no action” on Antonio’s part and to keep the new (non-backwards-compatible) slugs.
I’ve been going in by hand with a text editor and doing search/replace on the slugs in the individual patches. it’s a pain and I’ve actually lost one patch trying to make the changes. Since the patches are in JSON and plain english, it’s not hard to write some code to just read the files, make the changes, and save it. I may get to in the next week or so, but if anyone wants to write it first, feel free.
sorry guys, I din’t realize it either until now…I didn’t change the slug intentionally, but I was rushing to get the update done and it slipped…
@antonio.grazioli Just saw your modules were updated or re-uploaded , version number is the same, was hoping you changed the slug back and didn’t listen to Andrew 
but that was not the case.
What changed ?
it was just a small bugfix on the BPM clock…
Definitely listen to Andrew! 
I’ve only used these modules since v. 1 so don’t want all my new patches to break. 
This is almost certainly a Feature Request, but I kind of wish VCV Rack had a “fallback slug” for modules. For instance, VultModulesFree should just “fallback” to “VultModules” if the “Free” versions aren’t found. A few developers use the same module in different packages and that would prevent us from having to install two different versions for preset compatibility. If that existed, that same kind of thing could be done for these Autodafe modules where if the old slug wasn’t found, VCV Rack could identify the new one. Would be easier than trying to hack presets in a text editor.