making Renoise 3.2 find them is usually not the problem, but making them actually work, can be an issue since the 0.1 increment from 3.1 has been made. i can’t get good old steinberg hypersonic to work at all for example, as it always crashes when loaded.
what you have to make 100% sure is, that the name of the VST(i) renoise registers after the scan complies entirely to the identifier saved within your .xrns
if it doesn’t, then you’ll get a “missing plugin” info.
there are two ways you can solve this issue:
- simply rename the .dll file of the respective plugin exactly to what renoise tells you would be missing, then rescan again
- extract song.xml from the xrns file, edit the song.xml, search for the VST identifier entry / entries and rename it/them to what the name of the actually installed .dll is, then place the .xml back into the xrns container and save it.
i have done this about 10 gazillion times in my life. it’s cumbersome, exhausting, but unfortunately the only way to reawake older projects.
sometimes they don’t even have to be explicitly old. a simple update from a vendor is enough to break things, because he decided that a name change would be a great idea jumping from e.g. v1.52 to v1.53 or whatever