You hit the point! Most annoying thing is if you try to find a workaround by avoiding some modules or recreateing the patch from scratch (even in another shell) doesn't change anything but stealing more time and effort. You wouldn't believe how often i thought i had a working versions only to find out after creating several presets that it was screwed up again.On 2003-09-27 07:20, Ben Walker wrote:
Hi there,
funnily enough I spent some time with Monomorph trying to recreate this problem. sure enough, even when I save the patch as a new patch and create a new set of presets, the problem still persists. I don't get 'these presets are only x% compatible' but I do get presets which don't store all the values of the modules in the patch, so the patches don't sound the same when you reload them. In particular I noticed that the AND/OR/XOR module bottom left doesn't get it's value saved, but I'm sure there are others.
This is a great shame as it seems like you've put a LOT of effort into building this file, recording sound examples, trying to fix the preset problem, etc.
If you like that one you would love the extended version which i was working on at last. That baby definitly rocksI certainly had great fun playing with the patch whilst trying to get the presets to work, but in its current state its not usable.

I guess they don't know what causes the troubles. As i mentioned earlier i suspect some (unfortunatly essential) modules in certain installations.Even if we don't get a fix soon from CW, it would be nice to have some advice on how best to operate in order to try and avoid this happening.
Regards, Stefan