Page 1 of 1
Posted: Tue Oct 25, 2005 7:28 am
by massusen
Hi,
On the topic of the preset bug - have anyone a solution to it? It has spared me until now. After a harddiskcrash I had to reinstall, and voila! Corrupted presets. My modules appear as they should, but for instance no Modulation inputs can be connected. So annoying. Anyone with the same experience - with the Mod. inputs?
M
Posted: Tue Oct 25, 2005 10:51 am
by roy thinnes
this sounds really strange...but what has the preset bug to do with that impossibility to connect something to the Mod inputs? And: is this a general behaviour / does that happened all the time when you try to connect sth to the Mod Ins?
Posted: Tue Oct 25, 2005 1:25 pm
by massusen
sorry, I will be more specific - this only happens when I load up a instrument that has been previously saved and try to change/modify it. If I build an instrumnt from scratch everything works fine. But if I save, reopen it and try to modify, bang - Mod. inputs are corrupted. But I just realised - only on 3:rd party modules - like Adern and Obsidian. All CW modules behave correctly. Strange, isn´t it...
Posted: Tue Oct 25, 2005 2:10 pm
by alfonso
If you modify the device routings or modules used, you must delete the preset list and make a new one from scratch and save the device as a new one. A preset list is strictly connected to a certain structure...I'd say logically...
Posted: Tue Oct 25, 2005 2:13 pm
by alfonso
This other bug you mention is strange, didn't understand all the conditions it occurs....it might be a defective installation.
Posted: Tue Oct 25, 2005 8:11 pm
by at0m
massusen, If something doesn't want to connect, and it should according to connection type, pick another connection on the module and hook it up somewhere. Right-clicking the module and 'disconnecting' from the menu resets input convertors.
If you add/remove modules, loading the old preset list will return 'only xx% compatible' - just save the list as a new file, and disregard the message. I do this always with a patch that has a BPM module: I don't like the BPM to jump around when I'm working with a tune at xyz BPM, so I delete that module and load a fresh one from the menu, which isn't referenced to in the preset list.
Hey Alfonso, one could use the right-hand preset panel to make a new preset list, select one by one from the old list on the left and resave them in the rh panel - restoring as much as possible from the original preset list.
Enjoy
Posted: Wed Oct 26, 2005 1:27 am
by massusen
alfonso, you´re right - it probably hasn´t anything to do with the preset bug - more likely it´s a defective installation...
I guess that´s better. I can fix that. And as it´s related to 3rd party modules I guess I´ll just have to start there.
Boring...
M
Posted: Wed Oct 26, 2005 9:28 am
by dbmac
I had to remove all Obsidian files from an SFP installation to correct Scope wierdness (many years back). I would start there.
/dave